What is a Statement of Work?
A Statement of Work, usually shortened to SoW, is the document that defines exactly what a consultancy will do for a client: the scope, the deliverables, the timeline, the people, the commercials and the way changes are handled.
It normally sits underneath a master services agreement. The MSA sets the legal relationship once; the SoW is written per engagement and describes this specific piece of work. Once both parties sign it, it is the reference point for whether the work has been delivered.
A good SoW does two jobs at the same time. It gives the client confidence that they know what they are buying, and it protects your margin by making the boundary of the work explicit before delivery begins.
SoW, proposal or contract?
These three documents are often confused, and the confusion causes real problems when a project goes sideways.
Proposal
Persuasive. Written to win the work. Frames the problem, your approach and why your firm.
Statement of Work
Operational and contractual. Written to govern the work. Scope, deliverables, dates, team, fees.
Master services agreement
Legal. Signed once. Liability, IP, confidentiality, termination, insurance.
The ten sections every SoW needs
Formats vary by firm and by client procurement rules, but a SoW that covers these ten sections will survive both a legal review and a difficult delivery.
- 01
Background and objectives
Two or three paragraphs on why the client is doing this work and what success looks like in their language. If a dispute ever arises, this is the section that reminds both parties what they were trying to achieve.
Generated in ConsultCloud as Overview and Objectives.
- 02
Scope of work
The specific activities you will carry out, written as verbs. Be concrete: 'run six stakeholder interviews' rather than 'engage stakeholders'. Vague scope is the single largest cause of margin erosion on consulting projects.
Generated in ConsultCloud as Scope of Work.
- 03
Out of scope
An explicit list of what you are not doing. Anything a reasonable client might assume is included but is not belongs here: data migration, training, third party licences, ongoing support.
Added from your template library as an Exclusions section, or held as reusable boilerplate.
- 04
Deliverables
Each deliverable named, described, and given a format and an acceptance criterion. 'Target operating model report, 30 to 40 pages, delivered as PDF, accepted on written sign off within five working days.'
Generated in ConsultCloud as Deliverables.
- 05
Timeline and milestones
Phases with start and end dates, milestone dates, and the dependencies that could move them. Tie payment milestones to deliverable acceptance rather than to calendar dates alone.
Generated in ConsultCloud as Timeline, built from your phases.
- 06
Team and resourcing
Named consultants where possible, their role, seniority and the days they are committing. Clients buy people as much as they buy method, and this section is where resourcing reality meets commercial promise.
Generated in ConsultCloud as Team & Resourcing, with roles, days and rates pulled from the live resource match.
- 07
Client responsibilities
What you need from the client and by when: access to systems, availability of stakeholders, sign off turnaround, workspace. Every one of these is a dependency you can point to if the plan slips.
Added from your template library, usually alongside Roles and responsibilities.
- 08
Commercials
Fee basis (fixed price, time and materials, or capped), day rates, total value, expenses policy, invoicing schedule and payment terms. State whether figures exclude VAT.
Rates and effort come from Team & Resourcing; fee basis and payment terms sit in the Commercials template section.
- 09
Change control
How a change to scope, timeline or fee is requested, assessed and approved, and who on each side can approve it. Without this clause, scope creep has no friction.
Held as standing boilerplate and inserted from your template library.
- 10
Assumptions, success criteria and sign off
The assumptions the estimate rests on, how completion will be judged, the governance rhythm (weekly checkpoint, monthly steering group), and a signature block for both parties.
Generated in ConsultCloud as Assumptions and Success Criteria; signature is handled by the built-in e-signature flow.
A worked structure
For a twelve week operating model review, the skeleton of the document would look like this. The first eight sections are the ones ConsultCloud drafts for you from the brief; the remainder are added from your template library so your standing terms stay identical across engagements.
Generated from the brief
1. Overview
2. Objectives
3. Scope of work
3.1 Phase 1: Discovery (weeks 1 to 3)
3.2 Phase 2: Design (weeks 4 to 9)
3.3 Phase 3: Roadmap and handover (weeks 10 to 12)
4. Assumptions
5. Deliverables
6. Timeline and milestones
7. Team and resourcing (roles, days, rates)
8. Success criteria
Added from your template library
9. Exclusions (out of scope)
10. Client responsibilities and dependencies
11. Commercials
11.1 Fees and rate basis
11.2 Expenses
11.3 Invoicing schedule and payment terms
12. Change control procedure
13. Terms and boilerplate
14. Sign offKeep the numbering stable across engagements. Clients who work with you repeatedly learn where to find things, and your own delivery leads stop missing sections.
How ConsultCloud maps to this
Eight sections are written for you from the brief. The rest are standing content you configure once and reuse.
- Background and objectives
- Overview, Objectives (generated)
- Scope of work
- Scope of Work (generated)
- Assumptions
- Assumptions (generated)
- Deliverables
- Deliverables (generated)
- Timeline and milestones
- Timeline (generated from phases)
- Team and roles
- Team & Resourcing (generated from the resource match)
- Acceptance criteria
- Success Criteria (generated)
- Out of scope
- Exclusions (template library)
- Client responsibilities
- Roles and responsibilities (template library)
- Commercials
- Rates and days from resourcing, fee basis from the template
- Change control
- Standing boilerplate (template library)
- Sign off
- Built-in e-signature flow
More detail on Statement of Work software and SoW and proposal templates.
Common mistakes
- Describing effort instead of outcomes, so acceptance becomes a matter of opinion.
- Leaving the out of scope section blank because it feels negative to the client.
- Committing named consultants before checking their actual availability.
- Copying a previous SoW without revisiting assumptions, rates or dates.
- Omitting change control, then absorbing the cost of every extra request.
- Writing a 40 page document when a focused 8 page one would be signed faster.
Frequently asked questions
- What is a Statement of Work?
- A Statement of Work (SoW) is a document that defines the scope, deliverables, timeline, team, commercials and governance for a piece of work. It sits under a master services agreement and turns a commercial agreement into a specific, accountable plan.
- What is the difference between a SoW and a proposal?
- A proposal is a persuasive document written to win the work. A Statement of Work is a contractual document written to govern the work once it has been won. The proposal argues why you; the SoW records exactly what, when, by whom and for how much.
- Is a Statement of Work legally binding?
- A SoW is normally binding once both parties sign it, either on its own or as a schedule to a master services agreement. Because it is binding, the scope, out of scope and change control sections carry real commercial weight.
- How long should a Statement of Work be?
- Long enough to remove ambiguity and no longer. Most consulting SoWs land between six and fifteen pages. Clarity in the scope and deliverables sections matters far more than total length.
- Who writes the Statement of Work?
- Usually the consultancy drafts it, based on the agreed brief and proposal, then the client reviews it with their procurement or legal team. Drafting it yourself means the scope and assumptions are framed in your terms.
Generate the SoW instead of writing it
ConsultCloud turns a client conversation into a structured brief, a client-ready proposal and a complete Statement of Work, then matches available consultants to the roles in it. See Statement of Work software or SoW and proposal templates.