A statement of work template is a ready-made blueprint for a project or contractor engagement. It spells out the work, deliverables, dates, fees and sign-off rules before anything starts, so both sides agree on expectations and scope creep has nowhere to hide.
A statement of work, or SOW, is the document that describes exactly what a supplier will do for you on one project: the tasks, what they hand over, when, where, for how much and how you will confirm it is done. A SOW template gives you that structure ready to fill in.
Buyers use an SOW template whenever they hire a consultancy, agency, contractor or software partner for defined work. It usually sits under a master services agreement, which holds the legal terms, while the SOW holds the project detail and can be repeated for each new piece of work.
Its main job is to stop disputes. When scope, exclusions and acceptance criteria are written down before work begins, both sides can point to the same page when questions about extra work or late delivery come up.
The parties, project title, background and the version date of the SOW.
The goals, the problem being solved and how success will be judged.
Tasks and activities, explicit exclusions, and whether work is remote, hybrid or on-site.
What is handed over, at which milestone, and the schedule for each.
Total cost, pricing structure and invoice schedule, such as Net 30 after acceptance.
The criteria each deliverable must meet and who approves it.
Ready to use in Word, Google Docs and PDF. Fill it in, save it, reuse it.
The project owner lists objectives, tasks and exclusions. Procurement checks there is an approved request and budget.
The buyer or supplier fills in the template. Most buyers prefer to start from their own version.
Both sides check scope, dates and fees, legal checks it against the master agreement, then both sign.
The supplier delivers each milestone and the buyer signs it off against the acceptance criteria.
Invoices follow accepted milestones. The project closes once the final deliverable is signed off.
The simplest usable SOW answers six questions in two pages: who, what, what not, by when, for how much, and how we will know it is done.
Copy this outline into your SOW template and keep the numbering, so invoices and change requests can refer to sections. Write in plain, testable terms: if a sentence cannot be checked at acceptance, rewrite it.
Parties, project title, reference to the master agreement, background and the SOW version and date.
What the project must achieve, the problem it solves and measurable success criteria.
Every task and activity the supplier will carry out, followed by an explicit list of exclusions.
Where the work happens: remote, hybrid or on-site, with addresses, travel rules and access needs.
Each deliverable, its format and the milestone it belongs to.
Start and end dates, milestone dates and any dependencies on the buyer.
Total fee, pricing model, expenses policy, invoice schedule and payment terms.
Named contacts on both sides, the buyer's obligations and the supplier's team.
How changes to scope, dates or fees are requested, priced and approved in writing.
Acceptance criteria, review period and the signature block for both parties.
3.2 Exclusions. The following are out of scope: [exclusion 1], [exclusion 2] and [exclusion 3]. Any work not listed in section 3.1 requires a signed change request under section 9. 7.1 Payment. [Buyer] will pay [Supplier] a fixed fee of [amount], invoiced on acceptance of each milestone as set out in section 5. Invoices are payable within [30] days of receipt. 10.1 Acceptance. [Buyer] will review each deliverable within [10] business days of receipt. A deliverable is accepted when it meets the criteria in section 10.2, or if [Buyer] gives no written rejection within that period.
This sample shows how the template reads once filled in. Every deliverable is something you can inspect, every date is fixed and every payment is tied to acceptance rather than to time passing.
1. Introduction. This SOW, version 1.0 dated [date], is issued under the master services agreement between Lumen Retail (Buyer) and Brightline Software (Supplier) dated [date]. Project: CRM implementation. 2. Objectives. Replace three spreadsheets with one CRM for 120 sales staff, with all active accounts migrated and weekly pipeline reports produced automatically. 3. Scope. Supplier will configure the CRM, migrate 18,000 account records, build four reports and train 120 users. Excluded: integration with the billing system, custom mobile apps and data cleansing of source records. 4. Location. Remote, with two on-site training days at Buyer's head office.
| Milestone | Deliverable | Due | Acceptance test | Payment |
|---|---|---|---|---|
| M1 Discovery | Signed design document | Week 3 | Approved by sales director | 19,200 |
| M2 Configuration | CRM set up in test | Week 8 | 20 test scenarios passed | 28,800 |
| M3 Migration | 18,000 records live | Week 12 | Sample of 500 records checked | 24,000 |
| M4 Go-live | Training and launch | Week 16 | 120 users active for 2 weeks | 24,000 |
| Total | 96,000 |
Illustrative SOW example with fictional companies. Payments due Net 30 after each acceptance.
Scope creep rarely starts with a big request. It starts with small favours that nobody wrote down, which later turn into a disputed invoice. An exclusions list and a simple change request form stop that early.
| Area | In scope | Out of scope |
|---|---|---|
| Configuration | Standard objects, fields and four reports | Custom code and new modules |
| Data | Migrating active accounts from three spreadsheets | Cleaning or de-duplicating source data |
| Integrations | Email and calendar sync | Billing and ERP integration |
| Training | Two on-site sessions and recorded videos | Ongoing training after go-live |
| Support | Two weeks of hypercare after launch | Support beyond hypercare, covered by a separate SLA |
Illustrative, from the CRM example above.
Change request no. [CR-001] SOW reference: [SOW title, version] Requested by: [Name, company] Date: [Date] Change: [What should be added, removed or changed] Reason: [Why it is needed] Impact on scope: [Sections affected] Impact on timeline: [Days added or saved] Impact on fees: [Amount and pricing basis] Approved by Buyer: [Name, signature, date] Approved by Supplier: [Name, signature, date]
The pricing model decides who carries the risk if the work takes longer. Fixed fees protect the buyer but need a tight scope, while time and materials protects the supplier and needs a cap. Write the invoice schedule and payment terms into the SOW, not only the master agreement.
| Model | How it is billed | Best for | Protect yourself with |
|---|---|---|---|
| Fixed fee | Agreed total, paid by milestone | Well-defined projects | Payment only on acceptance |
| Time and materials | Hours or days at agreed rates | Discovery or changing scope | A not-to-exceed cap |
| Milestone-based | Set amount per milestone | Phased delivery | Clear acceptance tests per milestone |
| Retainer | Fixed monthly fee for set capacity | Ongoing support or advisory work | Monthly report of hours used |
Sign the SOW only once the spend is approved. See how procurement contracts fit together.
Vague criteria like "to the buyer's satisfaction" invite argument. Set a review period, say what happens if the buyer is silent, and allow a set number of fix rounds before escalation.
| Weak criterion | Testable criterion |
|---|---|
| Reports work properly | Four named reports run in under 10 seconds with live data |
| Data migrated | 18,000 records migrated, and a 500-record sample matches the source |
| Users trained | 120 users attended training and logged in at least once in week 1 |
| System is stable | No priority 1 defects open for 10 business days after go-live |
Illustrative criteria from the CRM example.
Milestone: [M2 Configuration] SOW reference: [SOW title, version] Deliverable received: [Date] Criteria met: [Yes / No, with notes] Open issues: [List, with agreed fix date] Accepted for Buyer: [Name, role, signature, date] Acknowledged for Supplier: [Name, role, signature, date]
Signed SOWs get lost in inboxes. Spendflo's Contracts Agent keeps terms, dates and renewals in one place.
See the Contracts AgentMaster services agreement: the legal terms that every SOW under it inherits.
A specific output the supplier hands over, such as a report, a system or a trained team.
A point in the schedule where deliverables are reviewed and, often, paid for.
Work added gradually without a change request, price or new date.
The maximum fee on a time and materials SOW, unless a change request raises it.
Payment due within 30 days of the invoice date, or of acceptance if the SOW says so.
Buyer-drafted SOWs keep your terms and structure, rather than the supplier's.
Name what is out of scope so extra work is clearly chargeable or refused.
Note the data, access and people you must provide, and by when.
Link invoices to signed-off milestones rather than calendar dates.
Number each signed change request and update the SOW version.
Describing effort rather than deliverables leaves you paying for activity.
Time and materials work without a cap can run far past budget.
Legal terms in the SOW that contradict the master agreement create confusion over which applies.
Agreeing extra work by email without a change request leads to disputed invoices.
Write the problem and two or three measurable goals for the project.
List tasks, then exclusions, then where the work will happen.
Group deliverables into milestones with dates, tests and payments.
Check against the master agreement, get legal review and sign.
Midway through the Lumen Retail project, the sales team asks Brightline Software to connect the CRM to billing. The SOW lists billing integration as excluded, so Brightline raises CR-001: 12,000 and three extra weeks. Lumen approves it in writing, the fee rises to 108,000 and go-live moves to week 19. Figures are illustrative.
Every part on this page, in Word, Google Docs and PDF, with the examples filled in.
Add environments, data migration volumes, integrations and test scenarios. Tie the final payment to a stable period after go-live.
Describe outputs such as reports or workshops, name key staff and set a time and materials cap for discovery work.
Specify site addresses, access hours, safety rules and equipment, and who provides materials.
Best for negotiation with tracked changes.
Best for drafting with the project team.
Best for the final signed copy.
$3.7B in software spend processed through Spendflo, at 30% average savings.
See your savingsA good SOW template makes scope, deliverables, dates and payments testable before work starts. Once it is signed, keep it with the master agreement, track every change and know when the engagement ends.
Quick answers to what people ask most about the statement of work template.
Start with the objectives, then define the scope and exclusions, list deliverables by milestone with dates and fees, and finish with acceptance criteria and sign-off. Check it against the master agreement before signing. Download the template to follow that order section by section.
A common example is a software implementation SOW, where a vendor configures a system, migrates data and trains users for a fixed fee paid by milestone. The CRM example on this page shows one filled in. Download the template to get the example in Word or Google Docs.
Yes: the example on this page covers a 16-week CRM project with four milestones, a 96,000 fixed fee and testable acceptance criteria. It includes the introduction, objectives, scope, exclusions and location. Download the template for the full filled example as a PDF.
Write one short paragraph for each section: overview, objectives, scope, location, deliverables, timeline, payment and acceptance, using real names, numbers and dates. Keep each statement testable. Download the template and copy the sample clauses as a starting point.
You can download a free SOW template on this page in Word, Google Docs or PDF. It includes the ten-section outline, sample clauses, a filled example and a change request form.
Contracts
Purchase orders
Vendor management
Sourcing and RFx
Budgets and business cases
Procurement
Accounts payable
Purchasing
Software buying
Supply chain
Spendflo handles intake and approvals before the SOW is signed, then tracks contracts and renewals with the Contracts Agent.
Enter your work email and we'll unlock every format.
Didn't start, or need another format? Pick one below.
Google Docs: upload the file to Google Drive, then open it with Google Docs.
