Video review and approval workflow at the rough cut stage
How to run the video review and approval workflow at the rough cut: what to review, how to consolidate feedback, and how to lock changes without costly rework.

A rough cut is a preliminary version used to review a video’s narrative proposal. It is not polished, but supports decisions about story, pace, order, length, voice, and temporary music before finishing. Review and approvals can continue at later stages.
What it's for
The rough cut helps you make decisions before investing time in fine finishing. At this stage you check whether the video tells what it's supposed to tell. Color, mix, final graphics, subtitles, or sound adjustments may still be missing.
It shouldn't be evaluated as a finished piece. It should be reviewed as structure.
Difference from the assembly version
The assembly version gathers takes into an initial sequence. The rough cut selects and adjusts that sequence to develop the story; this does not mean the earlier version has no narrative intent. Adobe’s rough-cut guide describes this progression.
What to review
- Is the main idea clear?
- Does the opening hook?
- Does the storyflow work?
- Is the length right?
- Are any shots or assets missing?
- Does the music support the tone?
- Is the CTA clearly present?
- Are there any sensitive messages to review?
How to give feedback
Feedback should be specific. Instead of "it doesn't flow," note the timecode, the problem, and a proposal: "at 00:42 context is missing," "the interview comes in too late," "the product should appear sooner," or "this block repeats an idea." When several people review the same rough cut, it's best to consolidate comments before sending them to the editor. Sending three contradictory messages in different threads tends to create more confusion than direction.
For pieces with an external client, a good practice is to send the rough cut with the creative team's own notes. Those notes indicate what will be fixed in the next version and what is already considered locked, which avoids redundant feedback on details that don't reflect the final direction.
Centralize comments, owners, and review status in the tool agreed with the team. Polimake lets you store and retrieve audiovisual versions and source material. Preserve the editing project and its dependencies so work can continue. See also post-production and the initial assembly.
Operational metric
Measure rounds of changes, time to approval, and the number of problems detected late. A well-reviewed rough cut avoids expensive rework in the final phase. A sign of a healthy process: most structural changes show up in the rough cut and not in the final version; if script or order corrections keep coming up in the last round, the review came too late and it's worth rethinking the flow on the next project.
Frequently asked questions
What is a draft cut?
Draft cut is another name for the rough cut, or first edit: an unfinished working version for reviewing structure and length. Since naming varies between production companies, it's worth spelling out in the quote what gets delivered at each version and how many rounds of changes are included.
What comes after the rough cut?
The fine cut, where cuts, pacing, and length are refined once the structure has been approved. When the edit is declared final (picture lock), finishing begins: color grading, sound mixing, final graphics, and subtitles.
How many rough cut versions are normal?
However many the contract sets: it's common to agree on a number of revision rounds per phase and to budget additional ones separately. If a piece needs many rounds of structural changes, it's usually a sign that the script or the brief wasn't locked before editing began.
Why does the rough cut have temporary music and titles?
Because temp music and placeholder titles help judge pacing and intent without waiting for the final material. The client should be told they're temporary, and any music that isn't licensed for the final use has to be replaced before publishing.