Every studio has a project that ate itself: the "two weeks" website that took three months, the app that absorbed one small change at a time, the retainer that quietly became a full-time role. None of those failed at delivery — they failed at definition. There was no shared document saying what "done" means, so both sides imagined their own.
The fix is one page, written before kickoff and signed before the first invoice. Eight fields:
1. Objective — one sentence, outcome not activity. "Replace the legacy site so the team can publish a post without a developer, by Nov 30."
2. Deliverables — countable nouns with numbers. 5 page templates, 1 CMS setup, 1 migration (300 posts), 2 revision rounds. The rule that separates scope from a wish list: if you can't count it, you can't bill for its changes.
3. Out of scope — the most valuable section. Whatever you don't exclude, a client will eventually assume was included. End with the catch-all: anything not listed under Deliverables is not promised.
4. Milestones — dates, each attached to a deliverable. Design approved Oct 10, migration Oct 24, launch Nov 14.
5. Price & payment schedule — total plus the trigger for each payment. $18,000: 50% on signature, 25% at design approval, 25% at launch.
6. Client responsibilities — what you need from them and by when, plus the schedule-slip rule: client delay moves every downstream date one-for-one. Half of all blown timelines are the client's; this clause is where the arithmetic is agreed before anyone needs it.
7. Acceptance criteria — how "done" is judged, observably. Page loads under 2 seconds, 300-for-300 migration, a non-technical editor can publish unaided. Add a review window: feedback within 5 business days or the deliverable is accepted. That window is the difference between a project that ends and one that drifts for a quarter.
8. Revision rounds — one round = one consolidated feedback list from one named decision-maker, covering all deliverables in that round. Twelve emails from four people is not a round; it's four rounds wearing a trenchcoat.
Three metrics keep it honest: signed-SOW-before-kickoff rate (target 100%), change-order rate traced back to SOW lines, and margin variance per project — the misses tell you which field was vague.
Worked example: a six-person studio rebuilt a site on a two-page proposal and a handshake. Eleven weeks later they'd absorbed a redesign of the redesign, three feedback rounds from five people, unpriced copywriting, and a hosting setup that became an ops role — roughly $14,000 of unpaid work. The next client got the one-page SOW. Two out-of-scope requests in week two became change orders totaling $6,800, approved in one email — because the SOW had already defined what a change was. Same work. Different definition.
The full template (with the worked table) is free on our site: Scope of Work Template for Small Teams — part of the HIVE80lab ops-notes library, where every template comes with a worked example and three metrics. If you want the whole scoping-to-invoice loop in one pack: Ops Starter Kit ($14, code HIVE20 for 20% off).
Related: Change Order & Scope Creep Checklist · Upfront Deposit Checklist · Client Onboarding Checklist
Top comments (0)