The Statement of Work is the operational backbone of a consulting engagement. The engagement letter is the legal frame; the SOW is the working contract for the specific scope, deliverables, and timeline. SOWs that are vague produce disputes; SOWs that are specific produce engagements that actually deliver what both parties expected.
This guide covers what belongs in a consulting SOW, how to phrase the trickier sections, and the structural patterns that work for fixed-fee, hourly, and hybrid engagements.
SOW vs. engagement letter — the working distinction
The engagement letter is the relationship-level agreement: parties, governing law, IP ownership, confidentiality, termination, dispute resolution. It applies across all work you do for the client.
The SOW is the engagement-level agreement: scope, deliverables, timeline, fee, payment schedule. It defines a specific engagement under the umbrella of the engagement letter.
For a client you're engaging with once, the two are often combined into a single document. For ongoing relationships with multiple engagements, the engagement letter is signed once and each new engagement gets its own SOW. The structure matters because it makes scope conversations clean: "this is in the SOW for engagement 3" is easier to enforce than "we discussed this in the master agreement."
Core SOW sections
Every consulting SOW should contain these sections:
Engagement title and reference number. Identifies the SOW for internal tracking. "SOW-2026-014 — Acme Corp Market Entry Analysis."
Engagement summary. One paragraph describing the purpose of the engagement. Not the activities — the purpose. "The purpose of this engagement is to deliver a board-ready recommendation on entering the European market."
Scope of services. The specific activities you'll perform. Bulleted, concrete, and bounded. Each bullet should pass the test: could two reasonable people agree on whether you did it?
Deliverables. The artifacts the client will receive. Each with a target date, a format, and a definition of "complete." A deliverable that doesn't specify what "done" looks like is a deliverable that gets re-litigated.
Out of scope. Explicit list of things that look like they might be in scope but aren't. This section is the most under-used in consulting SOWs and the one that prevents the most disputes.
Timeline. Start date, milestone dates, target end date. Phase the engagement if it's longer than 4–6 weeks.
Fee and payment terms. Total fee or hourly rate plus the payment schedule. Be specific about what triggers each payment.
Client responsibilities. What the client must do for the engagement to succeed. Provide data access, designate a point of contact, attend regular check-ins, approve deliverables within N business days. Most consulting engagements that slip slip because the client couldn't hold up their end — the SOW should make their responsibilities explicit so accountability is shared.
Change request process. How scope changes get added. Required reading for both parties. Usually: written request → impact estimate → written acceptance → addendum to SOW.
Acceptance criteria. What the client needs to do to formally accept each deliverable. This sounds like overhead until your first dispute about whether a deliverable was "done."
Writing the scope section
The scope section is where most SOWs go wrong. The trap is writing scope at the wrong level of abstraction — either too vague to enforce or too granular to keep current.
A working scope bullet looks like: "Conduct primary interviews with 8–12 executives at target companies in the European market, using a standardized interview guide developed in collaboration with the client. Interviews will be conducted over a 4-week period, with summaries documented and shared via the project portal."
That bullet specifies the activity (interviews), the volume (8–12), the population (executives at target companies), the standard (interview guide developed in collaboration), the timing (4 weeks), and the output (documented summaries shared via portal). A scope bullet at this level of specificity supports the deliverable. A bullet that just says "conduct interviews" doesn't.
The out-of-scope section that prevents disputes
Most scope disputes in consulting are not about what the SOW says — they're about things the SOW didn't say. The out-of-scope section is your tool for explicitly excluding the things that look adjacent but aren't included.
A good out-of-scope section has 4–8 bullets, each a specific thing that a reasonable client might assume is included. Examples:
- "Implementation of the recommendations is not included in this engagement."
- "Translation of materials into languages other than English is not included."
- "Travel to the European market for in-person interviews is not included; interviews will be conducted via video conference unless the client elects to fund travel separately."
- "Updates or revisions to deliverables after acceptance are not included."
The out-of-scope section feels mildly hostile when you write it. It feels essential when a dispute would otherwise be happening.
Acceptance criteria — the often-missed section
Every deliverable needs an answer to "how does the client formally accept this?" Without acceptance criteria, deliverables drift in a limbo state where the client thinks "we're still reviewing" and the consultant thinks "this is done." The misalignment compounds.
A working acceptance pattern: client reviews the deliverable within 5 business days of receipt → provides written acceptance OR provides written list of specific changes needed → consultant addresses changes within N days → final acceptance.
The N business days matters. Without a deadline, deliverable reviews can sit indefinitely. With one, the client either reviews or grants implicit acceptance.
Hybrid engagements
If the engagement has a fixed-fee component (the strategy work) and an hourly component (the follow-on implementation support), the SOW should structure them as two distinct phases with separate fee structures. Trying to bundle them into a single fee with vague phrasing about "and any follow-up support as needed" is the source of more consulting fee disputes than any other pattern.
Phase the work, fee each phase distinctly, define each phase's completion criteria. The client can elect to proceed with phase 2 or not — that's a clean conversation when the SOW is phased and an awkward one when it isn't.
Where the SOW lives after signing
Same answer as the engagement letter: with the rest of the engagement record. The SOW should be one click from the deliverables, the time entries, the invoices, and the messages. When everything lives together, "is this in scope?" is a fast lookup. When the SOW lives in someone's inbox, scope conversations are emails about emails.
Ready to manage SOWs, deliverables, and engagement records in one place? Start your free trial and see how ConsultBase keeps the entire engagement — including the SOW that defines it — connected.