← All Kits · All Guides · Data Migration Series

When the Client Goes Quiet

The project management half of the job, and the research behind it · Part of the Analyst Prep Kit

A client who stops replying is the most common reason a migration stalls, and the response most people reach for is a polite nudge that changes nothing. This article gives you an escalation ladder that works, the wording for each rung, and the evidence trail that protects you if the delay is ever reviewed.

The short version. Make the next action specific, attach an external deadline, then raise it to the person who owns the outcome. Keep every attempt where someone else can see it.

Why the polite nudge fails

Before the explanation: think about the last request you left unanswered. What would have made you answer it?

Usually two things. Knowing exactly what was being asked, and a reason it mattered this week rather than any week.

"Just checking in on the mapping document" has neither. It does not name an action, and it carries no consequence. Gollwitzer and Sheeran's meta-analysis of ninety four tests found that converting an intention into a specific plan of when, where and how produced a medium to large improvement in whether it got done. A vague nudge is the opposite of that, so it performs like one.

Rung one: make the action impossible to misread

Rewrite the request so it names the person, the action, the object and the day.

"Sarah, the mapping sheet needs a decision on the 14 rows highlighted in yellow. Could you send those back by Thursday the 12th? Everything else on the sheet is agreed."

Then say what it unblocks, in their terms: "That lets cleaning start on the 13th, which keeps the October go-live in place."

A surprising share of quiet clients are quiet because the ask was too big to start. Fourteen highlighted rows is startable. A four hundred row spreadsheet is not.

Rung two: attach a deadline that is not yours

Deadlines improve completion, and where they come from matters. Ariely and Wertenbroch found that people do set their own deadlines to manage procrastination, and that externally imposed deadlines improved performance more than self imposed ones.

So use the real external ones instead of inventing pressure. The contract end date. The client's own audit. The go-live date they chose. The point at which a resource is no longer available.

"Our contract runs to September 1st. After that, remaining work may carry additional cost. I would much rather finish inside it, and to do that I need those 14 rows this week."

That sentence works because it is true, it is not a threat, and the pressure belongs to the calendar rather than to you.

Rung three: raise it to whoever owns the outcome

Which of these three do you think moves a stalled project fastest: your contact's manager, the person who signed the contract, or your own account team? Decide, then read.

Usually the signer. Stakeholder salience theory explains why. Mitchell, Agle and Wood argue that a claim gets attention in proportion to three attributes held by the person making it: power, legitimacy and urgency. Your contact may have legitimacy and urgency but not the power to reprioritize their own week. The signer has all three, which is why a stalled project moves the moment they can see it.

Do it as a courtesy copy, not an escalation announcement. The email is addressed to your contact and reads exactly as it would have anyway. It states the goal date, what is outstanding, what it is blocking, and what you need. The signer reading it is enough. You never have to say that is why they are copied.

Tell your own side at the same time. Account management or client success should never learn about a stalled project from the client.

Be ready to be asked why it slipped

When a project goes late, someone eventually asks what happened, and both sides get asked. You need to be able to show three things without assembling them in a panic.

• You communicated consistently. A regular rhythm, not a burst of chasing at the end.
• Every request was specific. Named action, named person, named date. Which is exactly what makes them get done anyway.
• You replied quickly. Your own turnaround is the first thing checked, and it is the only part of this entirely within your control.

This is not defensive paperwork. It is the same behaviour that prevents the delay, kept where it can be read.

The wording, rung by rung

Move one rung at a time, with a week between, and never skip to the top. An escalation that arrives without the earlier rungs behind it damages a relationship you still need.

What not to do

Do not go quiet back. A stalled project where both sides stopped writing is one where you share the blame.

Do not keep working around them indefinitely. Filling the gap by guessing at decisions feels helpful and it produces work the client never approved, which becomes rework.

Do not let the tone drift. Every message stays warm and stays on their goal. The moment it reads as frustrated, the conversation becomes about the tone rather than the fourteen rows.

The one habit

Never send a nudge. Send a specific action, a date, and what it unblocks. That email is both the thing most likely to get answered and the thing you will be glad to have on file.

What has actually worked for you when someone stopped replying?

References

1. Gollwitzer, P. M., & Sheeran, P. (2006). Implementation intentions and goal achievement: A meta-analysis of effects and processes. Advances in Experimental Social Psychology, 38, 69–119.
2. Ariely, D., & Wertenbroch, K. (2002). Procrastination, deadlines, and performance: Self-control by precommitment. Psychological Science, 13(3), 219–224. doi:10.1111/1467-9280.00441
3. Mitchell, R. K., Agle, B. R., & Wood, D. J. (1997). Toward a theory of stakeholder identification and salience: Defining the principle of who and what really counts. Academy of Management Review, 22(4), 853–886.