How to Write a Scope of Work
A scope of work turns a vague agreement into something both sides can point to. This guide walks through each section — objective, deliverables, acceptance criteria, exclusions, timeline, and terms — with practical guidance and free templates to start from.
How to write a scope of work, step by step
- 1
Start with the objective
Open with one paragraph on the outcome the project delivers — the business goal, not a task list. Everything downstream is judged against this.
- 2
List deliverables concretely
Name each output and its format ('a 20-page PDF audit', 'a deployed staging site'). Concrete deliverables are what make a SOW enforceable and acceptable.
- 3
Define acceptance criteria
For each deliverable, state how it's judged complete and the review window. Ambiguous acceptance is the top cause of 'it's not done' disputes.
- 4
State what's out of scope
List the near-misses people assume are included. Exclusions prevent more scope creep than any other section.
- 5
Set milestones and dates
Tie deliverables to target dates and review gates, and note the dependency on timely client feedback.
- 6
Add assumptions and change control
List what the plan depends on, and a rule that scope/schedule/fee changes go through a written change request before work proceeds.
- 7
Add fees, payment, and sign-off
State the fee basis, payment schedule, and a signature block. Then export a clean PDF for signature.
What a scope of work should contain
Each section answers a question the other party will otherwise ask later.
- Purpose / objective
- The outcome in business terms. Anchors every other decision.
- Deliverables
- The concrete outputs and their formats — the spine of the document.
- Acceptance criteria
- How each deliverable is judged done, and the review window.
- Exclusions
- What is explicitly not included — your best defence against scope creep.
- Timeline & milestones
- Dates tied to deliverables and review gates.
- Assumptions & dependencies
- What the plan relies on, so delays have a clear owner.
- Change control
- A written process for changing scope, schedule, or fees.
- Fees & sign-off
- The fee basis, payment schedule, and a signature block.
FAQ
- What is a scope of work?
- A scope of work is the document that defines exactly what a project will deliver: the objective, the deliverables, how they'll be accepted, what's excluded, the schedule, and the terms. It turns a vague agreement into something both sides can point to.
- What's the difference between a scope of work and a statement of work?
- They overlap and are often used interchangeably. In strict usage, a statement of work (SOW) is the broader engagement document — scope, schedule, payment, and terms, often under a master agreement — while the scope of work is the part that describes the work and deliverables. For most freelance and small-agency projects, a single well-written document covers both.
- Who writes the scope of work?
- Usually the provider (freelancer, consultant, or agency), because they know the work best. The client reviews and agrees. Writing it yourself is an advantage — you get to define the boundaries before the work starts.
- How detailed should a scope of work be?
- Detailed enough that a stranger could tell whether each deliverable was met. Name deliverables and formats, define acceptance, and list exclusions. Avoid padding — precision on deliverables matters more than length.
- Is a scope of work legally binding?
- It depends on how it's executed and what it's attached to — often it's incorporated into a signed agreement. Treat it as a business document, keep the terms clear, and have a lawyer review any contractual language for your situation. This guide is not legal advice.