How to Rewrite Your Entire Screenplay

The moment I knew my second feature needed a full screenplay rewrite, I was on page 47, trying to fix a scene between my protagonist and his estranged father. I'd been patching it for two days — tweaking dialogue, adjusting blocking, tightening action lines. Nothing was landing. And then it hit me: the scene didn't work because the scene before it didn't work, and that scene didn't work because the entire second act had been built on a structural assumption I'd made in the outline that turned out to be completely wrong.

I closed Final Draft. I opened a blank document. And I forced myself to figure out what was actually broken before I changed another single word of the script.

A full rewrite is one of the most disorienting experiences in screenwriting. You have a document that is technically complete — a beginning, middle, and end, characters with names, scenes with locations. And yet something fundamental is wrong, and you have to locate it precisely before you can fix it. Most writers dive straight into the scenes, fixing whatever looks most obviously broken. It almost never works. Rewriting a screenplay the right way means imposing a strict order on what otherwise becomes chaos.

Read your draft like a stranger before you change anything

Before you touch a single word, read your entire draft as if you've never seen it. Print it out if you can — there's something about paper that breaks the spell of familiarity. Read fast, the way a reader at a production company would on a Tuesday afternoon with twelve scripts in the pile. Take margin notes, but do not fix anything. You're diagnosing, not treating.

What you're looking for in this first read are big-picture problems, not surface ones. Not "this line of dialogue is clunky" — that's cosmetic. What you're hunting for: Does the protagonist have a clear, emotionally compelling want? Does the story actually escalate through Act Two, or does it wander in circles? Is there a dead stretch between pages 45 and 75 where nothing seems to change? Does the ending feel earned, or does it arrive suddenly like someone remembered they needed to write an ending?

I use a separate notebook for this pass — paper, not a new document. I'll write things like "Act Two is a flat line" or "protagonist is completely reactive, never drives anything forward." These are structural diagnoses, and they have to come before everything else.

The diagnosis pass is the most important thing you'll do in a full rewrite. Don't skip it to get to the "real" work.

Diagnose before you treat — and work from large to small

The instinct in a rewrite is to go straight to the scenes that feel most broken and start fixing them. Resist this hard. The scene on page 47 that isn't working is almost always a symptom of something structural, not the disease itself. Fix the symptom and you'll find a new symptom two weeks later, in a different part of the script.

Once you've completed your read, make a list of the real problems in order of severity. Structure first. Then character arcs. Then individual scene work. Then dialogue and description last. This is the order you work through a rewrite — always from the largest level down to the smallest. There's no point polishing language in a scene you might cut. There's no point working on a character's Act Three arc before you've confirmed Act Two is solid.

If your problem list includes things like "the protagonist's goal changes without motivation at page 55" or "the antagonist disappears for 30 pages," those are structural issues. They get addressed first, before you touch anything else.

Use index cards before you open the script again

When I'm working through structural problems, I don't open the script. I open Scrivener's corkboard, or sometimes I go analog — physical 3x5 index cards spread across my kitchen table. Each card represents one scene. On each card I write what the scene actually does: its plot function, its character function, and what changes by the end of it.

Staring at 90 cards arranged in sequence, you can see things that are invisible inside the script itself. You can see where momentum dies. You can see four consecutive scenes that all accomplish the same thing — four scenes where your protagonist is sad, or four scenes where the antagonist makes threats. The card view makes rhythm visible in a way the script document never can.

Rearranging cards is cheap. Moving a plot point from page 60 to page 45 on the corkboard costs you nothing. Moving it in the script after you've written all the surrounding material costs you a week of rewrites. Do the structural work on the cards first. Then open the script.

Decide what to keep before you start cutting

Not everything in your draft is broken. Some scenes work exactly as written. Some dialogue is already exactly right. Part of the diagnosis phase is identifying what is genuinely working so you don't accidentally destroy it during the rewrite.

I keep a separate "keep" document alongside my rewrite draft. It's a running list of scenes, specific exchanges, and moments I want to preserve. When I'm deep in a rewrite and feel the urge to tear everything out, I look at this list to remind myself I'm not starting from zero — I'm rebuilding with more knowledge than I had the first time through. This list also protects against a failure mode I've watched plenty of writers fall into: getting so frustrated with the draft that they rewrite away the things that were actually working.

Keep a running list of what's working. A full rewrite isn't about destroying the draft — it's about rebuilding it with better knowledge.

When to commit to a page-one rewrite

Sometimes the problems are so foundational that scene-level patching will never work. If your protagonist's core motivation is wrong — if the thing driving them through the story isn't emotionally compelling enough to sustain ninety pages — you cannot fix that by adjusting scenes. You have to go back to the premise.

A page-one rewrite doesn't mean deleting your old draft. Keep it. Keep every draft — I have scripts with seven or eight versions sitting in folders on my hard drive. A page-one rewrite means opening a new document and rebuilding the story from the premise up, using everything you learned from the draft that didn't work as your map. You'll find that certain scenes almost write themselves the second time, because now you understand the characters and the world far better than you did on draft one.

Page-one rewrites are faster than you expect. You're not discovering the story anymore — you're clarifying it. The heavy lifting of figuring out what happens has already been done. Now you're just writing the version the story was always trying to become.

The order of passes in a major rewrite

After structural work, I move to character. I'll go through the script and read only one character's scenes from beginning to end — just their arc in isolation, nothing else. Does their want stay consistent? Does it escalate? Do they change? Are their decisions motivated by what we've established about them? This is much easier to assess when you're not distracted by the rest of the story moving around them.

After the character pass, I do a scene-by-scene pass. I'm looking at each scene as an individual unit: Does something change by the end of it? Is there genuine conflict — not necessarily hostility, but competing agendas? Does it connect causally to what comes before and after? I've been using WriterDuet lately for this pass because the side-by-side view makes it easier to compare a scene against its previous version.

Then, and only then, do I do a dialogue and description pass. By this point, the architecture is sound. I'm not going to cut a scene I've just labored over. Now I can afford to care whether a line is perfectly tuned, whether an action line is reading too flat, whether a slug line needs to be reconsidered.

Each pass has its own job. The dialogue pass should only happen after structure and character are solid — not before.

Protect your old drafts obsessively

Before any major rewrite pass, save a new version. I use a naming convention: script_v2, script_v3, script_v3_structural, script_v4. Something in the fifth pass will always make you wonder if a moment from the third pass was better — and if you've been overwriting the same file, that moment is gone.

Final Draft's built-in version management is functional but basic. I duplicate the file in Finder before each major pass. Inelegant, but it's never failed me in seven years of doing this. Some writers I know use git for version control on their scripts, which sounds extreme until the one time you desperately need to recover a draft.

The mental side of a full rewrite

The hardest part of a major rewrite isn't craft — it's psychology. There will be days when the draft looks worse than when you started. Days when you genuinely question whether the story is worth saving at all. Both are part of the process, not signs that something is wrong.

The momentum in a rewrite doesn't come from inspiration. It comes from the process itself. You show up, you do the next pass, you trust the order of operations. The writers I know who reliably turn weak first drafts into strong scripts aren't necessarily more talented. They're more methodical. They understand that a full rewrite is not one task — it's a sequence of smaller tasks, each manageable on its own.

When you finish a full rewrite done this way, the script doesn't just feel cleaner. It feels like it was always supposed to be this version. The earlier drafts start to look like rough sketches of the real thing — evidence of a process that worked, not proof of failure.

That's the goal. Not a perfect first draft, but a process that reliably gets you to a strong one.

← All articles