Around 1.20, the bit with the guy
The first cut goes to the client on a Vimeo link. The marketing manager emails four notes. Her boss replies all with two more, one contradicting hers. The product manager sends a WhatsApp to the producer: can we lose the bit at around 1.20 with the guy. The CEO gives notes on a call, which the producer writes down on the back of the call sheet.
The editor receives a forwarded email chain, a screenshot of the WhatsApp and a photo of the call sheet. She works out which guy, which 1.20, and whether the boss's note overrides the marketing manager's. The v2 goes back with one note missed and one done that the client did not want.
Why feedback arrives in pieces
- Clients have several reviewers, each sending notes in their own way.
- Nobody on the client side collates notes before sending them.
- Timings are approximate, and the version being watched is not always clear.
- Senior people give notes by phone, and they are not written down precisely.
- Contradictory notes are not spotted until the editor is in the timeline.
Review tools like Frame.io, Vimeo review and Filestage handle timecoded comments well, and if your clients use one consistently, this is mostly solved. The trouble comes when clients do not, or when notes still arrive through other routes.
What scattered feedback costs
Missed notes mean another version. Contradictions resolved by the editor's guess cause friction with the client. The producer spends hours collating notes instead of managing the job. And extra rounds created by confusion eat into what was quoted, which is its own problem.
How we build the review flow
- Each cut is uploaded to a review page, either in a review tool you already use or a simple player we set up, with a clear version number.
- Each reviewer gets their own link and comments on the timeline, so every note has a timecode and a name.
- Notes sent by email or WhatsApp to the producer can be forwarded into the review, and a language model suggests where in the cut each one belongs for the producer to confirm.
- Notes from calls are typed in by the producer against the timecode, marked as from the call.
- Conflicting notes at the same point are flagged, and the named client lead is asked to decide before the editor starts.
- When the review closes, the editor receives one checklist of changes, grouped by timecode, each with who asked and any decision made.
| Feedback route | How it reaches the checklist |
|---|---|
| Reviewer comment on the timeline | Directly, with timecode and name |
| Email to the producer | Forwarded in, placed on the timeline, confirmed |
| WhatsApp message | Forwarded in, placed, confirmed |
| Phone call | Typed in by the producer against the timecode |
| Conflicting notes | Flagged for the client lead to decide |
Reviewing v1 the new way
The client lead gets a review link and shares individual links with her colleagues. Comments arrive with timecodes. The product manager still sends a WhatsApp, which the producer forwards in, and it is placed at 1:18, on the shot of the engineer. Two notes conflict on the music, and the client lead chooses.
The editor opens one checklist and works through it. Nothing is missed, nothing extra is done, and v2 is closer to final.
The review record also settles later questions. If the client asks why a shot was cut, the note, the timecode and the person who asked are all on the v1 review, and nobody has to search old emails to find out.
Is this your feedback loop?
- Client notes arrive by email, WhatsApp and phone.
- Notes use rough timings like around the middle.
- Editors piece feedback together from screenshots.
- Contradictory notes are resolved by guesswork.
- Versions go back with notes missed.