How to create an assembly cut document in Premiere Pro
An assembly cut is the first complete version of a film assembled from selected takes, even before pacing, music, titles, and polish are finished. It gives editors and producers a shared map of the story. In Premiere Pro, this is usually called a rough cut or stringout, while the saving container is a project file containing bins, clips, and sequences.
Creating an assembly cut document in Premiere Pro is therefore a matter of building a sequence inside a well-organised project, then saving that state deliberately. This guide covers the full path from media preparation to a reviewable export, with settings and review habits relevant to Australian productions.
Understanding the project and sequence structure
Premiere Pro does not create a separate file type called an assembly cut document. The practical equivalent is a Premiere Pro project, saved as a .prproj file, with a clearly named sequence holding the assembly. Keeping source clips, proxies, graphics, and the assembly in separate bins makes later revisions much easier.
Choose the sequence frame rate before adding footage. Broadcast work commissioned in Sydney or Melbourne commonly uses 25 fps for 1080p delivery, with 50-field interlaced material captured as 25p or 50i depending on the broadcaster. Match the source and delivery requirements rather than changing frame rate after the first edit, since that can make every clip and audio sync point move.
Create bins for rushes, selects, interviews, music, graphics, and exports. This simple structure prevents an initial assembly from becoming a search exercise once a documentary runs several hours or a commercial campaign accumulates hundreds of clips. Give the main sequence a descriptive name that identifies its stage, such as Assembly_v01.
Preparing footage for a reliable edit
Before importing, copy camera cards rather than editing their only copy. Start with File > New Project, choose a controlled working location, and then use File > Import to select the footage folder. If the clips came from an iPhone, DigiSNS’s Premiere Pro import guide provides useful background on bringing MP4 files into Premiere, although current iPhones may record HEVC codecs that require a recent version of Premiere Pro.
Build the project bins as you import. Use consistent names that include the camera, reel, and take, and add keywords for people, locations, and usable ratings. Relink rather than repeatedly importing duplicate files; on a long interstate shoot, one clear folder structure can save hours when a drive arrives separately from the camera cards.
Test a small group before ingesting everything. Professional cameras can record XAVC, AVCHD, BRAW, or MXF, and a card may contain more than one format. Import a representative file from each card and note any decoding or frame-rate warnings. This check prevents a bad camera setup from becoming a hidden problem in the first assembly.
Building the first chronological assembly
Create the main sequence at the project resolution and frame rate, then begin with a single video track and one or two audio tracks. Drag selected clips into the timeline with the Overwrite command. This removes gaps without generating accidental black frames, and it lets you judge the story before visual refinement makes each edit feel permanent.
Build the assembly by selecting the strongest usable moments for each part of the narrative. Keep a generous handle around every clip so interviews can be shortened and visual transitions can be moved later. For a documentary, establish the beginning, main progression, turning points, and ending before deciding how much the cut should compress.
Watch the sequence from beginning to end with the sound off, then again with sound on. The first viewing exposes structural problems that frame-by-frame work can hide: a missing explanation, two similar interviews doing the same job, or a sequence ending without a clear resolution. Record major omissions while they are obvious, but leave detailed timing work for the next pass.
Refining rhythm, sound, and continuity
Turn the assembly into a rough cut by trimming pauses, tightening entrances and exits, and using Ripple Edit to close unwanted space. Use Slip and Slide judiciously when a reaction shot needs a small timing adjustment. Transitions should support meaning rather than disguise weak joins, so dissolves and simple cuts usually provide the cleanest first refinement.
Rebuild the audio mix from dialogue outward. Normalise interview levels, remove hum and noisy passages, and check that lip sync remains intact after edits. Add music only after the dialogue structure is stable; otherwise, changes in running time can create work twice. In Premiere Pro, label dialogue, music, effects, and ambience tracks clearly so revisions remain manageable.
Before fine trimming, finish any working-copy conversion required by mixed camera media. If a camera recorded MXF that Premiere Pro cannot decode directly, the Pavtube iMIXMXF workflow provides one Windows and Mac route to prepare the material. Keep the camera originals untouched, then compare converted duration, frame count, audio sync, and timecode with the source before replacing the working file.
Add temporary titles, lower thirds, and simple visual references only after the narrative order is secure. Check title safe areas, aspect ratio, and readability on a standard Australian television screen. Avoid burning permanent branding into the assembly sequence; place graphics in separate dynamic-link or nested-sequence setups so a client note can be resolved without redesigning the whole timeline.
Running reviews with Australian teams
Export a review file with timecode burn-in, then use Premiere Pro’s markers to point producers to the exact frame of concern. Where a team uses Premiere Pro’s review panel or a compatible review service, reviewers can add comments beside the sequence. A short verbal walkthrough still helps when several people are joining from different cities.
Treat culturally sensitive material carefully. Projects involving 25 April, ANZAC Day, or Australia Day may require additional permissions, archival clearances, and respectful review by people connected to the events or communities represented. Record those decisions in the project notes so an editor working months later can see why a clip was retained, shortened, or excluded.
Remote reviews need a little Australian scheduling discipline. Sydney and Melbourne observe daylight saving, while Perth does not, so confirm the time zone and call time rather than assuming every participant sees the same clock. Australian sets also rely on Type I power points, which should be checked in venues and studios before a long review or recording day.
Saving, versioning, and delivering the cut
Organise the project for reopening before sending a review. Use File > Save As to create versioned project names such as Assembly_Cut_v01.prproj. Consolidate media into a controlled folder, keep camera originals in read-only storage, and use Purge Unused Media only on a duplicate after checking every bin. This avoids creating a tidy project that has accidentally lost an early assembly.
For browser-based approval, compare the client’s process with a suitable QloudPress web workflow, while retaining a downloadable review file and a contact sheet. Label every export with its version, date, frame rate, and audio status. Budget for Creative Cloud subscriptions and cloud storage in AUD, since Australian accounts are commonly billed locally.
Use this internal assembly check before circulating a review:
- Assembly version 03 saved as 1080p25 with a full mix
- Camera originals backed up to two separate drives
- Main sequence opening cleanly in Premiere Pro
- Timecode and frame rate noted in the review email
For an external review or final delivery, confirm:
- H.264 MP4 export meeting the broadcaster’s resolution requirements
- Captions, music rights, and credits checked against delivery terms
- Client-approved version stored separately from working files
- Project folder tested after transfer to the delivery drive