
An assembly edit, or assembly cut, is the first full version of your sequence: every shot and selected line laid down in order, start to finish, with no trimming for pace and no polish. Its only job is to prove the story holds together as a whole. It is meant to be long, loose, and a little ugly. That is the point.
New editors often try to make the assembly good. Do not. An assembly you have fussed over is a rough cut wearing the wrong name, and you have spent hours polishing material you might cut entirely once you see the shape.
The assembly answers one question: does this thing work as a sequence? You take everything you decided to keep, your selects from the paper edit or your marked clips, and you put it in order on the timeline. Then you watch it. You are looking for structure, not finesse. Does the opening earn attention? Does the middle build? Does the end land? If the bones are wrong, you find out now, before you have invested in trims, sound, or color.
As Filmsupply puts it in their guide to the cut stages, the assembly is where you 'build the film's bones and see if it holds together.' Everything after is refinement. Get the bones wrong and no amount of polish saves it.
The standard progression goes paper edit, then a stringout of selects, then the assembly, then a rough cut, then a fine cut, then picture lock, then final. Frame.io's breakdown of the editing stages lays out the same ladder.
The line people blur most is assembly versus stringout. A stringout is just selects in a row, no real story decisions. An assembly is the first version where you have committed to an order that is meant to tell the story. A stringout is raw material organized; an assembly is a draft.
Longer than your final, on purpose. A useful rule of thumb: keep the assembly under roughly 140 percent of your target runtime. If you are aiming at a 10-minute film, an assembly around 12 to 14 minutes means you have selected with discipline and left yourself room to tighten. An assembly that is three times the target length means you have not actually made decisions yet, you have just collected.
That said, on a documentary feature the first assembly can run wildly long, sometimes hours, because the story is still being discovered. The 140 percent guideline is for projects where you already know the shape. Adjust to the job.
Concretely: a 90-second social edit might have an assembly of two to three minutes. A 10-minute corporate film, 12 to 15 minutes. A 22-minute episode, maybe 30. A feature documentary, anything from 90 minutes to several hours on the first pass. The constant is not the ratio, it is the intent, lay in everything you might keep, in order, and refuse to trim until you have watched the whole thing. The number is a sanity check, not a rule to obey.
You are cutting a four-minute customer testimonial reel from three interviews. Your paper edit gave you 18 selects across the three people. You drop all 18 on the timeline in the planned order. No trims, no music, no b-roll yet. It runs five and a half minutes. You watch it once, straight through.
Immediately you see two problems the page did not: speaker two repeats speaker one's point, and the strongest line, currently in the middle, should open the piece. Neither is a trimming problem. Both are structural, and you caught them in the assembly instead of after you had carefully tightened a sequence you were about to rearrange anyway. You fix the order, drop the redundant select, and now you have a real rough cut to refine.
Notice what the assembly did there: it surfaced two issues in a single five-minute viewing that would have stayed hidden if you had jumped straight to polishing. The redundant point is invisible on paper because you read the two speakers minutes apart. The weak opening is invisible until you feel the piece start slow in real time. That is the entire reason the stage exists. An assembly is cheap insurance against discovering a structural flaw after you have already invested hours treating the symptoms.
A first assembly is overwhelming if you do not know what you are watching for. You are not judging quality. You are judging shape. Three questions, in order:
Does it start in the right place? Assemblies almost always open too slow because you placed the chronological beginning, not the strongest one. Note where the energy actually arrives. That is often your real opening.
Where does it sag? Every first assembly has a dead patch, usually a stretch where two selects make the same point or a tangent you were fond of in the room. Mark the spots where your attention drifts. Those are cuts, not trims.
Does the ending land? If the last line leaves you flat, the payoff is somewhere else in the assembly and needs to move. You will feel this in the gut before you can explain it.
Write these reactions down as you watch, do not fix them mid-viewing. The point of the assembly is one honest read of the whole thing. Stopping to tinker after every problem means you never see the shape.
On scripted or short-form work, the assembly is a quick structural check. On a documentary feature it can be a major undertaking that runs for hours and gets rebuilt several times, because the story is genuinely being discovered in the edit, not just executed. Editors on long docs often build multiple assemblies from different angles, this character leads, no this theme leads, and watch each to find which version of the film wants to exist. That is not indecision, it is the job. The footage does not come with a script, so the assembly is where the script gets reverse-engineered.
This is also why paper editing pays off most on exactly these projects. If you have already wrestled the structure into shape on the page, your assembly starts from a real hypothesis instead of a shrug, and the hours of rebuilding shrink.
Polishing too early. Adding music, color, and frame-accurate trims to an assembly is wasted effort if the structure changes, and it will. Build it loose.
Not watching it as a whole. The entire value of an assembly is seeing the sequence end to end. If you only ever scrub around in it, you never get the read on structure that justifies the stage.
Confusing length with completeness. A long assembly is normal and healthy. It does not mean you are behind. It means you have raw material to carve.
Treating it as a deliverable. An assembly is for you, not the client. Show a raw assembly to a stakeholder with no framing and you will drown in notes about audio and color you already plan to fix. If someone outside the edit needs to weigh in this early, show them the paper edit instead, it is built to be read.
The slow part of an assembly is finding and placing each clip. If you paper-edited first and your selections carry timecode, the assembly is mostly mechanical, you are conforming a plan. This is where a transcript-based workflow pays off: in ScriptCut you highlight lines on the transcript, arrange them, and export a timeline (XML, EDL, or FCPXML) straight into Resolve, Premiere, Final Cut, or Avid, so your assembly arrives in the NLE already in order. See documentary editing from transcript to timeline for the full path.
If you paper-edited, the assembly is your plan made real, and the two should feel almost identical at first. That is the point. The paper edit decided the order; the assembly is that order playing in time. The value of building it is that time reveals what the page could not: a section that read tight now drags, a transition that looked clean now jars, a line you loved now feels redundant against the one before it. The assembly is the reality check on the paper edit, and a healthy workflow expects a few surprises here. If the assembly throws up zero surprises, you either got very lucky or you did not watch it honestly.
This is also the cleanest answer to the old objection that text-first editing ignores performance. You did your structural thinking on the page where it was fast, and now, at the assembly, you confront the actual footage and let it correct you. The page proposes, the assembly disposes. Editors who skip the paper stage and improvise structure straight in the assembly tend to spend far longer here, because they are doing the hard thinking in the slowest possible place.
The tedious part of any assembly is mechanical: finding each chosen moment in the bins, dragging it to the timeline, lining it up, repeating dozens of times. None of that is creative work, it is just friction between your decisions and the sequence. The way to kill the friction is to carry your selections in with their timecodes attached. When you build from a transcript where every highlighted line already knows its in and out point, the assembly assembles itself, you export an ordered sequence (XML, EDL, or FCPXML) into Resolve, Premiere, Final Cut, or Avid and start watching instead of hunting. That is the workflow ScriptCut is built around, and transcript to timeline walks the full path.
Treat the assembly as a structural test, not a draft you are proud of. Build it long, watch it whole, fix the order, then move on. The faster you get an honest assembly in front of yourself, the sooner you know whether the story works. Want the next stage? Read what is a rough cut. Want to build the assembly without hunting clips, try ScriptCut.
The assembly is everything in order, untrimmed, to test structure. The rough cut is the next pass where you trim for pace and start shaping performance. Assembly proves the bones; rough cut starts the polish.
Longer than your final. For projects where you know the shape, aim under about 140 percent of target runtime. Documentary features often run much longer at first because the story is still being found.
No. A stringout is selects in a row with no story decisions. An assembly is the first version arranged in an order meant to tell the story.
No. Keep it loose. Polish before the structure is settled is wasted, because the order will change once you watch it whole.