Scope change response scripts
Short, non-aggressive replies for the chat moment when a new request lands and you have thirty seconds. Every script says yes to the client without starting unpaid work.
The default reply
Works in Slack, email, WhatsApp, and out loud on a call. When in doubt, send this one.
Yes, I can do that. It is outside the current scope, so I will send a quick approval with the price and timeline impact before I start. Once you approve it, I will schedule it in.
When they say it is just a small change
Do not argue about the size. Agree with it, then point at the process.
On its own it is small, agreed. I run every change through a quick approval anyway, so the budget and timeline never surprise either of us. Sending it over now, it takes one click.
When the deadline is already tight
Make the trade-off theirs to choose. Both options protect you.
I can add it, but not without moving the date. Two honest options: we keep the current deadline and park this for right after launch, or I add it now and delivery shifts by [3 days]. Your call.
When you choose to do it free
Free favors are fine when they are rare and visible. Say it out loud, or free becomes the default.
Done, no charge for this one, it took two minutes. Anything bigger than this will go through the usual quick approval first.
When they push back on paying
Stay on the facts: the agreed scope, the request, and the options.
I get that it feels like part of the project. The agreed scope is [five pages with two revision rounds], and this sits outside it. I would rather flag it now than surprise you on the invoice. Happy to price it, park it for later, or swap it for something of similar size inside the current scope.
Why this script works
The client hears a yes and a process, not a refusal. The approval step does the negotiating, so you do not have to.
Consistency is what trains clients. By the third time they hear it, they start asking what is in scope before they request.
Each approval is one more written agreement. If the project ever goes sideways, you have receipts instead of memories.
You are not judging the request or the client. You are running a procedure, and procedures are not awkward.