Consulting Statement of Work Template + Example | NMS

Consulting SOW template to copy

Replace the bracketed fields, agree the acceptance checks with
the reviewer and give every dependency an owner. Use this for a
defined consulting project. If the work is still uncertain, scope
a discovery phase first and use its findings to plan the next
phase.

You can select and copy the text below. The copy button also
appears if your browser supports it.

CONSULTING STATEMENT OF WORK

1. PROJECT AND PARTIES
Project: [Name]
Client and consulting provider: [Legal names]
Sponsor and delivery lead: [Names and roles]
SOW version and date: [Version/date]
Governing agreement, if applicable: [Reference]

2. OBJECTIVE
Business problem: [Specific problem]
Decision or outcome the work supports: [Result]
Success measures: [Baseline, target and measurement period]

3. INCLUDED WORK
Business units and locations: [Included areas]
Processes, systems and data period: [Coverage]
Activities and quantities: [Interviews, workshops, analysis]

4. EXCLUSIONS
Work outside this engagement: [Explicit exclusions]
Potential later phases: [Separate approval required]

5. DELIVERABLES AND ACCEPTANCE
For each deliverable record:
[ID and name]
[Required contents and file format]
[Due date and named reviewer]
[Acceptance checks and supporting evidence]
[Review period, correction process and approval record]

6. SCHEDULE AND DEPENDENCIES
Start and completion dates: [Dates]
Milestones: [Deliverable/date/owner]
Client inputs: [Input/owner/due date]
Effect of missing inputs: [Assessment and escalation process]

7. TEAM AND RESPONSIBILITIES
Consulting team and availability: [Roles/commitments]
Client team and availability: [Roles/commitments]
Decision authority: [Who can approve what]
Replacement or escalation arrangements: [Process]

8. FEES AND PAYMENT
Fee model and currency: [Fixed fee/time/retainer]
Fees or rates and budget cap: [Amounts]
Invoice triggers and payment terms: [Agreed terms]
Expenses and taxes: [Treatment and approval]
Additional work: [Approval and pricing process]

9. PERFORMANCE MEASURES
For each KPI record:
[Name/formula/data source/baseline/target]
[Measurement period/review frequency/business owner]
Dependencies affecting results: [Client or external factors]

10. GOVERNANCE AND CHANGE CONTROL
Project review: [Frequency/attendees/decisions]
Decision, issue and risk log owner: [Name]
Change request: [Reason/scope/fee/schedule impact]
Required written approvals: [Authorized parties]

11. INFORMATION AND WORK PRODUCT
Approved data, access and tools: [Requirements]
Confidentiality and security: [Agreement references]
Ownership and permitted use: [Agreement references]
Data return, retention or deletion: [Requirements]

12. HANDOVER AND CLOSE
Final files and documentation: [List]
Training and knowledge transfer: [Sessions/recipients]
Open items and ongoing owners: [Register]
Pause, exit and termination arrangements: [Agreement references]
Final acceptance and authorized approvals: [Names/dates]

Stanford’s procurement resource also identifies objectives,
schedules, budgets, deliverables and closure checks as SOW
components.

Read Stanford’s SOW resource
.

Filled example: a six week billing process review

A company wants to understand why invoices are issued late and
decide which changes to implement. The engagement covers
diagnosis and planning. Implementation requires a separate scope
and approval.

Illustrative example: the project, quantities, schedule and
pricing below are fictional planning assumptions. They do not
describe an NMS Consulting client engagement or fee quote.

The SOW should make the final decision clear: which billing
process changes should the company fund and who will implement
them? A report that describes delays without supporting that
decision would leave the engagement incomplete.

How to write deliverables and acceptance criteria

Describe a deliverable as an output that someone can inspect.
An interview is an activity. An agreed process map is a
deliverable. Faster invoice issue is a business outcome. Each
needs a different way to track completion.

Use this acceptance pattern: required contents, evidence or
test, reviewer and review deadline. Replace phrases such as
“high quality report” with observable checks.

