How To Write A Scope That Stops Scope Creep

Every job that went sideways on me had the same cause. The scope said what we would do and never said where it stopped.

So when the client asked for one more thing, there was no document to point at. And there was no good way to say no without it feeling like a fight.

Write the exclusions

This is the whole trick. A scope with only inclusions is open ended, because anything not mentioned is arguable.

So after the list of what is included, there is a list of what is not. Plainly, without apology.

"Two rounds of revisions are included. Further rounds are quoted separately." "Copy for the five pages listed. Additional pages are quoted at the same rate." "We will not be managing the photography; we can arrange it as a separate scope."

Clients do not react badly to this. They react badly to being surprised by an invoice. A scope that states the edges makes you look like you have done this before.

Say it in deliverables and numbers

Vague scopes creep because nothing in them is countable.

"Social media management" creeps. "Twelve posts a month, three of them video, one round of amendments on each, scheduled by us" does not, because both sides can see when it is done.

Count everything that can be counted: pages, posts, revisions, meetings, reports, hours on site, days of shooting. Where something cannot be counted, define what finished looks like.

Define the approval points

Half of scope creep is really rework, and rework happens when nobody signed off on the step before.

So the scope names the gates. Concept approved before production. Copy approved before design. Design approved before build. Each one has an owner and a turnaround time.

And it says what happens when a gate is skipped. If the client approves the design and then changes the copy, that is a new round, and the scope said so before it happened. This is the same structure as what a good brief looks like, applied to the commercial side.

Put the client's obligations in writing too

Most delays are not on your side. They are waiting on assets, on access, on feedback, on a decision from somebody who is away.

So the scope says what the client provides and by when. Logos and brand files, access to accounts, product information, approvals within a stated number of business days.

And it says what happens if those do not arrive. Not as a threat. As a timeline that moves. That list is what to send an agency before you start written into the agreement.

Price the change, do not refuse it

Scope creep is not the client wanting more. It is the client wanting more for nothing, and that only happens when there is no mechanism for wanting more.

So there is one. A short variation note: here is the extra work, here is what it costs, here is what it does to the timeline, approve and we start. Sent the same day, not three weeks later with the invoice.

Done that way, extra work becomes extra revenue instead of a conversation nobody enjoys. And clients who are genuinely expanding the job appreciate the clarity, because they can decide.

The one page version

If your scope is twelve pages, nobody reads it and it protects nothing.

What works is one page: deliverables with numbers, exclusions, approval gates with dates, client obligations, and the variation process. Everything else is terms, and terms live separately.

That page goes in the proposal and it gets referred to on every job after that, which is why how to write a proposal that closes and the scope are the same document rather than two.

And when a project still goes wrong, the scope is what lets you work out whether it was the work or the fit, which is the question behind how to say no to a project and when to fire a client.