What is a statement of work? The four sections that matter.

A statement of work is a signed document covering one project: the work being delivered, the work excluded from it, the dates, the fee and the schedule the invoices follow. Agencies and clients shorten it to SOW, and it normally sits underneath a contract or master agreement that handles the relationship while the statement of work handles this particular job. The published contents lists run from eleven sections to fourteen depending on who wrote them, and that list is where most of the confusion starts.

Four of those sections carry the commercial weight and the remaining ten are context you write once and rarely reread. Sorting them takes about a minute if you know which question to ask, and the rest of this page works the sorting through against a real $28,350 project so the difference shows up in dollars rather than in the abstract.

What is a statement of work?

A statement of work is the project-level agreement that names the work, the timeline and the money in enough detail that neither side has to interpret anything later. It's the document a client signs to say yes to a specific job at a specific price, as opposed to the paperwork that governs how the two companies deal with each other in general. That distinction is the cleanest way to hold the whole family of documents in your head: the contract or master agreement covers every project you'll ever do together, and the statement of work covers this one.

Naming what it isn't does about as much work as the definition. An estimate is a number attached to work nobody has described closely enough to price properly, and a proposal argues for an approach while the client is still choosing between agencies, so neither one commits anybody to anything specific. The scope of work is closer, and it's the section inside a statement of work that describes the work itself. Plenty of small agencies write one document and call it either name, which is fine as long as the money sections are genuinely present, and where those two documents actually diverge is written up on its own page.

Read far enough and you'll meet four official types of statement of work, which are design, performance-based, level of effort and fixed price. Only the distinction underneath them matters to an agency: either you're selling a defined outcome for a fixed fee, or you're selling hours against a rate card, and which one you picked changes what the acceptance and change sections have to say.

Is a statement of work the same as a contract?

Not usually, though it can be. In most agency engagements the statement of work is one document inside a contract rather than a substitute for it, so the contract carries liability caps, intellectual property, confidentiality and termination, while the statement of work carries the deliverables, the dates and the fee. On a genuinely one-off project you can fold the commercial terms into the statement of work and have both sides sign that single document, and many agencies work that way for years without trouble.

The pairing only causes problems when the two documents disagree, which happens more often than anyone expects because they're usually drafted months apart by different people. One clause fixes it, and it belongs in the statement of work rather than the contract: a sentence naming which document wins when they conflict. How the two documents connect covers that wording in full, and the same question in its master-agreement form is answered in the MSA and SOW split.

Most of the sections in a statement of work describe the project, and four of them decide who pays for the next request.

What should be included in a statement of work?

The four sections that decide money are the deliverables counted rather than described, the exclusions with a price against each one, the acceptance test that says when a piece of work is finished, and the change path naming who can approve extra work and what happens before it starts. Everything else on the longest of those lists is real and worth writing, but project background, objectives, constraints, quality control procedures and success criteria have never once settled an argument about an invoice.

The test for sorting the rest is simple enough to run on your own template this afternoon. Ask whether a sentence would be quoted back at somebody during a disagreement about money. Six tracking screens gets quoted back and a tracking experience doesn't, because only one of those is countable. A price of $1,800 for copywriting you excluded gets quoted back, while a paragraph about the client's brand ambitions never does. The sections that survive that test are the ones to spend your editing time on, and the section by section version of the job shows the vague line most agencies write next to the rewritten line that holds.

Exclusions are where the money actually sits, and they're the section most templates leave as a bare list of refusals. Written properly each one names something a reasonable client would assume was included, excludes it, and prices it, which converts an awkward conversation in week five into an ordinary purchasing decision in week zero. The reasoning behind where that boundary gets drawn is worth reading before you rewrite yours.

The exclusion agencies forget most often is their own time in the room. If the fee covers two on-site workshops, say so, and say what a third one costs including travel, because a client who assumes visits are unlimited will keep asking for them and you'll be arguing about expenses by month two.

What does a statement of work look like with the numbers in it?

