SOW
Statement of work
The document defining what will be delivered, when, and for how much.
Sets out deliverables, timelines, responsibilities, assumptions and price. Distinct from the master services agreement, which governs the relationship as a whole; the SOW governs one piece of work inside it.
Key takeaways
- The assumptions section is the one that saves projects, and the one most often left as boilerplate.
- Exclusions matter as much as inclusions. What is not listed is arguable, and the argument comes at the worst moment.
- Without acceptance criteria a deliverable can be revised indefinitely by a client who cannot say what is wrong.
- Name the revision rounds. Two included and a rate for the third is a normal sentence that prevents an abnormal month.
- State what happens to the timeline when a client dependency slips, because it will.
What it is, and what the MSA is for
Two documents do two jobs and conflating them causes trouble in both directions. The master services agreement governs the relationship: liability, confidentiality, intellectual property, payment terms, termination, data protection. It is signed once and rarely revisited.
The statement of work governs one piece of work inside that relationship: what is being produced, by when, by whom, for how much. There can be several, and each should be able to stand on its own.
Putting commercial detail in the MSA makes it hard to change, since amending it reopens the whole agreement. Putting legal terms in every SOW means renegotiating liability every time somebody buys a landing page.
For a retainer the distinction is often skipped, which is where the trouble starts. A retainer without a SOW-equivalent describing the monthly scope is a recurring invoice with no definition attached, and every month is an opportunity to disagree about what it covers.
Assumptions, which is the section that saves the project
Almost every agency project depends on things the agency does not control: brand assets, access to systems, copy approval, a technical contact, sign-off from somebody who is on holiday. Those dependencies exist whether or not they are written down. Writing them down changes who is accountable when they slip.
A line saying the client provides brand assets within five working days of kickoff costs one sentence. Without it, a two-week delay waiting for a logo is an agency running late. With it, the same delay is a documented dependency, raised in week one, with the timeline adjusted accordingly.
The habit worth building is to write the assumptions after the plan rather than before, by asking what has to be true for this to work. Every answer is an assumption, and the ones that would be embarrassing to depend on silently are exactly the ones to write down.
It is also the least confrontational part of a SOW to negotiate. Clients rarely object to a list of things they need to provide, because it reads as organisation rather than as a defence, which it is.
Exclusions and the definition of done
A list of what is included leaves everything adjacent arguable. Does a website project include the copy. Does a campaign include the landing page. Does a report include a meeting to talk through it. Each of those has a reasonable answer in both directions, and the argument is always had at the point where it is most expensive to have.
Naming a handful of exclusions is quicker than it sounds and does most of the work: copywriting not included, hosting and domain not included, photography not included, translation not included. Nobody objects to clarity at the proposal stage.
Acceptance criteria are the other half and the one most often missing entirely. Without a definition of done, a deliverable remains open indefinitely, and the usual failure is not an unreasonable client but an unhappy one who cannot articulate what is wrong.
Revision rounds are the practical form of this. Two rounds included, further rounds at an hourly rate, is a normal sentence that converts an unbounded obligation into a priced one, and it gives the client a reason to consolidate feedback rather than send it in six instalments.
What happens when a dependency slips
The assumption is only half the protection. The other half is stating the consequence, because a dependency that slips without a stated consequence becomes an agency problem by default.
The clause is simple and worth having: if a dependency is late, the timeline moves by at least the length of the delay, and the agency will confirm the revised dates. That does two things. It prevents the expectation that the team will compress its own work to absorb somebody else lateness, and it makes the revised date an explicit communication rather than a silent slip.
At least is doing real work in that sentence. A three-day delay rarely costs three days, because the team has been reassigned and has to be scheduled back in. Saying so in advance is far easier than explaining it afterwards.
The other clause worth having covers the stalled project: work paused for more than a stated period may be rescheduled or re-quoted. Projects that go quiet for two months and then resume with the original deadline are common, and without that clause the agency absorbs the entire cost of the pause.
What it means for an agency
Cover three things or expect to eat the difference: dependencies on the client, the number of revision rounds included, and what happens to the timeline when a dependency slips.
Where it goes wrong
- Leaving the assumptions section as boilerplate, so a client delay becomes an agency running late.
- Listing inclusions without exclusions, which leaves every adjacent task arguable.
- Omitting acceptance criteria, so a deliverable can be revised indefinitely.
- Stating a dependency without stating the consequence, which makes the slip an agency problem by default.
In short
A SOW is not paperwork for the day things go wrong, it is the document that stops them going wrong. The sections that do that work, assumptions, exclusions and acceptance, are the three most often left as boilerplate, and they cost a paragraph each.
Frequently asked questions
What is the difference between a SOW and an MSA?
The master services agreement governs the relationship: liability, confidentiality, intellectual property, payment terms, termination. It is signed once. The statement of work governs one piece of work inside it: deliverables, timeline, responsibilities and price, and there can be several. Keeping commercial detail out of the MSA means changing the work does not reopen the legal agreement.
What should always be in a SOW?
Beyond deliverables and price, three things that are usually missing: the assumptions, meaning what the client has to provide and by when; the exclusions, since anything not named is arguable; and the acceptance criteria, including how many revision rounds are included. Each of those prevents a specific argument that otherwise happens at the least convenient moment.
How many revision rounds should be included?
Two is the common answer, with further rounds at an hourly rate. The number matters less than naming one, because an unnamed number is unbounded, and it gives the client a reason to consolidate feedback rather than send it in six instalments. Without it, the usual failure is not an unreasonable client but an unhappy one who cannot say what is wrong.
Do retainers need a statement of work?
They need the equivalent. A recurring invoice with no written definition of the monthly scope leaves every month open to disagreement about what it covers, which is the most common way a retainer becomes unprofitable. The document can be short, and it should still name inclusions, exclusions and what triggers a conversation about extra work.
Related terms
Last reviewed
Keplent keeps track of these for you.
It holds what each client agreed to, watches what their campaigns actually did, and tells you in plain sentences what needs you this week.
Join the waitlist