How to handle scope creep with clients (and keep them)

First, be precise about what you are handling

PMI's Pulse of the Profession 2018 describes scope creep as scope that expands without any matching adjustment to time, cost or resources. Read that definition slowly, because the second half is the whole point. A client asking for a fourth page is not scope creep. A fourth page delivered on the budget and the deadline of three is.

That distinction changes the goal. You are not trying to stop clients from wanting things — wanting things is why they hired you. You are trying to make sure every change arrives with its own time and its own price attached, or is given away on purpose.

That is a survey of project work in general, not of agencies, and it is still the most useful base rate available. The same report splits respondents into high performers and low performers, and the gap is smaller than you would hope.

So the realistic target is not zero. Even organisations that are demonstrably good at delivery see a third of their projects drift. What separates a profitable agency from a busy one is what happens next. It helps to sort every extra request into one of three kinds before deciding anything:

• A clarification. The client is asking for something the proposal already covers, in words you did not use. No change, no price — just confirm it is included.
• A small favour. Genuinely outside the baseline, genuinely small, and you choose to absorb it. Fine, as long as it is a choice and you say so.
• A change. Outside the baseline and big enough to move time or cost. This one gets a price, a date and an approval before anyone starts.

Before the project: sell a baseline you can count

Most scope arguments are lost at the proposal stage, weeks before the first extra request. If the proposal says “website redesign”, nearly anything a client asks for is arguably inside it, and you will be negotiating from a feeling. If it says five page templates with two revision rounds each, a sixth template is a fact.

A baseline you can defend has five parts:

• Deliverables by number. Five page templates, twelve social posts, one brand guideline document. Units somebody can count without asking you what you meant.
• Revision rounds per deliverable, and what a round is. A round is one consolidated set of feedback from the client, not every separate email. Without that sentence, “two rounds” quietly becomes eleven messages.
• Who approves. Name the person whose sign-off closes a round. A second stakeholder who appears in week four with a different opinion is the most common source of an extra round.
• What is excluded. Copywriting, stock photography, hosting, migrations — whatever clients most often assume is included in your kind of work. A short exclusions list prevents more arguments than a long scope list.
• How changes work. One sentence that describes the change process itself, so that using it later is the agreement working rather than you being difficult.

When the first extra request arrives

It is worth knowing where extra requests come from, because it sets the tone of your reply. The PMI report notes that its earlier research found the top three reasons projects fail — a change in the organisation's priorities, a change in project objectives, and poor requirements gathering — all feed uncontrolled scope. In other words, most scope creep comes from a client whose own situation moved, not from a client trying to get something for free. Reply to the situation, not to a suspicion.

The first extra request in a relationship sets the pattern for every one after it, so handle it deliberately:

1. Acknowledge it the same day, without saying yes or no. “Got it — let me check this against what we scoped and come back to you tomorrow.” That buys time without making a promise.
2. Check it against the baseline. Is it a clarification, a small favour or a change? If you cannot tell, the baseline was not countable, and that is a note for the next proposal.
3. Reply within one working day, with a price or a swap. One or two sentences, not a document. The details can follow once the client says yes.
4. Get a written yes before anyone starts. A reply to your email is enough to point to later. A “sure, go ahead” on a call is not.
5. Log it, whatever the answer. Date, request, what you decided. Favours included — the log is what makes the next conversation about facts.

Why a day matters is a mechanism rather than a measured result — we found no study that puts a number on it. A change priced while the client is still deciding whether they want it is a quote, and a quote is a normal part of buying something. The same change priced after the work has shipped is a bill for a favour they thought they already had, and that conversation goes badly for reasons that have nothing to do with the money.

What to say: four replies that keep the relationship

Most agency owners do not avoid change orders because they are afraid of money. They avoid them because they do not have the sentence ready. Here are four, with illustrative prices — use your own numbers.

The yes, with a price

“Happy to add a pricing page. It is outside the five templates we scoped, so it would be $900 and would move launch by three days. Shall I book it in?” Notice what that sentence does: it says yes first, names the baseline, gives a number and a date, and ends with a question the client can answer in one word.

The swap

“We can do the pricing page inside the current budget if we drop the careers page, which we haven't started. Which would you rather have?” The PMI report cites the agile practitioner Jesse Fewell making the same point: a deliverable that has not been started can be traded for something of equal or lesser cost without changing the budget. Swaps work well with clients whose budget is genuinely fixed.