For this example, allow five business days for a consolidated
review. Record any failed checks, agree a correction date and
document approval. Final delivery must leave time for that
review if acceptance is due by the end of week six.

Separate defects from new requests. A missing agreed analysis
needs correction. A request to add a third business unit needs
a scope change decision.

A related principle appears in US federal procurement: FAR
37.602 calls for describing required results and assessing work
against measurable standards. That rule governs its own
procurement setting; the acceptance examples here are suggested
practices for a commercial consulting project.

Read FAR 37.602
.

Connect consulting fees to a clear scope

State the currency, fee model, included work, expenses, taxes,
invoice triggers and approval process for extra work. A price
is difficult to compare if one proposal includes implementation
and another ends with recommendations.

In the fictional example, the fixed fee is $48,000: $12,000
after acceptance of the baseline, $24,000 after acceptance of
the cause analysis and $12,000 after final handover acceptance.
Approved expenses and applicable taxes would be addressed
separately. These amounts illustrate milestone arithmetic.

For more detail on commercial structures, see

consulting fees and pricing
.
If you are still comparing providers, use the

consulting RFP scorecard

before finalizing the SOW.

Manage scope changes and client delays

A change request should record what is changing, why it is
needed and its effect on deliverables, price, staffing and
completion dates. Name the people authorized to approve it.

1. Log the request and identify the affected SOW items.
2. Assess the effect on fees, timing, data needs and acceptance
   checks.
3. Agree if the work will be added, substituted, deferred or
   declined.
4. Record the required written approvals before the changed
   work starts.
5. Update the SOW version, schedule and budget forecast.

If the client requests a third business unit, document the
additional data review, interviews and process mapping. Do not
assume that the original fee covers the extra work.

If source data arrives late, record the missing input and the
affected activities. Assess if other work can proceed, then
agree any schedule or fee adjustment using the contract’s
change process. A dependency delay should not silently become
an unexplained missed milestone.

Choose KPIs that answer a project question

Use delivery measures to manage the engagement and business
measures to track the result after changes are implemented.
Record the formula, data source, baseline period, target,
review date and business owner for each KPI.

Set the baseline before choosing a target. A diagnosis project
can deliver an accepted improvement plan without guaranteeing
a later operating result that depends on client implementation.

A weekly review that produces decisions

Review upcoming deliverables, failed acceptance checks, missing
client inputs, open decisions and the latest fee forecast.
End with an action, owner and due date for each issue. The
sponsor handles decisions beyond the delivery team’s authority.

For the roles and approval paths behind that review, see

operating model design and decision rights
.

Handover and exit checklist

Define the handover at the start of the project so the client
can use the work after the engagement ends. Check the following
before final acceptance:

• Each deliverable has a recorded approval or an agreed open
  item.
• The client has the agreed editable files and can locate the
  supporting evidence.
• Calculations, assumptions, data definitions and limitations
  are documented.
• The ongoing owner can perform the agreed maintenance or
  refresh task.
• Open actions have owners, due dates and escalation routes.
• Access removal and data return, retention or deletion follow
  the agreement.
• Any further support has an agreed scope, price and end date.

If the project pauses or ends early, follow the agreed notice,
payment and work product arrangements. Record completed work,
remaining commitments and who takes over unresolved issues.
A review meeting by itself does not create a right to terminate
an agreement.

The UK Cabinet Office’s Consultancy Playbook treats knowledge
and skills transfer as part of getting value from consulting
engagements. A practical application here is to test if the
receiving team can use the delivered files.

Read the Consultancy Playbook
.

Common questions about consulting SOWs

Sources and use of examples

The template and worked example provide suggested drafting
choices. They are not reproduced from a client contract.
The following primary sources support the specific principles
cited above.

1. 
   Stanford University: Statement of Work
   .
   SOW components and completion checks.
2. 
   Acquisition.gov: FAR 37.602
   .
   Required results and measurable standards in US federal
   performance work statements.
3. 
   UK Cabinet Office: The Consultancy Playbook
   .
   Commissioning consulting work and transferring knowledge.