A client not responding on a freelance design job stops being "just busy" and becomes a follow-up problem on a fixed schedule: one check-in at day 3, a second, more direct message at day 7-10 naming what's blocked, and a final notice at day 14-21 that states the consequence in the contract and then acts on it. Guessing at how many times to nudge, or waiting indefinitely out of politeness, is what turns a stalled project into an unpaid one. The fix isn't a better message. It's a schedule you follow the same way regardless of how any single client feels about it, and a contract clause that tells you what happens when the schedule runs out.
Why This Needs a Schedule, Not a Feeling
Most designers handle an unresponsive client by instinct: wait a bit, send a friendly nudge, wait longer, feel increasingly awkward, and eventually either chase harder than feels comfortable or let the project quietly die. Both outcomes cost money. A schedule removes the guesswork by deciding in advance, before any specific client goes quiet, exactly when each follow-up happens and what it says.
This matters more for a solo practice than it would inside an agency, where a project manager or account lead would be the one deciding when patience runs out. Working alone, that decision is yours, and it's easier to make correctly when it's a rule you set once rather than a judgment call you make fresh, and under stress, every time a client goes silent.
The Follow-Up Sequence
| Day | What you send | What it does |
|---|---|---|
| Day 3 | A short, low-pressure check-in | Assumes good faith; costs nothing if they're simply busy |
| Day 7-10 | A direct message naming what's blocked and what it's costing the timeline | Moves from social to practical; still assumes good faith |
| Day 14-21 | A final notice referencing the contract term and stating the next step | States a consequence, then follows through on it |
The exact day counts can flex with the size of the project and how much is at stake, but the shape shouldn't. Three touches, escalating in directness, each one further apart than the last. Sending five friendly check-ins in a week reads as pressure, not professionalism, and it burns the goodwill you'll need if the client does resurface with a real explanation.
Day 3: The Low-Pressure Check-In
The first message assumes nothing has gone wrong. Most silence has a boring explanation: travel, an internal fire drill, an inbox that got away from them. A template:
"Just checking in, wanted to make sure this landed in your inbox okay. No rush, just flag me when you get a chance so I know where things stand."
This message does one job: it re-surfaces the request without implying anything is wrong. Sending it earlier than day 3 usually reads as impatient; sending it later starts eating into the timeline for no reason.
Day 7-10: Naming What's Blocked
If day 3 gets no reply, the second message changes register. It stops being purely social and states, plainly, what the silence is actually costing:
"Wanted to flag that this project is now on hold waiting on your input, and the [delivery date] we discussed is at risk the longer it stays paused. If something's come up on your end, happy to adjust, just need to hear from you so I can plan around it."
This does two things a friendly nudge doesn't. It names a real consequence (the deadline moving), and it invites an explanation without accusing the client of anything. Most clients who were genuinely just distracted reply here. The ones who don't are telling you something.
Day 14-21: The Final Notice
If the second message also goes unanswered, the third one is different in kind, not just tone. It references whatever your contract or agreement says about a stalled project, states what happens next, and then actually happens. A version that names a concrete step:
"I haven't heard back since [date], and per our agreement, a project on hold this long moves to [pausing further work / invoicing for time completed / a cancellation fee, per your terms]. I'm still glad to pick this back up whenever you're ready, just wanted you to know where things stand on my end."
The specific consequence depends entirely on what your own agreement with the client says, which is the honest limit of this article: it can describe the sequence and the tone, not the clause itself, because that varies by contract and by what was actually agreed at the start of the project. If a dormant-project term wasn't part of your original agreement, this is the gap that shows up the next time you're setting one up, covered in what belongs in a design brief.
What This Protects You From
Following a fixed schedule instead of your own patience protects you from two different failure modes at once. It stops you from chasing too hard, too early, which reads as desperate and can push a genuinely busy client further away. And it stops you from waiting too long out of politeness, which is the more expensive failure, because unpaid design hours sitting on a stalled project don't earn anything just by existing.
It also gives you something to point back to later. If the relationship does eventually need a hard conversation about payment for work already done, having sent three dated, professional messages on a known schedule is a much stronger position than "I emailed a few times and then gave up."
When the Client Resurfaces
Clients who go quiet mid-project and then come back rarely owe an explanation, and asking for one usually isn't worth the friction. The more useful move is to restate, briefly, where things left off and what's needed to restart: "Good to hear from you. Picking this back up, I'll need [the outstanding input] before I can move forward, then we're back on track." This avoids relitigating the silence and gets the project moving again as fast as possible.
If the resurfacing happens after the final-notice stage and a consequence was already triggered, whatever that consequence was (a hold, a fee, a formal pause) stays in effect unless you decide otherwise. Reversing it automatically, just because they replied, undoes the entire point of having a schedule in the first place.
What Silence at the Approval Stage Specifically Means
Silence right after presenting concepts or sending a project for sign-off is its own version of this problem, and it's worth naming separately, because "no reply" at that stage is easy to misread as implicit approval. It isn't. Nothing is approved until it's actually confirmed in writing, which is exactly why getting sign-off that holds up treats a same-day written confirmation, not silence, as the real marker of approval.
FAQ
How long should I wait before following up with an unresponsive client?
Three to five business days for the first, low-pressure check-in. If that gets no reply, a more direct message at seven to ten days naming what's blocked, then a final notice around two to three weeks in that states the contract's next step.
Should I keep working while waiting for a client to respond?
Generally no, past the point where their input is actually required to continue. Working ahead on guesses risks producing something that has to be redone once they finally reply, which costs more than the pause did.
What do I say if the client never explains the silence?
Nothing needs to be asked. Restate where the project left off and what's needed to move forward. Chasing an explanation usually adds friction without adding anything useful to the project itself.
Can I invoice a client who stopped responding?
That depends entirely on what your contract says about dormant projects, partial completion, and deposits, which is why that term needs to exist in the agreement before a project starts, not after a client has already gone quiet.
Is it rude to send a firm final notice?
No, as long as it states a fact (the timeline, the contract term, the next step) rather than an accusation. A calm, factual message that follows through on what was already agreed reads as professional, not confrontational.