How to give video feedback an editor can act on

Feedback an editor can act on has four parts: where (the timecode), what you see, why it matters, and what should change. It also has to fit the stage: notes on color during a rough cut waste everyone’s time, and notes on story during the grade come too late. Collect the notes from everyone on your side into one list per round, resolve the conflicts yourself, and send that.

What makes a note actionable?

A note is actionable when the editor does not have to guess.

PlayPause, which makes review software, breaks useful notes down into being placed in time, pointing at the right part of the frame, saying what to change, saying who it comes from, and saying what it does not affect. That last one is often missed: “the logo feels small in the end card, but leave the rest of the layout” saves a whole round of unwanted changes. PlayPause also argues that one ambiguous note can cost an extra round, because the editor interprets, the reviewer corrects, and the cycle starts again.

A simple template, close to the four-part structure PlayPause suggests, works for almost every note:

Timecode + what I see + why it bothers me + what I would like instead

Compare these two:

Weak note	Note an editor can act on
“The middle drags.”	“00:18-00:26: the three product shots feel slow. Could we lose one and keep the close-up?”
“Make it pop more.”	“00:41: the packshot looks dark against the white background. Lift it so the label is readable.”
“Not sure about the music.”	“Whole film: the track feels too relaxed for a launch. Something with more drive, same length.”
“Fix the text.”	“00:52: ‘colour’ should be ‘color’ for the US version.”

You do not need to know the technical fix. “The label is hard to read” is enough; the editor or colorist knows whether that means the grade, the light or the framing.

What should you look at in each stage?

Judge what the stage is meant to decide, and leave the rest for later.

Stage	Look at	Leave for later
Rough cut	Does the story work? Is anything missing? Is the length right? Is the order clear?	Color, sound mix, temporary music, title design
Fine cut	Pacing, shot choice, performance, where supers and the end card sit	Exact color and final mix
Grade	Skin tones, product color, consistency between shots, mood	Re-editing
Sound mix	Voice clarity, music level, sound effects, the end	Re-editing
Online and finishing	Spelling, legal lines, logos, the right versions and formats	Anything creative

A rough cut usually has temporary music, flat color and placeholder titles. That is intentional, not careless. If something temporary distracts you, say so in one line (“the temp track makes it hard to judge the pace”) rather than giving detailed notes on it.

For CGI and animation the same rule holds with other stage names. In an animatic you judge timing and camera; in blocking, movement; in lighting, mood and materials. Studios that work in CGI, such as Not Important Studio, share rough work in progress as video walkthroughs so the client can review at their own pace while ideas are still cheap to change. Early, rough looks are where a client’s notes have the most effect for the least cost.

Where should notes go?

On the frame, in one place, not spread across email, chat and calls.

Most review tools let you pause on a frame and leave a timestamped comment, mark a range from an in point to an out point, and draw on the frame. Frame.io’s help pages describe exactly these options. Use them. A circle around the wrong logo is clearer than a sentence describing where it is. A range note is better than a single timestamp when your note is about a whole passage.

Keep notes about the film separate from notes about the process. “Can we have this by Thursday?” belongs in a message to the producer, not on frame 1,200.

Who should send the final list?

One person on the client side, after the internal discussion is done.

When three people each send their own notes, the editor receives contradictions: one wants the voiceover louder, another wants it gone. The editor should not have to choose between your colleagues. Agree internally first, then send one list.

A practical way to do it:

1. Everyone on your side reviews the same version within the same window.
2. One person, usually the producer or brand lead, collects the notes.
3. That person removes duplicates, resolves conflicts and marks each note as “must” or “nice to have”.
4. The list goes to the studio before the window closes.

If your tool separates internal comments from client comments, use the internal ones for the discussion and send only the result. In Kadrenta, made by the same team behind The Production Brief, review supports timestamped and range remarks, drawing on the frame, internal versus client comments, and a PDF of all remarks, so the consolidated list exists as one document as well as on the frames.

What should you avoid saying?

Avoid notes that reopen earlier decisions without saying so.

• Retroactive notes. Changing something you approved last round is allowed, but say that you are doing it. It is a change, not a correction.
• Feel-only notes. “It’s not there yet” with nothing else.
• Group-think notes. “We all feel…” when one person does.
• Notes on the wrong stage. Detailed color notes in a rough cut.
• Scope in disguise. “Can we also have a vertical version?” is a new deliverable, not a note. Put it on the deliverables list.

How do you know your notes worked?

The next version answers every note, and you can check each one off.

Before you send, read your list as if you were the editor. Could you start working on each line without asking a question? If not, rewrite it. After the next version arrives, go through the list and confirm each note was handled or explained. Then you are ready to close the round. How many rounds you get, and what counts as one, is covered in what counts as a revision round.