Statement of Work (SOW) Template
A statement of work is the document that turns a sold project into a delivery contract. It names what you will produce, by when, for how much, and what sits outside the line. The master agreement sets the legal terms once; each SOW hangs off it and defines a single engagement.
The structure below is the one a working SOW needs. In Ascend it is a pre-built template: pick it and you get a database, an example row, an intake form, and the Word document already tagged — so every project becomes its own finished .docx in one click.
What’s in the document
Every section below is a placeholder that fills from a record. Generate one finished Word document per row — change the values, generate again.
The sections every SOW needs
Each is a placeholder in the template — it fills from the project record when you generate.
| Field | What goes here |
|---|---|
| Parties & effective date | Client and agency legal names, and the date the SOW takes effect under the master agreement |
| Background / objectives | Why the project exists and what success looks like for the client |
| Scope of work | The work you are committing to — phases, activities, and the approach |
| Deliverables | A line per deliverable: what it is, the format, and the acceptance criteria. This is the repeating section that expands to fit |
| Timeline & milestones | Start, key milestone dates, and the target completion |
| Pricing schedule | A line per fee item — fixed fees, rates, or milestone payments — with the total |
| Assumptions & dependencies | What you are relying on from the client (access, content, sign-off windows) |
| Out of scope | What this SOW deliberately excludes — the line a change order has to cross |
| Acceptance & sign-off | Names, signatures, and dates for both parties |
How to use this template
- Pick the Statement of Work template in Ascend — it creates the database, an example row, an intake form, and the tagged Word document together.
- Fill a record for the project, or collect the details through the matching intake form so the client supplies them.
- List each deliverable and each fee as its own row — the deliverables and pricing sections expand to one line per item.
- Generate the SOW from the record and download the finished Word file to send for signature.
- When scope changes mid-project, log it with the scope change request form rather than editing the signed SOW.
SOW vs master services agreement vs proposal
These three documents do different jobs and most disputes come from collapsing them into one. A proposal sells the work — it is persuasive, and it is not signed as a contract. A master services agreement sets the legal terms once — liability, IP, payment terms, confidentiality — and rarely changes. The statement of work is the operational contract for one project: what, when, how much, and what is excluded.
The pattern that scales is MSA once, SOW per project. The legal review happens a single time on the MSA; each new project only needs a fresh SOW, which is far faster to agree because the terms are already settled.
The section that protects your margin: out of scope
Most SOW templates describe the work in detail and leave the exclusions vague. That is backwards. The scope section tells the client what they are buying; the out-of-scope section is what stops a reasonable-sounding request from quietly becoming unpaid work.
Name the things a client will assume are included but are not — extra revision rounds, additional pages, content writing, ongoing maintenance, rush turnarounds. When one of them comes up, you point at the line, and the conversation becomes a change order instead of a favour. The exclusions list is the cheapest margin protection in the document.
Why generate it from your data instead of a blank file
A downloaded Word template is a blank you retype for every project. The client name, the deliverables, the fees, the dates — all rekeyed, and any one of them is a typo waiting to reach a client. An Ascend document template fills from the record that already holds the project, so the SOW matches the project database and the deliverables expand to exactly the number of lines the project has.
Change a fee on the record, generate again, and the new SOW reflects it. The layout, fonts, and branding come from your Word template, so the document you send looks like yours — only the values dropped in.
Related templates
Master Services Agreement Template
The legal terms each SOW hangs off — sign once, then SOW per project.
Business Proposal Template
Win the work first — the persuasive document the SOW formalises.
Scope Change Request Form
Document changes against the signed SOW instead of absorbing them.
Client Project Database Template
The roster the SOW generates from — one record per project.
Frequently asked questions
What is a statement of work?+
A statement of work (SOW) is a document that defines a single project under a broader agreement — its scope, deliverables, timeline, pricing, and what is excluded. It is the operational contract a client signs to authorise the work, distinct from the legal terms in a master services agreement.
What should a statement of work include?+
At minimum: the parties and effective date, background and objectives, scope of work, a deliverables list with acceptance criteria, a timeline with milestones, a pricing schedule, assumptions and dependencies, an explicit out-of-scope section, and sign-off lines for both parties.
What is the difference between an SOW and an MSA?+
A master services agreement (MSA) sets the legal terms once — liability, IP, payment terms, confidentiality — and rarely changes. A statement of work defines one specific project and is issued fresh each time. The MSA is the framework; the SOW is the project that runs inside it.
Is the SOW template free?+
Setting up the template in Ascend is unlimited on every plan, including Free. Generating finished documents is metered per month — 5 on Free, 100 on Solo, 500 on Studio, unlimited on Enterprise. Only generated documents count toward the number; the templates themselves do not.
Can I reuse one SOW for multiple projects?+
You reuse the template, not the document. Each project gets its own record and its own generated SOW. That keeps the scope, deliverables, and pricing specific to the project — which is exactly what makes an SOW enforceable.
How do I handle scope changes after the SOW is signed?+
Do not edit the signed SOW. Record the change on a change order that references the original SOW, with the revised scope, cost, and timeline, and get it signed. This keeps a clean trail of what was agreed and when.
Related template
Master Services Agreement Template
A SOW needs a master agreement to hang off. Set the legal terms once, then issue a fresh SOW for each project without re-running legal review.
Generate the SOW from the project, not a blank file.
In Ascend the statement of work fills from the same record that runs the project — deliverables and fees expand to fit, and the document matches your data every time. The free tier covers one project end to end.
Start with Ascend free