How to Write a Statement of Work That Protects You and Your Client
The short answer
A statement of work (SOW) is the document that turns an accepted proposal into a precise, shared description of the job. Write it after the client chooses an option and before work starts. It should list checkable deliverables with acceptance criteria, assumptions, client dependencies, exclusions, revision rounds, the timeline, fees and payment schedule, the change process, and IP, confidentiality and sign-off, in plain words both sides' project people can use.
- The proposal persuades; the statement of work protects both sides
- Every deliverable needs a quantity or format, acceptance criteria, an acceptor and a response window
- Write client dependencies with owners and dates, and say what happens to the timeline if they slip
- Define revision rounds and exclusions: they are the cheapest scope protection there is
- IP does not always pass to the client automatically; agree ownership in writing with your lawyer
- No change work starts before a change order is approved in writing
What is a statement of work, and how is it different from a proposal?
A proposal is written to help a client decide. It explains their situation, the outcome they want, your approach, a few options and a price. A statement of work is written after they decide. It describes exactly what will be delivered, how each piece will be accepted, what it depends on, what it costs, when it will be paid for and how changes will be handled.
The two documents do different jobs, and mixing them causes trouble. A proposal full of contract terms is hard to read and slow to approve. A statement of work written like a sales document leaves out the details that matter in week five, when someone asks what 'brand guidelines' or 'website' actually meant.
Independent work is now a large share of how services are bought. The Upwork Research Institute's Future Workforce Index, published in April 2025, found that 28% of US skilled knowledge workers freelance or work independently, and MBO Partners' 2026 State of Independence research reports a record 74.9 million Americans earning income independently. More independent suppliers means more clients comparing proposals, and more projects that rely on a clear SOW to finish well.
What should a statement of work include?
Twelve parts cover almost every service project, from a logo to a software build. You can merge some for small jobs, but think about each one before you leave it out.
| Part | What it says | Why it matters |
|---|---|---|
| 1. Parties and reference | Who is agreeing; which proposal and master agreement it sits under | Avoids confusion over which document applies |
| 2. Objectives | The outcome and how it will be measured | Keeps everyone focused on why the work exists |
| 3. Deliverables | Numbered things with quantity or format | The core of the scope |
| 4. Acceptance criteria | How each deliverable is judged done, by whom, within what time | Prevents most scope disputes |
| 5. Assumptions | What you rely on being true | Triggers the change process if it proves false |
| 6. Client dependencies | What the client provides, owner, date | Protects the timeline |
| 7. Exclusions | What is not included | Cheap, clear scope protection |
| 8. Revisions | Rounds per stage and what counts as a round | Stops unlimited revisions by omission |
| 9. Timeline | Milestones and how dates move when dependencies slip | Sets expectations both ways |
| 10. Fees and payment | Amount, currency, tax, deposit, milestones, terms | Protects cash flow |
| 11. Change process | Request, assess, price, approve in writing | Turns scope creep into a conversation |
| 12. IP, confidentiality, sign-off | Who owns what and when; signatures | Avoids the most expensive misunderstandings |
How do you write deliverables and acceptance criteria?
A deliverable is a thing the client will receive, described precisely enough that two reasonable people would agree whether it exists. 'Website' is not a deliverable. 'Twenty pages built on the client's CMS, using the approved templates, on a staging site' is.
Acceptance criteria then say how both sides will know the deliverable is done. Good criteria are observable. For an online booking feature, for example: 'A patient can book any of the five routine appointment types at any practice on mobile and desktop, and the booking appears in the practice system within five minutes.' Add who accepts it and how long they have to respond, and say what happens if they raise specific defects.
Some suppliers add a clause that a deliverable is treated as accepted if no specific defects are raised within the response window. Whether that is appropriate, and how to word it, depends on your contract and local law, so ask your lawyer.
- Number every deliverable; use the numbers in invoices and change orders
- Give each a quantity, format or other checkable description
- Write criteria the client could test without asking you
- Name one acceptor and a response window
- Accept against the criteria, not against new wishes
Why do assumptions, dependencies and exclusions matter so much?
Most projects that run late are waiting for something: content, access to a system, an approval, a third party. Write each client dependency with an owner and a date, and say plainly that if it arrives late, the affected milestones move by at least the same time. This is not a threat. It is a fair description of how the work happens, and it lets you have the conversation early instead of in the final week.
Assumptions are the things you are relying on being true, such as 'the booking software provider gives interface access within ten working days'. If an assumption proves false, the change process applies. Exclusions list what is not included in plain words: new copywriting, photography, hosting fees, advertising. Clients rarely object to a clear exclusion at the start; they often object to a surprise one at the end.
How should a statement of work handle revisions and changes?
Leave revisions undefined and you have agreed to unlimited revisions by omission. State how many rounds are included at each stage and what a round means, for example one consolidated set of written feedback from the nominated contact. Say what happens after the included rounds: a stated rate, or a change order.
The change process is the most useful clause in the document. Either side can request a change; the supplier sends a short change order with the cost, the effect on the timeline and any effect on other deliverables; nothing starts until the client approves it in writing; the approved change becomes part of the SOW. The old project-management idea of the triple constraint explains why: scope, time and cost are linked, so a change to one moves another.
Decide in advance what you will absorb as goodwill, such as anything under two hours, and log it anyway. That way you know what you gave, and you can mention it when the project ends.
Reading helps; measuring tells you what to work on. These AI-graded assessments on AssessAll pair with this topic:
Who owns the work: what about IP and confidentiality?
Many freelancers and clients assume the client owns whatever it pays for. In many countries that is not automatic. In the United States, for example, the Copyright Office explains in its Circular 30 that work by an independent contractor counts as 'made for hire' only if it falls into one of nine specific categories of commissioned work and both parties sign a written agreement saying so. Outside those cases, rights generally have to be transferred, and rules differ by country.
So the SOW, or the contract it sits under, should say what the client will own, when ownership passes (often on payment in full), and what you keep: your tools, templates, code libraries, know-how and, if agreed, the right to show the work in your portfolio. Confidentiality should cover both sides' information. Have your lawyer draft the wording; the SOW's job is to make the commercial agreement clear.
What should the fees and payment section say?
State the total fee, the currency and whether tax is included. Then set out the payment schedule: a deposit on signature, payments tied to accepted milestones, and the final payment. State the payment terms in days and what happens if payment is late, in line with local law.
Late-payment rules vary. In the UK, the government's guidance explains that if no payment date is agreed, a business-to-business payment is late 30 days after the customer gets the invoice or you deliver, whichever is later, and statutory interest can be claimed at 8% plus the Bank of England base rate unless the contract sets a different rate. New York State's Freelance Isn't Free Act, in force statewide since August 2024, requires a written contract for freelance work worth USD 800 or more and sets payment within 30 days of completion where no date is agreed. Other countries have their own rules, so check yours and ask your accountant about tax on services, especially across borders.
When do you need a master services agreement as well?
If you expect more than one project with a client, put the general legal terms in a master services agreement (MSA): payment, IP, confidentiality, liability, termination and governing law. Each project then needs only a short SOW. The client's legal team reviews the MSA once, and later projects move faster. Make sure the documents say which one wins if they conflict.
Small agencies and freelancers often skip this and attach the same general terms to every SOW. That works too, as long as the terms are consistent and reviewed by a lawyer. The point is to stop renegotiating liability and IP on every small project.
How can AI help you write a statement of work?
AI assistants are useful for the drafting and checking parts of the job: turning a list of deliverables into checkable descriptions, suggesting acceptance criteria, spotting assumptions you have not written down, and checking a draft against the twelve parts above. They are not a substitute for a lawyer, and they can produce confident contract language that does not fit your country's law.
Two rules keep it safe. First, check your client agreement and your tool's data settings before pasting anything in, and remove names and confidential figures where you can. Second, a person reviews every line before it goes to a client, prices every change and signs every SOW. If you want a structured way to practise reading commercial terms, AssessAll's Commercial Terms and Contract Reading Assessment for Freelancers, Managers and Small Business Owners is one option, and a Jobulary development plan can turn what you learn into a practice routine.
The Proposal and Statement of Work Kit from Bodhih Training includes a plain-words SOW template in these twelve parts, a change order form, an MSA discussion sheet and a workbook that tracks deliverables, acceptance and change orders.

