Statement of Work
When To Use
The client has said yes. In three weeks someone on their side will paste the scope into a model, ask "what else should a good consultant cover?" and forward you the list. Run this now, so both of you have one document that says what is delivered, how anyone will know it is finished, who does what by when, and how a new idea gets handled.
When Not To Use
If the client has not picked an option, stay with the Consulting Proposal. If the scope is still disputed, settle it in MoSCoW Scope; this document records a scope, it does not decide one.
Inputs
- The accepted option, your phases, and the scope with its won't list
- The dates you can commit to, and what the client must supply (access, people, decisions, data)
- Your AI use statement, and any contract template either side already uses
If you have none of this, I start from the accepted option, leave each date and standard as a [placeholder] and mark it as a first draft.
Approach
The rule for the writing is taken from FAR 37.602 (acquisition.gov/far/37.602), which asks that work be set out as required results and measurable standards, not as hours or method. It is a public procurement rule borrowed here purely as a way of writing, with the usual practitioner sections around it. The failure it prevents is a deliverable such as "support the change programme", which can never be finished and can always be widened.
Workflow
- Ask, in one go: which option was accepted? Which dates are fixed on either side? Who at the client accepts deliverables?
- Objectives as results: what will be true when the work ends, in the client's measures. An activity is not an objective; "hold three workshops" becomes whatever the workshops are for.
- Deliverables, each with an acceptance criterion the client can check: form, content, rounds of review, the accepting role and the number of days they have. You set each standard; a deliverable with none is flagged.
- Timeline with your dates, and client responsibilities with theirs. The document says plainly that a late input from the client moves the dates that depend on it.
- Assumptions, then exclusions: the won't list is copied word for word from your scope, so nothing dropped earlier creeps back. Refer to your AI use statement for how AI is used.
- Change control: any new request is written down, sized, priced and approved in writing before work starts. That includes requests the client's own AI tools suggest, treated like any other, no better and no worse. Liability, IP, confidentiality and payment stay as [placeholders] marked "check with a qualified adviser". Draft in Claude Docs or as an exported document; you send it.
Output Format
# Statement of Work
Client: [organisation] · Consultant: [you] · Version: [n], [date]
## Objectives (results)
- [What will be true at the end, in the client's measure]
## Deliverables and acceptance
| Deliverable | Acceptance criterion | Review rounds | Accepted by (role) | Within |
|---|---|---|---|---|
| [deliverable] | [standard you set] | [n] | [role] | [days] |
## Timeline and responsibilities
| Date | Consultant delivers | Client provides | Owner (role) |
|---|---|---|---|
| [date] | [item] | [access / data / decision] | [role] |
## Assumptions and exclusions
- Assumption: [ ]
- Not included (won't list, word for word): [ ]
## Change control
[How a request is raised, sized, priced and approved in writing before any work on it starts]
## Terms
[Liability, IP, confidentiality and payment stay as placeholders; check with a qualified adviser]
## Decision
[Client signer role] and [you] approve version [n] by [date]; a qualified adviser reviews the terms before anyone signs.
Done When
- Every deliverable has an acceptance criterion and an accepting role
- The won't list appears word for word and the change route is written out
- Every date was supplied by you or the client, or is a [placeholder]
Quality Bar
- Written as results and standards, never hours; every deliverable can be finished
- The client's responsibilities are as specific and as dated as yours
- No legal wording is offered as advice; terms stay placeholders for an adviser
- Standards, dates and terms are yours and the client's; I invent none, contract points go to a qualified adviser, and you send the document.
Next
Run firm-proposal-red-team (Proposal Red Team Review) to have the whole draft read the way the buyer will read it.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: firm-statement-of-work3description: Writes a results-based statement of work, with objectives as results, deliverables each with an acceptance criterion and an accepting role, a dated timeline, client responsibilities, assumptions and the won't list word for word, and change control for any new request including ones the client's AI suggests, with contract terms left as placeholders. Use for "run firm-statement-of-work", "write the statement of work", "SOW for this engagement", "acceptance criteria for my deliverables", "stop scope creep before it starts", "change control wording", "scope document the client can sign", part of the Claude for Consultants · Team in Claude Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/firm-statement-of-work6---78# Statement of Work910## When To Use11The client has said yes. In three weeks someone on their side will paste the scope into a model, ask "what else should a good consultant cover?" and forward you the list. Run this now, so both of you have one document that says what is delivered, how anyone will know it is finished, who does what by when, and how a new idea gets handled.1213## When Not To Use14If the client has not picked an option, stay with the Consulting Proposal. If the scope is still disputed, settle it in MoSCoW Scope; this document records a scope, it does not decide one.1516## Inputs17- The accepted option, your phases, and the scope with its won't list18- The dates you can commit to, and what the client must supply (access, people, decisions, data)19- Your AI use statement, and any contract template either side already uses20If you have none of this, I start from the accepted option, leave each date and standard as a [placeholder] and mark it as a first draft.2122## Approach23The rule for the writing is taken from FAR 37.602 (acquisition.gov/far/37.602), which asks that work be set out as required results and measurable standards, not as hours or method. It is a public procurement rule borrowed here purely as a way of writing, with the usual practitioner sections around it. The failure it prevents is a deliverable such as "support the change programme", which can never be finished and can always be widened.2425## Workflow261. Ask, in one go: which option was accepted? Which dates are fixed on either side? Who at the client accepts deliverables?272. Objectives as results: what will be true when the work ends, in the client's measures. An activity is not an objective; "hold three workshops" becomes whatever the workshops are for.283. Deliverables, each with an acceptance criterion the client can check: form, content, rounds of review, the accepting role and the number of days they have. You set each standard; a deliverable with none is flagged.294. Timeline with your dates, and client responsibilities with theirs. The document says plainly that a late input from the client moves the dates that depend on it.305. Assumptions, then exclusions: the won't list is copied word for word from your scope, so nothing dropped earlier creeps back. Refer to your AI use statement for how AI is used.316. Change control: any new request is written down, sized, priced and approved in writing before work starts. That includes requests the client's own AI tools suggest, treated like any other, no better and no worse. Liability, IP, confidentiality and payment stay as [placeholders] marked "check with a qualified adviser". Draft in Claude Docs or as an exported document; you send it.3233## Output Format34```markdown35# Statement of Work36Client: [organisation] · Consultant: [you] · Version: [n], [date]37## Objectives (results)38- [What will be true at the end, in the client's measure]39## Deliverables and acceptance40| Deliverable | Acceptance criterion | Review rounds | Accepted by (role) | Within |41|---|---|---|---|---|42| [deliverable] | [standard you set] | [n] | [role] | [days] |43## Timeline and responsibilities44| Date | Consultant delivers | Client provides | Owner (role) |45|---|---|---|---|46| [date] | [item] | [access / data / decision] | [role] |47## Assumptions and exclusions48- Assumption: [ ]49- Not included (won't list, word for word): [ ]50## Change control51[How a request is raised, sized, priced and approved in writing before any work on it starts]52## Terms53[Liability, IP, confidentiality and payment stay as placeholders; check with a qualified adviser]54## Decision55[Client signer role] and [you] approve version [n] by [date]; a qualified adviser reviews the terms before anyone signs.56```5758## Done When59- Every deliverable has an acceptance criterion and an accepting role60- The won't list appears word for word and the change route is written out61- Every date was supplied by you or the client, or is a [placeholder]6263## Quality Bar64- Written as results and standards, never hours; every deliverable can be finished65- The client's responsibilities are as specific and as dated as yours66- No legal wording is offered as advice; terms stay placeholders for an adviser67- Standards, dates and terms are yours and the client's; I invent none, contract points go to a qualified adviser, and you send the document.6869## Next70Run firm-proposal-red-team (Proposal Red Team Review) to have the whole draft read the way the buyer will read it.7172## About the makers7374This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).