What Is a Statement of Work? Definition, Examples, and How to Write One

A statement of work, or SOW, is a document that defines the specific work for one project or engagement: the deliverables, the scope, the milestones, the schedule, the acceptance criteria, and the payment terms. It is the operational contract that says exactly what will be built or done, by when, and for how much. In most professional services relationships the SOW is issued under a master service agreement (MSA), which holds the legal terms so the SOW can stay focused on the work itself.

If you hire agencies, consultants, contractors, or vendors, or you sell those services, the SOW is the document that keeps both sides pointed at the same result. Below is what goes in one, the differences people mix up most often, and a practical way to structure your own.

What is a statement of work?

A statement of work is a written document that describes the work to be performed on a project, including the deliverables, timeline, milestones, acceptance criteria, and price. It turns a general agreement to work together into a concrete plan for one engagement. Vendors and clients both sign it, and it becomes the reference point for what counts as done.

The whole reason a SOW exists is to remove ambiguity. Without one, "build us a website" can mean five pages or fifty, one round of revisions or endless ones, copy included or copy your problem. A good SOW answers those questions in advance and in writing, which is why it doubles as a scope-creep defense. When a request lands that is not in the document, the SOW is what you point to.

What is included in a statement of work?

A statement of work includes the project objective, the scope of work, the deliverables, a timeline with milestones, acceptance criteria, assumptions and exclusions, the payment schedule, and the signatures of both parties. Some SOWs also list the location of the work, the people or roles assigned, and the standards the deliverables must meet before they are accepted.

Here is a section-by-section checklist you can lift straight into a template:

The acceptance criteria section earns its keep on almost every project. "Client approves the homepage design" is vague; "Client approves the homepage design within five business days, with up to two rounds of revisions" is enforceable. Write that section as if a stranger will have to judge whether the work is finished, because sometimes one does.

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

A statement of work is the entire document; a scope of work is one section inside it. The scope of work describes the boundaries of the project, the specific tasks in and out, while the statement of work wraps that scope together with the timeline, deliverables, pricing, acceptance terms, and signatures. Both share the abbreviation SOW, which is why people conflate them.

A quick way to keep them straight: the scope of work is the "what we will and will not do" list. The statement of work is the whole signed agreement that contains that list plus everything else needed to run and bill the project. If someone hands you a one-page "SOW" that only describes tasks and has no dates or price, you are looking at a scope of work, not a full statement of work.

What is the difference between an SOW and an MSA?

A master service agreement holds the legal terms that govern the whole relationship; a statement of work defines a single project under it. The MSA is signed once and covers liability, confidentiality, intellectual property ownership, indemnification, and termination. Each new project then gets its own SOW that references the MSA and adds only the deliverables, schedule, and price.

This split is what lets a vendor and client move fast on project two without renegotiating the whole legal framework. The heavy terms are already settled in the MSA, so the SOW can be a couple of pages about the actual work. For a deeper look at how the two documents stack, see our guide on the master service agreement vs statement of work.

Who writes the statement of work?

The statement of work is usually written by the vendor or service provider, since they know the effort, the deliverables, and the realistic timeline. The client then reviews it, negotiates the scope and price, and both parties sign. On larger or government contracts, the buyer sometimes drafts the SOW first and asks vendors to bid against it.

Whoever holds the pen, the SOW should be a two-way document by the time it is signed. The best ones get marked up in both directions: the vendor proposes the plan, the client tightens the deliverables and acceptance criteria, and the assumptions section grows as edge cases surface. That back-and-forth is a feature, because every question resolved on paper is a dispute avoided later.

What are the types of statement of work?

There are three common types of statement of work, and they mostly differ in how the work and payment are structured:

• Design / deliverable-based SOW: Payment is tied to specific outputs. The client pays for a finished website, report, or campaign, and the vendor carries the risk of how long it takes. Common in fixed-price creative and product work.
• Level-of-effort / time-and-materials SOW: The client pays for hours and materials rather than a fixed output. Used when the work is open-ended or hard to scope, like ongoing development or consulting retainers.
• Performance-based SOW: Payment depends on hitting defined outcomes or standards rather than listing every task. The vendor decides how to get there and is measured on results.

Many real engagements blend these. A project might be fixed-price for the initial build and time-and-materials for support after launch, all captured in one SOW with two payment sections.

How does milestone billing work in a SOW?

Milestone billing ties payment to progress instead of the calendar. Rather than invoicing monthly or waiting until the very end, you break the project into milestones, discovery complete, design approved, build delivered, and attach a payment to each. The client pays as each milestone is accepted, which keeps cash flowing to the vendor and gives the client a natural checkpoint to confirm the work before releasing more money.

When you structure a SOW this way, tie each milestone to a clear acceptance criterion and an invoice trigger so both sides know exactly what unlocks payment. Clean milestone terms are one of the simplest ways to get paid faster on completed deliverables, because there is nothing to argue about: the deliverable was accepted, so the invoice is due. Vague milestones do the opposite, they stall payment while everyone debates whether the work really counts as finished.

Is a statement of work legally binding?

Yes. A statement of work is legally binding once both parties sign it, the same as any business contract. It sets out an offer, acceptance, and consideration, and courts treat it as an enforceable agreement. When a SOW sits under an MSA, the two are read together, so the SOW inherits the legal protections spelled out in the master agreement.

Signing is straightforward, and electronic signatures are the standard now. An e-signed SOW is valid and enforceable under the federal ESIGN Act and the Uniform Electronic Transactions Act (UETA), which every US state has adopted, so there is no need to print and scan. You can send a statement of work for signature online and have it back in minutes with a full audit trail. For the details on that, read whether a statement of work can be signed electronically.

This article is general information, not legal advice. For how a specific SOW should be structured or enforced in your situation, check with a qualified attorney.

Putting it together

A statement of work is where a working relationship becomes a real plan: what gets delivered, when, how it is judged done, and how it gets paid for. Keep the legal terms in an MSA, keep the SOW focused on the work, write acceptance criteria a stranger could apply, and tie payments to milestones. Do that and the document does its job long before anyone needs to argue about it.