A printed interview transcript marked with highlighter and pencil notes next to a laptop showing the same transcript in an editing tool, illustrating the paper edit process.
Paper editing

How to Do a Paper Edit, Step by Step

The ScriptCut Team
/
June 9, 2026
/
11 min read

A paper edit is a written plan for a video built from the transcript before anyone touches a timeline: transcribe with real timecode, read everything once, highlight the strongest lines, arrange them into a story on the page, then verify each line against the footage before you cut a single frame. It predates digital editing and survived the switch to it for a plain reason: reading a page is faster than scrubbing a clip, and dragging a paragraph costs nothing compared to re-trimming one.

Skip the paper stage and every structural decision gets made inside the timeline instead, where changing your mind means re-cutting rather than re-reading. Do the paper stage first and the timeline work becomes mostly mechanical, because the real decisions, what to keep, where it goes, whether it actually plays, already happened on the page. What follows is the process stage by stage, a worked example, the mistakes that show up most often, and the places editors genuinely disagree about the method.

Origins

An old technique that never really went away

The paper edit gets its name from film and early video, when editors marked a printed, timestamped transcript in pencil and physically cut it apart with scissors. Columbia College Chicago's documentary program still teaches a version of it: a two-column script template with picture on one side and dialogue on the other, where a cut line stays visible in strikethrough instead of vanishing, so a decision can be reconsidered without losing the sentence around it. It is standard film-school material well beyond one program. Michael Rabiger's Directing the Documentary treats structuring a film's spine from selects, on paper, before assembly, as baseline craft rather than a shortcut.

Not every editor endorses it. Errol Morris, director of The Thin Blue Line and The Fog of War, told Transom: "No, I don't edit from the transcripts, ever. I edit from the film," adding that paper cuts can give an editor a false sense of the material. He's talking about observational, performance-driven documentary, where tone and behavior carry more weight than the words themselves, and there his objection lands. Most unscripted production, interviews, panels, testimonials, is built more on what people said than on how the room felt, which is exactly what a transcript captures faithfully. Below, documentary filmmaker Jacob Pander walks through building a paper edit from an interview transcript start to finish.

Preparation

Start from a transcript with real timecode

A paper edit only works if every line can be found again fast, which means starting from a transcript that carries accurate, ideally word-level, timecode. Without it, the plan is a well-organized essay with no way back into the footage. Word-level timing is what turns a highlighted sentence into an exact in and out point later, instead of a guess someone has to hunt for by eye.

Auto-transcription handles the bulk of this now; clean up names, jargon and obvious misheard words rather than retyping the whole document. Read the entire transcript once before marking anything. The strongest moment in an hour-long interview is often buried well past the midpoint, and highlighting from line one anchors your attention on the wrong material before the real shape of the conversation has shown itself. On longer footage, read in one sitting where you can; stopping and restarting resets your sense of where the good material sits relative to everything else.

Selects

Highlight ruthlessly, then pull the keepers into a clean document

Mark only the lines worth defending, not the lines that are merely fine. A useful test: would this line survive being cut if someone challenged why it made the page? If half the transcript ends up highlighted, that was a skim, not a decision.

Copy the marked lines, with speaker name and timecode attached, into a fresh document, and group them by beat rather than original order: setup, tension, turn, payoff. Most unscripted material has a version of that shape even when the conversation itself wandered. This grouped document is raw material, not a story yet, the text equivalent of a stringout: everything usable, nothing arranged for flow.

It helps to know the chain of terms this sits inside, since editors use them loosely and it causes real confusion on a crew. The order, roughly, runs: paper cut (the plan itself, called a radio cut when the source is audio-only), selects (the individual lines you pull, also called pulls or lifts), a stringout (every usable select strung together in rough order, unarranged), then the assembly cut built from that plan, the rough cut, the fine cut, picture lock and the final cut. An assembly cut, by convention, should land close to the planned runtime, ideally no more than about 140 percent of the target length, or the paper edit wasn't selective enough. If your assembly is twice your target, the problem started on the page, not in the timeline.

