How to give feedback on a video edit without burning the budget

Most revision rounds cost more than they should because of how the notes are written, not because of how many there are. Here is the format that keeps them cheap.

September 2, 2026 · 10 min read

The first cut lands in a shared channel on a Thursday afternoon. Within an hour there are nine messages. The founder wants it shorter. The head of product wants the dashboard shot to stay. Someone asks if the music can be more energetic. A designer replies that the logo animation feels off, without saying at which second. Two of the notes contradict each other and nobody says which one wins.

The editor now has a choice: guess, or ask. Guessing produces a second cut that satisfies nobody. Asking costs two days of back and forth before any work happens. Either way the round has already become the most expensive part of the week, and none of that expense came from the edit itself.

Revision rounds are not the problem. They are how a film gets good. What makes them costly is the format the notes arrive in, and that is entirely inside your control as the client. The rest of this is the format we ask for, and why each part of it exists.

Describe the problem, do not prescribe the fix

This is the single highest leverage habit, and most teams get it backwards. A note like "cut the third shot" is a solution. It hides the actual observation, which might have been that the section drags, or that the product appears too late, or that the transition broke the rhythm. The editor executes the solution, the underlying problem survives, and round two opens with the same feeling described differently.

Compare the two registers on the same moment in an edit.

The right hand column is the point. A described problem has several possible fixes and the editor is the person best placed to pick one. A prescribed fix has exactly one outcome, and if it was the wrong diagnosis you have paid for a change that did not help. You are not being vague by describing a feeling: "I lose interest at 0:06" is a precise, checkable observation.

One document, one round, one decision maker

Notes from five people arriving separately over three days is not a round of feedback, it is five rounds paid at the price of five. Every message restarts the editor, and consolidation gets pushed onto the person least able to resolve a disagreement between your CEO and your head of product.

The mechanics that make this work are dull and they matter more than anything creative in this article.

1. 01Collect internally first. Everyone watches, everyone writes, into one shared document. Nothing goes to the studio until the collection window closes.
2. 02Resolve contradictions before sending. If two stakeholders want opposite things, that is your decision to make, not the editor to arbitrate. Send the resolved version.
3. 03One named owner sends it. A single person owns the document and is the only channel for notes that round. Everyone else routes through them.
4. 04Set the window and hold it. Twenty four or forty eight hours, agreed in advance. Notes arriving after the window go into the next round, not this one.
5. 05Number the notes. So the studio can reply against each one and you can see what was addressed and what was deliberately not.

The named owner is the piece teams resist and the piece that saves the most. Somebody has to be allowed to say "we are not doing that" to a colleague. If nobody has that authority, every preference in the company becomes a change request, and the film converges on the average of all opinions, which is the one version guaranteed to be forgettable. This is the same decision structure we describe in our post on how to work with a motion design agency, where the approval path is agreed before the first frame exists.

Timecodes, or it did not happen

Every note about something visible or audible needs the second it happens at. Not "the middle section", not "the part with the graph". A timecode turns a conversation into a task.

A note in the format that works looks like this: 0:14, the caption appears while the voice is still finishing the previous line, so I read and listen at the same time and follow neither. Timecode, observation, reason. It takes fifteen seconds longer to write than "the captions feel off" and it saves a round.

A few practical rules on top of that:

• Use a review tool that pins comments to frames if you have one. If not, a numbered list with timecodes in a document is completely adequate. The tool is not the point, the format is.
• Watch it once through before writing anything. Notes written while scrubbing catch details and miss the shape, and the shape is what round one is for.
• Watch it on the surface it will be published on. A film for a muted feed judged on a laptop with headphones is being judged in the wrong conditions.
• Separate opinion from blocker. Mark each note as must change or would prefer. Studios prioritise correctly when they know which is which, and you get the important ones done.
• Do not send screenshots without timecodes. A frame grab with no time attached sends someone hunting through the sequence to find it.

What each round is actually for

Rounds are not interchangeable. Each one opens certain kinds of change cheaply and closes others. Sending structural notes at the polish stage is the classic way a budget goes: the work being discarded is finished work.

Read that table as a schedule for your own opinions. If the pacing bothers you, say so at the first cut, not after the grade. If the claim in the voice-over makes your legal team uneasy, that belongs at script. Holding a structural doubt until the film looks finished is the most common way a two round project becomes a four round one, and it is also the honest reason many teams believe video is expensive. The cost drivers we listed in what a brand video actually costs are mostly late direction changes, not day rates.

Some assets do not need a review round at all

Not everything you publish deserves the process above. A hero brand film or a launch teaser does, because it carries the story and it will run for a year. A one off cutdown for a Tuesday post, or a quick asset for a moment that will be over by Friday, usually does not: reviewing it costs more attention than making it.

Deciding that in advance is worth doing explicitly. Agree at kickoff which deliverables get two rounds, which get one, and which are published on the studio judgement with no round at all. Teams that skip this end up giving the same scrutiny to a fifteen second social cut as to the film it was cut from, which is how a review process quietly becomes the bottleneck it was meant to remove.

There is also a category below that: the placeholder you need this afternoon. Rather than point at a competitor, we will point at something of ours. ShipTeaser is a separate product from the same founder as this studio: a product URL goes in, a 15 second 1080p motion graphics teaser comes out, built for muted feeds, with an optional music bed and the first video free without a card. There is no review round because there is nothing to review against, no voice-over, no avatars and no timeline to edit, and it will not match a visual system it has never seen. For a stopgap it is honest work. For the film your launch rests on, it is not what you want.

When the notes mean the brief was wrong

Sometimes a round of feedback is not feedback. If the notes on a first cut are about what the film is trying to say, who it is for, or what the product does, the edit is not the thing that failed. The brief was never settled, and the cut is where that surfaced.

The signals are recognisable once you know them.

• Notes disagree about the audience. One person is judging it as a sales asset, another as a brand piece. No edit satisfies both readings.
• The reference set changed. Somebody sends a new film to match at the second cut. That is a new brief wearing the clothes of a note.
• Every section gets a note. Uniform dissatisfaction is rarely about execution. It usually means the direction was approved without being agreed.
• The claim is contested. If people argue about whether the product really does the thing on screen, stop editing and settle that.

When you see these, the cheapest move is to pause the round and go back to the brief for an hour, with the same named owner in the room. Pushing a doomed round through produces a second cut that fails for the same reason, and now you have spent two. Studios will not usually force this conversation, so it tends to be the client who has to call it. Calling it early is a sign of a team that has done this before, not a failure.

Everything above is a process for buyers rather than for editors, which is deliberate: the leverage sits with whoever writes the notes. If you want to see the kind of work these rounds are protecting, the projects page is the honest sample, and the ongoing shapes we work in are on the service cards. Teams weighing whether to run this internally instead will find the trade offs in our post on an in house designer versus an agency.