What is a Statement of Work (SOW)? Definition and Examples

What Is a Statement of Work (SOW)? Definition and Examples
Published On:
November 2, 2026
Go deeper
Download our professional services ‘cheat sheet’ now

What is a statement of work? A plain definition, the sections every SOW needs, and three annotated examples from consulting, engineering and IT projects.

For a consulting firm, the statement of work is what the delivery team gets held to and what finance invoices from. When a client asks whether an extra workshop is included, or finance needs to know whether a milestone can be billed, a good SOW answers the question without anyone going back to the proposal.

Key Takeaways

  • A statement of work defines what a consulting firm will deliver on an engagement and when it can bill for that work.
  • The change process in a statement of work decides whether a new client request counts as extra, billable work.
  • Contract value erosion averages 8.6%, and scope disputes are among the causes.
  • A performance-based statement of work describes the results a client needs rather than the hours or methods.
  • A consulting proposal persuades a client to buy, and the statement of work records what the client bought.

What is a statement of work?

A statement of work (SOW) is a signed document that sets out the work a firm will do on one engagement. It covers the deliverables and how each is accepted, the timeline, who does the work, and the price and payment terms.

Most consulting firms sign a master services agreement (MSA) once with each client to cover legal terms like liability and confidentiality. Each new engagement then gets its own SOW, which holds the scope and price for that piece of work. People often treat "statement of work" and "scope of work" as the same thing, but a scope of work is only one section of an SOW.

What a statement of work does for a consulting firm

For your delivery team, the SOW is the list of what you owe the client. Anything that isn't in it is either a favor or a change request. For your finance team, it sets when each invoice can go out and what has to happen first, such as a deliverable being signed off. And when a client asks for something new, the change process in the SOW decides whether that work gets billed.

Vague SOWs cost money.

8.6%

average contract value erosion, the gap between what a contract was expected to deliver and what it actually delivered.

Source: World Commerce & Contracting, 2025

Scope disputes and invoicing errors are among the causes it lists. The figure spans all industries rather than consulting specifically.

‍

What's in a statement of work

Each section takes some care to draft well, and our step-by-step guide to writing an SOW walks through them in order.

Most SOWs include these nine sections

  1. Purpose. Why the client is buying the work.
  2. Scope. The scope of work, listing what’s included and what isn’t.
  3. Deliverables and acceptance criteria. What the client receives, and how you’ll both agree each item is done.
  4. Timeline and milestones. Start and end dates, plus the key checkpoints.
  5. Roles. Who does what on each side, and who can approve work.
  6. Pricing and payment terms. How you charge and when each invoice goes out.
  7. Assumptions. What you need from the client, and by when.
  8. Change process. How new requests get priced and approved.
  9. Governance and sign-off. How progress gets reported, and who signs the SOW.

‍

Types of statement of work

There are three main types of SOW, and the right one depends on how clearly the client can define the work up front.

A design/detail SOW spells out exactly what you'll produce and how. It suits work with a clear spec, like an engineering package built to an existing standard.

A level-of-effort SOW pays for your team's time, usually on time and materials. It suits discovery work, ongoing advisory and phased design, where later work depends on what you find early on.

A performance-based SOW describes the result the client needs and leaves the method to you. (US federal rules tell agencies to write these around required results rather than methods or hours - FAR 37.602. You get more freedom in how you deliver, but more risk if success is hard to measure. Firms in government contracting see this type most often.)

Statement of work examples

The three SOW examples below are illustrative composites, not real client documents. Each uses a different way of charging, and each table shows four lines a delivery lead should check before signing.

Fixed-fee strategy engagement (management consulting)

A 25-person consultancy is running a 10-week operating model review for a healthcare group, for a fixed fee. The client wants a recommendation its board can vote on.

SOW section Example wording Why it holds up
Scope
In and out
Review of finance, HR and procurement at the three head-office sites. Regional clinics are out of scope. If the client later wants the clinics included, that becomes a priced change.
Deliverable
With acceptance test
Operating model recommendation as a board paper. Accepted when the steering committee approves it, or after 10 business days with no written objection. Sign-off doesn't wait on a board vote the firm can't control.
Billing trigger
Fixed fee
40% on signature, 30% on acceptance of the current-state findings, 30% on acceptance of the board paper. Cash comes in as the work progresses instead of all at the end.
Assumption
Client inputs
Client provides process owners for up to 12 interviews in weeks 2 and 3. If interviews slip, the delay sits on the client's side of the schedule.
Illustrative example. A composite fixed-fee SOW, not a client document.

On a fixed fee, a clear acceptance test protects your margin, because an open-ended deliverable is where unpaid work creeps in.

