A consulting statement of work template, filled in.

A consulting statement of work template is a reusable two-page document naming the work you'll hand over, what it costs, when it's due, and whose written yes counts as approval. Filled in, it also prices the work you're not doing, sets the payment schedule, and states the rule for what happens when the client moves the work. The whole thing is printed further down this page with the numbers already filled in for an $18,500 engagement, because the three sections that decide whether extra work gets paid for are the priced exclusions, the acceptance rule and the change-control paragraph, and almost every template online leaves all three as empty brackets. Copy it, swap the names and dates, and keep the figures as a starting point for a project somewhere in the fifteen to twenty-five thousand dollar range.

Most writing on this subject is aimed at enterprise procurement teams or at corporate consultants selling into legal departments, which is a different job from the one you have. You're two people, or six, quoting a messaging project or a website rebuild, and what you need is the exact sentence that stops a client assuming a fourth round of revisions is free. So the numbers here are real, and the awkward paragraphs are written out rather than described.

What goes into a consulting statement of work template?

Eleven sections, and four of them do nearly all the work once a project gets difficult. The other seven go faster: the purpose, the deliverables, the assumptions you priced against, the dates and their milestones, the fee and payment schedule, the ownership terms, and the paragraph on ending early. Those are worth writing carefully once and then leaving alone, because none of them is what gets argued about later.

The deliverables are the part almost everyone writes badly, even though they're easy to fix. Compare "a refreshed brand message and updated website copy" against "one message platform document containing a positioning statement, three audience-specific value propositions and a proof-point library of twelve items, plus rewritten copy for six named pages". The first is an adjective wearing a suit. The second is something you can point at in week seven and count, which is the only property that matters when somebody disagrees with you.

Then there are the four sections that earn their keep. The priced exclusions name what you're not doing and what it would cost to add. The acceptance rule says what counts as finished and how long the client has to object. The change-control paragraph sets out how new requests get priced and approved. And the named approver line puts one person, by name and email address, in charge of saying yes. Those four are the difference between a document that describes a project and a document that survives one, so the rest of this page is mostly about them.

What does the finished statement of work look like?

Here's the whole thing, ready to copy into a document or the body of an email. Anything in square brackets is specific to your project and gets replaced. Every dollar figure, hour count and review window is filled in as a working default, so you can send this as it stands and adjust the numbers once you've seen how they land with a client.

Two things about it are worth noticing before you start editing. Much of the total length sits in sections 3, 6, 8 and 9, which is deliberate, because those are the sections a client reads once and you read every time something changes. The numbering isn't decoration either, because writing "that's covered by 3.2" in a reply is faster and far less confrontational than restating the argument from scratch, and a client who can find 3.2 in ten seconds stops pushing on it.

If the split between the description of the work and the agreement around it feels blurry, that's because it genuinely is on small projects. We wrote up scope of work vs statement of work separately for anyone whose client has asked for one specifically and meant the other. And if you only need the work half of it (the deliverables, exclusions, assumptions and acceptance rule, without the fee, the ownership transfer and the exit terms wrapped around them), a project scope template is that document on its own, filled in for a $32,000 build.

How do you write exclusions the client accepts?

Name something a reasonable client would assume is included, say it isn't, and put a price on it. Compare "revisions beyond two rounds are not included" against "a third and any later round of revisions is billed at $175 per hour, quoted and approved in writing before we start". Same boundary, completely different conversation in week six.

Pick the exclusions by looking at your last three projects and writing down what you absorbed for free. The same four items come up again and again: extra revision rounds, additional pages beyond the count you quoted, work touching a third-party tool nobody scoped, and anything continuing after handover. Five or six lines written this way out-earn every other paragraph in the document, and they cost you an hour once.

The prices should be slightly uncomfortable rather than punitive. An extra page at $650 when your blended day rate is around $1,100 is defensible on the phone and still profitable, whereas $200 invites the client to keep asking and $2,000 makes the whole section look like a trap. If a client pushes back on one of these numbers in the signing conversation, that's the cheapest possible moment to have the argument. A statement of work that skips the section moves that same argument to week six, where it costs you the work instead of the sale.

A bare exclusion reads as a refusal. A priced exclusion reads as a menu.

Section 3.1 comes with a warning, because excluding something without a price only works when the excluded item is genuinely a separate project you'd quote properly later. Don't use that form for small items, since "we can quote that separately" said about a two-hour job just means an awkward email and a discount. Anything under about half a day gets a number in the document or it gets absorbed.

What does the change-control paragraph need to say?

Four things: who can propose a change, how fast you'll respond with a price, who has to accept it, and the fact that nothing gets built or invoiced without that acceptance. Section 9 above says all four in five sentences, and the sentence that does the most work is the last one. Committing yourself to not invoicing unapproved work is what makes a client comfortable signing a paragraph that otherwise reads as a way to charge them more.