Write your next SOW with every part ready
The Proposal and Statement of Work Kit from Bodhih Training gives you a plain-words SOW template, a change order form, a proposal template and a workbook that tracks deliverables, acceptance and changes, so each step in this guide has a tool.
Sources
- U.S. Copyright Office: Circular 30, Works Made for Hire
- GOV.UK: Late commercial payments, charging interest and debt recovery
- Bond, Schoeneck and King: New York enacts statewide Freelance Isn't Free legislation
- Upwork: Study finds 1 in 4 U.S. skilled knowledge workers now work independently (Future Workforce Index, 2025)
- MBO Partners: State of Independence research
More from the Bodhih family
Questions people ask next
Is a statement of work a contract?
It can be part of one. Many SOWs sit under a master services agreement or general terms, and together they form the contract. Whether your SOW is binding on its own depends on its wording and local law, so have your lawyer review your template.
Who writes the statement of work, the client or the supplier?
Either can, but in small service projects the supplier usually drafts it from the accepted proposal, because the supplier knows best what will be delivered. The client then reviews it, especially the deliverables, acceptance criteria and dependencies.
How long should a statement of work be?
As long as it needs to be for both sides to know what done looks like. For a small project, two or three pages can cover all twelve parts. Length matters less than whether each deliverable is checkable.
What is the difference between scope and deliverables?
Scope describes the work in general terms, such as 'redesign and rebuild the website'. Deliverables are the specific things the client receives, such as 'twenty pages built on staging' or 'a sitemap approved in writing'. Acceptance criteria apply to deliverables.
How many revision rounds should I include?
There is no standard number. Two rounds per design stage is common in creative work, but choose what your estimate allows, define what counts as a round, and say what happens after the included rounds.
What happens if the client never formally accepts a deliverable?
Follow up when the response window passes and ask for acceptance or specific defects against the criteria. Some contracts treat silence as acceptance after a stated period; whether that suits your contract is a question for your lawyer.
Do I need a new SOW for a small change?
No. Use a change order that refers to the original SOW and says what changes, the cost and the effect on the timeline. Once approved in writing, it becomes part of the SOW.