Phased design engagement on time and materials (engineering)

An engineering firm is doing concept and preliminary design for a stormwater upgrade, billed on time and materials. The first phase is a site investigation.

SOW section Example wording Why it holds up
Scope
Phased
Phase 1 is site investigation and an options assessment. Phase 2, preliminary design, starts only on the client's written go-ahead. Phase 2 can't start informally on the back of Phase 1.
Deliverable
With acceptance test
Options report comparing up to three options on cost, buildability and permitting risk. Accepted when the client picks a preferred option in writing. The client's choice is the sign-off, so Phase 2 starts from a recorded decision.
Billing trigger
Time and materials
Monthly invoices for hours worked at agreed rates. Phase 1 is estimated at $48,000 and capped at $55,000 without written approval. The cap gives the delivery lead a set point to stop and check in with the client.
Assumption
Client inputs
Client supplies existing drainage survey data by week 2. Extra survey work is billed as a change order. Missing data becomes a priced change instead of a surprise cost.
Illustrative example. A composite time-and-materials SOW, not a client document.

Even on time and materials, clients tend to treat the estimate as a budget, so the SOW still needs a clear scope.

Milestone-billed software implementation (IT services)

An IT services firm is setting up a cloud finance system for a manufacturer, paid in milestones. The biggest payment depends on the client finishing user acceptance testing, and firms using this model often start from an IT and software SOW template.

SOW section Example wording Why it holds up
Scope
In and out
Set up general ledger, payables and receivables for two legal entities. Data migration covers open balances only. Data migration tends to grow once the client sees its old data, so it gets the tightest limit.
Deliverable
With acceptance test
System passes the agreed user acceptance testing (UAT) scripts in Appendix C. Minor defects can't block acceptance. Agreeing the test scripts up front stops the definition of done shifting during testing.
Billing trigger
Four milestones
25% on signature, 25% on design sign-off, 35% on UAT acceptance, 15% at 30 days after go-live. UAT is deemed accepted 10 business days after the final test round if no critical defects are open. Half the fee arrives before the build starts, and only 15% waits until after go-live.
Assumption
Client inputs
Client names a product owner who can approve design decisions within 3 business days. Slow approvals delay every later milestone, so the turnaround is written in.
Illustrative example. A composite milestone-billed SOW, not a client document.

With milestone billing, the acceptance clause controls your cash flow, because a client that's slow to test is also slow to pay.

When does a consulting firm need a statement of work?

You need one before any billable work starts, including a second phase with an existing client whose MSA is already signed. Smaller firms sometimes let a signed proposal act as the SOW. That works until there's a disagreement and the only record of the scope is a sales document.

A consulting proposal is written to persuade the client, while the SOW records what the client actually bought. The consultancy proposal format in Projectworks' How To Win More Work ebook keeps Scope & Deliverables, Pricing & Investment, and Assumptions/Exclusions as separate sections. The SOW turns each of those into a commitment. For example, a deliverable gets an acceptance test, and a price gets the event that triggers its invoice.

Start from an SOW that matches how your team works

Plenty of scope arguments start with an SOW rushed out the night before kickoff. Starting from one that already reflects how your team delivers means the hard questions are settled before the work begins.

Free template

Statement of work template for professional services firms

Start your next engagement from a structured SOW instead of a blank page.

Download the free template
Preview of the consulting statement of work template
Share:
Hardcover book titled 'Benchmark report' for consulting industry with green and black geometric design.
learn more

Download our professional services ‘cheat sheet’.

Whether you’re at $5M, $15M, or $50M, this cheat sheet maps the moves that separate firms who stall from firms who scale.

UP next:
By subscribing you agree with our Privacy Policy.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Keep reading

Read similar resources from Projectworks

This month is a special one - the Projectworks Consulting CRM and Proposals are now available for anyone to use or try out. A big thank you again to all of our design partners and early access firms, whose extensive feedback has shaped these features. There’s also lots more planned, so you’ll see them both in upcoming product updates! More tooling also landed in expenses and resourcing this month, so keep reading to find out more 👇

Bernadette Keating
November 2, 2026
resource type

It's the end of September and expenses got a lot of love this month, with a couple of big changes you can start using today and more on the way! We've also made updates across financial reporting, resourcing, HubSpot, and invoicing, dive in to see what's new.

Bernadette Keating
October 1, 2026
resource type
How Much Pipeline Coverage Does a Consulting Firm Need?

Most pipeline coverage advice is written for SaaS. Here's how a consulting firm sets coverage by deal stage and plans for the clients it will lose.

Ria Parish
October 12, 2026
resource type