Review the named cut as a whole before leaving comments. Some concerns are about the story; others are about facts, sound or a specific shot.
Identify the version
Start the review note with the filename or review version and duration. Comments on an older cut can send an editor backwards.
Adobe’s Frame.io review tutorial shows timecoded comments linked to moments in a cut. You can apply the same discipline in a simple document if that is the agreed workflow.
Turn reactions into instructions
Fictional review of STORY07 review v03, duration 2:10:
| Time | Problem | Requested action |
|---|---|---|
| 00:12 | Speaker starts before the viewer knows their role | Add the approved name and role title here |
| 00:38 | Two answers explain the same setup | Keep the clearer second answer; check the transition |
| 01:14 | Diagram label differs from the interview wording | Use the customer-approved term “triage owner” |
| 01:52 | Music obscures the last sentence | Reduce music under that sentence and review intelligibility |
These comments identify a usable edit. They do not require the editor to guess what “more polished” means.
Separate story decisions from technical corrections
Watch first for the main question: can the intended viewer understand the customer’s decision and experience? Then review factual details, visual clarity, audio and captions.
Do not spend the entire review correcting punctuation while leaving a confusing opening untouched. Equally, do not use “storytelling” as a reason to remove an important qualification from a quote.
Resolve conflicting feedback before the next cut
Suppose one reviewer wants a sentence removed and another wants it retained. The editor should not have to choose the client’s message.
The review owner can consolidate:
Retain the implementation detail, but remove the repeated introduction. The approved meaning must remain: the first test covered one team, not the whole company.
Record why a comment was accepted, rejected or deferred. Use the change-request log if a request introduces a new output or scope.
Check the revision against the request
When the new cut arrives, review the changed sections and watch the complete video. Removing ten seconds can create a new transition problem elsewhere.
Do not label the cut approved merely because all comments have checkmarks. The exact finished version still needs the agreed release decision.
A good feedback round reduces uncertainty for both client and editor. It gives the next cut a clear purpose rather than starting another cycle of subjective reactions.