If you sell services and you are still negotiating a full contract for every project, you are paying a tax you do not need to pay. The commercial and legal terms — liability, IP, confidentiality, payment, termination — do not change between projects. Only the work does.
The standard answer is a two-document structure: a master service agreement that you negotiate once, and a statement of work per engagement. Done well, a new project starts with a two-page SOW instead of a three-week legal review. Done badly, you get two documents that contradict each other and nobody knows which one governs.
What goes where
The allocation is not arbitrary. Anything that describes the relationship belongs in the MSA; anything that describes a specific piece of work belongs in the SOW.
In the master service agreement:
- Parties, and the fact that the MSA governs all SOWs entered under it
- Term of the framework, and how it ends independently of individual SOWs
- Payment terms, invoicing cycle, late payment consequences, expense policy, tax treatment
- Confidentiality
- Intellectual property ownership and licensing
- Data protection and security obligations
- Warranties and disclaimers
- Limitation of liability and indemnities
- Insurance requirements
- Subcontracting and assignment
- Non-solicitation, where applicable
- Termination rights and consequences
- Dispute resolution, governing law, and jurisdiction
- Order of precedence between the MSA and any SOW
In each statement of work:
- Reference to the MSA and its date, so the framework clearly applies
- Scope: what is being done, in specific terms
- Deliverables, each separately identified
- Acceptance criteria and the review window per deliverable
- Timeline, milestones, and dependencies on the client
- Fees, the pricing model, and the payment schedule tied to milestones
- Named personnel or roles, where the client is buying specific expertise
- Service levels, if the engagement is ongoing rather than project-based
- Assumptions the estimate relies on
- Explicit exclusions
That last pair — assumptions and exclusions — does more work than anything else in the document. Most scope disputes are not about what the SOW said; they are about what each side assumed without writing down.
Scope, acceptance, and the word "done"
Vague scope is the single largest source of friction in services work. "Build a customer portal" is not scope. Scope is a list of specific functions, an explicit statement of what is not included, and a defined number of revision rounds.
Acceptance criteria turn scope into something payable. For each deliverable, state:
- What objective test it must meet — not "client satisfaction", which is unmeasurable.
- How many business days the client has to review it.
- That the deliverable is deemed accepted if no written objection arrives within that window.
- What happens on rejection: the supplier corrects the identified deficiency, and the review clock restarts for that item only.
The deemed-acceptance provision is what stops a project sitting in permanent review while invoices go unpaid. Clients sometimes resist it; the reasonable compromise is a longer window rather than no deeming provision at all.
Change control: the clause that pays for itself
Scope changes. That is normal and not a failure. What causes disputes is scope changing without anyone recording the effect on price and timeline.
A workable change control clause says: any change to scope, deliverables, or timeline must be recorded in a written change order signed by both parties; the change order states the revised fee and revised dates; and until it is signed, the supplier continues on the existing SOW. That last part matters — without it, suppliers do the extra work first and negotiate afterwards from a weak position.
Keep the mechanism light. If a change order requires the same approval chain as the MSA, nobody will use it and you are back to informal creep.
Service levels, if the work is ongoing
Project SOWs need milestones. Retained or managed-service SOWs need service levels. If you are committing to ongoing support, define:
- Severity tiers with concrete examples, so classification is not argued about mid-incident.
- Response time versus resolution target — these are different commitments and only the first is fully within the supplier's control.
- Coverage hours and whether out-of-hours support is included or billable.
- Measurement period and who reports.
- Consequences — service credits are the usual remedy. Cap them, and state whether they are the exclusive remedy for missed levels.
- Exclusions — client-caused delays, third-party outages, and agreed maintenance windows.
An availability figure with no measurement method and no consequence is decoration. Either define all three or leave it out.
IP, confidentiality, and the tools you reuse
Service suppliers almost always bring pre-existing material: internal libraries, frameworks, templates, methodologies. Clients almost always assume they own everything delivered. Both positions are reasonable and the contract has to reconcile them.
The standard structure separates three things:
- Background IP — what each side owned before the engagement. Stays theirs.
- Foreground IP — what is created specifically under the SOW. Usually assigned to the client, commonly on payment in full.
- Supplier tools and know-how — reusable components embedded in the deliverable. Remain the supplier's, with a broad licence to the client to use them as part of the deliverable.
Get that third category expressly stated. A blanket "all IP created or used vests in the client" clause, signed without thought, can technically hand over the supplier's own toolkit.
Confidentiality sits in the MSA and covers both directions. Where the relationship involves particularly sensitive disclosure before any SOW exists, a standalone NDA signed first still makes sense; our NDA guide covers what that document should contain.
Liability, indemnities, and insurance
Liability caps are the clause most likely to stall a negotiation, usually because one side has anchored on a number without reference to contract value. A workable approach:
- Cap aggregate liability at a defined multiple of fees paid, or fees paid in the preceding twelve months for ongoing arrangements.
- Exclude indirect and consequential loss, and say plainly whether loss of profit and loss of data fall inside or outside that exclusion.
- Carve out from the cap the matters that are conventionally uncapped — confidentiality breach, IP infringement, wilful misconduct, and liabilities that cannot lawfully be limited.
- Match the cap to reality. A cap far below contract value is not commercially credible; a cap far above the supplier's insurance is not collectable.
Where the client requires specific insurance — professional indemnity, cyber, public liability — state the cover types and minimum amounts in the MSA and require evidence on request.
Termination that does not strand either side
The MSA and each SOW should terminate independently. Cover:
- Termination for convenience — notice period, and whether it applies to the MSA, to individual SOWs, or both.
- Termination for cause — material breach with a cure period, insolvency, prolonged force majeure.
- What happens to work in progress — payment for work performed and accepted up to termination, plus committed non-cancellable costs.
- Handover obligations — deliverables in whatever state they exist, credentials, documentation, and data return or deletion.
- Survival — confidentiality, IP assignment, and liability provisions continue after termination.
Clients should pay particular attention to handover. A supplier with no contractual obligation to transfer credentials and documentation has considerable practical leverage at exactly the wrong moment.
Executing both documents digitally
Neither an MSA nor a SOW generally needs a wet signature. Both are ordinary commercial contracts and are routinely signed electronically.
On WeSignDeal, the pattern that works is: execute the MSA once as a service agreement, then execute each SOW as its own short document referencing the MSA by name and date. Each document goes through the same flow — enter party details, upload supporting documents, issue a secure verification link to every signer for a live selfie and identity document upload, then collect eSign from each of them. Where stamp duty applies to the document type and jurisdiction, the platform can procure a Government eStamp, or accept a self-uploaded certificate where that option is enabled for your case.
Two practical notes. Where a party is a company, confirm the individual signing is authorised to bind it before issuing links. And note that fields lock once verification links are issued and payment is completed, so scope, fees, and dates should be settled at that point — a mid-flow price change means starting the document again. How it works walks through the sequence, and Pricing shows the per-signer eSign cost, which is the figure that matters when several people sign each SOW.
Pre-signature checklist
- MSA covers the framework; SOW covers the work — with no duplication.
- Order-of-precedence clause states which document governs a conflict.
- Scope specific, with explicit exclusions and stated assumptions.
- Acceptance criteria objective, with a review window and deemed acceptance.
- Change control mechanism defined and lightweight enough to use.
- Payment terms, milestones, and late payment consequences set.
- IP split into background, foreground, and supplier tools.
- Liability cap proportionate, with carve-outs identified.
- Insurance requirements stated where relevant.
- Termination, handover, and survival provisions complete.
- Signatory authority confirmed for corporate parties.
Related reading
- Freelance and independent contractor agreements
- Consultancy agreements
- Vendor and supplier agreements
- NDA guide
Start a service agreement, or see all document types on Do Agreement Online. The FAQ Centre answers questions on verification, stamping, and signing.
General information only, not legal advice. WeSignDeal is a technology and document facilitation platform, not a law firm. Contract law, liability limitations, and stamp duty treatment vary by jurisdiction — take professional advice on high-value or high-risk engagements.
