You sent the cut nine days ago. Nothing. You sent a follow-up on day five. Nothing.
By now you've constructed a story: they hated it, they've gone to someone else, the whole thing has quietly died.
The story is almost always wrong. The far more likely explanation is that the person who needs to approve it is on leave, or waiting on someone above them, and your project is one of eleven things on their list.
Silence is rarely a verdict. But it is a scheduling problem, and it needs a process rather than a mood.
First, separate the two kinds
They are completely different situations and conflating them causes most of the wrong responses.
Quiet before money: a quote or a proposal that hasn't come back. Low stakes. Follow up twice, then release the date and move on. That's following up without being annoying.
Quiet mid-project: they've engaged you, work is done or in progress, and now nobody is responding. Higher stakes, because your schedule is committed and possibly your money.
This article is about the second.
The ladder
Escalating, but never escalating in tone. The pressure comes from clarity, not from temperature.
Day 2: a nudge with something in it
Short. Ideally carrying something rather than just asking.
"Hi, checking you got v2 okay. No rush on notes; just flagging that Thursday keeps us on the original delivery date."
The deadline is doing the work, not the question.
Day 5: restate the consequence
"Still holding Thursday–Friday for the v3 edit. If notes land after Thursday I'll need to move delivery to the following week. Happy either way, just want to keep you posted."
Notice: no blame, no urgency theatre. You're reporting a fact about a schedule. Most people respond to this one, because it converts their inaction into a decision.
Day 10: change the channel and the person
Email isn't working. Try a call, or a message to the other contact you hopefully collected at kick-off.
If you only ever have one contact at a client, that's the actual vulnerability here. Ask for a second name at the start of every project, framed as "who should I copy if you're away?", which is a normal, easy question.
Day 15: the pause note
"I haven't heard back, so I'm going to pause this and release the edit days. When you're ready, just say. I'll need about a week's notice to reschedule, and the terms in the original agreement still stand."
This is not a threat and shouldn't read as one. It's the honest operational consequence: you cannot hold capacity indefinitely for a project that has stopped.
It also tends to produce a reply, because it's the first message that changes something rather than requesting something.
Protect yourself before it happens
The best handling is structural, and it's all decided at quote stage.
Deposit up front. A meaningful one. Non-negotiable, and normal in every adjacent industry.
Stage the payments. Deposit, a milestone at shoot or first cut, balance at delivery. If a client vanishes at 80% done, you've been paid for most of it.
Balance on delivery, not on approval. This is the important one. If payment is conditional on their sign-off, their silence is free: you're financing their indecision. Payment on delivery of the agreed deliverables ties your money to your work, not to their calendar.
Put a response window in the agreement. One line:
"Feedback due within 10 working days of each delivery. Beyond that, the project may be paused and rescheduling is subject to availability."
Nobody objects to this at signing, and it's the clause you'll be grateful for.
Money silence is a different problem
An unpaid invoice that's gone quiet gets a different, firmer ladder: a payment reminder at due date, a second at seven days with the late-payment terms restated, and a third that names the next step.
Two things that matter more than tone:
Have terms. Payment period and a late fee, stated on the invoice from the first one. You can choose not to enforce a late fee; you can't invoke one that was never there.
Keep the record clean. Dates, amounts, what was delivered. Most late payment resolves the moment it's escalated to someone in finance, and what they need is a clear record rather than a persuasive email.
Knowing when to stop
Some projects die. Clients get restructured, budgets get pulled, the champion leaves.
Two or three unanswered messages after a pause note is a real signal. Send a clean closing message (no bitterness, door left open), invoice for the work delivered under your terms, and move on.
The relationship is worth more than the last exchange. A significant amount of freelance work comes from people who went quiet once and came back eighteen months later, and they remember whether you were gracious about it.
Where Acumin fits
Running a booking through a Delivery Room helps mostly by making the record unambiguous: which version was delivered, when, what was said about it, and where the invoice sits. Most disputes that follow a long silence are disputes about what happened, and a single shared timeline settles those before they start.
Invoices attach to the booking rather than living in a separate folder, so chasing one doesn't mean reconstructing the project first.
It doesn't make anyone reply. Nothing does.
How to use this tomorrow
Look at your current agreement or quote template. Does it contain a feedback response window and a staged payment schedule?
If not, add both before the next quote goes out. That's the whole defence, and it takes ten minutes once.
Related: Managing expectations across a project is how to prevent most silences. Following up without being annoying covers the pre-money version.