Presenting a Rough Cut to Clients: How to Frame It and Get Useful Notes
Clients don't judge your edit, they judge whatever you forgot to label. How I frame scratch music, temp voiceover and missing graphics so a rough cut round comes back with story notes.
The worst rough cut review I ever ran in my agency had nothing to do with the edit, right, the structure was solid and the interview bites sat in a sensible order. I still lost the entire round, because I sent the link with one line saying the rough cut is ready, let me know your thoughts. What came back was a paragraph about the music, which was a scratch track, a question about why the logo looked blurry, which was a screenshot sitting in until their designer sent the vector file, and not one word about whether the story worked.
That was the day it clicked for me, right, that presenting a rough cut to clients is mostly a framing job. A client who has never sat next to an editor can't tell which parts of the cut are finished and which parts are basically sticky notes, so they react to whatever is loudest, and the loudest thing in a rough cut is almost always the stuff you haven't done yet.
So this one is for the editor or producer at a small agency about to send a first assembled cut and already nervous about the temp music and the empty graphics slots. I've been that person, right, and most of the fix turned out to live in the message that goes out with the link.
What a client should and should not judge in a rough cut
The textbook version of what a rough cut actually is is simple enough, it's the second of three stages of offline editing, after the initial assembly, and the first version where you can see the shape of the film. Clients don't read textbooks though, so I explain the stage every time in words that fit their project.
The way I explain it comes from the software side of my life, right, because when we design a new screen for PlayPause we start with a wireframe, and nobody in that meeting comments on the button color. A rough cut is basically a wireframe for a film, so the client judges the story, what's missing and where it loses them, and the music, color, mix and graphics stay off the table.
I go deeper on that line in the rough cut vs fine cut breakdown, but the rule I give my editors fits in one sentence, anything that will change anyway for technical reasons can wait, and anything that changes the shape of the film needs the client now, while moving a whole section is still cheap. Does that make sense, right, you're saving their attention for the decisions only they can make.
story order, what is missing, sections that drag, the opening and the ending
music choice, color, sound mix, graphics, exact trims and typos
Setting expectations before you send the link
The link is the easy part, right, because the message that travels with it is the only briefing the client ever gets on how to watch. Mine always carries the name of the stage, a plain list of what is placeholder, three questions and a date.
For a founder brand film, that message reads roughly like this: this is the rough cut, the whole story running long on purpose, with scratch music, our producer reading the voiceover for timing, grey slates where graphics will go and no grade or mix yet. Please look past all that and tell me whether the first twenty seconds make you want to keep watching, whether anything from the brief is missing or out of order, and where your attention drifted, and if the notes reach me by Thursday we keep the fine cut date.
The reason I'm this fussy is simple math. Say a project is quoted with three rounds and the first goes entirely on music notes that would have changed anyway, then a third of your revisions went on nothing, right, and the story problems you should have heard in round one arrive in round two, when every fix costs more.
Inside PlayPause I do two small things before the link goes out. The first is a custom status on the card, Rough cut: story review, so my team knows what kind of notes we're collecting and nobody starts polishing a cut that might lose a section tomorrow. The second is a comment on the very first frame, 00:00:00:00, where I paste that same placeholder list. Comments in PlayPause stick to the exact frame, so that note is the first thing on the timeline when the client opens the client review portal in their browser, with no account and no install.
Then there's who-watched analytics on Creator and up, showing who opened the link, when, and from which city. To be very honest it has saved me a lot of awkward chasing, because if nobody has watched by day two I send a nudge, and if the client opened it last night I leave them alone.
Scratch music, temp voiceover and missing graphics in a rough cut
Let me be very honest about scratch music, because some editors say never to put music in a rough cut, and I get the logic, but a talking head cut with no music plays slower than it really is. So I use it, and the catch here is what I pick, right, either a track from the library we'll actually license from or something deliberately neutral, because a client who falls in love with a temp track you can't afford will hear every licensed option as wrong.
Temp voiceover is the second trap. If the producer read the script into a phone for timing, the client needs to hear in writing that the voice is a guide and the real talent records after picture lock, otherwise you get notes on the accent of someone who will never be in the film.
Missing graphics are the third, and I'm strict with my editors here, a missing graphic is never a black hole in the timeline. It's a grey slate with the name of the graphic on it, for instance GFX pricing chart here. A black frame reads as a broken export and a stand-in screenshot reads as a bad logo, which is exactly how I lost that round, whereas a named slate reads as a plan. Add no grade, no mix, lower thirds not proofread and so on, and the whole list goes into that frame zero comment.
- Scratch music, the final track is licensed after picture lock
- Temp voiceover read by our producer as a timing guide
- Grey slates that name each missing graphic
- No color grade and no sound mix yet
- Lower third text not proofread
Asking for story notes instead of polish notes
Open questions like what do you think get open answers, and open answers from someone who isn't an editor drift toward whatever is easiest to describe, which is almost always the music, and that's why the three questions in my message are so narrow. I pull them straight from the original creative brief, right, because the brief is the document both sides agreed on before anyone shot a frame, and when a client rereads their own goals next to the cut the notes get very very specific.
Polish notes will still come, and I'm pretty sure no amount of framing stops a client from mentioning that they hate the font. I don't ignore them, I reply in the thread with noted for the fine cut and @mention the editor, so the note is captured but nobody touches it this round. What I refuse to do is fix them on a rough cut, because a polish fix on a cut that may still lose a section gets done twice, and that is how scope creep sneaks into a project without anyone signing a new brief.
For interview-heavy pieces some editors email a transcript for a paper edit, which works, but then the text and the cut live in different places. On the Agency plan and up, PlayPause does AI transcription with a clickable transcript and an SRT export, right, so a client who thinks in words gets the text to read and still leaves the note on the exact frame of the video instead of in the margin of a document. If a director is in the loop too, I keep separate director and editor communication protocols so their notes never collide with the client's.
A client who knows what they are looking at gives you story notes, and a client who has no idea gives you notes on the music.
Collecting pacing notes across whole scenes
Pacing notes are the most useful thing a client gives you on a rough cut and the hardest to capture, right, because pacing is a feeling across a stretch of time rather than a moment. Frame comments suit specific moments, like an abrupt cut at 00:37, but for drag you want range comments, where the client selects 01:05 to 01:48 and writes one note about the whole span. My walkthrough on commenting on a section of video and the time-coded annotations page show the mechanics, and the words on a range tell me why it dragged, which I can't read off my own timeline.
Picture that same founder brand film, where the brief asked for about two minutes and the rough cut runs 3:10. I'd much rather get three range comments saying the factory tour drags, the pricing section confuses and the ending feels rushed than one note saying cut it to two minutes. Cutting to time is my job, but knowing which part of their own story matters less is their knowledge, and you see what I mean here, the extra minute is what lets them show you.
Also assume the client watches on a phone between meetings, right, which I've covered in client video review on mobile, so each of the three questions has to be answerable in a line. When the notes come back, my editors who cut in Premiere Pro don't retype timecodes from a list. They see the comments inside Premiere through the Premiere Pro panel and click one to jump the playhead to that frame, which across twenty range notes is a lot of scrubbing nobody has to do.
A rough cut that runs past the target length gives the client room to say which parts of their story matter, and trimming to time is the fine cut's job anyway.
Moving from rough cut to fine cut on the same card
The fine cut is where the rough cut presentation pays off or falls apart, because a new version sent as a new link in a new email loses the thread of what the client asked for, and the proof that you did it. With version stacks, on Creator and up, I upload the fine cut onto the same card, it lands as MV2 on top of MV1, the rough cut notes stay attached to MV1, and the client opens the same link as last week.
Then I flip the status from Rough cut: story review to Fine cut: polish review, right, and now I invite the notes I parked, the music, the grade, the graphics, the font they hate. On the Agency plan and up there's side-by-side version compare, so on the fine cut call I play MV1 against MV2 and the client sees for themselves that the factory section got shorter. At the end of the day that builds more trust than any recap email I could write.
The last piece is making this how my whole team presents rough cuts, and that lives in Playbooks, also on Agency and up. Each client gets their own, so the placeholder list and the three story questions sit in the brand playbook as permanent rules, while a folder playbook holds one project's checklist, which isn't done until someone ticks it. Trust me on any level, a junior editor's first rough cut should go out exactly the way mine would.
From there it's the usual loop to picture lock, written up as the rough assembly to fine cut loop, and the rough cut review workflow page shows how it all fits together in PlayPause.
Frequently asked questions
Should I put scratch music in a rough cut?
Most of the time I do, because a cut with no music plays slower than it is and the client ends up giving notes about silence. Label it as scratch in the message and in the frame zero comment, right, and pick from the library you'll actually license from, so the client never falls for a track they can't have.
What should clients expect from a rough cut?
The whole story in roughly the right order, often longer than the final, with scratch music, temp voiceover, grey slates for graphics, and no grade or mix. What I ask them for is judgment on the shape of the film, what's missing, what's out of place and what drags, and I say that plainly before they press play.
How long should a client get to review a rough cut?
I usually give two to three working days with a clear date in the message. Longer than that and the rough cut gets forgotten, while shorter means a busy founder watches once on a phone and sends whatever they noticed first. If who-watched analytics show nobody has opened the link by day two, I send one short nudge.
What if the client only gives polish notes on the rough cut?
Then the framing didn't land, and that's on me. I reply in each thread with noted for the fine cut, then send a short follow-up asking the three story questions again, often with timecodes of the sections I'm least sure about. If there are still no story notes, I treat that as approval of the structure, confirm it in writing and move to the fine cut.
Every plan on the PlayPause pricing page starts with a 7-day free trial, so you can put your next rough cut through one real client round this way before you decide anything.
So yeah. That's my way of saying it.
Saumyajit co-founded PlayPause after years watching review and approval quietly eat creative teams' deadlines. He writes about the workflow side of video, feedback, versioning, and getting to a clean sign-off.
Related resources
Keep reading
Bring your team into one review space
Centralize feedback, lock approvals, and deliver faster, start free today.
Sign Up for Free