The Client Went Dark After You Sent the Review Link? How to Get Feedback Fast

You delivered the cut on time. The review link went out with a friendly note and a deadline. Then, silence. No comments, no reply, not even a thumbs up. Three days pass, then five, and your schedule quietly collapses, because every project behind this one was planned around feedback arriving this week. A client going dark is rarely a sign of disaster. It is usually a sign of friction, overload, or a reviewer who does not know they are the bottleneck. The good news is that silence responds well to a system. This is the exact sequence I use to restart stalled reviews, most of them within one business day.

First, rule out friction

Before you assume the client is ignoring you, check whether reviewing is simply hard for them. Did the link land in a spam folder or an overflowing inbox. Does the reviewer need to create an account or remember a password to comment, because that alone kills momentum for busy people. Are they trying to review on a phone between meetings, fighting a player that will not cooperate. Remove every barrier you control. A review link that opens instantly, plays the video, and lets the client comment with no login at all turns a chore into a two minute task. In File Approved that is the default: one link, zero accounts, comments pinned to the exact timecode. If your current process asks for more than clicking a link, fix that before sending another reminder.

The nudge ladder: escalate gently, on a schedule

Random chasing feels desperate and works badly. A planned ladder of nudges feels professional and works. Send each step on time, keep every message short, and always restate the one action you need.

1. Day one past the deadline: a friendly bump. Restate the link, the deadline that passed, and how long the review takes. Assume the message was buried, because it usually was.
2. Day three: add consequence, politely. Note that the edit slot reserved for their revisions moves to the next project if feedback lands after a stated date, and offer a fifteen minute call to collect notes live instead.
3. Day five: go around, not over. Copy the project sponsor or the person who signed the quote, summarize the stall in one line, and ask who should review if the original contact is swamped.
4. Day seven: the pause notice. State that the project is paused and the timeline restarts when feedback arrives, with a revised delivery estimate. Put it in writing and stop chasing. Silence after a clear pause notice is a business decision, and it is now documented as theirs.

Two nudges you can copy

Day one: Hi Sara, quick bump on the product video cut. The review link is below, and notes are most helpful by Thursday so I can hold your revision slot. The video is four minutes, and comments can go right on the timeline, no account needed. Thanks.

Day three: Hi Sara, if feedback lands after Friday, the revision slot moves to the following week and delivery shifts with it. If watching and commenting is hard to fit in, I am glad to grab fifteen minutes on a call, play it through, and take the notes live. Either way works on my end.

Notice what both messages do. They stay warm, they repeat the single link instead of starting a new thread, they say how long the task takes, and they attach a real schedule consequence without a hint of threat. That combination respects the client and still moves the project.

Make the review smaller than it feels

Many stalls are really avoidance. A forty minute video feels like homework, so the reviewer keeps postponing it. Shrink the task in your nudge. Tell them the three things you most need eyes on, with the timecodes where those moments live, and say the rest can wait for the next round. Offer the live option seriously: a short call where you play the video, they react, and you take notes removes the blank page problem entirely. Some clients will always prefer talking to commenting, and their feedback is just as valid once you capture it in the review thread yourself, summarized back to them for confirmation.

Find the real blocker

If the ladder produces a reply, listen for the hidden reason. The reviewer may be waiting on their own boss, who has not watched it yet. The budget holder may be quietly unhappy about something outside the edit. Legal may need to see it and nobody told you. Each blocker has a different fix, and none of them is another reminder to the same person. Ask one direct question in your day three message: is there anything blocking the review on your end. You will be surprised how often the honest answer arrives within the hour, because you finally asked about their problem instead of your deadline.

Silence is information. Treat it as a process problem to diagnose, not a client problem to complain about.

Prevent the next stall before it starts

Every recovered review teaches you how to prevent the next one. Agree on review dates before the edit begins, and put them in the kickoff message alongside delivery dates, so feedback time is scheduled rather than assumed. Name one approver and one backup, so a vacation does not freeze the project. State the feedback window and what happens when it closes: the round ends, late notes roll forward, and the delivery date moves by the length of the delay. Then make reviewing effortless with a single link and no account wall. Clients go dark on processes that cost them effort. They respond to processes that respect their time, and the fastest feedback I get now comes from clients who once took a week.

Send the day one nudge today, even if your stalled review is older than that. Start the ladder where you are, keep the tone light, and let the structure do the persuading. Most dark clients are one clear, easy next step away from giving you everything you need.