How to Turn Review Notes Into Usable Feedback

Feedback arrives as twenty-three lines in an email, written in the order the reviewer thought of them. Some have timestamps as 1:23, some as 00:01:23, two say “near the start” and one says “the bit with the graph”.

The editor spends forty minutes turning that into a work list before making a single change.

Chronological order is not a preference

An editor works along a timeline. Every note out of sequence means scrubbing back, reloading the render at that point, and losing the position they were at.

Twenty notes in a sensible order is an hour of work. The same twenty jumping between 0:45, 38:12, 2:10 and 41:00 is closer to two, and most of the difference is navigation.

Sorting is mechanical and nobody does it, because the person writing the notes is watching linearly and thinking non-linearly — they note something at 38:12 and then remember an issue at 0:45.

Timecode formats have to be normalised

1:23, 01:23, 00:01:23 and 83s are all the same moment. Mixed within one list they are a small tax on every note, and on a long video 1:23:45 versus 1:23 is genuinely ambiguous until someone checks.

Normalising to one format — HH:MM:SS for anything over an hour, MM:SS below it — removes the ambiguity and makes sorting possible in the first place.

Notes with no timestamp at all should be separated rather than guessed at. “The bit with the graph” is a real note and it belongs in a list the editor scans, not slotted into the timeline at a guessed position.

Severity is what the editor actually needs

The second transformation, and the one that saves more time than sorting.

A flat list gives an editor no way to know which notes are blocking and which are preferences. So they either treat everything as mandatory, which produces changes nobody wanted, or they guess, which produces another revision round.

Two or three levels is enough:

Marking a caption typo as blocking and a colour grade opinion as preference takes the reviewer two seconds per note and removes an entire revision round.

Notes against the wrong cut

Worth checking: a timestamp beyond the video’s duration means the note was written against a previous version.

That happens constantly when review overlaps with editing, and a note at 42:10 on a cut that is now 39:30 long is not actionable — the section it referred to may have moved or been removed. Flagging those rather than passing them through saves the editor working out which notes are stale.

Say what outcome you want

The most useful addition to any note, and the one most often missing.

“The music is too loud at 4:12” identifies a problem. “The music is too loud at 4:12 — bring it under the dialogue” identifies a solution, and the editor does not have to guess.

Where you do not know the solution, saying so is also useful: “something feels wrong about the pacing here, not sure what” is honest and invites the editor’s judgement rather than sending them looking for an instruction that was never given.

The failure mode is a note describing a feeling with no indication of what would resolve it. That produces a change, a review round, and a second note saying it still is not right.

Common mistakes to avoid

• Sending notes in the order they were thought of.
• Mixing timecode formats within one list.
• Providing no severity, so the editor treats preferences as requirements.
• Writing notes without timestamps where a timestamp was possible.
• Sending notes against an older cut without saying which version they refer to.

How to do it with Video Timestamp Comment Exporter

The Video Timestamp Comment Exporter restructures the notes.

1. Paste the notes in whatever form they were written.
2. Sort chronologically, which is the order the editor works in.
3. Group by severity so blocking issues are separated from preferences.
4. Check any timestamps beyond the duration — those are notes against an older cut.

Other video tools are in the tools directory.

Frequently asked questions

Why does chronological order matter so much?

Because an editor works along the timeline. Notes jumping around it mean scrubbing back and forth for every one, which can double the time a revision takes.

Why separate severity?

So the editor knows what must change and what is a preference. A flat list forces a guess, and guessing wrong in either direction costs a revision round.

What about notes with no timestamp?

They are kept separately rather than placed at a guessed position. A note like “the bit with the graph” is real feedback and belongs somewhere the editor scans, not inserted into the timeline.

Final thought

Sort by time and mark what is blocking. Two minutes from the reviewer removes an hour from the edit and usually a whole revision round.

Try the free Video Timestamp Comment Exporter