How to Write a Scope of Work (With a Fill-In Example)
A scope of work (SOW) is the document that defines exactly what you will deliver, what you will not, and on what terms. It turns a vague "redesign our website" into a list specific enough that you and the client cannot disagree later about what "done" means.
Most SOW templates only tell you what to include. The part that actually saves you money is what you exclude. This guide covers both, with a fill-in example you can copy.
Quick summary
- A SOW defines deliverables, exclusions, timeline, and acceptance criteria.
- The "out of scope" list prevents more disputes than the deliverables list.
- Cap revision rounds in the SOW, or "revisions" becomes unlimited free work.
- A SOW is narrower than an MSA (the master legal terms) and more concrete than a proposal.
What a scope of work includes
A complete SOW has seven parts. Keep each short and specific:
- Objective. One or two sentences on the outcome the work produces.
- Deliverables. The exact items, with quantities ("5 page designs," not "the site").
- Out of scope. What is explicitly not included.
- Timeline and milestones. Key dates and what triggers each.
- Acceptance criteria. How "done" is defined and approved.
- Assumptions. What the price depends on (client supplies content, one round of consolidated feedback).
- Price and payment terms. The cost and when it is due.
A stranger should be able to read it and know precisely what they are getting.
The most important section: what is out of scope
The deliverables list says what you will do. The exclusions list says what you will not, and that is where scope is actually protected.
Name the things clients commonly assume are included but are not:
- Copywriting, photography, or stock asset licensing
- Extra revision rounds beyond the number stated
- Ongoing maintenance or support after launch
- Third-party costs (plugins, fonts, ad spend)
A request that lands on this list is no longer an argument. It is a change order, priced and approved before you do the work.
Cap your revisions, or they are unlimited
"Revisions until you're happy" is an open-ended liability. State a number.
A clean clause: "Includes 2 rounds of consolidated revisions. Additional rounds billed at [rate]/hour."
This single line is the difference between a profitable project and one that quietly bleeds hours. It also gives the client a reason to consolidate feedback instead of sending it in dribs and drabs.
A fill-in scope of work example
Copy this and replace the brackets:
Objective: Deliver a [5-page] marketing website that [increases demo bookings] for [Client].
Deliverables: [5] unique page designs; responsive build; [1] contact form; basic on-page SEO setup.
Out of scope: Copywriting; photography; ongoing maintenance; more than [2] revision rounds; third-party plugin or license fees.
Timeline: Kickoff [date]; first designs [date]; launch [date]. Dates assume content is supplied by [date].
Acceptance: Each deliverable is approved in writing before the next phase begins. Silence beyond [5] business days counts as approval.
Assumptions: Client provides all content and one round of consolidated feedback per stage.
Price and terms: [$X], with [50%] deposit before work begins and the balance due [net 15] on launch.
SOW vs MSA vs proposal
These three documents get confused. They do different jobs:
| Document | What it covers | When it is used |
|---|---|---|
| Proposal | The pitch: outcome, approach, pricing options | Before the client says yes |
| SOW | The specific deliverables and terms for one project | Once the project is agreed |
| MSA (master service agreement) | The legal terms that govern all projects | Signed once, reused per SOW |
For ongoing clients, sign one MSA covering liability, IP, and payment defaults, then attach a short SOW per project. You negotiate the boring legal stuff once.
Not for you: when a heavy SOW is overkill
A full seven-part SOW is the wrong tool when:
- The job is a tiny, well-defined task. A one-paragraph email confirming deliverables and price is enough.
- You are mid-retainer with a trusted client and a shared backlog already defines the work.
- Speed matters more than formality on a low-risk, low-value piece.
Match the document to the risk. A $300 logo tweak does not need the same paperwork as a $30,000 rebuild.
Frequently asked questions
What is an example of a scope of work?
A scope of work example states the objective, lists exact deliverables with quantities, names what is out of scope, sets a timeline and acceptance criteria, lists assumptions, and states the price and payment terms. See the fill-in template above for a copyable version.
How do you write a simple scope of work?
Answer four questions in writing: what you will deliver (with quantities), what you will not, when each piece is due, and how "done" is approved. Add price and payment terms. Even a one-page version that covers these prevents most disputes.
What should a scope of work look like?
It should be short, specific, and scannable, organized into clear sections (objective, deliverables, exclusions, timeline, acceptance, assumptions, price) so a reader who was not on the call can understand exactly what is being delivered.
What is the difference between a scope of work and a contract?
A scope of work defines the specific deliverables and terms of one project. A contract, or master service agreement, sets the legal terms (liability, IP, payment defaults) that apply across the whole relationship. Many agencies use both: one contract plus a SOW per project.
Related guides:
Ready to streamline your business?
Try Agiled free and see how our all-in-one platform can help you manage your business more efficiently.