Radio Silence Isn’t a Sign-Off: A Mid-Project Protocol for Clients Who Vanish

When a client goes quiet halfway through a project, the first few days feel like a glitch. You check your sent folder. You refresh your inbox. You wonder if your last email was too long, too short or somehow landed in spam. Then a week passes and the project is just... sitting there.

The temptation is to either chase daily or quietly panic. Neither helps. What helps is treating silence as a project state with its own process. Not a personal rejection, not a reason to write off the relationship, and definitely not a reason to keep working for free in the hope that enthusiasm will bring them back.

Separate quiet from gone

Before you build an exit plan, check the obvious. Is the client on annual leave? Did they mention a hospital appointment, a house move or a mad week at work? Look at your last exchange. If they asked a question and you answered it, the ball is in their court. If you asked a question and they didn't answer, the ball is still in theirs, but you need to make that visible.

A useful rule: quiet is normal for three to five working days. Gone is when you have sent two clear prompts and received nothing for two weeks. Between those points, you are not ghosted. You are waiting.

The check-in ladder: three touches, then a decision

Don't send a daily nudge. It makes you look anxious and gives the client more email to avoid. Use a ladder instead, with each rung slightly firmer than the last.

Working day 3: the light touch. Reply in the same thread. Restate the one thing you need and why. Keep it to three sentences. Example: 'Just checking in on the logo route — I need your pick between A and B by Thursday to keep the website build on track.' No guilt, no essay.

Working day 7: the specific prompt. Now list what is waiting and what happens if it stays waiting. Bullets are good. 'I have the homepage and two inner pages ready for review. The next stage is development, which needs your sign-off. If I don't hear back by [date], I'll move the project to paused status so I'm not holding studio time.' This is not a threat. It is a calendar fact.

Working day 14: the formal pause. Send the pause notice and invoice. More on both below. This is the rung where you stop being available for this project and start protecting your own time.

Working day 21: the archive note. A short final email confirming the project is paused, files are archived and nothing further will happen until they reply. Then stop. Put a reminder in your diary for 30 days.

Pause the project in writing

A pause notice does three jobs: it records the date, it sets out what is complete and outstanding, and it tells the client what happens next. Keep it plain. 'As of 14 November 2026, work on [project] is paused. Completed: [list]. Outstanding: [list]. I will need [x] working days' notice to restart.' Add where the files live and how to reach you.

If your contract has a pause or suspension clause, quote it. If it doesn't, this email still creates a useful paper trail. It shows you didn't abandon the job. You simply stopped making assumptions on the client's behalf.

Invoice the work that exists, not the work you hoped for

The pause email is the right moment to invoice. Not the final invoice for the whole project, unless the contract says otherwise. Invoice the completed milestones, the deposit if it was earned on kick-off, and any agreed time you have already spent. If you work hourly, invoice the hours to date. If you work in stages, invoice the stage you finished.

Don't invent a 'ghosting fee' unless your contract already includes one. Don't invoice future work you haven't done. And don't sit on an invoice because you're worried it will look pushy. A paused project with an unpaid invoice is just a cash-flow problem with extra admin. Send it with your normal payment terms and a polite line: 'This covers work completed up to the pause date.'

If the client returns later, you can agree a restart fee or a new timeline then. That is a separate conversation.

Archive like someone else will open it

A paused project should be easy to restart and easy to hand over if it never restarts. Create a folder named something like PAUSED_ProjectName_2026-11-14. Put in the brief, contract, invoices, key emails, source files, exports, fonts and asset notes. Keep a read-only copy in cloud storage and a local backup. Don't delete the folder in a huff. Don't move files into a personal 'dead projects' pile where you'll forget them.

Set a diary reminder for 30, 60 and 90 days. After that, follow your normal retention policy. If the project contains personal data, keep it only as long as you need it and follow your usual GDPR housekeeping. The point is simple: if the client emails in March asking to pick things up, you should be able to open one folder and know exactly where you left off.

The closing email that leaves the door open

Here is a short template. Adjust the details, keep the tone even.

Subject: Project [name] — paused as of [date]

Hi [Name],

I've tried to reach you on [dates] about [specific decision]. As I haven't heard back, I'm pausing work on [project] from [date] so I'm not making assumptions on your behalf.

Here's where things stand: [completed work] is done. I'm waiting on [outstanding item]. I've attached invoice [number] for [amount], covering work completed to the pause date. Files are archived and ready to restart; I'd need [x] working days' notice to pick things up again.

No hard feelings — projects stall for all sorts of reasons. If you'd like to continue, just reply and we'll reset the timeline. If the project isn't going ahead, let me know and I'll close the file.

Best, [Your name]

That last paragraph matters. It closes the loop without slamming the door. You are not chasing. You are not sulking. You are telling the client exactly how to come back.

Prevention beats a perfect exit

The best exit plan is a contract that expects silence. Put milestone invoices in the schedule. Agree a decision deadline for each review round. Say what happens if feedback doesn't arrive. Take a deposit that covers the first stage. None of this guarantees a reply, but it makes the quiet far less expensive.

A vanishing client is rarely about you. Usually it's a budget freeze, a reorganisation, a life event or a project that lost its internal champion. Your job is not to guess which. Your job is to pause cleanly, invoice fairly, archive properly and leave a clear way back. That is the graceful ghost: no drama, no disappearing act of your own.