How to Brief Clients Before a Rough Cut Review So They Judge the Story, Not the Polish

Brief your client before you send a rough cut, and tell them in plain language what stage the edit is at, what you want them to judge, and what they should ignore for now. A rough cut review goes wrong when a client judges unfinished polish as if it were the finished film, so they spend their notes on color, audio levels, and titles while story problems sail through untouched. A short brief sent with the link fixes that, because it gives the client a job to do and a deadline to do it by.

What should clients judge in a rough cut?

A rough cut is for story, structure, and meaning, not for finish. Ask your client to judge three things and only three things. First, does the story make sense from start to finish, and does each section earn its place. Second, does the message land for the intended audience, in words that audience would actually use. Third, is anything missing, wrong, or out of order, such as a claim that is no longer true or a shot that shows the old packaging.

When clients have that short list, their feedback gets sharper fast. Instead of a vague note like it feels a bit flat, you get a usable note like the middle section repeats the opening claim, so cut the second version. That kind of note can be fixed in minutes, and it is easier to act on when the client pins it to the exact second where the problem sits.

What should clients ignore for now?

Name the unfinished work out loud, before the client has a chance to worry about it. Tell them the color is not graded yet, the audio is not mixed, the music is a placeholder, and the titles are temporary. Clients are not being difficult when they flag these things, they are trying to help and they have no way to know what is finished and what is not unless you tell them.

Put this in one sentence at the top of your message. A client who knows the audio will be cleaned up later will stop writing notes about background noise and start writing notes about whether the interview answer supports the claim on screen. That shift can save a full round of revisions.

How do you write a rough cut brief that actually gets read?

Keep the brief short enough to read on a phone, because many clients will open your link on their phone between meetings. Five lines are plenty, and each line should do one job.

• Stage, this is a rough cut for story and structure, and the polish comes later.
• Job, please judge the story, the order, and whether anything is missing or wrong.
• Ignore, please skip color, audio levels, music, and titles for this round.
• Deadline, please send all notes by Thursday so the next cut stays on schedule.
• Notes, please leave each note on the review link at the exact moment it applies to, so nothing gets lost in email.

That last line matters more than it looks. Notes scattered across email, text messages, and phone calls are where edits go wrong, because a note that lives in three places gets fixed twice or not at all. One review link keeps every note attached to the work it describes. With File Approved, reviewers open one link with no account to create, leave timecoded comments on the video, and the final approval produces a timestamped certificate that records the reviewer, the time, the file, and the version.

How do you stop polish notes from derailing the story?

Even with a good brief, some polish notes will slip through, and the trick is to handle them without starting an argument about them. Thank the client, log the note for the polish pass, and steer the conversation back to the story question that still needs an answer. A reply like that is logged for the finish, and can you confirm the middle section still makes sense once that claim is fixed, keeps the project moving and keeps the client feeling heard.

It also helps to show your working at the next cut. When you send the second version, list the story changes you made and note that the polish pass is now under way. Clients trust a process they can see.

What if the client still sends only polish notes?

If a client sends a dozen notes and every one is about polish, treat that as useful information rather than a failed review. It usually means the story is working so well that nothing in it bothered them, or they did not understand that this round was for story. Ask one question, whether the story and order feel right to them, and whether they are happy for you to move to polish on that basis. If they say yes, you have a clear go ahead. If they say no, you get the story notes you needed, just a little later than planned. Either way, you avoid polishing a cut for a week only to learn the client wanted a different story all along.

Should I send a rough cut with no music at all?

Silence can be more distracting than a placeholder track, so a simple temp track usually works better than nothing. Tell the client it is a placeholder and that the final music choice comes later.

How long should a client get for a rough cut review?

Two or three working days is a fair window for most projects, and a deadline in the brief makes it real. Without a date, a review can drift for two weeks while your schedule fills up, and then the rush to finish lands on you.

What if two reviewers disagree about the story?

Ask the named decision maker to settle it before you edit, rather than trying to satisfy both versions at once. Two opposite story notes cannot both be fixed in one cut, and guessing which one the client prefers is how a project ends up in a third round that nobody budgeted for.

A rough cut review is not a test of how finished your edit looks, it is a checkpoint for whether the story works. Brief the client on the stage, give them three things to judge, name what to ignore, and keep every note on one link. Do that, and the polish pass becomes what it should be, a finish on a story everyone already agreed on, not a rescue mission for a story nobody checked.