A direct script for handling scope changes without sounding rigid, defensive, or vague about the tradeoff.
Scope changes are not automatically a problem.
They become a problem when the consultant treats them as a favor, the client treats them as already included, and nobody names what changes in return.
Use a neutral opening
Start with the business reason, not the boundary:
"That can make sense. It changes the work in two ways: the deliverable expands, and the timeline needs a new decision point."
This keeps the tone collaborative while making the tradeoff explicit.
Offer three routes
Give the client a clean choice:
1. Replace an existing item with the new request
2. Add the request and extend the timeline
3. Add the request as a paid change order
This prevents the hidden fourth option: doing more work for the same fee and deadline.
Confirm in writing
After the conversation, send a short recap:
- what changed
- which route the client chose
- impact on timeline or cost
- next action
The recap is not bureaucracy. It is how you protect trust when memory gets selective later.
The goal is not to block change. The goal is to make change visible enough that both sides can make a clean decision.
[Handle consulting scope clearly](https://getconsultkit.com)
ConsultKit makes it systematic
From $9/month per app once your account is opened.
The Solo Consultant Brief
Weekly tips on referrals, pricing, and client management — straight to your inbox.
Prefer shorter ideas? Follow @getConsultKit on X.