When the client goes quiet: getting video feedback without chasing
Most quiet clients are not ignoring you. They do not know what is expected, by when, or what happens if they say nothing. Fix that before you send the cut: agree a review window with a fixed closing time, make “no notes” an answer the client can give, send one reminder halfway, and decide in advance that silence moves the job forward on the agreed round but never counts as approval of the final film.
Why do clients go quiet on a review?
Usually because the review asks more of them than they expected, or nobody told them when it ends.
From the freelancer’s side, silence looks like rudeness. From the client’s side, it often looks like this: a link arrived between two meetings, it asked for a sign-up, it was not clear whether to comment on the music or only the structure, and the person who really decides was away until Thursday. Matt Olpinski makes a similar point about ghosting in general: every bit of friction you add makes it more likely the client drops out of the conversation.
The common causes are practical, which is good news, because practical causes have practical fixes:
- No end date. “Let me know what you think” has no deadline, so it never becomes urgent.
- Unclear task. The client does not know what to judge at this stage, so they postpone judging anything.
- Hidden approver. Your contact is waiting for a manager and does not want to say so.
- Friction. A login, a large download, or a file that will not play on a phone.
- Nothing to say. The cut is fine, and “fine” does not feel worth an email.
That last one matters more than it seems. Many silent clients have no notes at all, and you cannot tell them apart from clients who have not watched yet.
What should you agree before sending the first cut?
The window, the reviewer, and what happens when the window closes. Put all three in your quote or kickoff email, not in the review email itself.
| Question | Write down | Why it helps |
|---|---|---|
| How long is a review window? | For example, two business days, closing at 17:00 in the client’s time zone | A fixed close turns “sometime” into a date |
| Who sends the notes? | One named person, even if several people watch | Nobody waits for someone else to reply first |
| What does “no notes” look like? | A one-line reply such as “No notes, go ahead” | The client can finish the round in five seconds |
| What happens after the close? | Late notes go into the next round; the schedule moves by the days lost | Silence has a known consequence, agreed while everyone was calm |
| What still needs an explicit yes? | Picture lock and the final version | Big decisions never happen by default |
Agreeing this at the start is the part that saves you later. When a window closes without a reply, you are not inventing a rule on the spot; you are pointing at something the client already accepted. For how rounds and windows relate, see what counts as a revision round.
How do you write a review email that gets answered?
Short, with one task, one deadline and one easy way to say “done”.
A review email should fit on a phone screen. Say which stage this is, what to look at, and what to ignore for now. Then give the closing time and the shortest possible answer. Something like:
Here is the rough cut (v1, 1:58). At this stage we are checking story and order; color and sound are still temporary. Please send your notes by Thursday 17:00. If everything works for you, a reply with “no notes” is enough and we move on to the fine cut.
Telling the client what to ignore is as useful as telling them what to judge. It removes the worry of commenting on the wrong thing, which is one of the quiet reasons people postpone. Our guide on video feedback an editor can act on has a stage-by-stage list you can link to.
How often should you follow up?
Twice before the close, once after it, and then stop chasing and start rescheduling.
A clear cadence keeps you polite and keeps the client informed, without daily nudges:
- Day 0: Send the cut with the closing time and the “no notes” option.
- Halfway: One short reminder. “A quick nudge on v1, notes are due Thursday 17:00.”
- Morning of the close: “The window for v1 closes at 17:00 today. Anything after that goes into the next round.”
- After the close, no reply: Confirm what happens now. “We have not received notes on v1, so we are going ahead with the fine cut as planned. Delivery stays on the 14th.”
- Still nothing after two working days on a stage that needs a yes: Pause the work that depends on it and send a new date. “Without approval of v3 we cannot start the grade. If we hear by Monday, delivery moves to the 18th.”
Step 5 is where many freelancers go wrong, by quietly working on and absorbing the delay. Decade Pictures describes the same pattern from a production company’s side: a first cut goes out on a Monday, notes come back a week later, and every day of waiting adds a day to delivery. Saying that out loud, with a date, is not pushy. It is the schedule.
Does silence mean approval?
For a work-in-progress round, silence can mean “carry on”. For the final version, it should never mean “approved”.
Some content teams do use approval by default. Contentoo’s approval guide recommends a review window of 24 or 48 hours and treats a missed deadline as approval, so the person who wants changes has to act. That works for a blog post that can be edited after it goes live. A finished video is different: the grade, the mix and the deliverables are built on it, and a client who discovers a problem after delivery will not accept “you did not reply” as an answer.
A practical split:
- Rough and fine cut rounds: If the window closes without notes, the round counts as used and you move to the next stage.
- Picture lock and final version: Wait for an explicit yes, in writing. If it does not come, the job pauses and the date moves.
Tools can help make that difference visible. In Kadrenta, made by the same team behind The Production Brief, a client opens the review through a link without creating an account, and according to its help pages an approval also posts a visible comment such as “Approved v2.” in the conversation. A client can approve or comment, with no reject button, so an approval is a recorded decision next to the work, and silence stays silence.
How do you protect your schedule from the next quiet client?
Build review time into the plan from day one, and treat the client’s window as part of the timeline.
Put each review window in your schedule as its own block, with the closing time, so the client sees that their days are part of the plan. Add a buffer of a day or two before any hard delivery date. And for repeat clients who always run late, make the windows shorter but more frequent: a two-minute check on a 30-second section is easier to fit between meetings than a full cut.
If a client keeps going quiet despite all this, look at who you are talking to. Often your contact is not the person who decides, and the fastest fix is asking, kindly, who else needs to see the cut before it can be approved, then inviting that person into the next round directly.
Frequently asked questions
How long should a client have to review a cut?
Two to three business days works for most cuts with one or two reviewers. Agree the exact closing time before you send, and add a day for every extra layer of approval on the client side.
Can I keep working while I wait for feedback?
Yes, on parts the review cannot change, such as prepping deliverables or cleaning up the project. Avoid polishing what is under review, because that is exactly what the notes may change.
Should I charge when a client is late with feedback?
Usually the cost shows up in the schedule, not the invoice: the delivery date moves by the same number of days. If the delay pushes you past other bookings, say so early and agree a new date in writing.
What if the client says they watched it but have no time to write notes?
Offer a 15-minute call and write the notes yourself while you watch together. Send them back as a list for the client to confirm, so the round still ends with written feedback.