The Rough Cut Review: How to Give Edit Notes That Help

The rough cut lands in your inbox at 4 p.m. You watch it once on your phone between meetings, you feel a vague dissatisfaction with the first thirty seconds, and you reply with three words: "make it pop." The editor reads that note the next morning, has no idea what you actually saw, guesses, and spends four hours on a version that guesses wrong. Now you are one revision round deeper into a fixed three-round budget, the delivery date is closer, and nobody is happier. That entire loss came from the note, not the edit.

This is the most common and most expensive failure in post production, and it has almost nothing to do with editing skill. A good editor can execute nearly any note you give them cleanly. What they cannot do is read your mind. The quality of the finished piece is capped by the quality of your feedback, and most feedback is worse than the person giving it realizes. This post is about how to give edit notes that actually move the cut toward what you want, on the first pass, without burning rounds you will need later.

A revision round is a real unit of money

Before we talk about how to write a note, it helps to understand what a bad one costs, because the cost is not abstract. On a commercial or branded project, editorial is almost always sold in a fixed number of revision rounds. Two to three rounds is the standard structure in an AICP-style bid: the first cut, then a bounded number of passes to refine it, with anything beyond that billed at an hourly or daily rate. A freelance editor in a mid-size US market runs somewhere between $500 and $1,200 a day depending on experience and the finish level. A round is not one note, it is a full pass: the editor works through every note in the batch, re-exports, and sends a new version for review.

So when you spend a round on a guess, you are not spending three words. You are spending a chunk of a day of skilled labor plus a slot on a delivery calendar that has a hard end. Blow through your three included rounds early because the first two were vague, and the fourth round is now an overage line item, an awkward conversation, or a corner someone cuts to hit the date. None of those outcomes are good, and all of them trace back to notes that could not be executed without a guess.

The math is worth sitting with. If a clean, specific set of notes gets you to a lock in two rounds and a vague set gets you there in four, you have not lost two rounds of editing. You have lost two rounds of editing plus roughly a week of calendar plus whatever the relationship costs when a project that should have felt smooth felt like pulling teeth. Specific notes are not a nicety. They are the cheapest schedule protection you have.

The three things a usable note contains

A note an editor can execute without guessing has three parts. Miss any one and you have handed them a puzzle instead of an instruction.

The first is a timecode. Rough cut review tools such as Frame.io, Wipster, and Vimeo Review all timestamp a comment to the exact frame you were looking at when you wrote it. Use that. "The pacing feels slow" is unactionable across a ninety-second spot. "The pacing drags from 00:34 to 00:41" points the editor at seven specific seconds. A note without a timecode forces the editor to hunt for the moment you meant, and half the time they land on the wrong one and fix something you never had a problem with.

The second is the specific observation: what you actually saw or heard that is not working. Not the fix, the problem. "The cut on 00:12 lands a beat before he finishes the word" is a specific observation. So is "the music comes up over the VO at 01:03 and I lose the last line." You are describing the thing your eye or ear caught, in plain terms, at the frame where it happens.

The third, and the one almost everyone skips, is the intent behind the note: what you are trying to achieve. This is the part that lets a good editor solve the problem better than your stated fix would. "Make it punchier" is a fix with no intent. "I want the opening to feel urgent, like we are already mid-action when the spot starts" is intent. Given the intent, the editor might trim the first shot, or drop the establishing beat entirely, or change the music in point, and any of those might beat the specific trim you would have asked for. When you give the intent, you are hiring their judgment instead of overriding it.

What the bad notes really mean

Almost every useless note is a real reaction wearing the wrong clothes. The reaction is legitimate. The words fail to carry it. The fix is to translate the feeling back into what triggered it. A few of the usual offenders:

"Make it pop" almost always means one of three concrete things: the color is flat and needs more contrast or saturation, the pacing is sluggish and needs tighter cuts, or the opening does not grab and needs a stronger first image or a music change. Those are three completely different jobs in three different rooms. Decide which one you actually mean, name it, and put a timecode on it.

