To write a scope of work that holds up, write every line so that someone who wasn't on the sales call could decide whether a new request is included. In practice: numbers on deliverables, a "not included" list, counted revisions and hours, dated client inputs, sign-off points, and a written rule for extras.

Think of it like a spec. If a line can't be checked, it will be argued about.

What the document is for

A scope of work says what you'll deliver, what you won't, how many revisions and hours the price covers, and what happens when the client asks for more. It's the page you open when someone says "wasn't that included?", so it has to answer that question without you in the room.

A PMI conference paper on scope summarises the PMBOK Guide (4th edition) minimum for a scope statement: a product description, the deliverables, the boundaries (an explicit statement of what's out of scope), acceptance criteria, constraints such as budget and schedule, and assumptions. The same paper calls scope "fuzzy" and often the biggest source of conflict on a project, because time and cost are numbers and scope usually isn't.

So the job is simple to state: turn the fuzzy part into something as close to a number as you can.

The sections, in order

  1. Goal. One or two sentences, in the client's words. "Get more booked consultations from the website" is a goal. "Website redesign" is a project name.
  2. Deliverables, each with a number. Pages, templates, posts, concepts, hours, integrations.
  3. Definition of done for each deliverable.
  4. Not included. Especially the things clients in your field tend to assume.
  5. Limits. Revision rounds, hours, response times.
  6. Client responsibilities and assumptions. Content, access, feedback deadlines.
  7. Timeline and sign-off points.
  8. How changes work and how extras get priced.

Price and payment terms usually live in the proposal or contract next to it. Keep them close, but don't let fee talk crowd out the description of the work.

Goal

The goal looks small, but it settles arguments early. If a podcast page shows up halfway through a project meant to drive consultation bookings, you can ask how it serves the goal before anyone talks money.

Bill Duncan, writing in PM Network, contrasts "reduce costs" with "reduce unit costs by 20 percent within one year." You don't need a percentage, but you need something sharper than the project title.

Deliverables

This is the core. Every output gets a quantity or a limit.

- Social media content. + 8 Instagram posts a month (static images or carousels), with captions. + Reels and paid ads aren't included. 

Duncan's example: "clinical trials" isn't a usable deliverable, but "three Phase I trials completed according to the approved protocol" is. If you leave the number out, the client picks it later, and it won't be small.

Definition of done

Without acceptance criteria, "done" means "when the client stops asking for changes." Use checks that don't need a debate:

  • Approved in writing by the named approver.
  • Live on the client's domain, with all 6 pages loading and the contact form sending to the agreed inbox.
  • Final logo files delivered in SVG, PNG and PDF.

US federal contracting leans the same way: FAR 37.602 asks for work described in terms of required results, not how it's done or the hours spent, with measurable performance standards. If you can't check it, you can't close it.

Not included

The section most scopes skip, and the one that prevents the most "I assumed..." conversations. Some typical exclusions:

  • Web: copywriting, stock photos, extra pages, hosting, maintenance after launch.
  • SEO: link building, content writing, technical fixes on platforms you don't control.
  • Social: community management, ad spend, video production.
  • Branding: printing, signage, extra concepts after one is chosen.
  • Development: integrations not named, support for old browsers, data migration beyond an agreed amount.

Say each one can be quoted separately.

Limits

A limit is what makes the next round or hour visibly extra. Count the rounds and define what a round is.

- Revisions included. + 2 revision rounds per deliverable. A round is one combined list of + changes sent in writing by the approver. Further rounds are quoted + before work starts. 

On a retainer, write the monthly hour cap and whether unused hours carry over.

Client responsibilities and assumptions

A lot of delay and creep comes from things the client was supposed to send. Say what they provide, in what form, and by when.

Then list the assumptions your price depends on. A PMI paper on scope statements describes an assumption as something believed to be valid that may not be; when it proves invalid, whatever depended on it has to change. Written down, a broken assumption becomes a reason to revisit scope rather than your problem to absorb:

  • Client provides final copy for all pages before design starts.
  • The site runs on WordPress with the existing theme.
  • One person on the client side gives feedback and approves each stage.
  • Feedback within 5 business days. Later feedback moves the timeline by the same number of days.

Timeline and sign-off

Tie dates to inputs ("first designs 10 business days after we receive all content") so a late client doesn't make you late. And name the approver. "The client" isn't a person; a name and job title is. When a new stakeholder appears in week six, the scope says whose sign-off counts.

Changes

Scope will change, and that's fine. What matters is that every change takes the same path: one place to send it, a check against the scope, and a written quote approved before work starts. Write that path down in plain words.

Lint the wording

Treat vague words like a linter treats unused variables. Anything that needs an opinion to measure ("as needed", "minor", "etc.", "support", "ongoing") gets replaced with a number, a list or a date, plus what happens past the limit. A line is fixed when two people reading it separately reach the same answer about a new request.

The US Department of Defense's handbook for preparing statements of work (MIL-HDBK-245D) flags "any", "assist", "as required", "as applicable", "as necessary" and "as directed". It says "including but not limited to" creates ambiguity (only list known requirements), that "etc." brings in unidentified requirements, and that "support" is ambiguous unless you say what kind. It also tells a story worth remembering: an engineer wanted a damaged roof edge repaired and repainted, wrote "match existing", never wrote "repaint", and the contractors matched the flashing and refused to paint it.

Some before/after lines (the numbers are placeholders; use your own):

Area Vague Checkable
Web design "A website with all the pages you need" "Up to 6 pages built from 3 templates. More pages are quoted separately."
Web design "Fully responsive" "Layouts checked at 375px and 1440px widths in current Chrome and Safari."
Development "Integrate with their systems" "Connect the contact form to one existing HubSpot list. Other integrations are quoted separately."
SEO "SEO optimization" "Title tags and meta descriptions for 15 existing pages, plus one keyword report a month."
Content "Blog content" "2 articles a month, 1,200 to 1,500 words each, one round of edits per article."
Support "Ongoing support" "Fixes to delivered work for 30 days after launch. New features are quoted separately."
Feedback "Client will review promptly" "One combined set of feedback per round, within 5 business days."
Lists "Including but not limited to X, Y, etc." "X and Y. Anything not listed here is quoted separately."

Three habits from the same handbook: use the same word for the same thing every time (don't drift between "page", "screen" and "view"), avoid "and/or" and "either", and repeat the noun when "it" could point at two things.

How long should it be?

Long enough that every deliverable has a number and a finish line, short enough that the client actually reads it. Duncan says most scope statements "can be done well in a page or two."

Too thin: a deliverable with no number, no exclusions, revisions mentioned but not counted, dates that don't depend on client inputs.

Too heavy: your internal task list, legal terms already in the contract, or so many pages nobody reads it before signing.

If you can't get that specific because the client doesn't know what they want yet, that's a sign you need a short paid discovery stage first.

Projects vs retainers

One-off project Monthly retainer
Deliverables A fixed list with a finish line A menu per month ("up to 4 content edits, 1 report")
Limits Revision rounds per deliverable Hour or quantity cap per month, plus rounds
Unused capacity Not relevant Say whether hours roll over, and for how long
Ends when All deliverables are accepted The term ends or someone gives notice
Typical creep Extra pages, features, rounds "Small" asks that add up past the cap

"Website updates as needed" on a care plan is the retainer version of "all the pages you need."

A worked rewrite (hypothetical)

This is a made-up example with round numbers, not a real client. A two-person studio quotes $4,000 for a brand identity for a new cafe. The first draft says:

Logo design and brand identity, including colours, fonts, etc. Revisions included. Deliverables provided in all formats. Timeline: around 4 weeks.

Read it as the client: "brand identity" could cover a menu and signage, "etc." could cover anything, "revisions included" sounds unlimited, "all formats" could mean an animated logo, and "around 4 weeks" starts whenever.

The rewrite:

  • Goal: a logo and basic brand kit the cafe can use on signage, menu and Instagram from opening day.
  • Deliverables: 3 initial logo concepts on one video call; 2 revision rounds on the chosen concept (a round is one combined list of changes from the owner); a palette of up to 5 colours with HEX and CMYK; 2 fonts from free or client-licensed families; a one-page brand sheet; final logo files in SVG, PNG and PDF, in full colour and black and white.
  • Not included: menu design, signage, packaging, social templates, photography, printing, font licence fees, further concepts after one is chosen. All can be quoted.
  • Client provides: a short brief and 3 to 5 reference brands within 3 business days of kickoff; one combined set of feedback per round within 5 business days.
  • Timeline: concepts 10 business days after the brief; finals 5 business days after the last approved round. Late feedback moves dates by the same number of days.
  • Changes: new requests go by email; anything outside the list gets a written quote and starts only after the owner approves.

In week three the owner asks for a menu layout. It's under "Not included", so it gets a quote. Later they want a third round. The scope says two, so that's a quote too, a flat $300 they can take or skip. Neither is an argument, because the answer was already written down.

Test it before you send it

Take three to five awkward requests from past clients and check each one against the draft using only what's written. If you can't say "included" or "extra" from the page alone, that line needs work. Then ask someone who wasn't on the sales call to do the same.

Pre-send checklist:

  • [ ] Every deliverable has a number or limit
  • [ ] Every deliverable has a finish line (who approves, in what form)
  • [ ] There's a "not included" list
  • [ ] Revision rounds are counted and defined
  • [ ] Client inputs have due dates, and the timeline depends on them
  • [ ] One approver is named on the client side
  • [ ] There's a written rule for extras: requested in writing, quoted, approved before work
  • [ ] No vague words left: "as needed", "minor", "etc.", "support", "ongoing", "unlimited", "including but not limited to"

The past-requests test matters more than any checklist, because it's the same check you'll be doing every week once the project starts. If you'd rather start from a filled-in structure, there's a free scope of work template.

Easy mistakes

  • Writing the scope after the price. The scope stretches to fit what the client thinks they paid for. Describe the work, then price it.
  • Copying sales language. "A modern, high-converting website" sells. It doesn't scope anything.
  • Hiding limits in the small print. Put them next to the deliverables.
  • Never mentioning the scope again. Walk through it at kickoff, especially the exclusions.
  • Saying yes before checking. Look it up before you agree on a call, not after.

Originally published at creepless.online. This version was drafted with AI assistance.