How to get a client to actually watch your cut (when they keep sitting on it)
You sent the video three days ago. Silence. The problem usually isn't a slow client — it's that reviewing your way is more work than it should be. Here's how to make feedback the easy option, so cuts stop stalling for a week.
The reason your client hasn’t replied is rarely that they don’t care — it’s that watching and replying the way you’ve set it up is a chore, so it keeps losing to everything else on their day. Make reviewing a single tap that needs no download, no account and no typing out timecodes, and the week-long silences mostly stop.
Every freelance editor and small studio in India knows the dead patch: you export, upload, send the link, and then nothing. Day one you assume they’re busy. Day three you send a polite “any update?”. Day five you’re refreshing WhatsApp. The deadline doesn’t move for all this — it just eats your buffer, and the rushed changes land the night before delivery.
Why clients go quiet (it’s usually friction, not laziness)
- The link makes them work before they can watch. A Google Drive or WeTransfer link means download a big file, wait, open it in a player, then think about feedback. That’s three steps before they’ve even started — so “I’ll do it tonight” turns into Thursday.
- They don’t know how to give feedback cleanly. If their only option is to type “at 1:12 the logo, and around 2:30 the music”, they’ll put it off because it feels like homework. Vague dread is a great reason to not open a link.
- Nothing reminds them, or you. The link sits in a chat that scrolled away an hour later. Nobody nudges the client, and you don’t know whether they even opened it — so you chase blind.
- It’s not clear what you’re asking for. “Have a look when you can” has no finish line. “Can you approve or drop notes by tomorrow 2pm” does. People act on a clear, small ask; they ignore an open-ended one.
None of this is the client being difficult. It’s that the handoff quietly asks a non-editor to do editor-shaped work, and they route around it.
Make reviewing the path of least resistance
The fix is to remove every step between the client and giving feedback:
- Let them watch in the browser, instantly. A share link plays the cut in the browser — no download, no waiting on a 3GB file. They tap and it’s playing. If the edit lives on YouTube or Vimeo, you can review against that too.
- No account, no sign-up. The client opens the link, watches and comments without creating anything. Every extra login is a reason to close the tab and “do it later”. Zero logins means later becomes now.
- Let them point instead of describe. They click the exact frame and leave a comment there — pinned to the second, on the version they’re watching. Feedback stops being an essay they dread writing and becomes a tap on the screen.
- It works on their phone. Most clients will open your link on a phone between other things. The review page is built for that, so “I’m not at my laptop” stops being the reason it waits till Monday.
When giving feedback is easier than typing a WhatsApp reply, it gets done — often the same hour.
Stop chasing blind — let the tool do the nudging
- See whether they actually opened it. The share activity shows you if the client has viewed the cut. Now “did you get a chance to watch it?” is a question you already know the answer to — you chase only when they genuinely haven’t opened it, not on a guess.
- Get pinged when feedback lands. Turn on notifications so a comment or approval reaches you without you refreshing a tab all evening.
- Pull the right person in by name. If a project has more than one reviewer, an @mention puts it in front of the exact person who needs to look, instead of a group where everyone assumes someone else will.
Ask in a way that gets a reply
The tool removes the friction; your message sets the expectation. A few habits that move cuts faster:
- Give one clear, small ask with a time. “If this looks good, hit Approve — if not, drop notes on the frame. Aiming to lock by tomorrow 2pm.” A deadline you name is a deadline they can meet; “whenever” is one they never do.
- Send one link per round, not a new file each time. Stack each cut under the same link with a new version, so the client is never hunting for “the latest one” — that hunt is a common reason the review stalls.
- Make the finish line a button. When you want this to be the final pass, ask them to approve on the cut itself rather than reply “ok good”. It’s a smaller action for them and a recorded sign-off for you.
- Chase twice, politely, then stop guessing. One nudge at the deadline, one the morning after. With view activity in front of you, you’re nudging a real silence, not an imagined one — and you spend the saved energy editing.
The quiet cost of stalled reviews
A cut that waits a week isn’t just annoying — it compresses every later stage into the last day, which is where rushed mistakes and extra free rounds come from. Speeding up the slowest part of the job, the part you don’t control, is often worth more than shaving minutes off the edit itself.
Editlock is built so the review is the fast part: browser playback, no client account, frame-pinned comments, view tracking and approval in one link. It’s priced on storage, not per person — flat ₹ pricing, every reviewer and teammate included — so inviting one more client to review never costs extra. You can start on the free plan and move one live project in to see whether your next cut comes back in a day instead of a week.