How to stop scope creep: the four sentences that do the work

Scope creep is stopped in writing, before the project starts, in about four sentences. Everything else — the kickoff conversation, the polite pushback, the moment you decide whether this one is free — is downstream of whether those sentences exist. This post is the sentences.

Which is worth saying plainly, because the genre mostly isn't. Read the well-ranked guides on this query and you will find a great deal about communicating early, educating your client, and learning to say no, and almost no actual words you could paste into a document tomorrow. The frameworks are fine. They are also the easy part.

Sentence one: what the scope line says

A young designer delivered a UI project the client praised, along with demo HTML to show it working. The client then refused to pay, because the agreement said the work was "supplied as HTML and CSS" and the demo, apparently, was not production-ready. He lost about a grand and got a lecture about how the lesson was worth more than the invoice. He tells it in the Clients From Hell archive, and says ironclad contracts since have saved him hundreds of thousands.

The clause that beat him was five words long and meant two different things to two people. So write the scope line to be boring and countable:

Three homepage concepts, one taken to full design across five page templates, delivered as a Figma file plus exported assets. Copywriting, photography, and CMS build are not included.

Counts and named artefacts. The second half is the half people skip, and it is the half that does the work: a list of the neighbouring things this project is not. You cannot creep into a room whose door is labelled.

Sentence two: the revision cap, and what a round means

Two rounds of revisions are included. A round is one consolidated set of feedback from your side; further rounds are billed at the rate below.

Naming the number is the well-known advice. Defining the unit is the part that actually holds. Two rounds where a round means "one email from the marketing lead, then another from her boss on Thursday, then three more when the founder gets back from leave" is not two rounds. It is however many people are in the room, times however long they take, and it is the single most common way a fixed fee turns into an hourly job at a rate you would refuse.

Give the extra round a price and put it in the same sentence. A round with a number next to it is a decision. A round without one is an argument.

Sentence three: the change order

When the request lands, the reply is one short note, and it is friendly. Say the client asks for a pitch deck on a project scoped as five page templates:

Happy to add the pitch deck. That is outside the five templates we scoped, so it is +$900 and pushes delivery to the 14th. Want me to go ahead?

Three facts and a question. No sigh, no lecture about scope, no invitation to debate whether it counts as extra. The client is not being told off; they are being quoted. Most of them say yes, which is the outcome you wanted, and the ones who say no were never going to pay for it and have now decided that themselves rather than making you decide it for them.

I will spend longer on this than the section deserves, because it is where the money is and where the advice is thinnest. Send it the same day, before you do the work. A change order sent afterwards is an invoice for a favour, and it reads that way. Send it in writing even when the client is standing next to you and it feels absurdly formal, because the reason it feels absurd is that it is a small amount of money, and small amounts of money are precisely what this problem is made of. And send it for the twenty-minute ones too, occasionally priced at zero and shown as zero, so the client can see what they are getting free. A line that reads "additional logo variant — no charge" is worth more to the relationship than silently absorbing it, and it establishes that the meter exists.

Sentence four: the kickoff warning

If anything comes up outside what we scoped, I will send you a quick note with the price and the new date before I start it, so there are no surprises on the invoice.

Said out loud in the kickoff call, and again in the first email. Thirty seconds, and it converts every later change order from a confrontation into a thing you told them you would do.

What the numbers actually say

You will see it claimed that 72% of projects experience scope creep, usually attributed to the Project Management Institute. It is not their figure and we could not trace it to any research at all. The real PMI number, from their 2018 Pulse of the Profession, is around half of projects — and it covers project management broadly rather than creative work specifically, so treat it as weather rather than a benchmark for your studio.

That gap between the quoted number and the real one is the tell for this whole category of advice. When a page has a suspiciously satisfying statistic and no words you can use, the statistic is doing the work the words should be doing.

If it has already happened

You are past prevention, so pick one and mean it. Absorb it and say nothing, which is fine occasionally and corrosive as a habit. Absorb it and name it once ("that one is on me, but the next set of changes I'll need to quote"), which resets the boundary at the cost of one slightly awkward sentence. Or stop and quote, which is right when the remaining work is bigger than the goodwill.

What does not work is the fourth option, doing it while resenting it, and then being unavailable for two weeks.

The scope line and the revision cap both belong in the proposal, not in a separate contract nobody opens — what belongs in a freelance design contract covers where each one lives, and the change-order template is the note above with the blanks left in. When North drafts a proposal from your call notes it writes the scope line and the revision cap as part of the price, and flags the request that falls outside them later.

Write the four sentences once. Reuse them forever.