It looks like a price list with dates attached, which is easier to see on a real project than in the abstract. Fennimore Grain Co. is a farmer-owned cooperative that publishes an annual report for its members every autumn, and the statement of work below covers ten weeks of design and production work for a total fee of $28,350.

Two lines in that block are doing more work than they look like they are. The exclusion carries its own rate, so the document already contains the price of the most likely thing a co-op will ask for halfway through, and nobody has to invent a number under pressure. The named approver means one person's written yes counts as the cooperative's decision, which matters at an organization where nine board members all feel entitled to an opinion on the cover.

The payment schedule is tied to events rather than to calendar dates, and that's deliberate. Design approval is something the client controls, so an invoice triggered by it stays honest when they take three weeks over the first round, where fixed dates would have you billing for a milestone that hasn't happened.

What happens when the client asks for more in week seven?

The document answers it, which is the entire reason for writing one. In week seven Dana asked for a Spanish-language edition of the report for the cooperative's Spanish-speaking members, a request that had never appeared in any conversation and sat well outside the four deliverable lines. Nobody had to negotiate a price for it, because the rates were already on the page.

The quote went back the same afternoon, and writing it was arithmetic rather than judgment: 64 pages of re-flow at the excluded rate of $65 a page comes to $4,160, the second press check is $580, so the change is $4,740 and two extra weeks on the delivery date. That's just under seventeen percent of the original fee, arriving as a priced change rather than as unbilled work absorbed into an already tight schedule. The reflex answer of saying yes and squeezing it in would have cost the agency the same $4,740, just silently, and what that pattern costs across a year is a number most agencies have never sat down and worked out.

Two paragraphs in the original document made that possible, and they're worth having in your own template close to word for word.

The change paragraph binds the agency as tightly as it binds the client, and that's why clients sign it without pushing back. The acceptance paragraph matters for a different reason: it puts an end to the project. Without a defined finish a print job can stay open for months while somebody keeps spotting a comma, and the final invoice sits unsent the whole time.

Who issues a statement of work, and who signs it?

It depends entirely on which side of the deal you're on, and most published advice quietly assumes the wrong one. In corporate procurement and government contracting the buyer issues the statement of work and suppliers respond to it, which is where the document originally comes from and why so many definitions describe receiving one. In agency and consulting work it goes the other way, because the agency is the side that knows how the work breaks down and what a realistic count of pages, screens or rounds looks like.

Both parties sign, and the signature that matters is the client's named approver rather than whoever happens to reply first. A single line naming that person by name and email address closes most of the gap, since it stops a marketing coordinator waving through a $4,000 change on a Tuesday that the finance director later says nobody authorized. Settling that at kickoff is easier than raising it in week seven, and the two-minute version of that conversation makes every later change order feel routine.

When is a project too small to need one?

When the whole fee arrives in a single payment. That's a more useful line than any dollar threshold, because a statement of work exists to sequence money against work, and a project with one invoice has nothing to sequence. A logo refresh billed once on delivery is covered perfectly well by an email naming the deliverable, the rounds included and the price of another round.

The moment the fee splits across two or more invoices, write one. Every stage now needs a trigger, every trigger needs a definition of done, and both of those live in the statement of work or they live nowhere. The same applies when the work runs past a single month, since anything longer than that will collect requests that nobody remembers agreeing to, whatever the fee happens to be.

A statement of work earns its keep in week seven, not week one

The sentence that saved the Fennimore project money was an exclusion nobody expected to use: "re-flowing the approved layout into supplied translated copy is $65 a page". It was written weeks before anyone had mentioned a Spanish edition, and it meant the request could be answered in one email with a number both sides had already agreed to, rather than with a figure the agency had to defend on the spot. A statement of work that reads well and prices nothing will feel fine for six weeks and then leave you improvising a figure in front of a client who has already decided what it should cost.

So when you next open your own template, the four sections to work on are the deliverable counts, the priced exclusions, the acceptance test and the change paragraph. A consulting statement of work with the numbers already filled in shows all four in place on the page, and the same four appear inside a project scope filled in as a sample if you'd rather see them in a build context than a consulting one.

Frequently asked questions