Statement of Work (SOW) Template

A statement of work (SOW) template is a reusable document that defines exactly what a vendor will deliver on a specific project: the scope, deliverables, timeline, milestones, acceptance criteria and payment schedule. It turns a sales conversation into a concrete project plan both sides sign before work starts.

This guide walks through each SOW section, shows an example milestone and payment table and explains how services teams generate SOWs automatically.

What is a statement of work?

A statement of work is a project-level document used in professional services, consulting, IT, agencies and government contracting. It describes the “what, when and how much” of a project.

An SOW usually sits under a master services agreement (MSA). The MSA holds the legal terms that apply to the whole relationship, such as liability, confidentiality and IP. Each new project gets its own SOW, so you do not renegotiate legal terms every time.

SOW vs MSA vs proposal

What to include in a statement of work template

1. Project overview. Background, business goals and a one-paragraph summary.
2. Reference to the MSA. “This SOW is governed by the Master Services Agreement dated [date].”
3. Scope of work. The tasks and activities the vendor will perform.
4. Out of scope. Explicit list of what is not included.
5. Deliverables. Each tangible output, with a short description.
6. Timeline and milestones. Key dates and phases.
7. Acceptance criteria. How each deliverable will be reviewed and approved, and the review period.
8. Roles and responsibilities. Vendor team, client team, decision makers.
9. Assumptions and dependencies. What the plan relies on, such as timely client feedback or system access.
10. Pricing and payment schedule. Fixed fee, time and materials, or milestone billing.
11. Change management. How scope changes are requested and approved.
12. Project governance. Status meetings, reporting and escalation.
13. Signatures. Authorized signers for both parties.

Example: milestone and payment table

Tie payments to accepted milestones rather than dates. That keeps both sides focused on outcomes.

Statement of work template outline

• Statement of Work #[number] under the MSA dated [date] between [Vendor] and [Client].
• 1. Overview: [Client] engages [Vendor] to [project summary] in order to [business goal].
• 2. Scope: [Vendor] will perform the following activities: [list].
• 3. Out of scope: The following are excluded: [list].
• 4. Deliverables: [Deliverable, description, format].
• 5. Timeline: The project will start on [date] and is expected to finish by [date].
• 6. Acceptance: [Client] will review each deliverable within [5] business days. Deliverables are accepted if no written rejection with reasons is received in that period.
• 7. Responsibilities: [Vendor team roles]; [Client team roles].
• 8. Assumptions: [List].
• 9. Fees: [Fixed fee / rates], invoiced [per milestone / monthly].
• 10. Changes: Changes require a signed change order.
• Signatures.

Common SOW mistakes

• Vague deliverables such as “support the migration.” Define outputs you can point to.
• No out-of-scope section, the single biggest cause of scope creep.
• Acceptance without a deadline, which can hold invoices hostage.
• Missing assumptions. If the client’s delays shift the timeline, say so up front.
• Retyping data from the proposal, which introduces pricing and date errors.
• Many versions in email. Keep one source of truth.

How to generate SOWs automatically

Services teams often build SOWs by copying the last one and editing it. A better approach:

1. Start from the CRM opportunity with products, services, hours and rates.
2. Pick SOW building blocks. Conditional sections add standard scope text for each service package.
3. Generate the SOW from your Word template, including milestone and payment tables.
4. Route for internal approval by delivery and finance.
5. Send for e-signature to the client.
6. Kick off delivery: the signed SOW creates the project in your PSA, ERP or project tool.

How Noca helps

Noca generates SOWs from CRM data using your own templates, with conditional sections and dynamic tables, then handles approvals, e-signatures and the handoff to delivery systems. You can also ask ChatGPT or Claude to draft and send the SOW through the Noca MCP Server. Learn more about Noca document generation.

This article is for general information and is not legal advice.

Related guides

• Free Offer Letter Template (Word, PDF & E-Sign)
• Independent Contractor Agreement Template

Frequently Asked Questions

What is a statement of work?

A statement of work is a document that defines a specific project between a vendor and a client, including the scope, deliverables, timeline, milestones, acceptance criteria, responsibilities and pricing. It is usually governed by a master services agreement that holds the general legal terms for the relationship.

What is the difference between an SOW and an MSA?

An MSA sets the legal terms for the entire relationship, such as liability, confidentiality and intellectual property, and is signed once. An SOW describes one project’s scope, deliverables, schedule and fees. Companies sign a new SOW for each project under the same MSA.

Who writes the statement of work?

The vendor usually drafts the statement of work because it knows how the work will be delivered, but the client reviews and negotiates it. In government contracting, the buying agency often writes the SOW as part of its solicitation, and vendors respond to it.

Is a statement of work legally binding?

Yes, once signed by both parties, an SOW is generally a binding contract, often working together with the master services agreement it references. If the SOW and MSA conflict, the documents should state which one controls, typically through an order of precedence clause.

How detailed should a statement of work be?

Detailed enough that someone outside the deal can understand what will be delivered, when, how it will be accepted and what it costs. Clear deliverables, an out-of-scope list, acceptance criteria and a payment schedule are the minimum. Avoid unnecessary detail on internal methods.

What happens if the scope changes after the SOW is signed?

Scope changes should go through the change management process in the SOW, usually a written change order that describes the change and its impact on cost and timeline. Both parties sign the change order before the additional work begins.