The workshop design took longer than planned. The client’s second site wants its own sessions. The sponsor who agreed the brief has moved on, and the new one wants something different.
Every consultant, coach and learning provider knows the moment. The plan you sold no longer fits the work, and you have to decide what to say.
When should you tell the client?
As soon as you know the plan has changed. Not when you’ve worked out every detail.
The pull is to wait. You want to arrive with the new cost, the new timeline and a solution. You hope another week will make the old plan work after all. But every day you wait, the client is making decisions based on something you know isn’t true any more.
Why do we put it off?
Because passing on bad news is uncomfortable, even when it isn’t your fault.
Psychologists have a name for it: the MUM effect, our reluctance to deliver unwelcome information. For a consultant there’s an extra fear. Raising a change can sound like you mis-scoped the work, or like you’re angling for a bigger fee.
So the conversation gets softened, delayed or buried in a progress report, and the client finds out later than they should.
What does waiting cost?
More than the change itself.
A missed date or a bigger budget is a problem. Finding out that the provider knew and didn’t say is a different kind of problem. In one study, trust damaged by unreliability recovered as behaviour improved, while trust damaged by deception did not recover, even after good behaviour. A client who discovers a late surprise often starts to wonder what else they haven’t been told.
Research with clients and consultants found that trust is built through what the consultant does: showing they’re able, showing integrity, and showing they have the client’s interests at heart. An early, honest warning does all three at once.
How does the client hear “scope creep”?
Not the way you do.
Providers talk about scope creep, change requests and additional fees. Clients hear different questions: why doesn’t the original agreement cover this? Is this fair? Did they get it wrong at the start? Are they protecting themselves at my expense?
A reset lands well when it answers those questions, not when it defends your position.
What should you say?
Keep it plain, early and fair. A useful structure:
- What’s changed. The facts, including anything you got wrong. “The design needs two more days than I estimated, because the second site has different needs.”
- Why it matters. What it affects: time, cost, quality or what’s possible.
- The options. Usually more than one. Keep the scope and move the date, keep the date and reduce the scope, or add budget.
- Your recommendation, and your reasoning. Explanations matter. People who understand why a decision was made tend to trust more afterwards.
- What you need from them, and by when.
Then put it in writing, so you both have the same record.
Which trust behaviours does this use?
Several of the behaviours that strengthen trust:
- Give updates on progress and raise issues early when there are risks or delays.
- Say clearly when something cannot be delivered.
- Explain the reasoning behind decisions that impact others.
- Share relevant information openly, not selectively.
And one that prevents the next reset: only agree to what you can realistically deliver and control.
What about the next piece of work?
The best time to prepare for a reset is before the work starts.
Agree at the outset how changes will be handled: who you’ll tell, how quickly, and who decides. Name your assumptions in the proposal, so a changed assumption is something you both recognise rather than something you have to prove.
None of this guarantees a client will be happy about a change. What it does is give them a reason to keep relying on you when it happens. In client work, that’s what turns a proposal into a partnership.