What to Do When a Project Goes Silent Mid-Billing Cycle

You're three weeks into a project. Work is happening. Hours are piling up. Then the client goes quiet.

No replies to your check-in. No feedback on the last deliverable. Nothing.

This is one of the more disorienting situations in freelance work, because you're not sure whether to keep going or stop. And every decision you make during the silence has billing consequences.

The instinct to keep working is risky

When a client goes quiet, a lot of freelancers keep working. The deadline is still on the calendar. The scope is clear enough. It feels wrong to stop.

But here's the problem: if you keep logging hours on a project where the client has gone dark, you're accumulating unbilled work with no confirmation that they're still engaged. When they come back — and they usually do, often with a changed direction — you may have hours you can't recover.

Scope creep after silence is a real pattern. The client disappears, reappears with new ideas, and suddenly the work you did during the quiet period doesn't fit what they now want. You did it. You tracked it. But they'll push back on billing it.

Silence is a scope event

That sounds dramatic, but it's accurate. When communication breaks down mid-project, the scope is effectively on hold. What you should not do is treat it as business as usual.

Send one clear message. Not a follow-up chain, not a passive nudge. One direct note that says: I'm pausing active work until I hear back. Here's what I've completed so far, here's where I am in the budget, and here's what I need from you to move forward.

That message does three things. It documents your position. It shows professionalism. And it stops the hour count from running on a project that may be stalling or dying.

Your time records are your protection

If the project eventually comes back to life and the client disputes what you've billed, your only defense is a clean time record.

Memory won't cut it. A rough log won't either. What you need is a record that shows exactly when you worked, what you were doing, and how long it took. Session by session. Task by task.

Automatic screenshots are worth mentioning here. Not because you need to prove yourself to every client, but because when a dispute happens during a silence period, questions like "were you actually working on my project?" come up. Screenshots taken during your tracked sessions answer that without any back-and-forth.

Time-Trak captures those screenshots automatically while the timer runs. You don't have to do anything extra. They're just there if you need them.

What to bill when the client comes back

When they reappear, send a status update before anything else. Not an invoice. A summary of where things stand.

Here's what was completed. Here's the time logged. Here's where we left off. Does this still match what you need?

That conversation, done before you send a bill, prevents most disputes. The client sees the hours in context. They understand what they're paying for. And if the scope has shifted, you have a clean place to negotiate — or to say clearly that the new direction will cost more.

Don't assume the project died

Clients go quiet for a hundred reasons that have nothing to do with you. Budget freezes. Internal chaos. Someone went on leave. The project got deprioritized for a month.

But quiet doesn't mean you work for free. And it doesn't mean you keep running up hours on a project that may never resume.

Pause, document, communicate. Your time records tell the story of what happened. Make sure they're clean enough to tell it accurately, because when the client comes back, that story is the first thing that needs to be agreed on before any money moves.

Track your time, bill every minute.

Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.

Free during beta.

macOS + Windows · Floating widget · Auto screenshots