Multi-speaker footage, a panel, several separate interviews on one topic, a roundtable, needs one more piece of metadata: attach the source file to every select, not just the timecode, since two people can say something similar twenty minutes and two different files apart. Tag each select by speaker as you pull it, then build structure across speakers rather than within one file at a time. The strongest version of a scene often cuts between two people answering the same question, a move that's trivial to spot on paper and tedious to discover by scrubbing four separate timelines looking for it.

Structure

Arrange it into a story, then read the whole thing aloud

Order the grouped selects so they build, cutting anything that repeats or stalls momentum. A strong opening line earns attention, the middle should escalate rather than circle, and the ending should pay off what the opening promised. Reordering at this stage costs nothing, since it's text being dragged around, not footage being re-cut.

Then read the full arrangement out loud. This catches what silent reading misses: the answer that needs its question restored, the point that repeats itself, the place where two ideas collide instead of connecting. A killer line that depends on the sentence before it, a common problem with quotes pulled out of context, reveals itself the moment it's spoken without its setup. If the arrangement doesn't flow out loud, it won't flow on screen either, and it's far cheaper to fix here than after assembly.

Verification

Watch every select against the footage before locking anything

Reading well and playing well are not the same thing, which is the entire basis of Morris's objection to paper cuts and the reason the method never stops at the page. A line can read perfectly and still fail on screen: flat delivery, a stumble mid-sentence, a wrong eyeline, a phone ringing somewhere off camera. Watch each selected line against its source clip before trusting it in the final structure, and swap or cut anything that doesn't hold up.

This is where transcript-bound tools change the math. A plain document leaves verification as a manual hunt through file bins to find each timecode; a transcript-based editor keeps the transcript and the clip welded together, so checking a line is a click instead of a search. The broader category, text-based editing, is what made this verification step fast rather than theoretical. Reduct, built specifically for this stage, lets editors highlight directly on a transcript and drag selections into a reel, and ScriptCut plays any selected line straight from the transcript for the same reason: the check Morris says the page can't give you happens before the plan ever reaches a timeline.

Where paper edits actually go wrong

The method fails for predictable reasons, almost always a skipped step rather than a bad idea. Watch for these:

  • Highlighting on the first pass. Marking lines before you've read the whole transcript locks you onto early material before you know what the strongest moments actually are.
  • Never reading the arrangement aloud. Silent reading hides awkward transitions and orphaned answers that are obvious the second you say them out loud.
  • Trusting the page over the footage. A line that reads sharp can play flat. Skipping verification is how a paper edit becomes a transcript of good writing instead of a plan for a good cut.
  • Losing the timecode. A select without a precise in and out point is a line you'll have to re-find by scrubbing, which erases most of the time the method was supposed to save.
  • Stitching fragments into a statement nobody made. Reordering and tightening someone's words is normal editing; assembling a sentence from pieces that changes its meaning is a frankenbite, and it's an ethics problem, not a style choice.

Example

A worked example, start to finish

Take a 45-minute founder interview being cut into a 90-second customer story. A full read surfaces roughly 20 candidate lines out of thousands spoken, most of them clustered in two stretches of the conversation rather than spread evenly through it, which is typical: people tend to say their sharpest things once they've warmed up and once more near the end, not steadily throughout. Highlighting and pulling those lines into a grouped document takes a fraction of the time a full re-watch would.

Arranging them by beat surfaces the actual opening: not the founder's origin story, which reads first chronologically but plays slow, but the specific problem the company solves, which lands harder as a hook. Reading the arrangement aloud kills two redundant lines that said the same thing in slightly different words, and exposes one answer that needs its question restored to make sense on its own. The verification pass against the footage catches a single strong line ruined by a cough mid-sentence; a slightly weaker phrasing from earlier in the interview replaces it because it actually plays clean. What started as 45 minutes of raw conversation becomes a plan that assembles in well under the time the interview itself ran.

Assembly

Turn the plan into a timeline

