How Do I Give Feedback on a Video Edit?
Watch the whole cut through once before commenting, then gather every reviewer's notes and send them together, in one place. Say what isn't working and how it should feel, with a reason for each note, and let the editor suggest the fix. Settle disagreements between stakeholders before the notes go back. If new scenes would push the video past its agreed length, decide what comes out to make room.
Key Facts
- On a first cut, we play the video through before anyone discusses it, and name the one section we know isn't working.
- On a rebuild, we cut the first 30 to 45 seconds first, so disagreements about style surface while they're cheap to fix.
- We keep every version of an edit, because a client sometimes prefers an earlier cut.
What Makes Feedback on a First Cut Useful?
Notes on the whole piece, each with a reason. Watch it all the way through first, the way your audience will, before anyone starts discussing the opening line. Then write down what isn't working, why, and how you want that moment to feel.
Describing the problem leaves the editor room to solve it, and the best fix often keeps your idea while changing how it's delivered. When text on screen in one of our edits read as too technical, the fix we suggested kept it, in shorter blocks with a change of colour between sections.
A few checks are worth running before you send anything.
- Watch it on mute. If it still tells the story without sound, it's doing its job.
- Show it to someone who hasn't worked on it. If they're confused where the team wasn't, that's useful information.
- Check the brand and the call to action. The brand should appear early, and the call to action should stay up long enough for people to act on it.
The production company has a part to play too. We play the cut first and talk after, and we name the one section we know isn't working before you find it.
What Does Useful Feedback Look Like?
Specific, tied to a moment in the video, with a reason attached.
Be clear, be direct and have an opinion. If you like it or don't like it, that's fine. But expressing that with specificity makes the feedback useful.
| Less useful | More useful |
|---|---|
| "Can it be more engaging?" | "The section around 1:16 needs something that shows the result." |
| "The opening doesn't work." | "Two of us found the opening confusing, and here's what we expected to see." |
| "Make the music banging." | "Here are three tracks we like, and what we like about each." |
| Five emails from five reviewers, some contradicting each other | One list from everyone, with the disagreements already settled |
| "Add these two scenes." | "We need these two scenes. What should come out to stay within the runtime?" |
| Notes from memory on a phone call | Comments on the review link, at the exact time code |
How music and pace are chosen in the first place is covered in what happens in the edit.
How Do You Stop Stakeholders Pulling It in Different Directions?
Gather everyone's notes in one thread, and settle the disagreements before they reach the editor.
- Put every approver on one email thread, on purpose. Everything arrives at once, and nothing gets argued separately.
- Ask for options instead of open questions, and get the sign-off in one place.
- Plan for the least adventurous approver. An idea has to survive them, so ask the production company for options and the reasons behind each, ready for the sceptical room.
- Ask to see what was rejected. Seeing the option that didn't make it lets the surviving choice read as a decision.
- Agree legal limits before the edit. When legal has to approve, get its sign-off on what can stay before editing starts. The method we use is in reusing footage.
What If an Agency and a Client Are Both Reviewing?
The agency reviews every cut first, and the production company acts on its notes before anything goes to the client. One agency described a supplier who forwarded the agency's feedback straight to the end client instead of acting on it. That's a process failure, and a good production company builds the agency's review into the timeline from the start.
Keep one main channel for feedback, such as comments on a review link. If a review tool doesn't suit how your team works, say so. How the rest of the relationship runs is in working with agencies.
How Should Versions and Revisions Work?
One version at a time, with every reviewer's notes collected before the next one starts.
- One list per round. Version one goes out, the reviewers collate their feedback into one list, and that list becomes the brief for version two. Handing it over is the signal that review is finished.
- Every version kept. A client sometimes prefers an earlier cut, so nothing gets thrown away.
- Fewer rounds overall. Fold other pending pieces, such as the social cutdowns, into the same feedback round.
- A short section first. On a rebuild, we cut 30 to 45 seconds and get the direction approved before the rest. Disagreements about style or transitions surface while they're cheap to fix, which trades two quick rounds for one on the full film.
Why Can One Change Make the Whole Edit Fall Down?
Because a tight edit is interlocked. One client described it as taking out one wall and watching the whole house fall down. Change one element and the editor may be rebuilding everything around it. The answer is to settle the structure early, before the detail, rather than leaving all the scripting until after the shoot. If a note looks small but touches the structure, ask what else it moves.
What If New Scenes Push It Past the Runtime?
Decide what comes out to make room. When additions land, ask what the runtime ceiling is, then choose what to trade. A good production company answers with the arithmetic instead of arguing taste. The brief set a length, and the new scenes take it past. If a scene you want needs footage nobody has yet, they should ask you for it rather than refuse the note.