Statement of work (SOW)
Definition
Statement of work (SOW)
A statement of work (SOW) is a contract document that locks in the scope, deliverables, timeline, pricing, and acceptance terms for one project between a client and a service provider. It sits under a master agreement, where the day-to-day promises live.
The master services agreement handles the legal frame. The SOW handles the work itself: what gets built, by when, for how much, and what counts as finished. One agreement can carry a dozen SOWs.
If you outsource anything — a software build, a support ramp, a content pipeline — the SOW decides whether the project ships or turns into a finger-pointing exercise. Get it right and the rest of the relationship mostly runs itself.
Key takeaways
- A SOW is the project-level contract that turns a vague engagement into a measurable, billable plan.
- Three working types (design, level of effort, and performance-based) split risk differently between buyer and vendor.
- Weak scoping stays the top failure mode, and the Project Management Institute’s Pulse of the Profession 2024 puts scope creep at the centre of it.
- Every SOW sits under one master services agreement and governs a single project at a time.
- Without an acceptance clause you get a deliverables list, then an argument about what “done” meant.
How it works
A SOW sits one layer below the master services agreement. That agreement covers the legal frame (liability, intellectual property, confidentiality, payment terms), while each SOW spells out one specific piece of work.
A well-built SOW answers seven questions in writing: what is being built, who does each piece, when each milestone lands, how success is measured, what the client must supply, what it costs, and how change requests are handled.
Skip any one of those and you have left a hole the project will fall through. The three working types map to three different ways of carrying risk.
| SOW type | Best for | Who carries the risk | Pricing shape |
|---|---|---|---|
| Design / detail | construction, engineering, fixed-spec builds | vendor, which must follow the exact spec | fixed price |
| Level of effort (LOE) | short engagements, staff augmentation, research | client, who pays for hours rather than output | time and materials |
| Performance-based | most professional services and BPO work | shared, weighted to the vendor on KPIs | outcome or hybrid |
| Phased / hybrid | discovery-then-build programmes | shifts by stage, fixed first, outcome later | mixed per phase |
Performance-based SOWs have become the default in offshore outsourcing because they tie payment to a measurable outcome (tickets resolved, leads qualified, code shipped) rather than seat-hours.
The US Government Accountability Office reported in 2022 that agencies shifting from level-of-effort to performance-based contracting cut average professional-services overruns by roughly a third.
Once both sides sign, the SOW becomes the source of truth. Any change — a new feature, a shifted deadline, an extra seat — should trigger a written change order that amends it, not a chat message everyone forgets.
Acceptance criteria do the heaviest lifting. Write them as testable statements (“99% of tickets routed within 30 seconds, measured monthly”) so both sides read “done” the same way and disputes settle on evidence.
Buyers scoping offshore work for the first time often talk to an Outsource Accelerator advisor before drafting, mostly to pressure-test the acceptance clause and the change-order mechanism.
Examples
SOWs look different in every sector, but the working shape stays consistent: named deliverables, a dated timeline, a price, and a test for acceptance. These four engagements show how the types play out in practice.
A US fintech signs a 2024 SOW with a Manila-based BPO for 40 support agents, setting average handle time at 4 minutes 30 seconds, a satisfaction floor of 88%, and a 90-day ramp.
The deal is performance-based: the vendor earns a 5% bonus in quarters that clear all three targets, and absorbs a 3% claw-back if satisfaction slips under 85%.
An Australian healthtech engages a Polish development shop on a fixed-scope, design-type SOW for a patient portal: eight named user stories, a 14-week build, AUD 220,000 fixed price, two acceptance gates.
Anything outside those eight stories needs a signed change order before a line of code is written.
A UK marketing agency uses a level-of-effort SOW to book a Cebu copy team for a six-week product launch: 320 hours capped, GBP 35 per hour, weekly burn reports.
When the launch slips a fortnight, the agency simply tops up the hours rather than renegotiating a fixed deliverables list.
A Singapore SaaS company runs a phased SOW with an Indian engineering partner: a fixed-price discovery stage, then a performance-based build tied to sprint velocity and uptime.
One master services agreement covers both stages, but each stage carries its own signed SOW, so the risk profile stays clean and the invoicing matches the work.
Related terms
These seven terms sit closest to the statement of work, and buyers usually meet them in this order: the bid document, the umbrella contract, the project scope, then the metrics and amendments that keep it honest.
- Master Services Agreement: umbrella contract governing the legal relationship between client and vendor, under which every SOW operates.
- Service Level Agreement: document fixing the measurable performance thresholds a vendor must hit, often referenced inside a SOW.
- Business Process Outsourcing: delivery model where an external provider runs a defined business function, almost always governed by a SOW.
- Key Performance Indicator: quantitative metric used to score progress against the targets set in a performance-based SOW.
- Scope Creep: unmanaged expansion of requirements past the original SOW, and the most common reason budgets blow out.
- Request for Proposal: pre-contract document a buyer issues to gather vendor bids, which later feed the negotiated SOW.
- Change Order: written amendment revising a signed SOW’s scope, price, or timeline.
FAQ
How is a SOW different from a contract?
The contract, usually the master services agreement, sets the overall legal relationship. The SOW is the project-specific schedule that hangs off it and covers one engagement at a time. You sign the agreement once and a fresh SOW for each project.
How long should a SOW be?
Long enough to answer the seven questions and no longer. Most professional-services SOWs run 4–12 pages. Under two pages usually means the acceptance criteria are missing, and over 25 usually means it is doing the master agreement’s job.
Who signs the SOW?
An authorised signatory from each side, typically a procurement or finance lead for the client and a delivery or commercial director for the vendor. The project manager drafts the document but rarely holds signing authority.
What happens if the SOW is breached?
The remedies sit in the master services agreement rather than the SOW: cure periods, service credits, or termination for cause. A precise SOW makes a breach provable, while a vague one turns it into a negotiation.
Can a SOW be changed after signing?
Only through a written change order signed by both sides. Verbal agreements and email confirmations do not amend a SOW, even when both parties behave as though they do. That is exactly how scope creep starts.
Are SOWs required for offshore outsourcing?
Yes in any credible engagement, and a provider willing to start offshore work without one is a provider worth skipping.
If you are scoping an offshore project, compare vetted providers in the Outsource Accelerator directory before you sign your first SOW.
Independent
