Contracts · Statement of Work
What an SOW is, how it differs from a proposal, contract and PRD, what it contains and a template to adapt.
Last updated: October 2026. Written by Athar Ahmad, Certified Bubble.io Developer and Tech Architect, Simple Automation Solutions.
Quick answer
A statement of work (SOW) defines the specific work to be performed under an agreement: scope, what is out of scope, deliverables, timeline, responsibilities, acceptance criteria, fees, change process, assumptions and signatures. It differs from a proposal, which persuades, a contract, which sets general legal terms, and a PRD, which details what a software product does. Always include acceptance criteria and a change process, and have a lawyer review your template.
Key takeaways
- An SOW defines the specific work, not the general legal terms.
- Always list what is out of scope and how acceptance is judged.
- Include client responsibilities, since delays often start there.
- Tie payments to milestones and agree a change process.
- This is general information; have a lawyer review any template.
In this guide
A statement of work, usually shortened to SOW, is one of the most useful and most misunderstood documents in client projects. Done well, it makes everyone’s expectations explicit. Skipped or rushed, it leaves room for the disagreements that sour projects: “I thought that was included” and “you never said that was due by Friday”.
This guide explains what a statement of work is, how it differs from a proposal, a contract and a PRD, what it should contain and includes a template. It is general information, not legal advice. Have a lawyer review any template before relying on it.
What is a statement of work?
A statement of work is a document that defines the specific work to be performed under an agreement: what will be delivered, by when, by whom, under what conditions and for what payment. It is often attached to or issued under a master services agreement or other contract, which sets the general legal terms.
SOW vs proposal vs contract vs PRD
| Document | Purpose | Binding? |
|---|---|---|
| Proposal | Persuades the client and describes the offer | Not usually |
| Statement of work | Defines the specific work, deliverables, schedule and payment | Yes, when signed or incorporated into a contract |
| Master services agreement or contract | Sets the general legal terms between the parties | Yes |
| PRD (Product Requirements Document) | Describes in detail what a software product should do | Usually attached or referenced, not a legal document itself |
For software projects, a PRD often sits alongside the SOW or is referenced by it, giving the detailed requirements. See our Discovery Sprint, which produces a PRD in 24 hours for $345.
What should a statement of work contain?
| Section | What it covers |
|---|---|
| Purpose and background | Why the work is being done |
| Scope of work | What is included, described specifically |
| Out of scope | What is explicitly excluded |
| Deliverables | Each item, its format and due date |
| Timeline and milestones | Key dates and dependencies |
| Roles and responsibilities | Who does what, on both sides |
| Acceptance criteria | How completion of each deliverable is judged |
| Fees and payment schedule | Amounts, milestones, invoicing and expenses |
| Change management | How changes are requested, priced and approved |
| Assumptions and dependencies | What must be true or provided for the plan to hold |
| Ownership and confidentiality | Who owns deliverables, how information is protected |
| Support and warranty | What happens after delivery |
| Termination | How the work can be stopped and what is owed |
| Signatures | Authorised representatives of both parties |
SOW template
1. Parties and reference
This Statement of Work is issued under [Master Agreement / Contract reference] between [Provider] and [Client], effective [date].
2. Purpose
Background and goal of the work: ________
3. Scope
Included: ________
Not included: ________
4. Deliverables and schedule
Deliverable 1: ________ Format: ________ Due: ________ Acceptance criteria: ________
Deliverable 2: ________ Format: ________ Due: ________ Acceptance criteria: ________
5. Responsibilities
Provider will: ________
Client will: ________ (for example provide content, access and timely feedback within ___ business days)
6. Fees and payment
Total fee: ________ Payment milestones: ________ Expenses: ________ Invoice and payment terms: ________
7. Changes
Changes to scope, schedule or fees require a written change request, estimate and approval by both parties before work begins.
8. Assumptions
List the assumptions behind the schedule and price: ________
9. Acceptance
The Client has ___ business days to review each deliverable and either accept it or provide specific written reasons for rejection.
10. Signatures
Provider: ________ Name, title, date. Client: ________ Name, title, date.
What are the common mistakes?
- Vague scope such as “develop a website”.
- No out-of-scope list.
- Deliverables without acceptance criteria, so nobody knows when they are done.
- Ignoring client responsibilities, which cause most delays.
- No change process.
- Payments not tied to milestones.
- Copying a template without adapting it to the project.
How do you make an SOW easy to agree?
- Write it in plain language.
- Walk the client through it on a call before asking for a signature.
- Use specific, measurable deliverables.
- Agree what happens when things change before they do.
- Keep a signed copy where both sides can find it.
See how to avoid scope creep and what to cut before you build.
Frequently asked questions
What is a statement of work?
A document that defines the specific work to be done under an agreement: scope, deliverables, schedule, responsibilities, acceptance and payment.
What is the difference between a statement of work and a contract?
A contract sets the general legal terms. A statement of work describes the specific project. An SOW is often issued under a master agreement.
What is the difference between an SOW and a PRD?
An SOW defines the commercial and delivery terms of the work. A PRD describes in detail what a software product should do. They often work together.
Do I need an SOW for a small project?
A short one is still valuable. Even a page that sets scope, deliverables, dates and price prevents most disputes.
Who writes the statement of work?
Usually the provider drafts it with the client’s input, and both parties review and sign it.
Want a clear scope to build your statement of work around?
Email us your idea. We will help you produce a PRD and a quote that fits into an SOW.
Athar Ahmad, Certified Bubble.io Developer and Tech Architect, Simple Automation Solutions
About Simple Automation Solutions (SA Solutions)
Simple Automation Solutions is a Bubble.io development studio led by Athar Ahmad, a Certified Bubble.io Developer and Tech Architect. It builds web and mobile apps, client portals and SaaS products for founder-led businesses such as law firms, accounting firms, boutique agencies and consultants. Services include a free 30-minute Idea Audit, a $345 Discovery Sprint (a Product Requirements Document delivered within 24 hours, credited toward the build) and builds starting at $3,500. Website: sasolutionspk.com.
