Statement of Work (SOW): What to Include & Examples

What Is a Statement of Work (SOW)?

Statement of work (SOW) refers to a document that defines the specific work a vendor will perform for a client: the deliverables, the schedule, the acceptance criteria, and the price. It sits under a master services agreement, which supplies the legal terms the SOW does not repeat.

How a Statement of Work Works

A statement of work is written to answer four questions without ambiguity: what is being delivered, by when, judged how, and for how much. A complete SOW usually contains objectives, a scope section, an explicit out of scope section, a deliverables list, acceptance criteria, a timeline with milestones, assumptions and client dependencies, named roles and staffing, a pricing and invoicing schedule, and a change control process.

The out of scope section does more work than founders expect. Scope disputes rarely turn on what the document promised. They turn on what a client assumed because the document was silent. Writing down what is excluded, and what the client must supply to hit dates, converts a future argument into a paragraph both sides read before signing.

Statement of Work in Plain English

The master services agreement is the marriage. The statement of work is the trip you are taking this month. The first document says who is liable, who owns the IP, and what happens if the relationship ends. The second says the team lands on the fourth, the report is due on the eleventh, and the fee is $60,000. You sign the first once. You sign the second every time there is new work.

SOW vs MSA vs Order Form

The distinction is simple. The master services agreement (MSA) carries the legal terms that govern the entire relationship: liability caps, indemnity, confidentiality, IP ownership, warranties, termination rights, and governing law. It is negotiated once and rarely reopened.

The statement of work carries the commercial and operational terms for one engagement of services: scope, deliverables, milestones, acceptance, and fees. It incorporates the MSA by reference rather than restating it.

The order form carries what is being purchased in a product or subscription sale: SKUs, quantities, subscription term, price, and renewal mechanics. It also incorporates the MSA. The rough rule is that services are bought through a statement of work and licenses are bought through an order form, and complex deals often have all three.

One short clause matters more than its length suggests: order of precedence. Most well drafted agreements make the MSA control on legal terms and let the SOW control on scope, schedule, and fees.

Deliverables, Acceptance Criteria, and Milestones

A deliverable is only useful if someone can tell whether it arrived. Acceptance criteria should be objective and testable: a migration is complete when 100 percent of records transfer with a reconciliation report showing zero variances, not when the client is satisfied. Pair criteria with a deemed acceptance clause: a deliverable is accepted if the client does not submit written deficiencies within 10 business days. Without it, a milestone payment can hang indefinitely on a stakeholder who is on holiday. Milestones then tie payment to those acceptance events, which is what makes services revenue predictable enough to plan around.

Scope Creep and Change Orders

Scope creep is the accumulation of small unbilled additions that no one thought was worth a conversation. It arrives as a dashboard tweak, one more integration, and a second round of training, each defensible on its own and collectively fatal to margin. The control is procedural, not personal. Every SOW should require that changes to scope, schedule, or fees be made by written change order signed by both parties, and that out of scope work does not begin until it is signed. Teams that price change orders in hours rather than weeks find clients accept them far more readily.

Fixed Fee vs Time and Materials

A fixed fee SOW quotes one price for a defined scope, which puts estimation risk on the vendor. Clients prefer it because the budget is certain, and it works only when scope is tight and change control is enforced. A time and materials SOW bills hours at agreed rates, which puts the risk on the client and usually carries a not to exceed cap to bound exposure. Capped time and materials is the common middle ground: the client pays for actual effort but never above the cap. Larger engagements often mix the two, with a fixed fee for a scoped discovery phase and time and materials for the build that follows.

Statement of Work (SOW) and the Closing Motion

The statement of work is the artifact where Propose becomes Close for services revenue. It also creates the cash problem that follows. Milestone billing means the vendor staffs the team in month one and invoices on acceptance in month three, then waits out net 30 or net 60 terms, so payroll runs well ahead of collections on work already sold. Ratio addresses that gap at Collect: with Ratio Trade the client pays across the engagement while the seller collects the full contract value upfront. Precision in the SOW matters here too. Clear acceptance criteria and a disciplined change order process are what keep an engagement from turning into a disputed invoice, and disputed invoices are the most common reason services revenue never converts to cash.

Common Questions About a Statement of Work (SOW)

Is a statement of work legally binding?

Yes, once signed, though it is typically binding as part of a larger contract rather than on its own. Most SOWs incorporate an MSA by reference and rely on it for liability, IP, and termination terms. An SOW signed with no governing agreement behind it leaves those questions unanswered.

What is the difference between a statement of work and a scope of work?

Scope of work is a section inside a statement of work, describing the activities to be performed. The statement of work wraps that scope with schedule, acceptance, pricing, assumptions, and change control, which makes it a contract document rather than a description.

Who should write the statement of work?

Usually the vendor, because the vendor knows the delivery method and realistic sequence of work. The client should review scope, acceptance criteria, and dependencies closely, since those sections determine what happens when the project runs late.

Statement of Work (SOW)