Scope of Work Template for Small Teams
One page. The eight fields that make a project billable, testable, and finishable — written before the kickoff, signed before the first invoice.
Every studio has a project that ate itself: the website rebuild that was “two weeks” and took three months, the app that kept absorbing “one small change,” the retainer that quietly became a full-time role. None of those failed at delivery. They failed at definition — there was no shared document that said what “done” means, so both sides were free to imagine their own. The scope of work is not a legal formality. It is the page that turns a conversation into a contract of countable things, and it is the cheapest hour you will ever spend on a project.
The SOW, one page — eight fields
One page, filled in before kickoff, signed before work starts. Every field earns its line:
| Field | What goes in it | Example |
|---|---|---|
| Objective | One sentence, outcome not activity | “Replace the legacy site so the team can publish a post without a developer, by Nov 30.” |
| Deliverables | Countable nouns with numbers | 5 page templates, 1 CMS setup, 1 migration (300 posts), 2 revision rounds |
| Out of scope | What the client might assume and you won’t do | Copywriting, hosting, ongoing maintenance, extra revision rounds, third-party licenses |
| Milestones | Dates, each attached to a deliverable | Design approved Oct 10; content migration Oct 24; launch Nov 14; handover Nov 30 |
| Price & payment schedule | Total plus the trigger for each payment | $18,000: 50% on signature, 25% at design approval, 25% at launch |
| Client responsibilities | What you need from them, and by when | CMS access by Oct 3; brand assets by Oct 3; one named decision-maker; feedback within 3 business days |
| Acceptance criteria | How “done” is judged, testably | All pages load under 2s; 300 posts migrated with redirects; publishing a post takes <10 minutes by a non-technical editor |
| Revision rounds | How many, and what one round is | 2 rounds included; one round = one consolidated feedback list from the decision-maker |
Deliverables are countable nouns
The single rule that separates a scope from a wish list: if you can’t count it, you can’t bill for its changes. “Improve the onboarding flow” is not a deliverable — “3 redesigned screens, 1 new welcome email, usability test with 5 users” is three deliverables and a test. When a client asks for “a bit more polish,” the SOW answers with arithmetic, not feelings: the deliverable list has a count, the request exceeds it, and that makes it a change order — the same mechanic the change order checklist turns into billed hours instead of donated ones.
Out of scope: the most valuable section on the page
Silence is the enemy. Whatever the SOW doesn’t exclude, a client will eventually assume it was included — and you’ll discover the assumption the week you’re providing it for free. The out-of-scope list is short, blunt, and written for the reader who joins in week three: hosting, content writing, stock licenses, additional revision rounds, post-launch maintenance, anything not listed under Deliverables. That last line is the catch-all, and it does more margin protection than any clause: work not named is work not promised.
Client responsibilities: the dependencies clause
Half of all blown timelines are not your delay — they’re the client’s. The SOW names what the client must supply (access, assets, a single decision-maker), by which milestone date, with one rule attached: client delay moves the schedule one-for-one. “Brand assets due Oct 3, received Oct 17” means every downstream date shifts 14 days, and the SOW is where that arithmetic is agreed before anyone needs it. This section also protects the invoice rhythm that the upfront deposit checklist sets up — a payment triggered at “design approval” can’t be stalled by a client who simply goes quiet.
Acceptance criteria: how “done” is judged
“Done” that lives in one person’s head is a dispute on a deadline. Acceptance criteria are the tests both sides agree in advance — page loads under 2 seconds, the migration returns 300 for 300, a non-technical editor can publish unaided. Two rules make them real: criteria are observable (a stranger could verify them), and there is a review window — feedback within 5 business days of delivery, or the deliverable is accepted. The window is the difference between a project that ends and one that drifts for a quarter.
The revision-round economy
Rounds are where projects bleed. Define a round precisely: one consolidated feedback list, from the named decision-maker, covering all deliverables in that round. Twelve emails over three weeks from four people is not a round — it’s four rounds wearing a trenchcoat. Two rounds included, further rounds at the change-order rate, and the count written into the SOW. Teams that skip this line discover that “unlimited revisions” is how a fixed-price project becomes an hourly job at a 60% discount.
Three metrics that keep the SOW honest
- % of projects with a signed SOW before kickoff — target 100%. Every exception becomes a story you tell about a project that lost money.
- Change-order rate — logged changes per project, each one traced to a SOW line (or its absence). A high rate on out-of-scope work means the exclusions list is too short.
- Margin variance per project — planned hours vs actual. The projects that miss are your SOW retrospective: which field was missing or vague? Fix the template, not just the project.
Worked example: the project that became a favor
A six-person studio rebuilt a client’s website on a two-page proposal and a handshake. It was “two weeks.” Eleven weeks later they had absorbed a redesign of the redesign, three rounds of feedback from five different people, a copywriting job nobody priced, and a hosting setup that turned into an ops role. The project was profitable on paper and broke even in reality — roughly $14,000 of unpaid work hidden in “small asks.” The next client got the one-page SOW: five countable deliverables, an out-of-scope list that named hosting and copy, two revision rounds with a consolidated-feedback rule, a client-responsibilities clause with dates, and a 5-day acceptance window. The client requested two out-of-scope items in week two — both became change orders totaling $6,800, approved in one email because the SOW had already defined what a change was. The project delivered on schedule, invoiced on schedule, and nobody donated anything. The work was the same. The definition was different.
The SOW one-pager and the change-order loop are in the Ops Starter Kit. Want your contracts, scoping and delivery flow audited and documented? See the small-team ops audit & runbook service.