"I don't love it" is a gut reaction with the diagnosis missing. That is fine as a starting point, but do not send it. Watch the section again and find the frame where the not-loving starts. Nine times out of ten there is a specific moment, a cut, a line reading, a music swell, that turned you. Send that frame and what happened at it.

"Can we make it more dynamic" usually means the edit is holding on static wide shots too long and you want more cutting, more movement, or more variety in shot size. Say that. "From 00:20 to 00:35 we sit on the same wide, can we get some tighter coverage in here to build energy" is a note. "More dynamic" is a mood.

"The client wants changes" with no specifics attached is the worst one, because it launches a guessing round that helps nobody. If you are the middle layer between an editor and a client, your job is to convert the client's reactions into executable notes before they reach the edit bay, not to forward the vibe. An unconverted client note is a round you are volunteering to waste.

Batch the notes, single-thread the voice

Even perfect notes can wreck a schedule if they arrive wrong. Two process rules matter as much as the wording.

First, batch. Send one consolidated set of notes per round, not a trickle of one-off comments across three days. An editor who gets a note at 9 a.m., acts on it, then gets a contradicting note at 2 p.m. has done work that is now garbage, and you paid for it. Watch the whole cut, sit with it, collect every note, then send the batch. The rough cut review is a review, not a live chat. If something is genuinely broken and blocks the rest of the review, flag that one thing immediately and hold the rest.

Second, single-thread the voice. On projects with multiple stakeholders, the fastest way to stall a cut is to let three people send notes directly to the editor. They will contradict each other, the editor will not know whose note wins, and you will spend a round reconciling humans instead of improving the edit. Pick one person to own the notes document. Everyone routes their reactions through that person, who resolves the conflicts, kills the redundant notes, and sends one coherent voice to the edit. The editor should never be the one deciding whether the CMO or the brand manager was right.

A clean notes document has a predictable shape: grouped by timecode in order, each note stating the observation and the intent, with a clear separation between "must change" and "would be nice." That last distinction saves rounds on its own. If the editor knows which five notes are load-bearing and which four are preferences, they can prioritize when time is tight instead of treating a nice-to-have color tweak with the same weight as a broken audio sync.

Protect the person, not just the schedule

There is a relationship cost to bad notes that does not show up on the invoice but shows up everywhere else. An editor who gets vague, contradictory, drip-fed notes learns that this client is going to be painful, and they price it in next time, or they stop taking the calls, or they give you their B-effort because the A-effort keeps getting second-guessed by feedback they cannot parse. Good notes are how you stay the client an editor wants to work with, which on a freelance-heavy project is a genuine competitive advantage when you need someone good on short notice.

The tone of the note matters too, and it is cheap to get right. "This cut at 00:12 is jarring, I think we are landing a frame early on his line, can we let it breathe" respects the person. "The edit here is bad" does not, and it does not contain a single piece of information the editor can act on. You can be direct and specific without being dismissive. Direct and specific is exactly what a professional wants. Dismissive and vague is what makes them start looking for the exit.

None of this means you have to soften real problems or pretend a cut is working when it is not. Say the hard thing. Just say it as an observation tied to a frame with a reason behind it, and the editor will hear it as a professional flagging a professional issue, which is what it is.

The whole thing, in one habit

If you take one practice away from this, make it this: before you send any note, ask whether the editor could execute it without asking you a single follow-up question. If the answer is no, the note is not done yet. Add the timecode. Name what you saw. Say what you are trying to achieve. That thirty seconds of extra effort per note is the difference between a two-round lock and a four-round grind, and on a real project that difference is measured in days and dollars, not in vibes.

The rough cut is the most leveraged moment in the whole edit. It is the point where a few well-formed sentences steer a full day of skilled work in the right direction, or the wrong one. Spend your attention there. The cut you get back is only ever as good as the notes you send in.