The last five percent isn't about making the screenplay perfect. It's about knowing that it's finished — and trusting it to be read.
Phase 3 · Revision & Professionalization · Week 28 of 32 · ★ Phase GateThis is the last revision week. Not the last week of the curriculum — four optional weeks follow if you're building the bonus screenwriting tool — but the last week where your hands are on the screenplay. Everything after this week is packaging, submission, and letting go. The temptation this week will be to keep revising. You'll read a scene on page 47 and think "I could make that dialogue sharper." You'll scan the action lines on page 82 and consider whether "she looks away" is better than "she turns toward the window." You'll wonder if the midpoint is really right, if the ending is really earned, if the title is really the one. These impulses are normal. They're also the enemy of completion. A screenplay that's revised forever is never finished. A screenplay that's declared finished — even with imperfections the writer can still see — is a screenplay that can be read, evaluated, produced, and improved through future drafts. This week, you do the final technical polish, run one last diagnostic, and declare the screenplay done.
Knowing when to stop. The ability to stop revising is a professional skill — and one of the hardest to develop, because revision always feels productive. You're making the screenplay better with every pass, right? Sometimes. But there's a point of diminishing returns where each revision pass produces smaller improvements while risking larger damage: the tightened dialogue loses its natural rhythm, the compressed scene loses a beat the reader needed, the relocated sequence creates a new causality problem that didn't exist before. Professional screenwriters learn to recognize the moment when the draft has reached its best achievable state for this round of work — and they stop. Not because the screenplay is perfect. Because continuing to revise will make it different, not better.
Three signs that the screenplay is ready to stop:
Sign 1: You're making lateral changes, not improvements. You rewrite a line, then rewrite it again, then go back to the first version. You move a scene, then move it back. You cut a paragraph of action description, then add one of equal length in a different place. These are lateral moves — changes that feel productive but don't measurably improve the draft. They're the writer's equivalent of rearranging furniture. When you notice yourself making lateral changes, the draft is done.
Sign 2: The revision notes are cosmetic, not structural. Your notes have shifted from "the midpoint doesn't hinge" and "this scene is redundant" (structural problems) to "this adjective isn't quite right" and "should this line break come here or here?" (cosmetic preferences). When the problems you're finding are at the word level rather than the scene level, the structure is sound and the draft is ready for other eyes.
Sign 3: You're afraid to send it. The reluctance to declare the draft finished is often not about the draft's quality. It's about the writer's fear of evaluation. As long as you're revising, the screenplay is "in progress" — protected from judgment by its unfinished status. Declaring it done means declaring it ready to be read — and read means judged. That fear is legitimate. But it's not a craft problem. It's a human one. The screenplay is as good as you can make it right now. The next step is to let someone else see it.
The final polish protocol. This week's work is technical, not creative. You're not rewriting scenes or restructuring the arc. You're doing the last quality-control pass that ensures the manuscript is clean, consistent, and professional. The protocol has five steps:
Step 1: The typo pass. Read the entire screenplay aloud — every word, every line, every scene heading. Not silently. Aloud. Reading aloud forces your brain to process every word individually rather than skimming past familiar phrases. You'll catch typos, missing words, repeated words, awkward phrasings, and dialogue that doesn't sound right when spoken. This pass takes two to three hours for a full-length screenplay. It's tedious. It's non-negotiable. A single typo on page one tells the reader the writer didn't care enough to proofread. Ten typos across the manuscript tells the reader the writer isn't professional. Zero typos doesn't guarantee a good read — but it eliminates one reason for a reader to stop trusting you.
Step 2: The consistency check. Verify the following across the full manuscript: character names are spelled the same way every time they appear (check both action lines and dialogue headers), character names are introduced in CAPS the first time only (not re-capped later), scene headings are formatted consistently (INT./EXT., location name, time of day — same style throughout), every character who speaks has been introduced in an action line before their first dialogue, and any prop or detail referenced later in the screenplay has been established earlier. Consistency errors are invisible to the writer (who knows what they meant) and glaring to the reader (who only knows what's on the page).
Step 3: The page-one check. Re-read page one as if you've never seen it. Does it still deliver the five promises (tone, competence, world, protagonist, central question)? After twenty-eight weeks of revision, page one may have drifted — details added or removed during the macro and scene passes that changed the opening's feel. Page one is the audition page. It must be the cleanest, leanest, most carefully crafted page in the manuscript. If it's not, revise it now — this is the one creative exception to the "no rewriting this week" rule.
Step 4: The opening/closing bracket. Read the opening image and the final image back to back, with nothing in between. Does the bracket hold? Does the final image mirror, invert, or rhyme with the opening? If the images have drifted during revision (a detail removed from page one, a change to the final scene's staging), restore the connection. The bracket is the screenplay's visual thesis — the first and last things the audience sees. They must talk to each other.
Step 5: The export. Generate the final PDF. Verify: title page present and correctly formatted, page numbers beginning on page 2, 12-point Courier or Courier Prime throughout, margins at industry standard, no scene numbers, no extraneous headers or footers, no draft watermarks or "CONFIDENTIAL" stamps (unless required by a specific submission context). Name the file professionally: Title_LastName.pdf or Title_Draft2_Date.pdf. Not "finalfinal_v3_REAL.pdf." The file name is the first thing a producer sees in their inbox.
The final PDF is the deliverable. It's the artifact that leaves your computer and enters the world. The export process has specific technical requirements that affect how the screenplay reads on different devices and in different contexts.
PDF settings: Export to PDF from your screenwriting software (Highland, WriterSolo, Fade In, Final Draft, or Fountain-based tools). Verify that the PDF preserves the Courier/Courier Prime font, that the page breaks match the screenplay file, and that the title page is included as the first page of the PDF (unnumbered). If your software supports it, embed the fonts in the PDF so the formatting is preserved regardless of what the reader's system has installed. File size should be under 5MB — larger files can be rejected by email filters and submission portals.
File naming: The filename is a professional signal. Use the format: Title_LastName.pdf for general submissions, or Title_DraftNumber_Date.pdf for version tracking. Examples: The_Quiet_Season_Ellery.pdf or The_Quiet_Season_Draft2_Mar2026.pdf. Avoid spaces in filenames (use underscores). Avoid version names that reveal process anxiety: "FINAL_FINAL_DONE.pdf" tells a producer you don't have a system.
Submission standards by context: Different submission contexts have different requirements. For query letters and cold submissions: send the logline and synopsis in the email body, and the PDF as an attachment only if requested. Never send unsolicited full scripts — the logline is the first contact. For contest submissions: follow the contest's specific formatting and anonymity requirements (some contests require no name on the title page, only an ID number). For representation queries: include the logline, the genre, the page count, and a one-paragraph bio in the email. Attach the synopsis as a separate document if requested. The screenplay PDF is sent only when an agent or manager asks to read it — never before.
10-minute drill: Export your screenplay as a final PDF. Open the PDF (not the screenplay file — the exported PDF) and verify: title page present with correct contact info and draft number; page numbering starts on page 2; font is consistent Courier/Courier Prime throughout; no stray formatting artifacts (highlighted text, tracked changes, comments, or revision marks visible in the export); the file opens cleanly on a second device (phone, tablet, or a different computer). Rename the file using the professional naming convention. Total: one verified, correctly named PDF. Time yourself.
Assignment: Re-read your own final draft. Then read 1 screenplay you admire — not to compare, but to remind yourself what the form can do.
The final read of your own screenplay is not a cold read (you did that in Week 22) and not a revision read (you've done six weeks of those). It's a farewell read — the last time you'll read these pages before they belong to someone else. Read for the experience, not for problems. Notice what works. Notice the surprises the draft gave you. Notice the character moments that feel alive and the structural turns that land. This read is not diagnostic. It's valedictory. You're saying goodbye to the version of the screenplay that only you have seen.
Then read a screenplay you admire. Choose one that isn't in your genre — something that works in a different register, with different tools, at a different scale. Read it as a fellow screenwriter, not as a student. You've earned that perspective. Twenty-eight weeks ago, you watched films and tracked beats. Now you read screenplays and understand the machinery from the inside. The admired screenplay isn't a standard to measure yourself against. It's a reminder of what's possible — the range and ambition of the form you've spent half a year learning.
Journal Prompts:
1. During the farewell read of your own screenplay, what was the moment you were proudest of — the scene, the line, the image, the structural turn that felt most fully realized? Write about why it works and what you learned about your own craft by producing it. 2. What was the moment you wished you could fix but chose not to — the imperfection you're sending into the world? Write about the decision to leave it. Not every imperfection needs to be fixed in this draft. Some are fixed in the next draft. Some are fixed in the next screenplay. 3. While reading the admired screenplay, was there a technique — a structural choice, a dialogue strategy, a visual motif, a tonal register — that you want to carry into your next project? Name it specifically. 4. How does the admired screenplay handle its ending? Compare it to yours. Not better or worse — different. What does the comparison reveal about the range of endings available to screenwriters? 5. Write one sentence about the screenwriter you are now versus the screenwriter you were in Week 1. What changed? What do you know that you didn't know — and what do you know you still don't know?
Deliverable: Final script PDF + version notes + "Final Reader" test.
Constraints: Produce three artifacts:
(a) Final script PDF. Execute the five-step polish protocol: typo pass (read aloud, full manuscript), consistency check (names, headings, props, time, character introductions), page-one check (five promises verified), opening/closing bracket check (images connected), and export to PDF with correct formatting and professional filename. This is the submission-ready version of your screenplay.
(b) Version notes (1 page). A brief document recording: the final page count, the final scene count, a list of major changes made during Phase 3 (what was cut, moved, rewritten, and added), and any known remaining issues you chose not to fix in this draft (imperfections you're aware of but have decided to accept). The version notes are for your own reference — a record of the draft's state when you declared it finished. They'll be useful if you return to the screenplay for future revision or if a reader's notes prompt a new draft.
(c) "Final Reader" test. Run the Final Reader AI prompt (below). Compare the AI's report of what the screenplay is "about" to your Week 6 theme sentence. Document the comparison: match, partial match, or mismatch. If mismatch: note whether the divergence is a problem to fix or a discovery to embrace. If match: note what this confirms about the screenplay's thematic coherence. This comparison is the last diagnostic in the curriculum — the final check that the movie on the page is the movie you intended to make.
Quality bar: The final PDF must be clean — zero typos on a spot-check of any ten random pages, consistent formatting throughout, title page correctly formatted, professional filename. The version notes must be honest — the "known remaining issues" section is not an apology, it's a diagnostic that demonstrates awareness. The Final Reader test must be completed and the comparison documented, even if the result is a mismatch. A mismatch is information, not failure.
Estimated time: 6–10 hours (typo pass: 2–3 hours; consistency check: 1–2 hours; bracket and page-one check: 1 hour; export and verification: 30 minutes; version notes: 30 minutes; Final Reader test: 1 hour; farewell read + admired screenplay: remaining time).
Human Draft Reminder: For the last time in this curriculum: the pages are yours. Every word in this screenplay was written by a human — you — across twenty-eight weeks of craft study, structural design, rough drafting, and disciplined revision. AI helped you think. AI helped you diagnose. AI did not write your screenplay. You did.
This week's AI Workshop introduces a new prompt type: the Final Reader. Unlike the Two Readers (who evaluated specific aspects of the screenplay from specific perspectives), the Final Reader reads the screenplay cold — with no context, no theme sentence, no character dossier — and reports what the movie is "about." The Final Reader simulates the experience of a stranger encountering your screenplay for the first time and forming an impression of its meaning. If the Final Reader's impression matches your intended theme, the screenplay is communicating what you designed it to communicate. If it doesn't, you have a calibration issue — the screenplay is arguing something different from what you planned.
The Final Reader prompt should be run after the final polish — on the screenplay as it will be submitted, not on an earlier draft. Submit as much of the screenplay as possible (a detailed sequence-by-sequence summary if you can't submit full pages) so the Final Reader has maximum context.
After receiving the Final Reader's report, pull out your Week 6 theme sentence. Compare the two. Write a brief comparison document (half a page) answering:
The Final Reader said the movie is about: [their answer to Question 1]
My theme sentence says the movie is about: [paste from Week 6]
Match level: Full match / Partial match / Mismatch
What this means: [2–3 sentences interpreting the comparison — if match, what it confirms; if partial, what shifted; if mismatch, whether the drift is a problem or a discovery]
Action taken: [If match: none — the screenplay communicates its theme. If partial match: note for future revision or accept the emphasis shift. If mismatch: decide whether to revise (if there's time and the mismatch is a problem) or accept (if the screenplay found a better argument than the one you planned)]
This comparison is the final entry in your Disagreement Log — not a disagreement between two Readers, but a disagreement between intention and execution. It's the most honest diagnostic available to a writer: did the pages say what you meant them to say?
Budget tier this week: Your chosen tier, confirmed in the final draft.
Top 3 final production notes: 1. Final location count — count every distinct location in the finished screenplay. Compare to your Week 9 approved list. If the count exceeds your tier's range (micro: 1–3, indie: 5–15), note it in the version notes as a revision target for a future draft. 2. Final cast count — count every speaking role. If it exceeds ten for micro or twenty for indie, note which single-scene characters could be cut or combined in a future pass. 3. Final night exterior count — count every EXT. NIGHT scene. If the count feels excessive for your tier, note which ones could be moved to day in a production-oriented revision. These aren't problems to fix this week — they're data for a future production conversation.
Cheaper equivalent: A final draft that runs 112 pages at indie budget is a reasonable production document. A final draft that runs 125 pages at indie budget is a conversation about cuts that the writer should initiate before the producer does. Page count is a budget proxy: each page is roughly one minute of screen time, and each minute costs money. If the page count is at the high end of your tier's comfort zone, note it and be prepared to discuss which sections could be compressed in a production draft.
Worth-it spend: Registration. Before submitting the screenplay to anyone — contests, queries, representation — register it with the WGA (Writers Guild of America) or the U.S. Copyright Office. Registration costs between $20 and $65 and provides a dated record of the work's existence in its current form. It's not a legal guarantee (consult a lawyer for actual intellectual property questions), but it's the industry-standard first step in protecting your work. Add the registration number to the title page before final export.
The screenplay you're about to send into the world will be read by someone who doesn't know you. They don't know about the twenty-eight weeks of work. They don't know about the character dossier, the escalation ladder, the promise map, or the Disagreement Log. They know nothing except what's on the page. And they'll form their judgment in the first ten pages — the same ten pages you crafted in Week 16, revised in Week 23, compressed in Week 24, voice-checked in Week 25, clarity-checked in Week 26, and proofread this week. Those ten pages are the most worked-over, most refined, most carefully constructed pages you've ever written. They're ready. The reader is ready. The only thing left is for you to let the screenplay go — to trust that the work you've done is enough, that the pages can speak for themselves, and that the story you built deserves to be heard. It does. Send it.
You wrote a feature screenplay. Take a moment to sit with that statement without qualifying it — not "I wrote a rough feature screenplay" or "I wrote a feature screenplay that still needs work" or "I wrote a feature screenplay but it's probably not good enough." You wrote a feature screenplay. It has a beginning, a middle, and an end. It has a protagonist whose design you built from four structural elements. It has an antagonist whose pressure system you engineered across five levels. It has a world with rules the audience can track. It has a midpoint that splits the story into two different movies. It has a low point that's earned by the protagonist's own choices. It has a climax where the protagonist drives the action and the theme delivers its verdict through consequence. It has a final image that closes the bracket the opening image opened. Write about what it means to have produced this object — not as a student completing an assignment, but as a writer who made something that didn't exist before.
By the end of this week you should have:
• Re-read your final draft as a farewell read — for the experience, not for revision
• Read 1 admired screenplay as a fellow screenwriter
• Executed the five-step polish protocol: typo pass (read aloud), consistency check, page-one check, bracket check, export
• Produced a final script PDF with correct formatting and professional filename
• Written version notes documenting the draft's final state and known remaining issues
• Run the Final Reader test and documented the theme comparison
• Completed the export drill (PDF verified on second device, 10 minutes)
• Made the final entry in your Disagreement Log
• A FINISHED, PROOFREAD, SUBMISSION-READY SCREENPLAY EXISTS
If you're continuing to the Bonus Build (Weeks 29–32), Week 29 is Product Spec (Your Screenwriting App MVP) — where you translate the frustrations, insights, and workflow discoveries from twenty-eight weeks of screenwriting into a product requirements document for a simple screenwriting tool. The AI Workshop shifts entirely to "AI as Collaborator" mode — product spec, UX decisions, and code review. No screenplay prompts. If you're not doing the Bonus Build — congratulations. You wrote a feature. The screenplay is finished. The packaging is done. The front door is built. What happens next is up to you: submit to contests, query agents, share with trusted readers, or put it in a drawer for a month and come back with fresh eyes. Whatever you choose, the screenplay exists because you made it. That's the thing that matters.
Required artifacts to complete the screenwriting curriculum:
• A finished, proofread screenplay PDF — title page through FADE OUT, correctly formatted, professionally named
• A final logline (25–40 words)
• A one-page synopsis (400–500 words, ending included)
• A two-minute verbal pitch (written out, timed)
• Version notes documenting the draft's final state
• Final Reader test with theme comparison documented
• Disagreement Log with entries from Weeks 5–28
If you're not doing the Bonus Build: Congratulations — you wrote a feature screenplay. The curriculum's primary outcome is achieved. The screenplay, logline, synopsis, and pitch constitute a professional submission package. Register the screenplay (WGA or Copyright Office) before sending it anywhere. Then: submit to contests, query agents and managers, share with trusted readers for feedback, or set it aside for four to six weeks and return with fresh eyes for one more revision pass. The screenplay will be better for the distance.
If you're behind: The script must be exportable. The logline and synopsis can be rough. The verbal pitch can be unpolished. The Final Reader test can be run on a summary rather than full pages. Non-negotiable: a complete, proofread screenplay PDF exists as a single document. Everything else can be refined after the curriculum ends. The screenplay cannot.
If you're continuing to the Bonus Build (Weeks 29–32): The screenplay is complete. The Bonus Build is a separate track — building a simple screenwriting tool using vibe-coding and AI collaboration. No screenplay pages are written or revised in Weeks 29–32. The tool you build may incorporate principles from the curriculum (the scene engine, the Two Readers model, the causality lock), but the screenwriting work is done. You're a writer now. The Bonus Build is for builders.