How to Write a Statement of Work (With Template)
By Suraj Rao11 min readWhat You'll Learn
- A statement of work defines one piece of agreed work in detail: what you'll deliver, by when, how it will be accepted and what it costs.
- The sections that prevent most disputes are the exclusions, the client's responsibilities, the acceptance criteria and the change request process.
- Use one master contract for the legal terms and a short SOW for each new project, so you never renegotiate the basics with a returning client.

A statement of work (SOW) is the document that says exactly what you'll deliver on a project, by when, how the client will decide it's done and what it costs. It sits between the sales conversation and the legal terms. The proposal convinced the client. The contract sets the rules. The SOW pins down the work itself.
You don't need an SOW for every job. But once you work with a client more than once, or on a project with several phases, it's the cleanest way to agree each piece of work without rewriting your whole contract.
This guide covers how an SOW differs from a proposal and a contract, the 10 sections every SOW needs, how to write acceptance criteria and a change request process that actually work, and a full template you can copy at the end.
SOW vs contract vs proposal
These three documents overlap, which is why people mix them up. Here's how they divide the work:
| Proposal | Contract (master agreement) | Statement of work | |
|---|---|---|---|
| Purpose | Win the work | Set the legal rules for the relationship | Define one piece of agreed work |
| When | Before the client says yes | Once, at the start of the relationship | For each project or phase |
| Tone | Persuasive | Legal, neutral | Precise, practical |
| Key contents | Goals, approach, options, price | Payment terms, ownership, confidentiality, termination, liability | Scope, deliverables, exclusions, timeline, acceptance, fees, change control |
| Binding? | Usually an offer until accepted | Yes, once signed | Yes, once signed, under the contract |
A common setup for freelancers and small agencies is: one master contract, signed once, with a new SOW for every project. The SOW says it's governed by the contract, so all the legal terms carry over. Our post on proposal vs contract explains the first two documents in more detail, and freelance contract: what to include lists the clauses for the master agreement.
When you need a statement of work
You need an SOW when any of these are true:
- You already have a contract with the client and you're starting a new project.
- The project has phases or milestones that need separate sign-off.
- The client's procurement team asks for one. Larger companies often won't issue a purchase order without it.
- Several people will do the work, on your side or theirs, and everyone needs the same reference.
- The scope is easy to misread. If "a new website" could mean five pages or fifty, write it down.
For a one-off, two-day job, a signed proposal with your standard terms is usually enough.
The 10 sections of a statement of work
1. Background and objectives
Two or three sentences on why the project exists and what the client wants to achieve. This gives every later decision a reference point. If a request doesn't serve the objective, it's worth asking why it's there.
Northwind sells refurbished laptops online. Mobile visitors abandon checkout at twice the desktop rate. The goal of this project is to redesign and rebuild the mobile checkout to reduce abandonment.
2. Scope of work
What you'll do, described as activities. Keep it concrete: "design", "build", "test", "migrate", not "support" or "optimize".
3. Deliverables
The things the client will receive, each one specific enough that both sides would agree whether it exists. "Checkout designs" is vague. "High-fidelity mobile designs for the cart, shipping, payment and confirmation screens, in Figma" is a deliverable.
4. Out of scope
What you won't do. This is the section that saves the most arguments, because it answers the question before anyone asks it. List the things a reasonable client might assume are included:
- Desktop checkout changes
- Copywriting beyond button labels and error messages
- Payment provider integration changes
- Ongoing maintenance after launch
5. Timeline and milestones
Dates for each milestone, and what each date depends on. Tie dates to client inputs so a delay on their side moves the schedule fairly:
Designs delivered 10 working days after we receive brand assets and analytics access.
6. Roles and responsibilities
Who does what, on both sides. Name the client's single decision-maker, the person who can approve deliverables and changes. List what the client must provide, and by when: content, logins, feedback, test accounts.
7. Assumptions
The conditions your price and timeline rely on. If an assumption turns out wrong, the change process kicks in. For example:
- Feedback on each deliverable is consolidated and returned within 3 working days.
- The existing payment provider's API supports the required fields.
- No more than two rounds of revisions per deliverable.
8. Acceptance criteria
How the client will decide each deliverable is done, and what happens if they don't respond. More on this below.
9. Fees and payment schedule
The price, how it's calculated (fixed, hourly with an estimate, or a cap), and when each payment is due. Tie payments to milestones where you can. Our guide on how much deposit to ask for covers common splits.
10. Change control
How changes are requested, quoted, approved and added. Also covered below.
End the SOW with a line saying which contract governs it, then signatures and dates from both sides.
How to write acceptance criteria
Acceptance criteria answer one question: how will we both know this deliverable is finished? Without them, "done" becomes whatever the client feels on the day, which is how projects drag on for weeks after the last task.
Good acceptance criteria are:
- Specific. "Loads quickly" isn't testable. "The checkout page passes the tests listed in the test plan on the latest versions of Safari on iOS and Chrome on Android" is.
- Agreed in advance. Write them into the SOW, not after the deliverable arrives.
- About the deliverable, not taste. Taste is handled by revision rounds. Acceptance checks the agreed requirements were met.
- Time-limited. Give the client a review window, and say what happens if it passes in silence.
Here's an acceptance clause you can adapt:
Acceptance
When a deliverable is ready, we'll send it with a note confirming it
meets the acceptance criteria above. You have 5 working days to review.
Within that time, either confirm acceptance in writing or send a single
consolidated list of the criteria it doesn't yet meet. We'll fix those
items and resubmit, and the review period starts again for those items.
If we receive neither within 5 working days, the deliverable is treated
as accepted. Requests outside the acceptance criteria are handled as
change requests.The "treated as accepted" line, sometimes called deemed acceptance, stops a project stalling because nobody signs off. Whether it's enforceable, and how, depends on your contract and the law where you work. This is general information, not legal advice, so check it with a lawyer for larger projects.
Worked example: acceptance on a fixed fee
Say the checkout project is a fixed fee of $12,000 in three milestones: designs ($4,000), build ($6,000) and launch ($2,000). Each milestone invoice is sent when its deliverable is accepted. If the designs are delivered on 2 March and the client hasn't replied by 9 March (5 working days), the designs are accepted and you invoice $4,000 that day. Without the clause, that money waits until someone finds time to say "looks good".
How to handle change requests
Every project changes. The aim isn't to stop change, it's to make sure each change is priced and scheduled before work begins. Uncontrolled change is scope creep, and that post covers the warning signs and how to say no politely. Here, the focus is on what to write in the SOW.
A change control section needs four parts:
- How to request. In writing, to a named person.
- What you'll send back. A short change order with what changes, the effect on price and timeline, and anything that drops out.
- Who approves. The client's decision-maker, in writing, before you start.
- How it's billed. Added to the next milestone invoice, or invoiced separately.
Change requests
Either side can request a change to the scope, deliverables or timeline
by email to the project leads named in section 6. Within 3 working days
we'll reply with a change order describing the change, its cost and its
effect on the timeline. Work on the change starts only after the client's
project lead approves the change order in writing. Approved changes are
added to the next milestone invoice at the rates in section 9.Worked example: pricing a change
Midway through the build, the client asks to add a "save cart for later" feature. You estimate 14 hours at $95 an hour:
- Cost: 14 × $95 = $1,330.
- Timeline: the feature adds 2 working days, so launch moves from 30 March to 1 April.
- Change order: "Add save-for-later on the mobile cart. +$1,330. Launch date moves to 1 April."
The client approves, and $1,330 is added to the launch invoice: $2,000 + $1,330 = $3,330.
The hourly estimate only holds if you know how long similar work took last time. Tracking time against each project, and comparing it with the estimate, is how you get better at this. See how to estimate project hours for methods.
Common SOW mistakes
- Writing activities instead of deliverables. "Ongoing design support" has no end. "Up to 10 hours of design changes per month, used or lost" does.
- Leaving out exclusions. If it's not written down as excluded, the client may assume it's included.
- Forgetting client responsibilities. Your timeline depends on their inputs. Say so.
- No named decision-maker. Feedback from five people with no tie-breaker can double a project.
- Contradicting the contract. The SOW should cover the project; the contract covers the rules. If they conflict, say which one wins.
Statement of work template
Copy this into your editor and replace everything in square brackets. Delete what doesn't apply.
STATEMENT OF WORK
SOW number: [SOW-2026-03]
Date: [21 November 2026]
Client: [Client legal name, address]
Provider: [Your name or business name, address]
Governing agreement: This SOW is governed by the [Master Services
Agreement] dated [date]. If this SOW conflicts with that agreement,
[the agreement / this SOW] takes precedence.
1. BACKGROUND AND OBJECTIVES
[Two or three sentences: the client, the problem, the goal.]
2. SCOPE OF WORK
[Activities you'll carry out, in plain verbs.]
3. DELIVERABLES
3.1 [Deliverable, format, quantity]
3.2 [Deliverable, format, quantity]
3.3 [Deliverable, format, quantity]
4. OUT OF SCOPE
- [Item]
- [Item]
- [Item]
5. TIMELINE AND MILESTONES
Milestone 1: [Deliverable] - [date or "X working days after input Y"]
Milestone 2: [Deliverable] - [date]
Milestone 3: [Deliverable] - [date]
6. ROLES AND RESPONSIBILITIES
Provider project lead: [name, email]
Client project lead (approves deliverables and changes): [name, email]
The client will provide: [content, access, feedback] by [date].
7. ASSUMPTIONS
- [Feedback returned within X working days, consolidated]
- [Up to X revision rounds per deliverable]
- [Technical or business assumption]
8. ACCEPTANCE CRITERIA
3.1 is accepted when: [testable criteria]
3.2 is accepted when: [testable criteria]
Review period: [5] working days. If neither acceptance nor a list of
unmet criteria is received in that time, the deliverable is accepted.
9. FEES AND PAYMENT SCHEDULE
Pricing: [Fixed fee of $X / hourly at $X, estimated X hours, capped at $X]
Payment 1: [X% / $X] on signing
Payment 2: [X% / $X] on acceptance of Milestone [1]
Payment 3: [X% / $X] on acceptance of Milestone [3]
Invoices are due within [14] days.
Expenses: [billed at cost with receipts / included / not billable]
10. CHANGE CONTROL
Changes are requested in writing to the project leads. The provider
replies within [3] working days with a change order showing cost and
timeline impact. Work starts only after written approval. Approved
change orders form part of this SOW.
SIGNATURES
Client: ______________ Name: ______ Title: ______ Date: ______
Provider: ____________ Name: ______ Title: ______ Date: ______Managing an SOW in Tristiks Grow
Tristiks Grow doesn't have a separate SOW document type, but its contracts and projects cover the workflow. You can write your SOW as a contract from your own saved template, link it to the client and project it's for, and send it for signing. Each person at the client gets a secure link, signs by typing their name, and the signed version is locked. You can also link it to the proposal it follows. See the proposal and contract software page.
Once the work starts, give the project an estimate, break it into tasks with their own time estimates, and track time against them, so you can see tracked time against the estimate as you go (project time tracking). That's what tells you early whether a milestone is on budget; our guide to project budgets explains what to look for. For milestone payments, scheduled payments let you split a project into several invoices, each with its own amount, send date and terms.
Frequently asked questions
Is a statement of work a contract?
An SOW signed by both sides is usually treated as part of the agreement, especially when it says it's governed by a master contract. On its own, without legal terms, it can still be binding in many places, but it leaves gaps. This is general information, so check with a lawyer where you work.
Who writes the statement of work?
Usually the person doing the work, because you know what's realistic. Some larger clients send their own SOW template; in that case, read the acceptance, change and payment sections closely before you sign.
How long should a statement of work be?
Long enough that a stranger could tell what's included and when it's done. For most freelance projects that's two to five pages. A long SOW isn't better; a clear one is.
What's the difference between scope of work and statement of work?
The scope of work is one section of an SOW: the activities you'll carry out. The statement of work is the whole document, which also covers deliverables, timeline, acceptance, fees and change control.
Wrap up
A statement of work turns "we agreed to build the thing" into a list of deliverables, dates, acceptance tests and prices that both sides signed. Write the exclusions, the client's responsibilities, the acceptance criteria and the change process carefully. They're what keep the project on track when things change.
To send your SOW from a saved template, get it signed online and track time against the project estimate, try Tristiks Grow free for 14 days, or start from our free contract template.
Category: Client Management

Suraj Rao
Suraj Rao is the founder of Tristiks, the team behind Tristiks Grow and its desktop time tracker OneTrack. He writes about time tracking, client work and getting paid, and about DevOps, cloud and AI from years of building software.



