There's a specific unease that comes with total silence, as distinct from a slow response. A client who takes two weeks to approve something is annoying but legible — you know roughly what's happening. A client who stops responding entirely, mid-project, with real deliverables and often real money on the line, leaves you without even that. Did something happen internally? Did they lose interest? Are they just extremely busy? You genuinely don't know, and that uncertainty is often worse than any single answer would be.
What's usually actually going on
Budget got reallocated internally, and nobody on your side of the relationship was told, because informing the freelancer wasn't high on anyone's list during an internal reshuffle.
The person you work with left the company or changed roles, and the project simply fell through the cracks of a handoff that never fully happened.
They're embarrassed about a delay on their end and are avoiding the conversation rather than sending an awkward “sorry, still not ready” update — silence can feel easier in the moment than admitting they're behind.
Something outside the project entirely — a personal or business crisis — has temporarily consumed their attention, with your project simply not being urgent enough to interrupt it.
None of these are things you can diagnose for certain from the outside. What you can control is a clear, professional sequence of your own, and — better still — a contract structure that removes the guesswork about when and how to act.
A follow-up sequence for genuine silence
First message (about a week of silence): Light, assuming good faith. “Hope things are going well on your end — wanted to check in on [project], no rush if you're just swamped.”
Second message (two to three weeks): More direct, naming the actual status. “Checking in again on [project] — it's been a few weeks since we last connected. Let me know if priorities have shifted or if you'd like to pick things back up.”
Third message (a month or more): State the practical consequence plainly. “I haven't heard back in [X] weeks, so I'll be pausing further work on this and releasing the time I'd blocked for it. Happy to pick it back up whenever you're ready — just let me know.”
If real money is outstanding: A separate, more formal message specifically about payment, distinct from the project status check-ins above — mixing an invoice reminder into a “just checking in” tone tends to undersell how seriously it needs to be taken.
A real dormancy clause structure, not a vague policy
Rather than deciding case by case when silence has gone on “too long,” some freelancers build the threshold directly into the contract, removing the ambiguity entirely. One concrete structure, used by a working freelancer and worth treating as an example rather than a universal standard: a 30-day dormancy period — if the project sees no meaningful forward progress or communication for 30 days, it's formally marked dormant — followed by an additional 15 days (45 days total) before the engagement is treated as expired, with no refund and no further deliverables owed.
This kind of two-stage structure does real work beyond just picking a number: the first threshold (dormancy) is a clear, unemotional flag — not a termination, just an acknowledgment that the project has stalled — and the second threshold (expiration) gives the client real, visible notice before anything final happens, rather than an abrupt cutoff with no warning built into the process itself.
Notice-period requirements are worth pairing with this. Across several independent sources describing standard freelance contract terms, a written notice period of 14 to 30 days before either party terminates shows up consistently enough to treat as a reasonable default — long enough to be fair, short enough not to trap either side in an unworkable arrangement indefinitely.
What a kill fee looks like, concretely
If a project genuinely ends mid-way, a kill fee — compensation for the freelancer's committed time even though the engagement didn't finish — is a common mechanism, though the exact structure varies. One published example: a kill fee of 25% of the remaining project value if less than half the project was complete at the point of termination, on top of payment for whatever was actually delivered. This is one freelancer's specific structure, not an industry-wide standard, but it illustrates the shape a fair kill fee often takes — tied to how much work was left undone, not a flat arbitrary number regardless of project stage.
A legal limit worth knowing before relying on these clauses
Here's something worth understanding honestly, rather than treating a dormancy or non-refundable-deposit clause as an unconditional guarantee: these clauses are not automatically enforceable in every circumstance. Contract law generally distinguishes between liquidated damages — a genuine, reasonable pre-estimate of the loss a cancellation actually causes — and a penalty, which courts in many jurisdictions can decline to enforce even when a contract's language calls it something else. A 100% non-refundable deposit on a project where essentially no real work had begun, for instance, risks being viewed as punitive rather than compensatory if it were ever actually challenged.
There's a related point worth knowing, and it cuts in a direction that's actually reassuring for the situation this article is about: these clauses tend to hold up far better, and are more clearly fair on their face, when real, substantial work was genuinely completed before they're invoked. A freelancer who did three weeks of real work before a client went silent has a much stronger claim to a dormancy-clause kill fee than one attempting to invoke the same clause after doing almost nothing — which is less a weakness in the clause itself and more confirmation that it's functioning as intended: compensation for real committed time, not a penalty for a client's silence alone.
None of this is legal advice, and enforceability specifics vary significantly by jurisdiction — but it's worth knowing the general shape of the limit before assuming a contract clause is an ironclad guarantee regardless of circumstances.
A worked example
A consultant completes two of four scoped milestones on a strategy engagement — roughly 18 hours of real work — before the client contact goes silent. Weeks one and two of silence pass with the standard follow-up sequence above; no response. At day 30, per the consultant's own dormancy clause, the project is formally marked dormant, and a note goes out: “Per our agreement, this project is now dormant due to inactivity — if I don't hear back within 15 days, the engagement will be considered concluded, with payment due for the two completed milestones.”
No response arrives. At day 45, the consultant invoices for the two completed milestones (not a made-up penalty, but the real, itemized value of the 18 hours of documented work), closes the engagement per the contract, and reallocates the blocked calendar time to other clients. Two months later, the original contact resurfaces, apologetic, citing an internal reorganization — the consultant, having handled the silence cleanly and been paid for real work already done, is able to respond warmly and requote the remaining two milestones as a fresh, small re-engagement, rather than facing an awkward negotiation over unpaid work from a stalled project.
When to actually stop working
If a deposit was paid and work is underway, continuing indefinitely without a response is rarely the right call — it ties up your calendar capacity on a project that may not resume, and if unpaid deliverables keep accumulating, your financial exposure grows the longer you continue. A reasonable line, whether set by the follow-up sequence above or a defined dormancy threshold: once the clause (or your own stated pause point) is reached, stop active work and move on, while leaving the door open for the client to restart later.
Protecting yourself before this happens
Milestone-based payment structures limit how much unpaid work can accumulate during a silent stretch. If payment is tied to completed milestones rather than one lump sum at the end, a ghosting client caps your exposure at whatever's currently in progress.
A visible project timeline that the client can check independently reduces the odds of true silence in the first place. Part of what makes ghosting easier is that nothing reminds the client the project exists between emails — a persistent, always-accessible portal link is a small but real counterweight to that.
SwiftSignoff's automated nudges continue on schedule even during a genuinely quiet stretch, without requiring you to remember to manually follow up while you're also managing the uncertainty of not knowing what's going on — and because every reminder and view is logged, if the relationship does eventually need a “here's what I attempted to reach you about, and when” summary (useful both for re-engaging the client and for supporting a dormancy-clause kill fee if it comes to that), that record already exists.
Related guideWhy clients go silent after you send a draft
FAQ
How long should I wait before assuming a project is dead?
There's no universal number, but many freelancers use somewhere around 4-6 weeks of total silence, after at least two follow-up attempts, as a reasonable point to formally pause and reallocate capacity — a dormancy clause with defined day-thresholds removes the guesswork entirely.
Is it okay to reach out through a different channel if email goes unanswered?
Yes — a brief text or a message through another platform, if you have one, is reasonable after email attempts haven't worked, especially for time-sensitive projects.
Should I invoice for work completed even if the client has gone silent?
Yes — send the invoice for whatever's been delivered regardless of their responsiveness; going silent doesn't remove their obligation to pay for completed milestones.
Is it worth trying to re-engage a ghosted client months later?
Often yes, especially if the silence was likely due to internal factors on their end rather than dissatisfaction — a brief, no-pressure “still around if you'd like to pick this back up” message costs little and occasionally successfully restarts a stalled relationship.
Is a non-refundable deposit or dormancy clause always enforceable, no matter what?
Not automatically — contract law in most places distinguishes a genuine pre-estimate of loss from a punitive penalty, and a court can decline to enforce a fee it views as the latter, particularly if very little real work was performed before the clause was invoked. This is general information, not legal advice, and it generally reinforces the case for these clauses rather than undermining it: they tend to hold up better, and are more clearly fair, when they reflect work genuinely completed.
Silence doesn't have to mean stalling indefinitely — especially once the threshold for it is written down instead of felt out in the moment.
PricingSee how automated nudges keep projects moving on the pricing page