The later

“That's a good idea, and I don't want it to slow the launch. Let's ship what we scoped on the 12th, then I'll quote the pricing page as a follow-up.” This one protects the deadline and often turns into a second project rather than a lost argument.

The deliberate favour

“This one is on us — it's small, and you've been great to work with. Anything more on that page would be a change order.” A favour you name out loud buys goodwill. A favour nobody mentions buys nothing, and it quietly teaches the client that the baseline is soft.

Two replies to retire: “no problem”, with nothing after it, and “we'll sort it out later”. Both feel kind in the moment. Both move the money conversation to the point where it is hardest to have.

Charging for the change without the awkwardness

If this feels hard, you are in the majority. Ignition surveyed 273 agency managers and executives for The 2025 Agency Pricing & Cash Flow Report, and most of them do not reliably charge for extra work.

The same survey puts a price on it: 57% of agencies lose between $1,000 and $5,000 a month on unbilled projects and tasks, and 30% say scope creep costs them more than $5,000 a month. Those are Ignition's respondents describing themselves, not a measurement of your agency — but they explain why the habit is worth building. A few rules make it far less awkward:

• Price in the first reply. A change order that arrives after the work is a debt collection. One that arrives with the answer is a quote.
• Use the rate from the proposal. A change order at a new, higher rate reads as punishment. The same rate reads as the agreement continuing.
• Don't discount it. A discounted change teaches the client that scope is negotiable. If you want to be generous, give the work away openly instead.
• Batch the small ones. Three tiny changes in a week are easier to approve as one short change order on Friday than as three interruptions.
• Keep it short. What changed, what it costs, what it does to the date, and a way to say yes. Anything longer loses to “let's just do it”.

On a retainer, scope creep is quieter and costs more

A project has an end, so drift eventually shows up in the final hours. A monthly retainer has no end. Every month a little extra becomes the new normal, and after a year the client is receiving noticeably more than they are paying for — and would be surprised to hear it. The fix is the same idea, applied to a month instead of a project:

1. Define the month in units. For example: twelve social posts, two blog articles, one monthly report, one strategy call. Not “ongoing social media support”.
2. Track usage against it every month. A one-line summary to the client — “this month: 14 of 12 posts, 2 of 2 articles” — makes drift visible to both sides before it becomes an argument.
3. Agree in advance what happens to overage. It is billed at the proposal rate, traded against next month, or declined. Pick one and write it into the retainer.
4. Re-scope every quarter. Bring the usage log. If the client consistently needs more, that is not a problem — it is a bigger retainer, and the log is the evidence for it.

When the client pushes back

Sometimes the client will say the extra work was always included. Don't argue from how the project feels; go back to the countable baseline and read it together. “The proposal lists five templates with two rounds each; this would be the sixth template” is hard to disagree with. “This is a lot more than we agreed” is easy to disagree with.

Then offer choices rather than a verdict: pay for it, swap it for something not yet started, move it to a later phase, or leave it out. A client who picks an option has made a decision. A client who is told no has lost an argument, and people remember losing arguments.

Be honest about your own mistakes, too. If the proposal clearly included something and you underestimated it, that is not scope creep — it is an estimating error, and it is yours to absorb. Saying so plainly is what makes your next change order believable.

Make it a habit first, then a system

The whole playbook fits on an index card:

• Sell a baseline in countable units, with rounds, approvers, exclusions and a change process.
• Sort every extra request: clarification, favour or change.
• Acknowledge the same day, reply with a price or a swap within one working day.
• Get a written yes before work starts, and log every request — favours too.
• Price at the proposal rate, never discount, batch the small ones.
• On retainers, track units monthly and re-scope quarterly.

None of this needs software. A shared document and some discipline will do it, and for a small studio with one or two projects running that may be enough. The trouble is that habits lose to busy weeks — the week two projects run long and the person who would log the request is the person putting out the fire.

That is the gap Tave is built for: the deliverable as the unit of work, watchers that compare what is actually happening against the baseline you sold, and a finding that turns into a change order your client can approve in one click. If you would rather start by seeing what unbilled work costs you, our scope-creep calculator does that arithmetic without asking for an email address. Either way, start with the card above. It is the part that matters.