Scope creep: 10 messages that stop it politely

Scope creep rarely arrives as one big request. It arrives as small ones: "Could you also tweak this?", "While you are at it, can you add that?" Each one seems reasonable, and each one is a little more unpaid work. By the end, a three-week project has become six weeks, and you are both unhappy.

The fix is not to become rigid. It is to respond to each extra request clearly and calmly, so the client always knows what is included, what is not, and what a change would cost. Below are ten messages you can adapt. Replace the brackets with your details.

First, know what the scope is

None of these messages work if the scope was never written down. Before you send anything, check that you have a document that lists deliverables, number of revisions, timeline and price. Even a half-page summary is enough. If you do not have one, send a recap now: "To make sure we are aligned, here is what is included in the project." Then continue with the messages below.

1. The friendly reminder

Use this when the request is slightly outside scope and you want to keep the tone light.

Happy to help with that. Just a note that [request] was not part of the original agreement, which covered [list]. I can add it for [price] and [time]. Would you like me to go ahead?

2. The two options message

Giving the client a choice keeps control in their hands without a refusal.

For [request], there are two options. Option A: I include it now and the delivery moves to [date], with an additional fee of [price]. Option B: we keep the current plan and add it as a second phase after launch. Which do you prefer?

3. The swap

When the budget or deadline is fixed, offer to trade instead of adding.

I can fit [new request] in if we remove [existing item] from this phase. Would you like to swap them, or keep the original list?

4. The "that is a new project" message

For larger requests that change the nature of the work.

This is a bigger change than a revision. It is closer to a new piece of work, so I would like to send a separate quote. I will have it to you by [day]. In the meantime I will continue with the agreed scope.

5. The revision limit reminder

Revisions are the most common source of creep. Mention the limit before it is used up, not after.

Just so you know, this is revision round [2] of the [3] included in the project. After the third round, further changes are billed at [rate]. If you can send all feedback in one message, we can make the most of the remaining rounds.

6. The clarifying question

Sometimes you are not sure whether a request is in scope. Ask, and write the answer down.

Before I start, can you help me understand whether [request] is meant to replace [existing item] or be added to it? That will help me confirm the timeline and cost.

7. The timeline impact message

Clients often do not realize a small change moves the date.

Adding [request] is possible. It would take about [time], so the new delivery date would be [date]. If the original date is fixed, I can instead [alternative]. Let me know how you would like to proceed.

8. The after-the-fact message

You have already noticed the work has grown. It is not too late.

Looking back over the project, we have added [A], [B] and [C] since the original agreement. I was glad to do it, and I want to make sure the paperwork matches the work. I will send an updated invoice covering these items. Please let me know if you have questions.

Use this one carefully and do it early. The longer you wait, the harder it is to explain.

10. The closing message

At the end of the project, set the boundary for the future without sounding cold.

The project is complete as agreed: [list]. Any further changes or additions can be handled as a new request, and I am happy to quote them. Thank you for the smooth collaboration.

How to use these without sounding defensive

Say yes to the person, not to the work. "Happy to help" and "I can do that" tell the client you are on their side. Then add the cost or time.

Be specific. "That is out of scope" sounds like a wall. "That would add three days and $150" is a decision the client can make.

Respond in writing. If a request comes by phone, follow up with a message that restates it and the price. This also builds the record you need if there is a disagreement later. For more on this, see our guide on getting client approval in writing.

Do not apologize for your terms. You are not asking for a favor. You are explaining how the project works.

Keep your tone consistent. If you are relaxed about small things for the first month and strict in the last week, the client will feel ambushed. Decide early what you include as goodwill, and say so: "Happy to include this small fix at no charge."

Need the messages ready to copy?

The Client Approval Log + 50 Client Messages pack collects short messages like these, grouped by situation, together with a log for recording approvals. Use the button below to see it on Gumroad.