Skip to content

Assembly version: what it is and why it matters when reviewing video with clients

What the assembly version is and why it matters when reviewing video with clients: first organization of raw footage, narrative order, and rough cut prep.

Editorial teamUpdated

The assembly version is a first organization of raw footage on a timeline. For your agency or studio, it serves to order shots, confirm that no material is missing, and prepare the piece before building a rough cut to show the client.

What it includes

At this stage, the editor isn't yet aiming for a polished version or one that's ready for the client. The usual steps are:

  • Importing raw footage.
  • Reviewing shots.
  • Chronological or narrative ordering.
  • Basic audio sync if applicable.
  • Initial selection.
  • Detecting missing material.
  • Flagging problems.

It's like laying all the ingredients out on the table before you start cooking.

Why it matters

The assembly version makes it possible to catch early whether you're missing an interview, a B-roll shot, an audio track, a logo, or a key scene. The sooner the problem shows up, the easier it is to request a file, shoot pickups, or adjust the story.

It also helps direction, production, and editing share an initial sense of the material available.

Difference from a rough cut

The assembly gathers and orders selected takes; the rough cut develops and adjusts that narrative proposal. Adobe’s editing guide distinguishes these steps. Terminology and when versions are shared with clients can vary between teams.

Managing the process

Record which version is in assembly, review, or finishing in the project’s tracking tool. Polimake lets you store and retrieve audiovisual material; also preserve the editing project and its dependencies so the edit can be continued.

Checklist

  • Is all the raw footage here?
  • Is the audio synced?
  • Are any important shots missing?
  • Does the overall order make sense?
  • Were any technical problems detected?
  • Has a safe backup been saved?
  • Does the team know what comes next?

Reviewing material early can reveal unsynced audio, a missing shot, or a logo whose correct version is on another drive. The time needed to resolve it depends on the problem; this stage does not guarantee a fixed saving of hours or days.

Frequently asked questions

What else is the assembly version called?

In English it's called the assembly or assembly cut. Spanish-speaking teams also call it "primer montaje" or "premontaje"; what matters is that the whole team uses the same name for the same stage so it doesn't get confused with the rough cut.

Do you show the assembly version to the client?

Usually not. It's an internal tool, long and without rhythm, and showing it invites comments on things that haven't been worked on yet. It makes sense to share it when the client has to make early decisions about the footage, as in documentaries with lots of interviews.

How long is an assembly version?

It's usually much longer than the final piece, because it includes all the usable takes in order before anything is selected and trimmed. There's no fixed ratio: it depends on how much footage was shot and the planned length of the deliverable.

For productions with several editors working in parallel, or with clients who receive intermediate reviews, it's also worth documenting naming conventions, project structure, and delivery folders starting with the assembly version. A consistent organization from the first pass holds up; a messy one only gets worse with each iteration. Coordinate it with post-production and store raw footage, clean audio, music, graphics, and permissions in your cloud library so anyone on the team can continue the project without rebuilding the context.