Statement of Work

Engagement: [Short name for this piece of work] Client: [Client legal name] Provider: [Your legal name / company] SOW date: [Date] Effective from: [Date] Governing agreement: [Reference to the master service agreement, if any]

---

1. Parties

This Statement of Work is entered into between [Client legal name] (the "Client") and [Provider legal name] (the "Provider"). It is governed by the [service agreement / master services agreement] dated [date], and where this SOW conflicts with that agreement, the [agreement / SOW] prevails as stated there.

2. Background and objectives

[A short paragraph on why this work is happening and the outcome it should achieve. Keep it to the business goal, not the task list.]

3. Scope of work

In scope

[Describe the work in plain, countable terms. Break it into the main areas of effort.]

• [Work area 1 and what it covers]
• [Work area 2 and what it covers]
• [Work area 3 and what it covers]

Out of scope

[List anything a reader might reasonably assume is included but is not.]

• [Exclusion 1]
• [Exclusion 2]

4. Deliverables

#	Deliverable	Description	Format	Owner
1	[Deliverable name]	[What it is]	[e.g. PDF, repo, file]	[Provider]
2	[Deliverable name]	[What it is]	[Format]	[Provider]
3	[Deliverable name]	[What it is]	[Format]	[Provider]

5. Timeline and milestones

Milestone	Description	Target date
M1	[Kickoff / discovery complete]	[Date]
M2	[Core build / draft delivered]	[Date]
M3	[Review and revisions]	[Date]
M4	[Final acceptance / handover]	[Date]

6. Acceptance criteria

[State the objective tests each deliverable must pass to be accepted, and the review process.]

• A deliverable is accepted when it meets [the criteria listed in Section 4] and [any agreed standard].
• The Client has [X business days] from delivery to accept or to return written, specific revision notes.
• If no response is received within that window, the deliverable is deemed accepted.
• Revisions outside the stated scope are handled under Section 9 (Change control).

7. Fees and payment schedule

Pricing model: [Fixed price / Time and materials / Milestone-based]

Item	Basis	Amount
[Phase or deliverable 1]	[Fixed / rate x hours]	[$]
[Phase or deliverable 2]	[Fixed / rate x hours]	[$]
Total		[$]

Payment schedule

• [e.g. 30% on signature of this SOW]
• [e.g. 40% on acceptance of M2]
• [e.g. 30% on final acceptance]

Invoices are due within [14] days of issue. [State any expenses policy and tax treatment.]

8. Assumptions and dependencies

[List the conditions the plan relies on. If one fails, the timeline or price may need to change via Section 9.]

• [The Client will provide [content / access / approvals] within [timeframe].]
• [Required third-party services or licences are in place by [date].]
• [Work is performed remotely / on-site at [location] during [hours].]

9. Change control

[Define how new or changed requirements are handled once work begins.]

• Either party may request a change in writing.
• The Provider will assess the impact on scope, timeline, and price and issue a written change request.
• No changed work begins until both parties approve the change request in writing.
• Approved changes are appended to this SOW and may adjust the fees and dates above.

10. Sign-off

By signing below, both parties agree to the scope, deliverables, schedule, and fees set out above.

For the Client: ______________________ Name / title: ____________ Date: ____________

For the Provider: ______________________ Name / title: ____________ Date: ____________