EDITLOCK How to give your video editor clear feedback
Vague notes cost you rounds and cost your editor days. Here's how to give feedback on a video edit that gets you the cut you actually want, faster.
To give a video editor clear feedback, pin every note to a specific second, put it all in one place, and be explicit about what “done” means — most extra rounds come from how the notes are shaped, not from the editor missing the point.
If you’ve ever felt like your edits go back and forth forever, the cut usually isn’t the problem. The feedback is. “Make the intro punchier” feels clear when you write it, but your editor has to guess what punchier means to you — and every wrong guess is another day and another round. Tighten how you give notes and you get the video you pictured in fewer passes.
Why vague feedback costs you
Here’s what actually happens on the editor’s side when a note is fuzzy:
- They translate, then guess. “The middle drags” isn’t an instruction — it’s a feeling. The editor has to figure out which shot, how much to trim, and whether you mean pacing or music. Sometimes they guess right. Sometimes you get round three.
- Notes scatter. You send one on WhatsApp, one in email, one as a screenshot, one on a call. Something always slips through, and the thing that slips becomes the next revision.
- You’re not both looking at the same cut. You comment on a file you downloaded on Tuesday; they’re already on Thursday’s version. Half your notes are things they’ve fixed.
None of this needs you to learn editing. It just needs you to give notes in a shape your editor can act on.
1. Comment on the frame, not in a paragraph
The single most useful thing you can do is tie each note to a timestamp. “At 01:12, cut half a second earlier” is a task your editor does once and knows they got right. “The pacing feels off somewhere” is a round they’ll repeat.
Most proper review tools let you leave a comment pinned to the exact second you’re watching. When something is visual — the wrong logo, a title that’s too high, a distracting element — draw straight on the frame instead of describing where it is. “Move this,” with an arrow on the thing, beats a paragraph every time.
If you want the full method, we wrote a separate guide on collecting timestamped feedback on a video.
2. Say what you want, not just what’s wrong
“I don’t like the intro” tells your editor to stop; it doesn’t tell them where to go. Add the direction:
- Not “the intro drags” → “cut the first 3 seconds, start on the wide shot.”
- Not “the music is off” → “drop the music under the voiceover so the words are clear.”
- Not “make it pop” → “the colours look flat to me — can the greens be richer?”
You don’t need the right jargon. You need the outcome you’re after. A rough “I want it to feel faster and more energetic here” is far more useful than a confident-sounding note that points in no direction.
3. Keep every note in one place
Feedback that arrives in four apps gets actioned in three. The fix is to put all of it on the review itself — one link, one thread, one version — so nothing lives in a chat your editor has to scroll back through at 11pm.
This also solves the awkward multi-person problem. If there’s a second decision-maker — a manager, a client of your own — get them commenting on the same link so they resolve their disagreements before the editor cuts, not after. Good tools let extra people review without making an account; they just open the link and comment. There’s no reason to leave someone out of the review.
The best note is one your editor can read once, do once, and tick off. If they have to message you back to ask what you meant, the note wasn’t finished.
4. Send all your notes at once, per version
Trickling in notes — three now, two more after lunch, one the next morning — turns one round into three. Watch the whole cut, gather everything, and send it as a single batch against that version. If you spot something after you’ve sent, add it to the same thread rather than opening a new channel.
Then wait for the next version before the next batch. Reviewing a cut the editor has already replaced just creates notes for work that’s already gone.
5. Be clear about “yes”
A round only ends when someone actually approves it. “Looks good!” in a chat isn’t approval — it leaves the door open for one more small change, and the loop never formally closes. When you’re happy, approve that specific version so it’s recorded. After that, anything new is understood as a new request, which is fairer to your editor and clearer for you.
Why the tool matters here
You can do all of this over email if you have to — but the friction quietly pushes everyone back toward bad habits. On per-seat tools, adding another reviewer costs the editor money, so people get left out of the review and their notes arrive late as a surprise round. That’s a cost problem creating a workflow problem.
A tool priced on storage instead of seats removes that: the editor can bring you, your colleague, and anyone else onto one link for free, so everyone reviews the same cut at the same time and the notes collapse into one round. That’s why Editlock is priced on storage, not per person — a flat ₹ plan with unlimited free reviewers, timestamped comments, on-frame drawing, and a clean approval, all on one link.
The short version
Give feedback pinned to a timestamp, aimed at an outcome, all in one place, batched per version, and closed with a real “yes.” Do that and your editor stops guessing — and you get the cut you wanted in two rounds instead of five.
If you’re an editor tired of decoding notes, send this to your next client. If you’re the client, try it on a real job — the free tier is enough to run a full review and feel the difference.