The screenplay is the movie. The logline is the reason someone reads it. The synopsis is the reason someone considers it. The pitch is the reason someone says yes.
Phase 3 · Revision & Professionalization · Week 27 of 32You've spent twenty-six weeks building a screenplay from the inside — premise, character, structure, scenes, dialogue, clarity. This week you build it from the outside. Not the movie itself, but the case for the movie: the documents that make someone who has never read a page of your screenplay want to start. This is a different skill from screenwriting. It's packaging — the art of compressing a hundred-page experience into a sentence (the logline), a page (the synopsis), and a two-minute conversation (the pitch). Most writers resist this work because it feels reductive: how can you distill something you spent six months building into thirty words? But the resistance is misplaced. Packaging isn't reduction. It's translation — converting the screenplay's dramatic experience into the language of decision-making. A producer doesn't decide to read a script because the theme is profound or the character arc is elegant. They decide because the logline created curiosity. The synopsis confirmed the curiosity was justified. The pitch convinced them the writer understands what they've made. You're not simplifying your screenplay. You're building its front door.
The logline. One sentence. Twenty-five to forty words. Contains three elements: a protagonist (described by their situation, not their name), a conflict (the central obstacle or question), and stakes (what happens if the protagonist fails). That's all. The logline is not a plot summary. It's a curiosity engine — a sentence designed to make a reader think "I want to know what happens." The difference matters. A plot summary tells you what occurs: "A teacher investigates water contamination and confronts the chemical company responsible." Accurate, but inert — there's no reason to care, no hook that makes you lean forward. A logline tells you why it matters: "A chemistry teacher discovers the town's water is being poisoned by the same company funding her school — and the school board already knows." Now there's a protagonist with a specific dilemma, a conflict with built-in irony (the funding and the poisoning come from the same source), and implied stakes (her career, her students, the truth).
The logline formula. The formula is a guideline, not a cage: When [inciting event], a [protagonist description] must [central action], or else [stakes]. Variations abound — not every logline follows this structure — but the elements must be present regardless of form. The protagonist should be described by their defining quality or situation, not by name or demographic: "a by-the-book chemistry teacher" is better than "Nora Chen, 42." The conflict should contain an element of irony, dilemma, or contradiction that makes the situation inherently dramatic. The stakes should be specific enough that the reader can imagine what failure looks like.
Common logline failures: too vague ("A woman must confront her past to save her future" — this describes every film ever made), too detailed ("A 42-year-old chemistry teacher at Jefferson High School in Millbrook, Ohio discovers that..."), too focused on plot mechanics rather than dramatic tension ("After filing a public records request and collecting water samples from three sites..."), or missing stakes ("A teacher investigates water contamination" — and? What happens if she succeeds? What happens if she fails? Why should I care?). The test: give your logline to someone who knows nothing about your screenplay. Do they have a follow-up question — "What happens?" "Does she succeed?" "Who finds out?" If yes, the logline is working. If they nod politely and change the subject, it isn't.
The one-page synopsis. The synopsis is the whole story, compressed into a single page of prose — approximately 400–500 words. It includes the beginning, middle, and end. It spoils the ending. This is not a teaser. The synopsis is a professional document read by producers, agents, and executives who need to evaluate the complete story arc before committing time to the full screenplay. Withholding the ending in a synopsis signals that the writer doesn't understand the document's purpose.
The synopsis has a specific structure: a setup paragraph (protagonist, world, inciting incident — roughly 100 words), a development paragraph (complications, midpoint, escalation — roughly 150–200 words), and a resolution paragraph (low point, climax, ending — roughly 100–150 words). The prose should be vivid but compressed — active verbs, concrete nouns, no adjective pileups. Write in present tense, third person. Mention the protagonist by name. Mention the antagonist by name. Mention no more than four or five characters total — the reader can't track more than that in a one-page document. Every sentence should advance the story. No thematic commentary ("this film explores the tension between institutional loyalty and truth"). The theme is visible in the events. Let the events argue.
The hardest part of the synopsis: deciding what to leave out. Your screenplay has fifty to sixty scenes. The synopsis has room for perhaps twelve to fifteen story beats. You must choose the beats that constitute the story's essential shape — the events without which the arc collapses. Everything else — subplots, secondary complications, atmospheric scenes, relationship textures — is omitted. The test: if a reader read only the synopsis and then watched the film, they should recognize the movie. Not every scene — the essential shape. The skeleton, not the skin.
The two-minute verbal pitch. The pitch is the logline's verbal expansion — a spoken version of the story's case, delivered in approximately two minutes (roughly 300–350 words when written out). Unlike the synopsis, the pitch is not a complete plot summary. It's a performance — a controlled act of storytelling designed to make the listener want to read the script. The pitch includes the logline (opening hook), the setup (who and where), the central conflict (what's at stake and why it's hard), two or three key moments that demonstrate the story's dramatic power (not a beat-by-beat walkthrough — selected highlights that create the feeling of the film), and a gesture toward the ending (enough to indicate resolution without flattening the surprise).
The pitch should be practiced aloud. Timed. Rehearsed until it feels natural rather than recited. Two minutes is approximately the duration of a trailer — and the pitch should function like a verbal trailer: it creates anticipation, communicates tone, and makes the listener think "I need to see how this ends." A pitch that runs over three minutes is losing the listener. A pitch that runs under ninety seconds hasn't made the case. Two minutes is the target.
A critical distinction: the pitch describes what makes someone want to see this movie, not what the movie is about. "It's about institutional complicity and the cost of truth-telling" is a theme statement, not a pitch. "A chemistry teacher finds poison in the water — and the school she built is paying for it" is a pitch. The pitch communicates experience, not meaning. Meaning is what the audience discovers inside the theater. The pitch gets them to the theater.
You formatted a title page in Week 5. Now you finalize it for the submission-ready version of your screenplay. The title page is the first thing anyone sees when they open your PDF. It should be clean, simple, and correctly formatted — communicating professionalism in the three seconds it takes a reader to glance at it before turning to page one.
The final title page contains: the title (centered, upper half of the page, in Courier or Courier Prime — no decorative fonts), "by" on the line below (lowercase), your name on the line below that. In the lower right: your contact information (email address and phone number, or your representative's contact if you have one). In the lower left: WGA registration number (if registered) and draft designation ("Second Draft — March 2026" or simply "Second Draft").
What changed from Week 5: the draft designation (no longer "First Draft"), the registration number (if you've registered — recommended before sending to anyone outside your trusted circle), and a final check that no extraneous information has crept in: no genre label, no logline, no page count, no "A Screenplay" or "A Feature Film," no copyright symbol (WGA registration is sufficient protection and the © symbol reads as amateur). The title page is an index card. Treat it as one.
One additional consideration: your title. After twenty-seven weeks with this screenplay, evaluate the title with fresh eyes. Does it create curiosity without giving away the plot? Is it distinctive enough to be remembered? Is it short enough to look clean on a title page (three words is ideal, five is the upper limit before the page starts to feel crowded)? A title that worked as a placeholder during drafting may not be the right title for submission. If you're uncertain, write five alternative titles this week and test them against the logline. The title and logline should feel like they belong together — the title creates a question and the logline begins to answer it.
10-minute drill: Write five alternative titles for your screenplay. For each, write the title followed by the logline on a single line — as if it were appearing in a festival program or a coverage database. Read all five title-logline pairs aloud. Which one creates the most curiosity? Which title would make you pick up the script? Choose the strongest and format a final title page. Time yourself.
Assignment: Read 2 produced feature screenplays chosen for scripts that were famously well-packaged or sold on the strength of the pitch.
Script Pair Brief: Select one screenplay known for having a high-concept premise — a film where the logline alone is enough to greenlight the project, where the premise contains so much built-in appeal that packaging was almost effortless. Then select one screenplay with a lower-concept premise — a film that's character-driven or tonally specific, where the story's appeal isn't immediately obvious from a one-sentence description and the packaging had to work harder to create interest. The first teaches you what a "sells itself" premise looks like on the page — and how the screenplay still must deliver on the logline's promise. The second teaches you how to package a film whose appeal lives in execution rather than concept — how to write a logline, synopsis, and pitch for a story whose virtues are subtle.
Where to find scripts legally: IMSDb, The Script Lab, SimplyScripts, studio FYC releases, and public library systems.
Why this pairing: Your screenplay falls somewhere on the concept spectrum — some screenplays sell on premise alone, others sell on the writer's ability to make a quiet story sound essential. Reading both extremes helps you identify where your screenplay sits and calibrate your packaging strategy accordingly. A high-concept screenplay needs a logline that captures the irony. A low-concept screenplay needs a logline that captures the emotional stakes. Both need synopses that prove the story delivers. Both need pitches that create urgency.
Reading Lens (track these while reading):
1. Before reading each screenplay, write a logline for it based only on what you know about the film. After reading, revise the logline based on the actual content. How did the logline change — and which version (the pre-read or the post-read) is a better selling document? 2. Write a one-page synopsis for each screenplay from memory, immediately after reading. Then compare your synopsis to the screenplay's structure: did you capture the essential shape, or did you include details that aren't structurally necessary? 3. For the high-concept screenplay: is the logline enough to create interest, or does the script deliver something the logline doesn't promise? Where does the screenplay exceed its packaging? 4. For the low-concept screenplay: what's the hardest thing to capture in a one-sentence logline? What makes the story compelling that doesn't fit into the logline formula? How would you pitch it? 5. Look at each screenplay's title. Does the title create curiosity? Does it work with or against the logline?
Journal Prompts:
1. Write the logline for each screenplay in the format: "When [inciting event], a [protagonist] must [action], or else [stakes]." Which screenplay's logline is easier to write? What does that tell you about the relationship between concept strength and packaging ease? 2. For the high-concept screenplay: if the logline were the only thing a producer saw, what would they expect? After reading the script, what did they get that they didn't expect? The gap between the logline's promise and the screenplay's delivery is where the film's depth lives. 3. For the low-concept screenplay: write three different loglines, each emphasizing a different element — the character, the situation, or the emotional stakes. Which version is most compelling? What does your choice reveal about what you think makes the story worth telling? 4. Write a two-minute pitch for one of the screenplays — spoken aloud, timed. What moments from the screenplay did you choose to highlight, and why? What did you leave out? 5. Look at your own screenplay's position on the concept spectrum. Is it high-concept (the premise sells itself) or low-concept (the appeal is in execution)? How does that positioning affect your packaging strategy?
Deliverable: Final logline + 1-page synopsis + 2-minute verbal pitch (written out, timed).
Constraints: Produce three packaging documents:
(a) Final logline (25–40 words). One sentence containing protagonist (described by situation, not name), conflict (with inherent irony or dilemma), and stakes (what failure costs). Write ten versions before selecting the final. Test each against the curiosity criterion: does it make someone ask "What happens?" Eliminate versions that are too vague, too detailed, or missing stakes.
(b) One-page synopsis (400–500 words). Three paragraphs: setup, development, resolution. Present tense, third person. No more than five named characters. The ending is included. Every sentence advances the story — no thematic commentary, no atmosphere-building, no "this film explores." The synopsis must convey the essential shape of the screenplay: a reader who reads only the synopsis should recognize the movie.
(c) Two-minute verbal pitch (300–350 words, written out). Opens with the logline or a variation. Includes setup, central conflict, two or three key moments (selected for dramatic impact, not completeness), and a gesture toward the ending. Written to be spoken aloud — shorter sentences, natural rhythms, conversational register. Time it. If it runs over 2:30, cut. If it runs under 1:30, expand. Practice reading it aloud at least three times until it sounds spoken, not read.
Quality bar: The logline must pass the curiosity test with someone who hasn't read the screenplay. The synopsis must convey the complete arc — beginning, middle, and end — in one page, with the ending included. The pitch must create the desire to read the script, not just understand its premise. All three documents must be consistent — the logline's promise must match the synopsis's story must match the pitch's highlights. If the logline promises a thriller and the synopsis reads as a character study, there's a misalignment in your packaging.
Estimated time: 6–10 hours (logline development: 2–3 hours; synopsis: 2–3 hours; pitch writing and practice: 2–3 hours; reading: remaining time).
Human Draft Reminder: You write these documents. AI can test them — but the voice, the hook, and the case for your movie must be yours.
This week's narrowed reader roles: Reader A asks "Does the logline contain a protagonist, conflict, and stakes?" — evaluating structural completeness of the packaging. Reader B asks "Would I read this based on the logline alone?" — evaluating whether the packaging creates genuine interest. Submit all three documents (logline, synopsis, and pitch text) to both readers.
Add this week's entry to your Disagreement Log. The packaging divergence: Reader A may find the documents structurally complete (all elements present, arc conveyed, genre signaled) while Reader B finds them emotionally flat (technically correct but not exciting — the packaging describes the movie without making someone want to see it). This is the central challenge of packaging: structural correctness is necessary but not sufficient. The logline must be complete AND curiosity-generating. The synopsis must be accurate AND compelling. The pitch must be clear AND infectious. If Reader A approves and Reader B doesn't, the revision is in energy — more vivid verbs, sharper irony in the logline, more dramatic selection of highlights in the pitch. If Reader B is hooked but Reader A finds structural gaps (missing stakes, incomplete arc), the revision is in specificity — grounding the excitement in the concrete elements that make the packaging a reliable preview of the actual screenplay.
Budget tier this week: Your chosen tier, communicated through the packaging.
Top 3 production implications of packaging: 1. The logline signals production scale — a logline that implies a contained thriller reads differently to a producer than one that implies an epic scope. Your packaging should signal your budget tier implicitly: a micro-budget screenplay's logline emphasizes intimacy and character pressure, not spectacle and scope. A producer reading the logline should have a rough sense of what the film costs before they open the script. 2. The synopsis reveals the production footprint — a one-page synopsis makes the total location count, cast size, and complexity profile visible at a glance. If the synopsis mentions twelve different locations and eight named characters, the producer calculates cost. If it takes place primarily in one building with three central characters, the math is different. Your synopsis should reflect the screenplay's actual production profile, not an inflated version. 3. The pitch's "how we'd make it" moment — in professional pitch meetings, the writer is often asked "how do you see this getting made?" This is a production question, not a creative one. Having a clear answer — "two primary locations, a cast of six, no visual effects, shootable in twenty-five days" — signals that the writer understands what they've written. You won't include this in the written pitch, but prepare the answer in case you're ever asked.
Cheaper equivalent: A logline that reads "a woman races across three countries to stop a conspiracy before it's too late" signals a globe-trotting production. The same story, reconceived: "Trapped in the embassy where she works, a diplomat has twelve hours to prove a conspiracy exists before the evidence is destroyed." Same stakes. Same urgency. One building instead of three countries. The packaging signals the tier.
Worth-it spend: Professional feedback on the logline. If you have access to screenwriting communities, pitch fests, or industry contacts, testing the logline with people who evaluate scripts professionally is the single most valuable use of external feedback at this stage. A logline that works in a room full of industry readers is worth more than a logline you love in isolation. The logline is the most compressed, most consequential document you'll produce. Get it right.
A professional script reader encounters your logline before they encounter your screenplay. It appears on the coverage form, in the query email, on the tracking board, in the festival submission database. The logline is the gatekeeper. A reader who finds the logline compelling will open the screenplay with goodwill — they're already interested, and they'll give the first ten pages more patience because the logline earned their attention. A reader who finds the logline generic or confusing will open the screenplay (if they open it at all) with skepticism — they're looking for confirmation that the script isn't worth their time. The logline doesn't just describe the screenplay. It determines the conditions under which the screenplay is read. A great logline buys you a generous reader. A weak one buys you a hostile one. The screenplay is the same either way. The reading experience is not.
Writing the logline required you to distill twenty-seven weeks of work into a single sentence. Write about what the distillation revealed. Was the logline easy to write — because the screenplay's dramatic core has been clear from the beginning and the sentence was waiting to be assembled? Or was it difficult — because the screenplay's appeal is distributed across its texture, characters, and accumulation, and no single sentence can capture it? If it was difficult, write about what the logline leaves out — the qualities of the screenplay that the logline can't represent. Those qualities aren't flaws. They're the reason the screenplay is a hundred pages and the logline is one sentence. But knowing what the packaging can't convey helps you understand what the screenplay itself must deliver in its first ten pages — the qualities the logline promised implicitly that the screenplay must make explicit immediately.
By the end of this week you should have:
• Read 2 produced screenplays with a focus on packaging strategy (high-concept vs. low-concept)
• Written a final logline (25–40 words) after testing ten versions
• Written a one-page synopsis (400–500 words) with setup, development, and resolution including the ending
• Written and timed a two-minute verbal pitch (300–350 words)
• Finalized the title page with contact info, registration number, and draft designation
• Evaluated and possibly revised the screenplay's title
• Completed the title drill (5 alternative titles tested against the logline, 10 minutes)
• Run all three documents through both Revision Specialist prompts
• Updated your Disagreement Log with this week's entry
Week 28: Final Polish + Submission Prep — the Phase 3 gate week. The revision passes are complete. The packaging is written. Next week is the last five percent: typos, formatting consistency, the final read-through for any surviving clarity or dialogue issues, and the export to final PDF. The craft lecture teaches knowing when to stop — the discipline of declaring a draft finished even when you can still see imperfections, because a screenplay that's submitted is infinitely more valuable than one that's revised forever. The AI Workshop introduces the "Final Reader" prompt: you ask AI to read the script cold and report what the movie is "about." If the answer doesn't match your Week 6 theme sentence, something needs attention. If it does — you're done. You wrote a feature screenplay.