Most video projects do not stall on editing skill - they stall on feedback that arrives vague, conflicting, or never. The editor's side of that conversation got its own guide (how to receive client feedback, even when it is not constructive); this one is the client's side: the etiquette rules that make a review round end in one pass instead of four. None of it requires learning an editor's tools - it requires deciding, before you watch, what kind of note is worth leaving.
The five ways client feedback breaks a round
- Vague timecodes. "Somewhere around the middle, the music part?" - the editor guesses, ships a guess, and the round doubles. A note pinned to the exact frame ends this before it starts.
- Conflicting reviewers. Two stakeholders leave opposite notes ("too fast" / "too slow") with no tiebreaker, and the editor becomes the referee for a decision that was never theirs.
- Notes as verdicts. "Make it pop" is a verdict, not a note. It gives the editor a feeling to chase and no condition for done - which is why rounds drift.
- Silent approval. "Looks good" in a chat thread, unwitnessed and unversioned, while the real feedback waits for the next call. Ambiguity is not kindness; it is a delayed revision.
- The round-three newcomer. A stakeholder who first appears in round three with structural notes is not giving feedback - they are restarting the project at 70% spend.
The rules that keep rounds short
- Comment on the frame. Put every note on the moment it concerns, in the review tool - not in email, not in a meeting from memory. Pinned notes are the difference between one interpretation and five.
- Say the what and the why; leave the how. "The logo hold is 3 seconds and it feels long - I want the pace tighter here" gives the editor both the observation and the goal, and the professional room to choose the fix.
- Name one approver. Many voices can comment; one named person decides. When stakeholders disagree, they resolve it inside the thread before the editor touches the cut - the approval-chain mechanics are in the video approval workflow guide.
- Batch before the deadline. A round is one review pass, not a slow drip of DMs. Collect every note inside the stated window, then let the editor work.
- Tag priorities: must / should / could. The editor ships the musts, weighs the shoulds, and bins the coulds without guilt - which is also how you avoid paying revision-round fees for niceties. The round-count question - how many rounds are normal, and when overages begin - is covered in how many video revision rounds.
| Instead of… | Try… | Why it works |
|---|---|---|
| "Make it pop." | "The opening feels slow - I want energy in the first five seconds." | Gives a condition for done, not a mood to chase |
| "Around 2:30, maybe?" | A comment pinned to the exact frame | Kills the guessing round-trip entirely |
| "Sarah thinks it's too fast." | "We split on pace - resolved as: keep current tempo." | Shows the editor a decision, not a dispute |
| "Looks good!" (in chat) | Explicit approval on the version, in the tool | Creates a record; ends the round for real |
| "One more thing…" (four times) | Everything batched inside the review window | One revision pass instead of five |
A note editors can send clients
"Before you watch: drop every note on the exact moment it concerns (tap the video, type). Tag each note must/should/could. If we disagree internally, resolve it in the thread before I touch the cut - and [name] makes the final call. Notes are due [date]; the fix lands [date]. That's the whole protocol - it's how this round ends in one pass." Feel free to paste this verbatim into your kickoff email; the shared-habit version of these rules also lives in video review best practices.
FAQ
What happens when two stakeholders disagree?
They resolve it, in the comment thread, before the editor works. Conflicting notes without a tiebreaker turn the editor into a referee for a decision that belongs to the client - and whichever way the editor guesses, half the room is unhappy.
How many revision rounds should feedback take?
Two to three is the healthy norm: structural notes early, polish last, approval explicit. If you are on round five, the problem is almost never the edit - it is unbatched feedback or a missing final approver, and the contract-clause fix is in the revision-rounds guide.
Is it rude to tell the editor which notes matter most?
The opposite - priority tags are the kindest note you can leave. An editor triaging twenty unprioritized comments spends effort where you may not want it; must/should/could tags point that effort exactly where it pays.
Should feedback arrive in a live review call instead?
Calls are for direction, rounds are for notes. A live session produces great alignment and zero durable record - whatever is decided on the call should land as pinned comments on the version, so the cut's history stays in one place.