Consulting Statement of Work Template: Scope, Evidence and Acceptance Criteria
A consulting statement of work fails when it describes activity but leaves the decision undefined. “Assess the operating model and provide recommendations” sounds professional, yet it does not say which questions will be answered, what evidence will be reviewed, what the client will receive or how completion will be accepted.
This practical template turns a consulting assignment into a controlled decision system. It is suitable for strategy, operations, finance, technology, compliance and organisational-change engagements. It is not legal advice; contract terms should be reviewed by qualified counsel in the relevant jurisdiction.
Start with the decision, not the deliverable
Before writing scope, complete this sentence:
At the end of the engagement, [named decision owner] must be able to decide [specific decision] using [required evidence], within [constraints], by [date].
If the sentence cannot be completed, the project is not ready for pricing. A deck, workshop or report is a delivery format, not the business outcome.
The SCOPE-8 statement-of-work structure
| Section | Question it must answer | Example evidence |
|---|---|---|
| S — Situation and decision | Why does the work exist and who decides? | Approved decision statement |
| C — Coverage and exclusions | What is inside and outside scope? | Process, entity, geography and system boundaries |
| O — Outputs | What will be delivered in usable form? | Report, model, register, workshop and handover files |
| P — Proof and method | Which sources and methods support the output? | Source inventory, interview plan, calculation rules |
| E — Evaluation and acceptance | How will the client know each output is complete? | Acceptance tests and reviewer |
| 8 — Eight controls | Owners, inputs, dependencies, changes, risks, confidentiality, fees and closure | Signed control schedule |
Copyable statement-of-work template
1. Engagement purpose
Business situation: [two to four sentences]
Decision to support: [one decision]
Decision owner: [role, not only a person]
Decision deadline: [date]
Success condition: [observable outcome]
2. Scope boundary
Included:
- business units, entities and geographies;
- processes, products or systems;
- time period and data cut-off;
- stakeholder groups; and
- decisions and deliverables.
Excluded:
- legal, tax, audit or certification opinions unless explicitly contracted;
- implementation work outside listed work packages;
- data sources unavailable by the input deadline; and
- decisions retained by management.
3. Work packages
| Work package | Activities | Client inputs | Output | Owner | Due date |
|---|---|---|---|---|---|
| WP1 Diagnose | Review evidence and confirm baseline | Data pack, policies, interviews | Baseline findings register | Consultant lead | [date] |
| WP2 Design | Develop options and trade-offs | Decision criteria | Options paper and model | Joint team | [date] |
| WP3 Decide | Facilitate decision and record rationale | Executive availability | Decision memo | Decision owner | [date] |
| WP4 Handover | Transfer tools, owners and review cadence | Named operational owners | Handover pack | Client owner | [date] |
4. Evidence and method
List the evidence universe, selection rules, interview roles, analytical methods, assumptions and limitations. Separate verified facts from management representations and consultant judgments. If AI tools are used, define what information may enter them and who verifies the output.
5. Deliverables and acceptance tests
| Deliverable | Format | Acceptance test | Reviewer | Review window |
|---|---|---|---|---|
| Findings register | Spreadsheet | Every finding links to source, impact and owner | Project sponsor | 5 business days |
| Options model | Editable workbook | Inputs visible; scenarios reconcile; no formula errors | Finance owner | 5 business days |
| Decision memo | Document/PDF | Options, recommendation, risks and dissent recorded | Decision owner | 3 business days |
| Handover pack | Native files + session | Owners can operate the tool without consultant access | Operational owner | 5 business days |
Acceptance should test fitness for the contracted purpose, not whether the client agrees with every finding.
6. Responsibilities and dependencies
State who provides data, schedules interviews, approves assumptions, resolves access problems, reviews deliverables and makes the final decision. A dependency has a due date and an owner. If a late input changes schedule or quality, state the consequence in advance.
7. Change control
A change request should record:
- requested change and reason;
- effect on scope, method, timing, fees and risk;
- options, including no change;
- approving roles; and
- revised baseline and effective date.
Do not let a meeting comment silently become new scope.
8. Commercial and closure controls
Specify fee basis, invoicing milestones, approved expenses, taxes, confidentiality, intellectual-property treatment, data retention, conflict rules, termination, transition assistance and the documents that survive closure. Legal counsel should adapt these terms.
A simple acceptance formula
For each deliverable, calculate:
Acceptance readiness = completed tests / applicable tests
If a model has eight applicable tests and seven pass, readiness is 87.5%. That does not automatically mean rejection. It makes the open test visible so the designated reviewer can accept with condition, request correction or change the requirement.
Worked example: compliance operating-model review
Weak scope: “Review compliance and recommend improvements.”
Decision-ready scope: “By 30 September, the Chief Compliance Officer will decide which three control gaps enter the funded 2027 remediation plan. The consultant will review the approved policy set, 12 months of issue data and interviews with 10 control owners; produce a traceable findings register, costed options and a decision memo; and exclude legal opinions and implementation.”
The second version can be estimated, governed and accepted because its decision, evidence, boundaries and outputs are visible.
Five common failure modes
- Activity scope: hours and workshops are listed, but the decision is absent.
- Invisible exclusions: both parties assume different boundaries.
- Unverifiable findings: recommendations do not link to evidence.
- Approval ambiguity: many stakeholders comment, but no one accepts.
- Scope drift: new work enters through meetings without a change record.
U.S. Federal Acquisition Regulation guidance for performance work statements emphasises describing required results, measurable performance standards and assessment methods. Private consulting engagements differ from public procurement, but the operating principle is useful: define the outcome and the evidence of acceptable performance rather than prescribing every hour of work.
MTF's Executive Decision Log Template helps preserve rationale after the engagement. The Change Impact Assessment Template helps evaluate implementation consequences once a recommendation is approved.
Practical conclusion
A strong statement of work is a small governance system. It aligns the decision, evidence, outputs, acceptance and change control before pressure exposes ambiguity. Copy the template, replace every bracketed field and ask a person uninvolved in drafting to identify what remains open.