The scope document that prevents most client arguments
Scope creep is rarely a client behaving badly. It is usually two people who agreed on a sentence while imagining different things. “A modern website with a few pages” is a sentence both parties can sign and neither can deliver against.
The seven sections
1. The outcome, in the client's words
One paragraph on what the business gets: more qualified enquiries, fewer support calls, a working checkout. This is not decoration. When a dispute arrives, this paragraph decides which side a grey-area request falls on.
2. Deliverables, counted
Not “website pages” but “six page templates: home, service, service detail, about, contact, blog listing.” Not “logo design” but “one primary mark, two lockups, three file formats, one page of usage notes.” Counting is the single highest-value change you can make to a scope.
3. Explicitly out of scope
The section clients read most carefully and agencies write least often. State plainly what is not included: content writing, photography, translations, ongoing SEO, third-party licences, hosting fees, data migration from the old system, training beyond one session, support after handover. Every item you name here is an argument you will not have.
4. Assumptions and dependencies
What you are relying on: content supplied by a date, access to the existing hosting, one named decision-maker, brand assets in usable formats, timely feedback. Then state what happens when an assumption fails — usually the timeline moves rather than the fee.
5. Revisions, by number and stage
“Two rounds of revision at design stage, one at build stage.” Define what a round is: consolidated feedback from all stakeholders, delivered once. Ten separate emails over three days is not one round, and saying so in advance is much easier than saying it later.
6. Acceptance and handover
How the client signals a deliverable is accepted, what happens if they go quiet, what is handed over, and in what format. Add a deemed-acceptance clause: if no feedback arrives within an agreed number of working days, the stage is accepted. Without it, a silent client can stall a project and the final payment indefinitely.
7. Money and timing
Total fee, payment schedule tied to stages rather than dates, what triggers each invoice, late-payment terms, and who pays for third-party costs. Tie money to stage completion, so a paused project does not park your cash flow.
Handling change requests without conflict
The mistake is treating every new request as either a favour or a fight. Use a fixed, boring process instead.
- Acknowledge the request positively. It is usually a good idea.
- Compare it against the scope, out loud: this is a new deliverable, or a change to an accepted one.
- Quote it: cost, timeline impact, and what it displaces.
- Get written approval before starting.
- Log it in one running list attached to the project.
Clients almost never object to paying for extra work they asked for. They object to surprise invoices and to being made to feel unreasonable. A calm quote produces neither.
Phrases that reliably cause disputes
| Avoid | Write instead |
|---|---|
| “A few pages” | “Six templates, listed below” |
| “Modern, clean design” | “Direction approved from three concepts at stage one” |
| “Basic SEO included” | “Title tags, meta descriptions, sitemap, and one technical audit” |
| “Mobile friendly” | “Tested on current Chrome and Safari, iOS and Android, at three widths” |
| “Ongoing support” | “30 days of bug fixes for delivered features, defined as X” |
| “Fast website” | “Passes Core Web Vitals on the supplied content at launch” |
| “Content to be provided” | “Final content in one document by 12 March; later delivery moves launch” |
The awkward clauses worth including
- Ownership on payment. Intellectual property transfers when the final invoice clears, not on delivery.
- Third-party costs. Fonts, stock, plugins, hosting: whose account, whose card, whose renewal.
- Kill fee. What is owed if the client cancels mid-project. Percentage of the stage in progress is the usual answer.
- Pause clause. Projects dormant beyond a set period are re-quoted, because your costs and calendar moved on.
- Portfolio rights. Whether you may show the work, and when.
- Named contact. One person approves. Committee feedback is the leading cause of infinite revision.
Keep it short enough to be read
A twenty-page contract nobody reads protects you legally and fails you practically. Aim for a two-page scope in plain language that the client genuinely reads and can quote back at you, attached to whatever standard terms you use. Then walk through it on a call, out loud, before signing. Half of all future disputes surface in that conversation, when they are still free to fix.
Once a scope has done its job on three projects, it becomes a template. That template is one of the more valuable assets a small agency owns, and it costs one careful afternoon to write.
No company paid for placement in this article. Verify current prices and terms with each provider before buying.