Picture a rough cut going out to six reviewers on a Tuesday. By Thursday the editor has an email thread with four replies, a PDF of screenshots with arrows on them, a voice memo recorded in a car, and a reply-all from someone who did not watch the first two minutes. Two of the notes contradict each other. One asks for a shot that was never filmed. Nobody has said whether the story works.
That editor now has to guess. Whose note wins? Is “make it pop” about color, music, or pacing? Should the section the VP wants gone come out before or after legal looks at it? Every guess costs a round, and rounds cost time and usually money.
This guide is for marketing managers, comms teams, and business owners who are about to give feedback on a video edit and want the next version to land closer to what they need.
Know which cut you are looking at
Edits move through stages. Editors name them a little differently, but the order is usually the same, and each stage wants a different kind of note.
Rough cut. The story is assembled. Shots run long, music may be temporary, and graphics are placeholders or missing. This is the time for the big notes: structure, order, what is missing, what can go, whether the opening earns the next ten seconds.
Fine cut. Structure is settled. Now you are looking at pacing, trims, which take of a line works best, and B-roll choices.
Picture lock. The timing of every shot is final. Color, the sound mix, and finished graphics are built on top of the locked timeline, so changing a cut after lock can mean redoing work in all three.
Final. Graded, mixed, titled, exported. Notes here should be fixes: a typo, a wrong logo, a level that jumps.
The most expensive note in post is a structural note on a final. It happens when the person who really owns the message sees the video for the first time at the end. If there is a senior stakeholder whose opinion will decide things, get them in front of the rough cut, even for ten minutes. Our article on what post-production involves walks through the stages in more detail, and color grading vs color correction explains what happens to the picture after lock.
Watch it once before you write anything
Watch the whole cut start to finish without pausing. You are checking one thing on that first pass: did it make sense, and did it hold you? Write down where your attention drifted, if it did. That single note is often more useful than twenty frame-level comments.
Then watch it again and take notes.
Watch it where your audience will. A video for LinkedIn or Instagram should be checked on a phone, with the sound off at least once, because some of your viewers will watch it muted. A video that plays in a ballroom should be checked on a big screen through real speakers, if you can get to one. Judging a vertical social cut on a laptop, or a keynote opener through laptop speakers, is how you end up giving notes about problems your audience will never have and missing the ones they will.
Put a timecode on every note
“The part near the middle where she talks about onboarding” could be three different places. “1:42” is one place.
Review tools such as Frame.io and the review pages in Vimeo let reviewers click on a frame and leave a comment pinned to that moment, which also keeps every reviewer’s notes in one place. If your editor sends a plain file instead, a numbered list works fine:
- 0:08 Logo animation feels slow compared to the rest of the open
- 1:42 I lose track of who is speaking here
- 2:15 Product name is misspelled in the lower third
Use the timecode the player shows, and say which version you watched. “v2, 1:42” saves an email.
Describe what you see before you suggest a fix
“At 1:42 I lose track of who is speaking” tells the editor what is happening to a viewer. “Add a lower third at 1:42” tells them one possible answer. The editor might add the lower third. They might also find that the cutaway right before it is the problem, and fixing that solves it more cleanly.
You are allowed to suggest fixes. You hired someone who sees a timeline all day, though, and naming the problem first gives them room to do the job. When you do have a specific fix in mind, say both: “I lose track of who is speaking. Would a lower third help?”
Be careful with taste words. “Make it pop,” “more energy,” and “feels flat” each mean something different to every person who says them. If you can, point to the moment and say what you expected. “I expected the music to lift when the product appears and it stays the same” is a note an editor can act on. Reference videos help here too, as long as you say exactly what you like about them.
Pick one person to own the notes
When six reviewers send notes separately, the editor gets contradictions and has to referee them. That is not the editor’s call to make.
Pick one person on your side to collect every reviewer’s notes, settle the conflicts, and send one consolidated list. That person is usually the project lead. They do not need to be the most senior person in the room. They do need the authority to say “we are keeping this shot” and have it stick.
There is a real tradeoff. One owner makes the process faster and the notes cleaner, but it means some reviewers will not see their note go through exactly as written. Committee review feels more inclusive and can produce a longer, muddier video, because every note gets honored a little. Most teams land somewhere in between. Decide who has final say before the first cut goes out, instead of after the second round stalls.
Separate must-fix from preference
Sort the consolidated notes into two groups before you send them.
Must-fix. Wrong names or titles, a product claim marketing or legal has not approved, a logo or brand color that is off, a person on screen who should not be there, a factual error.
Preference. Pacing, music choice, shot selection, order of soundbites.
Must-fix items get done. Preference notes are where the editor can push back with a reason, and you should want to hear it. Sometimes “we tried that and it broke the sentence” is the most useful thing they will tell you all week.
If the video needs legal, compliance, or brand review, schedule it at the fine cut, not the final. A claims change at the end can mean pulling a soundbite the whole structure depends on.
Know what the edit cannot fix
Some notes are really requests for footage that does not exist. A shot nobody filmed, an answer the interviewee never gave, audio with a hum that runs under every word, a product that was not on set. Editors can work around a lot, but they cannot cut what was not captured, and audio problems can only be cleaned up so far before it starts to sound processed.
When a note runs into this wall, the options are usually a workaround in the edit, a pickup shoot, or accepting the limit. Ask your editor which one they recommend and what each would take. Then fix it upstream for the next project with a better shot list and a dedicated production sound mixer on the day. If you are cutting highlights from a live event, record the program feed and camera sources locally, as our guide to livestreaming a corporate event recommends, so the editor has more than the platform archive to work with.
Music notes have their own limit. If you want a different track, the replacement needs to be licensed for how the video will be used. Our music licensing guide covers the basics.
Revision rounds, scope, and turnaround
Many edit quotes include a set number of revision rounds. Your scope of work should say how many, what counts as a round, and what falls outside it. New footage, a new script, or a new version for a different audience is usually a change in scope, not a revision.
A round is one consolidated list on one version. Three emails over two days about the same cut can count as three rounds, depending on the agreement, which is one more reason to consolidate.
Your turnaround matters as much as the editor’s. If the schedule gives the editor two days per round and the review sits in someone’s inbox for a week, the delivery date moves. Our article on how long post-production takes has more on building review time into the schedule.
Before you send the next set of notes
Check that the list names the version, has a timecode on every line, separates must-fix from preference, and comes from one person. Then read it once as the editor will. If a note would make you ask “what does that mean?”, rewrite it before you hit send.
If you need an editor in a specific city, the Production Help directory is a good place to start your search.