What Is a Statement of Work?
A statement of work (SOW) is the document that fixes what a supplier will deliver, in what quantity, by when, and what counts as done. It is not the contract.
A statement of work (SOW) is the document that fixes what a supplier will deliver, in what quantity, by when, and what counts as done. It is not the contract. The contract governs the commercial relationship, payment terms and liability. The SOW governs the work itself, and it is the only part of the arrangement you can audit month by month.
Why the SOW settles every argument that follows
Nine months in, when the relationship has cooled and somebody asks what you have actually received, the answer is whatever the SOW says. Not what was promised in the pitch. Not what the account manager implied on a call.
A vague SOW is not a neutral document. It transfers the burden of proof onto you, because a supplier can only be shown to have fallen short of something specific. If the page says ‘ongoing optimisation’, nobody can fall short of it, ever, and the conversation becomes a disagreement about feelings rather than a comparison against a list. That is also why the monthly reporting has to trace back to the same wording. When you can see what was actually delivered against what was named, the review takes ten minutes instead of a fortnight.
What a usable SOW contains
Length is not the measure. A short SOW made of countable things beats twenty pages of intent.
- Deliverables with counts. Each item stated as a noun and a number: four articles, twelve optimised URLs, one technical audit. If it cannot be counted, it cannot be checked, and it will not be missed when it is skipped.
- Acceptance criteria. What ‘done’ means for each item, and who signs it off. Published and live is a criterion. Delivered for review is a different one, and the gap between them is where months disappear.
- Dependencies and your obligations. Developer time, approvals, access. State the turnaround you owe and what happens to the schedule when you miss it, so the excuse is agreed in advance rather than invented later.
- Exclusions. The explicit list of what is not included. This is the most valuable section in the document and usually the shortest, because writing it forces both sides to admit what they assumed.
- Change control. How out-of-scope work gets priced, approved and recorded. In writing, before it starts, or it becomes a surprise line on an invoice.
- Reporting definitions. Which metric, from which source, over which date range. Broad terms like the work SEO actually covers mean different things to different suppliers, so the definitions belong in the document rather than in someone’s head.
| How it is usually written | What you can verify |
|---|---|
| Ongoing on-page optimisation | Nothing |
| Twelve named URLs optimised per quarter, listed in an appendix | The count and the list |
| Content strategy support | Nothing |
| One brief per month, each covering three target queries | The count and the briefs |
| Link acquisition activity | Nothing |
| Six placements on sites named before outreach begins | The count and the domains |
The blunt version
If your SOW lists activities rather than deliverables with counts, you have not bought outputs. You have bought hours, and you have no way of telling whether you received them. ‘Ongoing technical maintenance’ is satisfied by one person glancing at a dashboard for ten minutes, and it is equally satisfied by two days of genuine work. Both look identical from your side of the invoice.
Activity language is not sloppiness. It is margin protection, and it works beautifully. It lets a supplier scale the effort down to whatever the month’s capacity allows without ever breaching the agreement, because nothing in the agreement can be breached. Every agency knows this. Very few volunteer it while you are signing.
The test takes one minute. Hand the SOW to someone with no context and ask whether they could tell, from the document alone, if last month was delivered. If they cannot, neither can you, and neither can the supplier’s own account team.
Some real work genuinely resists counting: diagnosis, judgement calls, the hour spent talking you out of a bad idea. That work matters and it should be paid for. So name it as advisory time, state it in hours, cap it, and make everything else countable. A retainer that is mostly uncountable advisory is not a scope problem to be argued over later; it is a decision to be made now, which is also what counts as scope in a retainer.
Example
Say a manufacturer signs a twelve-month retainer whose SOW promises ‘technical SEO support, content optimisation and monthly reporting’. Six months later the site has had one audit, some meta descriptions rewritten and six reports. The client feels short-changed and cannot articulate why. The supplier feels unfairly attacked and is technically correct, because every listed activity happened at least once. Nobody breached anything. Rewrite the same scope as one audit in month one, twelve remediation tickets per quarter, eight optimised pages per month, and one report against a named metric set, and the identical disagreement becomes a two-column check anyone can run in an afternoon.
FAQ
Is a statement of work the same as a contract?
No. The contract covers payment, term, liability, confidentiality and how either side exits. The SOW covers what gets made and what done looks like. They are usually signed together and often bound into one PDF, which is why people conflate them, but the disputes that actually happen are almost always about the SOW.
Which section should I read first?
Exclusions. It tells you what the supplier already knows you will assume is included, and it is the fastest way to find the gaps between the pitch and the paperwork. If there is no exclusions section at all, write one yourself and ask them to sign it before the first invoice.
Can everything really be reduced to counts?
No, and pretending otherwise produces a different failure. Diagnosis and judgement resist counting, so name that portion as capped advisory hours and count everything else. The problem is not that uncountable work exists. The problem is a retainer where uncountable work is the whole document and nobody said so.
Related terms
- Soft 404 — the kind of fault that only ever gets fixed when a document says who owns it.
- Crawled – Currently Not Indexed — a finding that needs a named remediation deliverable, not a mention in a report.
- SEO — the umbrella term a scope document exists to break into countable parts.
If nobody outside the room could tell from your SOW whether last month was delivered, you are paying for effort and calling it work. Ask for counts before you sign, not after the third disappointing review.