The rough cut is where the edit gets its shape. Your editor has watched the footage, pulled the best takes and put them in order so you can judge the story, the structure and the pacing. The final cut is that same edit after every approved change. It adds color correction, a proper audio mix, licensed music, graphics and captions, and it is exported to the specs of the platform it is going to.
One is a draft for decisions. The other is the file you publish.
What does a rough cut look like?
Expect it to look unfinished. Audio levels may jump between clips, the color will be straight from the camera, and the music may be a temp track the editor dropped in to test pacing. Titles and lower thirds, the name and job captions at the bottom of the frame, are often plain placeholders or missing.
The spine of the video should be there. For a testimonial, that means the customer's best lines in an order that tells a before and after story. Gaps for b roll, the supporting footage cut over the interview, should be marked even if the shots are not in yet.
On a long interview, we often send a selects reel first. This is a string of the strongest moments with no structure, so you can pick what makes the cut. It saves building a rough cut around the wrong quotes.
What changes between the rough cut and the final cut?
Once you approve the structure, the edit reaches picture lock. From then on, the order and timing of shots stay fixed. Everything after that is finishing work built on top of that timeline:
- Color: correction to match shots, then a grade or LUT for the look.
- Audio: dialogue cleaned and leveled, with J cuts (the next clip's sound starting before its picture) to smooth transitions.
- Music: temp tracks replaced with licensed tracks you have the right to publish.
- Graphics: lower thirds, titles, logos and calls to action in your brand fonts and colors.
- Captions: burned in for social, or delivered as a separate file for YouTube.
- Export: the right aspect ratio, resolution and file format for each platform.
Many teams add a fine cut between the two. This is a tightened rough cut where the trims are frame accurate and the pacing feels right, but finishing has not started. On short form, the rough and fine cut often collapse into one draft.
How should you give feedback on a rough cut?
Judge the story, not the polish. Does the hook earn the next ten seconds? Does anything drag, is a point missing, does the ending land? Notes like "the font looks wrong" or "the color is flat" waste a round, because both get handled in finishing.
The rough cut is the cheapest moment in the whole edit to change your mind.
Leave time coded notes so the editor knows exactly which frame you mean. "At 0:42, cut the conference story and go straight to the result" is a note an editor can act on. "Make it punchier" is not. Frame.io lets you click a frame and type the note right there, and it is how we review every draft at Crispy Edits.
Send all your notes in one pass, and get every stakeholder's notes into that same pass. Two people sending conflicting notes a day apart is the most common reason we see a project run an extra round.
Why are changes after the final cut so expensive?
Finishing work depends on the timeline staying still. If you move a section after picture lock, the captions shift and the music edit breaks. Graphics land on the wrong shot, and the audio mix has to be rebuilt around the change.
Fix the story on the rough cut and the details on the final, never the other way around.
Notes on a final cut should be small and specific: a typo in a lower third, a wrong word in the captions, music sitting too loud under one line. If you want to reorder sections at this stage, the rough cut review was skipped or rushed. Say so plainly and treat it as a new revision, not a polish note.
If you pay for editing by the hour, this is where the hours go. In the projects we edit, late structural changes cost more time than almost anything else, including heavy graphics or a large pile of footage.
Treat the rough cut as a decision meeting and the final cut as a sign off. Approve the structure first, then let the editor finish it once.
