The Rewrite Loop

Screenplays aren't written; they're rewritten. Every writer has heard that line, and most of us nod along while secretly hoping our first draft is the exception. It never is. What separates working writers from aspiring ones isn't talent at drafting — it's stamina at rewriting, and stamina is exactly what the old process punished. One round of real notes per draft, weeks between them, momentum dead on arrival. The loop in this chapter fixes that. It's every technique from this course arranged into a cycle you can run in a week, on free tiers, alone at your desk.

Here's the whole system. Notice who does the writing at every single step — that part never changes:

• 1. Draft — you, alone, no AI in the room. Fast and ugly is fine; the loop feeds on finished drafts, not perfect ones.
• 2. AI coverage — run the full coverage sequence from Chapter 9, both framings, and keep only the overlapping notes.
• 3. Sort the notes — three piles: agree (fix it), disagree (write one sentence saying why, then drop it), test (not sure — probe it with follow-up questions before deciding).
• 4. Structure pass — the Chapter 7 questions: dropped tension, repeated jobs, missing setup, scenes that don't turn.
• 5. Dialogue pass — the Chapter 8 drills: table read, subtext check, trim. Your phrasing only, never pasted from the machine.
• 6. Save as a new dated draft — and go again — back to step 2 with fresh pages.

Version discipline: the boring habit that saves scripts

The loop generates drafts fast, and that speed will destroy your script if you're sloppy with versions. Two rules, non-negotiable. Never overwrite. Date everything. Every trip around the loop ends with a save-as — a filename with the date and a pass number on it — and the old draft stays exactly where it was, untouched. This isn't just tidiness. Rewriting with AI notes in your ear, you will sometimes take a wrong turn: flatten a scene that was working, fix a "problem" that was actually the movie. When that happens — and it will — the previous draft is your undo button. I keep a folder per project, drafts stacked chronologically, and I've reached back two versions to rescue a scene more times than I can count. Whether you work in Final Draft or plain Fountain files, the discipline is identical: the loop moves forward, the archive never moves at all. As a bonus, that dated stack is proof of your process — a complete record showing your hands on every draft, which matters more every year.

Knowing when to get out

Every loop needs an exit, and this one announces itself if you're listening. Early rounds, the notes converge — coverage, structure, and dialogue passes all point at the same broken things, and every fix visibly tightens the script. Then, somewhere around the fourth or fifth trip, the signal changes: this round says the opening is slow, last round said it was rushed; one pass wants more of a character the previous pass wanted cut. Contradiction is the finish line. It means the draft no longer has objective problems a pattern-reader can find — only choices, and choices are beyond the machine's jurisdiction. Looping past that point doesn't polish the script; it erodes it, sanding your voice toward the average one nudge at a time. Stop. Export the PDF. Send it to the human readers you've been saving since Chapter 9 — this is the draft that's earned them.

And take a second to notice what you just did. ChatGPT or Claude on the free tier, Fountain files that cost nothing, or the Final Draft you already own — a development process that used to require money and gatekeepers, run from a kitchen table. A free stack costs nothing but attention. Attention is the one thing you were always going to have to pay anyway.

You now have the complete engine. One chapter left — and it's the one that looks up from the desk: what all of this means for your career, your credits, and the future of the people who write movies.