What to Do When a Client Stops Responding Mid Project
by Eric Hanson, Backend Developer at Clean Systems Consulting
A client going silent mid-project is more common than it should be, and riskier than it looks. Here is how to handle it without losing the engagement or the payment.
Why Clients Disappear
The contractor who has been waiting five days for a client to respond to a critical question knows the particular discomfort of mid-project silence. The work is blocked. The deadline is still real. And there is nothing to do but wait and wonder.
Clients go silent for various reasons:
- Overwhelmed and deprioritizing the project without meaning to.
- Dealing with an internal issue that has nothing to do with you.
- Uncertain how to answer the question you asked and avoiding rather than admitting it.
- Losing confidence in the direction of the project.
- In a worst case, financial or business problems that make the engagement itself uncertain.
Most disappearances are the first two — the client is busy and the contractor's message got buried. This is not malicious. It is just real.
The First Response: One Nudge
If a client has not responded within the expected window (usually 24 to 48 hours for something time-sensitive), one clear, direct follow-up is appropriate:
"Following up on my message from [date]. I need [specific thing] before I can proceed with [specific part of the project]. If this is the blocker, just let me know and I'll adjust accordingly."
That message is direct, not passive-aggressive. It states exactly what is needed and why. It also implicitly signals: this is affecting delivery, so you need to respond.
When the Silence Continues
If a second message goes unanswered after a few days, the dynamic has shifted. This is no longer a missed message — it is a pattern.
At this point, two things need to happen:
Stop active work on the blocked portion. You cannot be held responsible for a delayed deliverable if the delay is caused by the client's non-response. Document this explicitly: "I've paused work on [component] pending your response on [question]. I'll resume as soon as I hear from you."
Escalate to a different channel. If you have only been using email, try phone or text. If there is another contact at the company, copy them in. A message that says "I've been trying to reach [name] about [project] — wanted to make sure this hadn't fallen through the cracks" is professional and occasionally more effective than another message to the primary contact.
The Financial Risk
Extended client silence creates a financial exposure, particularly in project-based engagements. If the project stalls for weeks and then the client reappears with changed requirements, you may have lost significant time without compensation.
This is where payment structure matters. Milestone-based payments that release upon completion of defined stages protect you from doing half a project for a client who then disappears. If you do not have milestones built in and silence is persisting, it is reasonable to request that outstanding invoices be settled before work resumes.
When It Might Be Over
Sometimes extended silence means the project is effectively cancelled — the client has moved on or their situation has changed. If this happens without a formal communication, the contract's termination clause becomes relevant.
A message that acknowledges the situation directly:
"I haven't heard back from you in [X weeks], and I want to make sure we're aligned on where the project stands. If circumstances have changed and you need to pause or end the engagement, please let me know so we can handle it properly. My last invoice for [period/milestone] remains outstanding — I'd appreciate settling that before we close."
This is professional. It opens the door for the client to be honest, provides an off-ramp, and addresses the payment issue directly.
Do not chase indefinitely and do not just stop working without communicating. Either path creates ambiguity that is harder to resolve.
A client going quiet is not automatically a lost engagement — but it requires a response before it becomes one.