The response time is the part agencies leave out and then regret. A client told they'll have a price within two business days will wait for it, while a client told nothing chases you on Slack and starts negotiating in the same thread. Two business days is realistic for most consultancies, whereas promising same-day sounds impressive and then breaks the first time a request lands on a Friday afternoon.

The approver line in section 8 is the piece that fails most often in practice, and it fails organizationally rather than legally. A marketing coordinator waves through a $650 addition because they don't know it costs anything, and their director says nobody authorized it six weeks later, and both of them are describing the situation honestly as they understand it. Naming one person in the document and then actually holding the line closes most of that gap. It's the same idea behind walking the client through change orders at kickoff, which is deciding who owns a decision before anyone needs to make one.

When do you send a statement of work, and what comes before it?

You write it rather than the client, which surprises people coming from corporate work where procurement issues the document. Send it once the client has said yes in principle and before you've done any billable work, which is usually the same week the proposal gets a positive answer. The proposal exists to win the engagement, so it's allowed to be persuasive and a little loose. The statement of work exists to run the engagement, so it has to be specific, and trying to make one document do both jobs produces something that's vague where it needs to be exact.

The sequence that works is a proposal, then a conversation about the number, then the statement of work, then a deposit, then a kickoff call, and only then any actual work. It's worth settling which document governs when the proposal and the contract disagree before you reach the third step. Skipping from a verbal yes straight to a first draft is how consultants end up three weeks in with nothing signed, at which point asking for a signature feels like an accusation. Send it while the client is still enthusiastic and it reads as ordinary paperwork.

Repeat clients deserve a shorter version of that sequence. Once you're running three or more projects a year for the same company, put the standing terms in a master agreement they sign once, and let each new project get a statement of work underneath it covering only sections 2, 3, 5, 7 and 9.

Is a consulting statement of work legally binding?

Sometimes, and the two most widely read pages on this topic state it as a flat yes, which isn't a safe thing to rely on. A statement of work carrying a fee, terms and signatures from both sides can function as the whole agreement on a single small project. The same document sent as an unsigned attachment to a proposal generally can't. Larger clients tend to want it sitting underneath a master services agreement that handles liability, confidentiality and disputes, and in that arrangement the statement of work governs the project while the master agreement governs the relationship.

None of that is legal advice, and the answer varies by state and by country. Have a lawyer read your template once, then reuse it for years. The version above is the shape consultants and agencies actually use rather than a substitute for that review.

What matters more day to day is a smaller question: when a disagreement happens, who can show what was agreed? Most scope disputes never go near a lawyer, and they end in a tense call where one side has numbered sections and a written approval while the other has a memory of a conversation. Being the side with the record settles it, and an approval trail that holds up matters more in that moment than the enforceability of the original paperwork.

What happens when the client asks for something on day 38?

You check the request against sections 2 and 3, and most of the time section 3 has already priced it for you. That's the return on the hour you spent writing exclusions, and it shows up as a reply that takes four minutes instead of a negotiation that takes four days.

Take a real shape of request. On day 38 of the eight-week engagement above, the client emails asking for a competitor comparison page, and separately wants another pass on the product page copy after they've already used both included rounds. Neither item is in section 2. But 3.2 prices an extra page at $650, and 3.3 prices further revision rounds at $175 an hour, and you estimate three hours for the product page pass. So the reply is $650 plus $525, which is $1,175, and it moves final delivery back three business days because it lands during the copy phase.

What makes that email easy to write is that you're reading numbers back to the client that they signed off in week zero, which is why the tone stays administrative rather than defensive. The approver named in section 8 replies yes, you record the acceptance, and the change is done. Handled without an exclusions section, that same request becomes a twenty-minute internal debate about whether to charge, followed by absorbing it, which is how the real cost of scope creep accumulates without ever appearing on an invoice.

For the requests section 3 doesn't cover, you need a short written record of the new work, its price, its effect on the date and the approval, which is what a change request form template gives you to copy rather than rebuild every time.

What should you fix in the last statement of work you sent?

Open it and change four things, which is about an hour of work on a template you'll reuse for years. Rewrite the deliverables as countable nouns with numbers attached, so every line can be checked instead of argued about. Add five or six exclusions written as priced options, chosen from what you actually absorbed on your last three projects. Put one person's name and email address in as the approver. Then paste in a change-control paragraph that commits you to a response time as well as committing the client to written acceptance.

Number the sections while you're in there, because a numbered clause is something both sides can point at and an unnumbered wall of prose is something both sides can reinterpret. Every reply you send about scope for the rest of the project gets shorter as a result.

The gap between an agency that absorbs scope changes and one that gets paid for them is rarely the quality of the drafting. It's whether the scope was specific enough to check against, and whether the change conversation was made easy enough that somebody actually has it. The document above handles the first half, and our pricing starts with a free plan for the second.

Frequently asked questions