Stop scope creep with a change-request process clients accept

What scope creep is (and what it isn't)

Scope creep is the gradual growth of the work you do for a client without a matching change to what they pay or to the agreement. It happens in small steps: one extra post, a quick resize, "while you're in there" updates. Each is reasonable on its own, which is exactly why they add up unnoticed.

It isn't the same as a client asking for more. A client who wants more work and is happy to pay for it is a growth opportunity, not a problem. The problem is when extra work happens with no decision attached, so neither side knows the scope has changed until you're doing noticeably more for the same retainer.

It also isn't a reason to refuse every small favour. Agencies that treat a two-minute typo fix like a contract amendment come across as difficult. The goal of a change-request process is visibility: both you and the client can see when something is extra, what it costs, and choose.

Start with what's in scope

Check each client's agreement answers four questions:

1. What do you deliver? Specific outputs, such as "12 social posts per month across two platforms," not "social media management."
2. How many revision rounds are included?
3. What's explicitly not included? A few common exclusions (ad spend, photography, new platforms) save arguments later.
4. What happens when they want more? This is where your change-request process gets written in.

If an existing agreement is vague, don't rewrite it mid-contract. Send a one-page scope summary and ask the client to confirm it's accurate.

Decide what counts as a change

Request	How to handle it
Under 15 minutes, occasional	Just do it. Note it in your log.
Fits inside current scope (swaps one deliverable for another of similar size)	Agree the swap in writing. No extra charge.
Adds new work, a new platform or a new deliverable	Change request.
Repeats every month	Change request, and discuss updating the retainer.

The log matters even for small favours. If the same "quick" request shows up every week, you'll have the record to talk about it.

The change request itself

A change request needs what they asked for (in their words), what it involves, the cost, the timing, and a clear yes/no. A reply template:

Hi [Name],

Happy to help with [the request]. This one sits outside our current scope, so here's what it would involve:

• Work: [e.g. design and write three extra carousel posts for the product launch]
• Cost: [e.g. a fixed [price], added to this month's invoice]
• Timing: [e.g. ready by Thursday; doesn't affect the regular schedule]

Reply "approved" and we'll get started. If you'd rather swap it for something already planned this month, tell me which and we'll do that instead at no extra cost.

[Your name]

Pricing changes without negotiating every time

Type of request	How to price it
Common extras (extra post, ad variant, one-off report, rush turnaround)	Fixed price from a rate card shared at onboarding
One-off requests not on the rate card	Hours at your standard rate, with a cap ("about 3 hours, capped at 4")
Recurring extras	Propose an updated retainer

Introducing the process to existing clients

Bring it up when things are going well, not during a disagreement:

Hi [Name],

A quick process update. As we've grown, we've started logging requests that fall outside each client's plan, so nothing gets lost and you always know what something costs before we start.

From next month, if you ask for something outside our agreed scope, I'll send a short note with the cost and timing for you to approve first. Anything small, we'll keep just doing.

I've attached a one-page summary of what's in your current plan. Let me know if anything looks off.

[Your name]

When a client pushes back

If a client says "I thought that was included," go back to the scope summary they confirmed. If it's genuinely ambiguous, do that one request for free and clarify the scope for next time. If a client pushes back on every change request, the retainer may no longer fit what they need, and it's time to talk about a different plan.

Steps you can take today

1. Pick your two longest-running clients and write a one-page scope summary for each.
2. Start a simple log of every out-of-scope request this month, including the small ones you just did.
3. Save the change-request reply above as a template in your email client.
4. Draft a rate card with prices for your five most common extra requests.
5. Send the process-update email to one existing client this week, attaching their scope summary.

FAQ

How do I stop scope creep with clients?

Write down exactly what's in scope, decide which requests count as changes, and answer those with a short change request the client approves before you start. Log small favours so patterns are visible.

What is a change request in agency work?

A short written note for work outside the agreed scope, covering what was asked, what it involves, the cost, the timing and a yes/no. The client approves it before any work starts.

What should a change request include?

The request in the client's words, a one- or two-line description of the work, a fixed price or capped estimate, the timing, and whether it affects anything already scheduled. Offering a swap for planned work is a useful extra.

How do I tell an existing client about a change-request process?

Introduce it while things are going well, framed around clarity for them: they'll always know what something costs before you start. Attach a one-page summary of their current scope and ask them to confirm it.

Should I charge for small extra requests?

Not usually. Occasional requests under about 15 minutes are worth just doing, but log them. If a small request repeats regularly, raise it and price it.

How do I price extra work quickly?

Keep a rate card with fixed prices for your most common extras, and quote everything else as capped hours at your standard rate. That way you rarely need to negotiate from scratch.

What if a client says the extra work was included?

Check the scope summary they confirmed. If it's genuinely unclear, it's often worth doing that request for free and tightening the wording for next time.