What to Do When a Client Ghosts Mid-Project

You sent the mockups. You asked for API keys. You noted the blocker in last week's update. Now it is Wednesday and the thread is dead. When a client ghosts mid-project, your brain fills the silence with worst cases — they hate the work, they found someone cheaper, they forgot you exist.

Usually it is simpler. They are underwater, the decision got stuck in internal approval, or your ask landed in the wrong inbox. Either way, your job is to make silence expensive to ignore without sounding desperate.

Step one — one clear blocker message

Do not send "just checking in." Send structure:

I am blocked on until I have {specific item}. Without it by , moves to {new date}. Reply with or tell me who else can provide it.

One ask. One date. One consequence. That pairs with how often to send status updates — do not wait for Friday if you are stuck on them today.

Step two — escalate on a ladder, not a flood

Use a predictable sequence:

| Day | Action | | --- | --- | | 0 | Blocker email with needed-by date | | +2 business days | Same thread, shorter — "Still need X to proceed" | | +5 business days | Copy their manager or project lead if you have a name | | +7–10 days | Pause note — work stops until reply; timeline resets |

Same subject line. Same facts. You are building a paper trail, not venting.

If you manage several accounts, log the follow-up date so one ghost does not eat the whole week — part of managing multiple clients.

Step three — pause work deliberately

Continuing to build while they ghost is how freelancers eat scope and miss other clients' deadlines.

Pause when:

• You need a decision before the next billable hour makes sense
• They are past an invoice date with no acknowledgment
• Continuing would commit you to a launch date they never confirmed

Your pause email is professional:

I am pausing active development until we reconnect on . When you are ready, we will re-baseline dates from that point.

That protects you and gives them a clean re-entry.

Document everything for payment disputes

Keep:

• Sent deliverables with timestamps
• Blocker messages and replies (or lack of)
• Contract clauses on client delays and payment terms

If they reappear angry that "nothing happened," your thread is the story. For delivery slips caused by their silence, see why freelance developers miss deadlines — early, documented, with a new plan.

Ghosting clients stall your whole queue.

WorkFocus tracks blockers and follow-ups per client so silence does not disappear into one long Slack scroll.

Try WorkFocus free

When ghosting means the engagement is over

Sometimes they do not come back until you invoice for work they never approved. Sometimes they reappear months later expecting you to be free.

Decide in advance:

• Minimum restart fee or re-onboarding block
• How long you hold their slot before taking other work
• Handoff policy if they want files without settling open invoices

You are a business, not an on-call friend.

The bottom line

What to do when a client ghosts mid-project:

• Send one structured blocker message — need, date, consequence
• Escalate on a schedule — not daily anxiety pings
• Pause billable work when silence creates unpaid risk
• Keep a written trail for timeline and payment conversations

If you want blockers and follow-ups visible across clients instead of buried in threads, try WorkFocus free. See what is stuck, who owes you what, and what actually moves today.