With every decision already made, the on-timeline work becomes mostly mechanical. Drop each verified select in order. Where two lines meet awkwardly, plan a J-cut or a cutaway to cover the seam rather than discovering the problem mid-assembly.

This is also where a transcript-first tool earns its keep over a plain document. A document still has to be manually conformed clip by clip against its timecodes; a bound transcript can hand off a sequence that opens already assembled in your editor of choice. Exporting a paper edit to Final Cut Pro and Avid covers that handoff in detail, including why the format matters more than people assume: ScriptCut builds its timeline as FCP 7 XML, a format Final Cut Pro, Avid, Premiere Pro and DaVinci Resolve all know how to read, rather than a file type tied to one app. That gap, a real conformed sequence versus a document someone has to re-time by hand, is the difference between a tool built for editors handing off to an NLE and one built mainly for solo, timeline-free output.

Format

How the method flexes by content type

The steps stay constant, but what counts as a strong select shifts with the format. Interview and documentary work is hunting for narrative arc, cross-cutting between speakers where it strengthens the story, and the paper edit is closest here to how the technique was originally built. Podcast-to-clip work is closer to pulling a series of self-contained moments, each one nearly its own tiny paper edit that has to make sense without the rest of the episode around it; turning a podcast into a YouTube video applies the same instinct at episode scale. Course and webinar footage usually already has a built-in agenda, so the paper edit becomes mostly subtraction, cutting tangents, dead air and technical hiccups rather than building structure from nothing. Testimonials sit in between: one clean arc, problem, turn, result, hidden inside a longer, friendlier conversation than the finished cut will ever show.

Approval

Get sign-off on the plan before anyone finishes the cut

A paper edit is the cheapest point to collect feedback, since a client or producer can react to a page of selected lines in minutes instead of scrubbing a rough cut for an hour. Circulating the arranged plan before assembly starts means notes come back while a change still just means moving text, not re-editing a timeline. Getting approval before you edit covers how to structure that review so it saves time instead of adding another round of notes later.

If your transcript includes a subtitle file that needs reformatting for a client preview, the free SRT to VTT converter handles the conversion in the browser without a signup.

Done end to end, transcribe, highlight, arrange, verify, assemble, share for approval, in one place instead of switching between a document, a set of bins and an NLE, in ScriptCut.

Sources

frequently asked questions

How to Do a Paper Edit, Step by Step FAQs

What is the difference between a paper edit and a paper cut?

They're the same thing in most usage; paper cut and paper edit are used interchangeably, with radio cut reserved for the audio-only version of the same method.

Do I need special software to do a paper edit?

No. A paper edit can be done in any word processor as long as the transcript carries accurate timecode. Transcript-based editors make the later verification and assembly steps faster, but the core method works on plain text.

How long should a paper edit take compared to the raw footage?

There's no fixed ratio, but a careful read-and-highlight pass on an hour of transcript is still far faster than scrubbing an hour of video, and it should leave you with an assembly plan close to your target runtime rather than double it.

Should I paper edit observational or verite documentary footage?

Use it carefully. Errol Morris has argued paper cuts can mislead on performance-driven material where tone and behavior matter more than the words; the method is strongest for interview-driven and unscripted talking footage.

What's the difference between selects and a stringout?

Selects are the individual highlighted lines you pull from the transcript. A stringout is those selects strung together in rough order with nothing arranged for flow yet, the stage right before you build an actual story structure.

Why read the paper edit out loud instead of just reading it silently?

Reading aloud exposes problems silent reading hides, like an answer that needs its original question restored or a quote that only works with context removed on the page but not when spoken.

Can a paper edit turn into a frankenbite?

Only if you let it. Reordering and tightening someone's own words is normal paper editing; stitching fragments together into a sentence they never actually said crosses into frankenbite territory and is an ethics problem, not an editing technique.

Get the ScriptCut newsletter
Editing tips and product news. No spam, unsubscribe anytime.

×

You might also like...

Get the next ScriptCut article in your inbox

One short email a week. Editing tips and product news. No spam, unsubscribe anytime.

Stop scrubbing.
‍Start selecting.