1 - Unseen Disturbance
InvestigationNo lens is broken, but Design is soft — this reads as a polish pass.
It restates its note rather than deepening it Development
HoldingA real force keeps it pushing forward.
Three parapsychologists lose their university funding and start a ghost-catching business in New York City, only to find themselves facing a supernatural threat of apocalyptic proportions.
See other logline suggestions
"Ghostbusters" is a supernatural comedy about a group of eccentric scientists who investigate and capture ghosts. The film's unique voice is characterized by its blend of humor, suspense, and action, and its fast-paced storytelling. The characters are well-developed and relatable, and the dialogue is witty and engaging. The film's special effects are also impressive, and they help to create a sense of realism and immersion. The film's themes are universal and timeless, and they resonate with audiences of all ages. "Ghostbusters" is a classic film that is sure to entertain and delight audiences for years to come.
Setting: Present day, New York City
Themes: The Power of Science and Technology, The Importance of Teamwork, The Supernatural and the Unknown, The Battle Between Good and Evil, The Importance of Humor and Wit
Conflict & Stakes: The Ghostbusters' struggle to save New York City from supernatural threats, while balancing their business and personal lives.
Mood: Humorous and suspenseful
Standout Features:
Comparable Scripts: Ghostbusters II, Beetlejuice, The Frighteners, 21 Jump Street, Men in Black, Stranger Things, Buffy the Vampire Slayer, Doctor Who, Supernatural, The Conjuring
The video is a bit crude as the tool is still Alpha code. Contact us if there's a problem or with suggestions.
Share URL:
This section delivers a top-level assessment of the screenplay’s strengths and weaknesses — covering overall quality (P/C/R/HR), character development, emotional impact, thematic depth, narrative inconsistencies, and the story’s core philosophical conflict. It helps identify what’s resonating, what needs refinement, and how the script aligns with professional standards.
Breaks down your script along various categories.
Breaks down the emotional journey of the audience across the script.
Scenes now use the full 0–10 scale, so your numbers will look lower and more spread out than before. That's the new, smarter model being honest — not a verdict on your script.
A 5 is fine. “Functional” (5–6) is a solid, professional scene — that's where most scenes sit. The scale rides low on purpose, so it has room to point down (where to fix) and up (what's working).
The table uses the same colors: warm = worth a look · neutral = fine · green = working. We re-scored our whole reference library the same way, so your percentile rankings stay a fair, apples-to-apples comparison.
All of your scenes analyzed individually and compared, so you can zero in on what to improve.
The percentile patterns suggest an intuitive writing style, with strengths in dialogue (51.6%) and story forward movement (67.89%). This intuitive approach could be complemented by developing more intricate plot structures and concepts.
Balancing ElementsIntuitive
Overall AssessmentWhile the screenplay has notable strengths in originality and concept, refining character development and intensifying emotional impact would elevate its potential.
| Percentile | Before | After | ||
|---|---|---|---|---|
| Scene Overall | 8.1 | 12 | the pursuit of happyness : 8.0 | a few good men : 8.2 |
| Scene Concept | 8.3 | 64 | face/off : 8.2 | fight Club : 8.4 |
| Scene Plot | 7.6 | 17 | Arsenic and old lace : 7.5 | fight Club : 7.7 |
| Scene Characters | 7.6 | 2 | Rear Window : 7.5 | the 5th element : 7.7 |
| Scene Emotional Impact | 6.7 | 6 | Arsenic and old lace : 6.6 | Madmen : 6.8 |
| Scene Conflict Level | 7.8 | 57 | Erin Brokovich : 7.7 | True Blood : 7.9 |
| Scene Dialogue | 7.7 | 29 | the boys (TV) : 7.6 | the dark knight rises : 7.8 |
| Scene Story Forward | 8.3 | 59 | True Blood : 8.2 | a few good men : 8.4 |
| Scene Character Changes | 5.9 | 8 | Boyz n the hood : 5.8 | Hot Fuzz : 6.0 |
| Scene High Stakes | 7.5 | 49 | True Blood : 7.4 | Erin Brokovich : 7.6 |
| Scene Unpredictability | 7.65 | 66 | The substance : 7.64 | Blackkklansman : 7.66 |
| Scene Internal Goal | 8.02 | 29 | fight Club : 8.00 | There's something about Mary : 8.03 |
| Scene External Goal | 7.73 | 89 | Lethal Weapon : 7.72 | Avatar : 7.74 |
| Scene Originality | 8.90 | 87 | the 5th element : 8.89 | Lucifer : 8.91 |
| Scene Engagement | 9.00 | 84 | Vice : 8.99 | Frankenstein : 9.01 |
| Scene Pacing | 8.30 | 55 | a few good men : 8.29 | Elvis : 8.31 |
| Scene Formatting | 8.14 | 47 | Erin Brokovich : 8.13 | Vice : 8.15 |
| Script Structure | 8.14 | 54 | Erin Brokovich : 8.13 | There's something about Mary : 8.15 |
| Script Characters | 8.60 | 90 | Knives Out : 8.50 | True Blood : 8.70 |
| Script Premise | 8.90 | 91 | Casablanca : 8.80 | Pinocchio : 9.00 |
| Script Structure | 8.00 | 56 | Black mirror 304 : 7.90 | Titanic : 8.10 |
| Script Theme | 8.00 | 34 | Bonnie and Clyde : 7.90 | Erin Brokovich : 8.10 |
| Script Visual Impact | 6.80 | 4 | True Blood : 6.70 | Bonnie and Clyde : 6.90 |
| Script Emotional Impact | 8.30 | 78 | Blade Runner : 8.20 | Titanic : 8.40 |
| Script Conflict | 7.40 | 41 | Rick and Morty : 7.30 | Casablanca : 7.50 |
| Script Originality | 8.30 | 66 | Rambo : 8.20 | Casablanca : 8.40 |
| Overall Script | 8.30 | 75 | the dark knight rises : 8.29 | Lord of War : 8.31 |
This section looks at the extra spark — your story’s voice, style, world, and the moments that really stick. These insights might not change the bones of the script, but they can make it more original, more immersive, and way more memorable. It’s where things get fun, weird, and wonderfully you.
Your whole script read on three things — Design (is it built), Execution (does it play on the page), and Read (does it grip) — then mapped scene by scene. The rows go Script → Acts → Sequences → Scenes in story order, left to right; a unit’s width is its length in pages.
Colour depends on the mode. By default you’re on Triage — a recommendation for each part: Keep (green), Polish, Rework, or Cut / rebuild (red). Switch Colour by (top) to a lens (Design / Execution / Read) or one of the twelve axes and the colour becomes that signal’s score instead — red (needs work) through green (strong), with grey where a part isn’t owed that signal. Either way it’s a map of where to look.
To explore: click any cell for its detailed read — what’s working, what’s dragging, and your options. When a script has acts, hover an act and hit ⤢ Focus to zoom into it. Use Colour by (top) to recolour by a single craft signal, or the Findings / Axes / Patterns tabs to read it different ways.
High-level overview
The screenplay follows a group of scientists turned ghost hunters who form the Ghostbusters and investigate paranormal activity in New York City. They encounter a series of supernatural events, culminating in a battle against an ancient evil known as Gozer. Along the way, they face skepticism, legal threats, and spectral manifestations as they strive to save the city from destruction. Despite setbacks and challenges, the Ghostbusters ultimately succeed in defeating Gozer, with moments of humor, drama, and action-packed sequences leading to a satisfying conclusion.
Scene by Scene Summaries
Act-by-act sequence summaries
After initial reports of paranormal activity (Scene 1), Venkman, Stantz, and Spengler respond to the library sighting. They assess the situation, track the spectral presence, and attempt direct engagement. The sequence climaxes when their containment effort fails as the ghost transforms into a demonic entity and attacks them, forcing their retreat.
After fleeing the library (Scene 5), the team is expelled from Columbia University. Venkman reframes this setback as an opportunity, convincing Stantz to start a business. They secure funding and acquire the firehouse headquarters, establishing the Ghostbusters' operational base.
Dana experiences eerie phenomena in her apartment, including a haunted TV and refrigerator portal. Simultaneously, the Ghostbusters prove their legitimacy by capturing a ghost at a family's home, showcasing their ghostbusting process while Dana's personal threat escalates.
Dana visits the firehouse to report her experience. The Ghostbusters conduct a lie detector test, confirming her story's validity. Venkman escorts her home to investigate, but finds no evidence and is rejected when offering to stay overnight, leaving the case unresolved.
After a supernatural attack at the hotel, the Ghostbusters respond. They track the vapor through corridors, face failed capture attempts, and engage in a chaotic banquet room battle. After overcoming near-disastrous proton stream crossovers, they successfully trap the entity, emerging as media heroes while negotiating payment.
The Ghostbusters handle city-wide hauntings (Yankee Stadium, Tudor City) amid growing media coverage. During a chance meeting, Dana reveals the name 'Zuul' to Venkman, linking her experiences to ancient texts about Gozer. Public and personal stakes intensify.
Overwhelmed by calls, the Ghostbusters hire Winston Zeddemore. Simultaneously, EPA agent Walter Peck demands access to their ghost storage. Venkman refuses, triggering a confrontation where Peck threatens legal action, endangering their containment system.
The team monitors their overfilled storage facility, warning of catastrophic energy surges. Concurrently, Dana is abducted by a Terror Dog in her apartment, forcibly transforming her into Gozer's Gatekeeper. The sequence ends with her imprisonment in a supernatural dimension.
A Terror Dog escapes at Louis' party, causing chaos and pursuing him through Central Park until he's possessed. Simultaneously, Venkman visits Dana's apartment, discovers her transformation into Zuul, and witnesses her levitation during a disturbing bedroom encounter. The sequence ends with both key human vessels (Louis as Keymaster, Dana as Gatekeeper) fully under supernatural control.
At HQ, Spengler interrogates possessed Louis, learning of Gozer's plan while dismissing Janine's warnings. Simultaneously, Stantz experiences a ghostly encounter elsewhere. When Peck arrives with officials to shut down the containment grid, the Ghostbusters unsuccessfully argue and physically intervene. The grid's shutdown causes a catastrophic explosion, releasing all captured ghosts.
The explosion creates an energy geyser heading toward Dana's building, interpreted by possessed Louis as Gozer's sign. Chaos erupts citywide: ghosts terrorize citizens, Louis scares off muggers by manifesting supernatural power, and Spengler faces authorities amid the crisis. The sequence ends with Louis irrevocably heading toward Dana as the city descends into supernatural anarchy.
The Ghostbusters analyze blueprints at HQ, identifying Dana's building as Gozer's antenna and its architect's cult ties. Taken to City Hall, they confront Peck's accusations and persuade the skeptical mayor to support them. As Louis unites with Dana at her apartment (triggering Gozer's arrival), the team departs City Hall with mayoral backing, charging equipment for the final confrontation.
The Ghostbusters arrive at Dana's building amid public chaos, survive a sinkhole, and ascend to the roof. They battle Gozer directly but fail when it absorbs their proton streams. After Gozer manifests as the Stay-Puft Marshmallow Man, the team adapts their strategy, sets it ablaze, and ultimately destroys it by redirecting their beams at the Terror Dogs. This defeats Gozer, frees Dana and Louis, and forces the Ghostbusters to cover up the incident.
The Ghostbusters emerge from the building as heroes to a cheering crowd. While departing in the Ectomobile, they pass citizens humorously processing the marshmallow debris, symbolizing the return to normalcy and their triumph.
Images and voice-over from your primary video
Final video assembled from the sections below.
In New York City, a group of eccentric scientists, Dr. Peter Venkman, Dr. Ray Stantz, and Dr. Egon Spengler, are introduced as they investigate paranormal phenomena. They are passionate about their work but face skepticism from the academic community.
The Ghostbusters receive a call about a ghost sighting at the New York Public Library, where a librarian has encountered a terrifying apparition. This event ignites their quest to capture ghosts.
The Ghostbusters successfully capture their first ghost at the library, thrilling them and proving their theories correct. They gain confidence and media attention.
As the Ghostbusters become more popular, they face increasing skepticism from the scientific community and government officials, particularly from Walter Peck of the EPA.
The Ghostbusters capture a powerful ghost, but their success leads to a surge in paranormal activity across the city, indicating that something much larger is at play.
The city is thrown into chaos as the Stay-Puft Marshmallow Man, a manifestation of their fears, begins to wreak havoc, forcing the Ghostbusters to confront their greatest challenge yet.
The Ghostbusters face defeat as their equipment fails against the overwhelming power of Gozer, and they are left questioning their abilities and purpose.
In a desperate bid to save the city, the Ghostbusters must confront Gozer and make a critical choice that will determine the fate of New York.
With teamwork and courage, the Ghostbusters defeat Gozer, restoring peace to the city and solidifying their legacy as heroes.
Each axis shows your script's raw score (0–10) in that category. We recently upgraded the AI models behind these categories, so percentile rankings are temporarily unavailable while we re-score our reference library.
Hover over each axis on the radar chart to see what that category measures and why it matters.
Analysis: The screenplay's character development is engaging and effective, with well-defined characters who undergo significant growth and transformation throughout the story. The interplay between character development and the screenplay's themes drives the narrative forward and deepens the emotional resonance of the story.
Analysis: The screenplay for "Ghostbusters" effectively establishes a compelling and clear premise, blending comedy, science fiction, and horror elements to create a unique and engaging narrative. The initial scenes quickly introduce the core characters, their scientific background, and their skeptical yet humorous approach to the supernatural. The premise's strength lies in its originality, combining elements of ghost hunting with witty dialogue and relatable characters. The clarity of the premise allows the audience to easily understand the central conflict and the Ghostbusters' mission to capture and contain supernatural entities. However, there's room for further exploration of the characters' backstories and motivations, particularly regarding their initial interest in the paranormal, to deepen audience engagement.
Analysis: The screenplay's structure effectively sets up the premise and character dynamics, leading to a thrilling climax and resolution. However, improvements to pacing and refining certain plot elements could enhance the overall narrative impact.
Analysis: The screenplay effectively explores and communicates its themes and messages, offering a blend of humor, suspense, and commentary on science versus the supernatural. While some themes are more fully developed and impactful than others, the screenplay manages to convey a coherent and engaging message about the importance of facing one's fears and embracing unconventional approaches to problem-solving.
Analysis: The screenplay employs a mix of humor and visual effects, but its descriptions lack vividness and creativity, relying on conventional imagery. Revisiting the screenplay with a focus on crafting unique visual descriptions and incorporating innovative visual storytelling techniques could enhance its cinematic impact.
Analysis: The screenplay effectively elicits emotional responses through witty banter, supernatural tension, and personal growth. To enhance the emotional depth, consider incorporating moments of vulnerability, exploring the fears of secondary characters, and adding scenes that focus on the emotional complexities of the supernatural elements.
Analysis: The screenplay effectively sets up a central conflict between the Ghostbusters, a group of scientists dedicated to catching and containing ghosts, and various supernatural forces threatening the safety of New York City. The stakes are personal for several characters, especially Dana Barrett, who becomes possessed by an ancient evil entity. While the screenplay succeeds in presenting an engaging conflict and escalating stakes, there are opportunities to deepen the emotional impact and heighten the narrative tension.
Analysis: The screenplay exhibits a delightful blend of nostalgia and innovation, capturing the essence of the original 'Ghostbusters' while introducing fresh elements that keep the story engaging and entertaining. The narrative deftly weaves supernatural thrills with comedic moments, creating a unique and immersive cinematic experience.
Expand to see detailed analysis
View Complete AnalysisProtagonist
Supporting Character
| Theme | Theme Details | Theme Explanation | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The Power of Science and Technology
30%
|
The Ghostbusters use their scientific knowledge and equipment to capture ghosts and defeat supernatural threats.
|
The film highlights the importance of science and technology in solving problems and protecting society from the unknown. | ||||||||||||
Strengthening The Power of Science and Technology
|
||||||||||||||
|
The Importance of Teamwork
25%
|
The Ghostbusters work together as a team to overcome challenges and defeat the supernatural.
|
The film shows that teamwork is essential for success and that we can achieve more when we work together. | ||||||||||||
|
The Supernatural and the Unknown
20%
|
The film explores the existence of the supernatural and the unknown, with the Ghostbusters facing a variety of ghosts, spirits, and other paranormal entities.
|
The film taps into our fear of the unknown and the supernatural, while also exploring the possibility of coexistence between the natural and supernatural worlds. | ||||||||||||
|
The Battle Between Good and Evil
15%
|
The Ghostbusters represent the forces of good, while Gozer and his minions represent the forces of evil.
|
The film presents a classic battle between good and evil, with the Ghostbusters fighting to protect the innocent and the city from supernatural threats. | ||||||||||||
|
The Importance of Humor and Wit
10%
|
The film incorporates humor and wit into its storytelling, with the Ghostbusters often using sarcasm and jokes to defuse tense situations.
|
The humor and wit add a lighthearted and entertaining element to the film, making it more enjoyable and relatable. | ||||||||||||
| Site | Description |
|---|---|
| Studio Binder | Movie Themes: Examples of Common Themes for Screenwriters |
| Coverfly | Improving your Screenplay's theme |
| John August | Writing from Theme |
| Title | Description |
|---|---|
| Story, Plot, Genre, Theme - Screenwriting Basics | Screenwriting basics - beginner video |
| What is theme | Discussion on ways to layer theme into a screenplay. |
| Thematic Mistakes You're Making in Your Script | Common Theme mistakes and Philosophical Conflicts |
| Goals and Philosophical Conflict | |
|---|---|
| internal Goals | The protagonist's internal goal is to confront their fears, prove themselves as capable Ghostbusters, and maintain composure in the face of supernatural threats. |
| External Goals | The protagonist's external goal is to protect the city from supernatural threats, capture ghosts, and maintain their ghostbusting business's reputation |
| Philosophical Conflict | The overarching philosophical conflict revolves around the clash between the known and the unknown, science vs. the supernatural, and skepticism vs. belief in the paranormal. |
| Site | Description |
|---|---|
| Creative Screenwriting | How Important Is A Character’s Goal? |
| Studio Binder | What is Conflict in a Story? A Quick Reminder of the Purpose of Conflict |
| Title | Description |
|---|---|
| How I Build a Story's Philosophical Conflict | How do you build philosophical conflict into your story? Where do you start? And how do you develop it into your characters and their external actions. Today I’m going to break this all down and make it fully clear in this episode. |
| Endings: The Good, the Bad, and the Insanely Great | By Michael Arndt: I put this lecture together in 2006, when I started work at Pixar on Toy Story 3. It looks at how to write an "insanely great" ending, using Star Wars, The Graduate, and Little Miss Sunshine as examples. 90 minutes |
| Tips for Writing Effective Character Goals | By Jessica Brody (Save the Cat!): Writing character goals is one of the most important jobs of any novelist. But are your character's goals...mushy? |
Everything above was written for you before you arrived. These are the things you can set running yourself, on the whole script or on one scene at a time.
Read them one at a time, or line them all up side by side.
Every scene is read two ways — Scene Mechanics (how the scene is built) and Craft Read (how it is written). Open any scene to see both.
No lens is broken, but Design is soft — this reads as a polish pass.
It restates its note rather than deepening it Development
HoldingA real force keeps it pushing forward.
All three lenses are solid — worth protecting as it stands.
The beats can be called before they land Unpredictability
HoldingIt commits to one clear thing and holds it.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingThe reader can follow what matters.
All three lenses are solid — worth protecting as it stands.
What happens here obliges what comes next Consequence
HoldingA real force keeps it pushing forward.
All three lenses are solid — worth protecting as it stands.
A real force keeps it pushing forward Pressure
HoldingWhat happens here obliges what comes next.
An aftermath beat lands the cost of what just happened rather than driving new action.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingThe reader can follow what matters.
A transition carries us between beats. It owes less structurally than a scene built to turn.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingThe reader can follow what matters.
An orientation beat sets up the world. It isn’t expected to carry a big turn, so a lower Design read here is often the shape of the scene, not a fault.
Design and Read are broken — this reads as a rebuild before polish.
The beats can be called before they land Unpredictability
HoldingThe reader can follow what matters.
A montage compresses time. It isn’t built to turn on a single thread.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingThe reader can follow what matters.
An orientation beat sets up the world. It isn’t expected to carry a big turn, so a lower Design read here is often the shape of the scene, not a fault.
All three lenses are solid — worth protecting as it stands.
A real force keeps it pushing forward Pressure
HoldingThe reader can follow what matters.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingEvery beat and line earns its place.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It restates its note rather than deepening it Development
HoldingThe reader can follow what matters.
Read is broken — a load-bearing lens isn’t doing its job yet.
It leans on mood instead of something actually pushing it Pressure
HoldingThe reader can follow what matters.
All three lenses are solid — worth protecting as it stands.
It restates its note rather than deepening it Development
HoldingThe reader can follow what matters.
All three lenses are solid — worth protecting as it stands.
It plays close to the version we’ve seen before Freshness
HoldingA real force keeps it pushing forward.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingThe reader can follow what matters.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingThe reader can follow what matters.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It restates its note rather than deepening it Development
HoldingThe reader can follow what matters.
Design and Read are broken — this reads as a rebuild before polish.
It restates its note rather than deepening it Development
HoldingEvery beat and line earns its place.
A montage compresses time. It isn’t built to turn on a single thread.
All three lenses are solid — worth protecting as it stands.
A real force keeps it pushing forward Pressure
HoldingThe reader can follow what matters.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingThe reader can follow what matters.
An orientation beat sets up the world. It isn’t expected to carry a big turn, so a lower Design read here is often the shape of the scene, not a fault.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingEvery beat and line earns its place.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingThe reader can follow what matters.
An orientation beat sets up the world. It isn’t expected to carry a big turn, so a lower Design read here is often the shape of the scene, not a fault.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingThe exit pulls you into the next one.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingA real force keeps it pushing forward.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingA real force keeps it pushing forward.
All three lenses are solid — worth protecting as it stands.
A real force keeps it pushing forward Pressure
HoldingIt commits to one clear thing and holds it.
No lens is broken, but Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingA real force keeps it pushing forward.
All three lenses are solid — worth protecting as it stands.
It restates its note rather than deepening it Development
HoldingWhat happens here obliges what comes next.
No lens is broken, but Read is soft — this reads as a polish pass.
The result doesn’t oblige what comes next Consequence
HoldingA real force keeps it pushing forward.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingA real force keeps it pushing forward.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingThe reader can follow what matters.
An aftermath beat lands the cost of what just happened rather than driving new action.
Design is broken — a load-bearing lens isn’t doing its job yet.
It restates its note rather than deepening it Development
HoldingEvery beat and line earns its place.
A montage compresses time. It isn’t built to turn on a single thread.
No lens is broken, but Design is soft — this reads as a polish pass.
It restates its note rather than deepening it Development
HoldingThe reader can follow what matters.
No lens is broken, but Read is soft — this reads as a polish pass.
It plays close to the version we’ve seen before Freshness
HoldingThe reader can follow what matters.
All three lenses are solid — worth protecting as it stands.
A real force keeps it pushing forward Pressure
HoldingIt commits to one clear thing and holds it.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
It isn’t clearly about one thing yet Contract
HoldingA real force keeps it pushing forward.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
It leans on mood instead of something actually pushing it Pressure
HoldingThe reader can follow what matters.
A transition carries us between beats. It owes less structurally than a scene built to turn.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingA real force keeps it pushing forward.
All three lenses are solid — worth protecting as it stands.
The situation deepens as it goes Development
HoldingIt commits to one clear thing and holds it.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
The result doesn’t oblige what comes next Consequence
HoldingThe reader can follow what matters.
Read is broken — a load-bearing lens isn’t doing its job yet.
It plays close to the version we’ve seen before Freshness
HoldingThe reader can follow what matters.
An aftermath beat lands the cost of what just happened rather than driving new action.
Your scene scores are compared against professional produced screenplays in our vault (The Matrix, Breaking Bad, etc.). The percentile shows where you rank compared to these films.
Example: A score of 8.5 in Dialogue might be 85th percentile (strong!), while the same 8.5 in Conflict might only be 50th percentile (needs work). The percentile tells you what your raw scores actually mean.
Hover over each axis on the radar chart to see what that category measures and why it matters.
“Functional” (5–6) is a solid, professional scene — that's where most scenes sit. The scale rides low on purpose, so it has room to point down (where to fix) and up (what's working).
Scenes now use the full 0–10 scale, so your numbers will look lower and more spread out than before. That's the new, smarter model being honest — not a verdict on your script.
The table below uses the same colors: warm = worth a look · neutral = fine · green = working. The point is awareness, not maxing every number — a scene can be light on plot or conflict for good reasons.
| Compelled to Read | Story Content | Character Development | Scene Elements | Audience Engagement | Technical Aspects | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Click for Full Analysis | Triage | Design | Overall | Clarity | Scene Impact | Concept | Plot | Originality | Characters | Character Changes | Internal Goal | External Goal | Conflict | Opposition | High stakes | Story forward | Twist | Emotional Impact | Dialogue | Engagement | Pacing | Formatting | Structure | |
| 1 - Unseen Disturbance | PolishInvestigationNo lens is broken, but Design is soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 8.5 / 8 | 8 / 7.5 | 7 | 6 | 6 | 4 | 2 | 3 | 4 | 5 | 6 | 3 | 3 | 7 | 5 | 5 | 7 | 8 | 7 | 7 | |
| 2 - Interrupted ESP Test | KeepPursuitAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8.5 | 7.5 / 7 | 7 | 6 | 7 | 8 | 1 | 7 | 8 | 6 | 4 | 4 | 6.5 | 6 | 4 | 8 | 6.5 | 5.5 | 8.5 | 6 | |
| 3 - The Library Investigation | PolishInvestigationNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.2 | 9 / 8 | 6 / 6.5 | 7 | 6 | 7 | 7 | 1 | 6 | 7 | 4 | 3 | 3 | 6 | 5 | 3 | 8 | 6.5 | 6.5 | 8 | 6 | |
| 4 - Ghostly Encounter in the Stacks | KeepInvestigationAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 8.5 / 8 | 8 / 7.5 | 8 | 6 | 8 | 7 | 2 | 6 | 7 | 6 | 6 | 5 | 7 | 8 | 6 | 8 | 7.5 | 7.5 | 7.5 | 7 | |
| 5 - Confrontation at the Lab | KeepAftermathAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8.5 | 8 / 7.5 | 7 | 7 | 7 | 8 | 3 | 6 | 7 | 7 | 6 | 7 | 8 | 5 | 6 | 7 | 7.5 | 7.5 | 9 | 7 | |
| 6 - The Birth of Ghostbusters | PolishTransitionNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 8.5 / 8 | 6 / 7 | 7 | 6 | 6.5 | 7 | 5 | 6 | 8 | 4 | 3 | 6 | 8 | 5 | 6 | 7 | 6.5 | 5.5 | 8 | 6 | |
| 7 - Awkward Neighborly Encounter | PolishOrientationNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.2 | 9 / 8 | 5.5 / 6.5 | 7 | 5 | 7 | 8 | 1 | 6 | 7 | 3 | 2 | 2 | 4.5 | 5 | 4 | 8 | 6.5 | 6 | 8.5 | 6 | |
| 8 - Supernatural Disturbances and Ghostbusting | Low on its ownMontageDesign and Read are broken — this reads as a rebuild before polish. | BrokenThe underlying story machine isn’t holding — worth looking at before polish. | 6.5 | 9 / 8 | 5 / 6.5 | 8 | 5 | 7 | 6 | 1 | 4 | 7 | 3 | 2 | 2 | 3 | 6 | 4 | 6 | 6.5 | 7 | 8 | 7 | |
| 9 - The Birth of Ghostbusters | PolishOrientationNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9 / 8.5 | 7.5 / 7 | 8 | 6 | 6.5 | 8 | 1 | 5 | 7 | 2 | 2 | 3 | 7 | 4 | 4 | 8 | 6 | 6.5 | 8 | 5.5 | |
| 10 - Dana's Mysterious Encounter | KeepInvestigationAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8.5 | 5 / 6.5 | 7 | 6 | 6 | 8 | 2 | 6 | 7 | 5 | 5 | 4 | 5.5 | 5 | 4 | 8 | 6.5 | 5.5 | 8 | 7 | |
| 11 - A Night of Frustration and Horror | PolishDeliveryNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 8.5 / 8 | 8 / 7 | 7 | 6 | 7 | 6 | 1 | 5 | 6 | 6 | 6 | 5 | 4 | 8 | 6 | 7 | 7 | 7.5 | 8 | 7.5 | |
| 12 - Hotel Disturbance | PolishDeliveryNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9 / 8.5 | 8 / 7.5 | 7 | 6 | 5 | 7 | 1 | 5 | 8 | 3 | 1 | 4 | 6 | 3 | 4 | 7 | 7 | 8 | 8 | 7.5 | |
| 13 - Ghostbusters Investigate the Apartment Building | ReworkInvestigationRead is broken — a load-bearing lens isn’t doing its job yet. | SoftThe structure works but is leaking power in places. | 6.2 | 9 / 8 | 4 / 6 | 7 | 5 | 5.5 | 7 | 1 | 5 | 6 | 4 | 3 | 3 | 2 | 6 | 4 | 8 | 6.5 | 6.5 | 9 | 6 | |
| 14 - Ray Encounter | KeepPursuitAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8 | 6 / 7 | 7 | 6 | 7 | 5 | 2 | 4 | 7 | 6 | 5 | 4 | 5 | 7 | 5 | 6 | 6.5 | 7 | 8 | 6 | |
| 15 - Paranormal Hallway Encounter | KeepPursuitAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8.5 | 8.5 / 7.5 | 7 | 6 | 7 | 7 | 4 | 7 | 8 | 7 | 8 | 6.5 | 6 | 7 | 6 | 7 | 7.5 | 8 | 9 | 7.5 | |
| 16 - The Banquet Room Battle | KeepPursuitAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 6.5 / 7 | 7 / 7 | 7 | 6 | 7 | 7 | 3 | 5 | 8 | 7 | 7 | 6 | 6 | 6 | 5 | 6 | 7 | 6 | 7 | 6.5 | |
| 17 - Ghostbusting Success | KeepDeliveryAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8.5 | 5.5 / 6.5 | 7 | 7 | 6 | 6 | 2 | 4 | 9 | 6 | 5 | 5.5 | 7 | 7 | 6 | 6 | 6.5 | 6.5 | 8 | 7 | |
| 18 - Ghostbusters Capture and Controversy | PolishDeliveryNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9 / 8 | 6 / 7.5 | 7 | 6 | 7 | 7 | 1 | 5 | 8 | 3 | 2 | 3 | 7 | 7 | 5 | 7 | 7 | 8 | 8 | 6 | |
| 19 - Ghostbusters on the Case | Low on its ownMontageDesign and Read are broken — this reads as a rebuild before polish. | BrokenThe underlying story machine isn’t holding — worth looking at before polish. | 6.2 | 9 / 8 | 5.5 / 6.5 | 7 | 6 | 6.5 | 5 | 0.5 | 1 | 2 | 2 | 2 | 3 | 6 | 7 | 4 | 5 | 6.5 | 6.5 | 8 | 5 | |
| 20 - Ghostly Encounters on the Airwaves | KeepRelationship shiftAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8.5 | 5.5 / 6.5 | 7 | 6 | 7.5 | 8 | 3 | 7 | 8 | 4 | 4 | 4 | 6 | 6 | 5 | 8 | 7 | 7.5 | 8 | 7.5 | |
| 21 - The Ghostbusters' Office | PolishOrientationNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9.5 / 8.5 | 5.5 / 7 | 8 | 6 | 6 | 7 | 1 | 5 | 6 | 4 | 3 | 4 | 5.5 | 5 | 3 | 7 | 6.5 | 7.5 | 9 | 6.5 | |
| 22 - Confrontation with the EPA | KeepContestAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8 | 5.5 / 6.5 | 7 | 6 | 6.5 | 6 | 1 | 6 | 7 | 6 | 5 | 5 | 5 | 5 | 4 | 8 | 6.5 | 7.5 | 9 | 7 | |
| 23 - Storage Facility Concerns | PolishOrientationNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9 / 8 | 7 / 7.5 | 8 | 6 | 8 | 7 | 1 | 4 | 6 | 3 | 4 | 7.5 | 6 | 7 | 5 | 6 | 6.5 | 5.5 | 8 | 7 | |
| 24 - A Nightmarish Encounter | PolishDeliveryNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 8.5 / 8 | 8.5 / 7.5 | 8 | 7 | 7 | 6 | 2 | 4 | 2 | 7 | 8 | 8 | 7 | 7 | 7 | 5 | 7.5 | 7 | 9 | 6.5 | |
| 25 - Unleashed Terror | KeepPursuitAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8 | 8 / 7.5 | 7 | 6 | 7.5 | 6 | 1 | 4 | 8 | 8 | 9 | 7.5 | 7 | 7 | 7 | 8 | 7.5 | 8 | 9 | 7 | |
| 26 - Louis Possessed | KeepPursuitAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8 | 8 / 8 | 7 | 7 | 7.5 | 6 | 7 | 7 | 8 | 8 | 8 | 8 | 8 | 8 | 6 | 8 | 7.5 | 8 | 9 | 7 | |
| 27 - Unveiling the Gatekeeper | KeepRelationship shiftAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8.5 | 8 / 7.5 | 8 | 6 | 7 | 7 | 6 | 6 | 7 | 7 | 7 | 8 | 8 | 8 | 6 | 8 | 7.5 | 7.5 | 8 | 6.5 | |
| 28 - Dana's Possession | PolishInvestigationNo lens is broken, but Execution and Read are soft — this reads as a polish pass. | SolidThe story machine is built and mostly working. | 6.5 | 8.5 / 7 | 6 / 7 | 8 | 6 | 7 | 7 | 3 | 7 | 8 | 7 | 7 | 7 | 6.5 | 6 | 6 | 8 | 6.5 | 5.5 | 8 | 5.5 | |
| 29 - The Keymaster's Revelation | KeepDeliveryAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8 | 7 / 7.5 | 7 | 6 | 7.5 | 8 | 2 | 6 | 7 | 4 | 3 | 7 | 7 | 7 | 5 | 7 | 7 | 6 | 7 | 6.5 | |
| 30 - Sensual Encounter | PolishDeliveryNo lens is broken, but Read is soft — this reads as a polish pass. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 7.5 | 5 / 6.5 | 8 | 5 | 8 | 7 | 3 | 6 | 4 | 6 | 4 | 4 | 2.5 | 8 | 5 | 3 | 7 | 7.5 | 8 | 7 | |
| 31 - Confrontation at the Firehouse | PolishContestNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 7.2 | 9 / 9 | 9 / 8.5 | 8 | 8 | 7 | 8 | 3 | 6 | 8 | 9 | 9 | 9 | 9 | 8 | 7 | 8 | 8 | 8 | 7 | 8 | |
| 32 - The Iridescent Geyser | PolishAftermathNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 7 / 7.5 | 8 / 7.5 | 7 | 6 | 6.5 | 7 | 3 | 5 | 6 | 8 | 7 | 7 | 7.5 | 7 | 6 | 6 | 7 | 6.5 | 7.5 | 6.5 | |
| 33 - Night of Terror | ReworkMontageDesign is broken — a load-bearing lens isn’t doing its job yet. | BrokenThe underlying story machine isn’t holding — worth looking at before polish. | 6.5 | 8.5 / 7 | 6 / 7.5 | 7 | 5 | 7 | 3 | 0 | 0 | 0 | 6 | 5 | 7 | 4 | 8 | 4 | 5 | 7 | 8 | 8 | 5 | |
| 34 - Unwelcome Encounter in the Dark | PolishDeliveryNo lens is broken, but Design is soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 7.5 / 6 | 4.5 / 6.5 | 8 | 6 | 7.5 | 5 | 2 | 6 | 7 | 4 | 3 | 6 | 4 | 7 | 5 | 5 | 6.5 | 6 | 7 | 5 | |
| 35 - Preparing for Gozer's Arrival | PolishInvestigationNo lens is broken, but Read is soft — this reads as a polish pass. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8 | 8 / 8 | 7 | 6 | 7 | 8 | 2 | 6 | 7 | 4 | 3 | 8 | 7 | 6 | 5 | 8 | 7 | 6.5 | 9 | 7 | |
| 36 - Confrontation at City Hall | KeepContestAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 9 | 8 / 8.5 | 7 | 7 | 7 | 6 | 4 | 5 | 8 | 7 | 7 | 9 | 8.5 | 7 | 6 | 8 | 7.5 | 8 | 9 | 7 | |
| 37 - Explosive Encounter and Preparations Amidst Earthquake | PolishDeliveryNo lens is broken, but Design, Execution and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 7.5 / 7 | 8 / 7.5 | 8 | 6 | 6 | 6 | 4 | 4 | 7 | 6 | 5 | 8 | 7 | 6 | 6 | 5 | 6.5 | 6 | 7 | 5 | |
| 38 - Arrival at Dana's Apartment Building | PolishTransitionNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 6.5 | 9 / 8 | 8 / 8.5 | 7 | 6 | 6.5 | 6 | 1 | 4 | 8 | 6 | 5 | 8 | 7 | 7 | 6 | 6 | 7.5 | 8 | 8 | 7 | |
| 39 - Confrontation with Gozer | KeepContestAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 6.5 | 9 / 8 | 8 / 8.5 | 8 | 6 | 8 | 7 | 2 | 4 | 8 | 6 | 7 | 8 | 7 | 7 | 6 | 7 | 7 | 6.5 | 8 | 6 | |
| 40 - The Stay-Puft Marshmallow Man Arrives | KeepDeliveryAll three lenses are solid — worth protecting as it stands. | SolidThe story machine is built and mostly working. | 7.5 | 9 / 9 | 8.5 / 8 | 9 | 7 | 9 | 8 | 2 | 5 | 8 | 8 | 8 | 8.5 | 8 | 9 | 7 | 7 | 8 | 7 | 9 | 7.5 | |
| 41 - Confrontation and Triumph: The Stay-Puft Marshmallow Man's Defeat | PolishDeliveryNo lens is broken, but Design and Read are soft — this reads as a polish pass. | SoftThe structure works but is leaking power in places. | 7.2 | 9.5 / 9 | 3 / 2 | 8 | 7 | 8 | 7 | 4 | 6 | 9 | 8 | 7 | 9.5 | 9 | 8 | 7 | 9 | 8 | 8.5 | 9 | 8 | |
| 42 - Post-Victory Celebrations | ReworkAftermathRead is broken — a load-bearing lens isn’t doing its job yet. | SoftThe structure works but is leaking power in places. | 5.5 | 9 / 8 | 1 / 2 | 6 | 3 | 6 | 4 | 0 | 0 | 8 | 0 | 0 | 0 | 1 | 6 | 5 | 5 | 5 | 6 | 7 | 5 | |
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a strong cliffhanger with the Librarian about to peek around a corner, creating immediate suspense and a clear question: what will she see? This strongly compels the reader to continue.
As the first scene, the script has established a compelling supernatural mystery and a sympathetic (if thin) protagonist in danger. The unresolved threat and the promise of more revelations create strong momentum to keep reading.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a clear call to action (Venkman leaving with Stantz) and an unresolved question: what is the ghost? This compels the reader to continue to the next scene.
The script so far has established a supernatural threat (the library ghost) and a compelling protagonist (Venkman) with a flawed but entertaining personality. The momentum is building, though the ESP test slowed it slightly.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the team about to investigate, leaving the reader curious about what they'll find, but the lack of a cliffhanger or strong hook makes it feel self-contained.
The script so far has established a compelling mystery (the library ghost) and a fun character dynamic, but the pacing is slow and the stakes are low, which slightly dampens momentum.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the team screaming and falling backwards, leaving the ghost's intentions unclear and the team's next move unknown. This cliffhanger compels the reader to continue to see what happens next.
The script so far has established the ghost as a real threat, the team's dynamic, and their initial failure. The unresolved confrontation and the ghost's mysterious nature create strong momentum to keep reading.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because it ends with the team losing their lab but gaining a new, more ambitious goal (catching a ghost), creating a clear hook for the next scene.
Given the whole script so far, the momentum is strong: the team has had their first real paranormal encounter, been fired, and now have a clear mission. The threads of the ghost at the library and the team's underdog status are gaining steam, pulling the reader forward.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the team securing a firehouse, which creates a sense of forward momentum and curiosity about how they will set up shop, but no cliffhanger or open question compels immediate continuation.
The script so far has built momentum from the library ghost encounter to the firing, and this scene solidifies the new direction, but the lack of a new paranormal threat or personal stake may cause some readers to pause.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a small hook (the strange TV image) that makes the reader curious about what Dana will see, but the scene is largely self-contained. The desire to continue is mild.
Given the whole script so far, the supernatural plot has been established and the Ghostbusters are forming their business. This scene introduces a new character and location, adding a romantic subplot and a potential new supernatural incident. The momentum is steady but not urgent.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene is self-contained and resolves the family's story, but the commercial break structure and return to Dana's story create a mild hook to see what happens next.
The script's momentum is maintained by the unresolved Dana plotline (the fridge vision) and the Ghostbusters' growing business, but this scene feels like a detour that slows tension.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Dana about to tell her story, creating a clear hook. The reader wants to know what she saw and how the Ghostbusters will react.
The script has built momentum through the library encounter, the expulsion, and the formation of the Ghostbusters. This scene solidifies the new status quo and introduces the first client, maintaining forward momentum.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Dana slamming the door on Venkman, creating mild curiosity about whether she'll call again, but no cliffhanger. The lack of supernatural action reduces urgency to continue.
The script so far has built momentum through the library ghost, the business setup, and Dana's initial encounter. This scene slows that momentum by focusing on character banter without advancing the supernatural plot, but the unresolved mystery of Zuul and the refrigerator keeps the reader interested.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a cliffhanger with the Groom calling for help, creating a strong desire to see what happens next and how the Ghostbusters will respond.
The script has established the Ghostbusters' financial woes and the escalating supernatural threat. This scene adds a new, vivid incident that raises the stakes, but the lack of direct Ghostbusters involvement slightly dilutes the momentum from their storyline.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the team arriving at the hotel, creating a strong hook to see what happens next. The reader wants to see the ghost encounter.
The script has multiple open threads: Dana's case, the team's new business, and the escalating paranormal activity. This scene adds a new case, maintaining momentum. The reader is pulled forward by the promise of action and comedy.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the team moving on, but no cliffhanger or open question compels immediate continuation—it feels like a self-contained comedic beat.
The script has built momentum through the team's formation and first client, but this scene stalls that momentum. The unresolved ghost at the hotel and Dana's subplot still pull the reader forward, but weakly.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the ghost escaping through a wall, creating a mild cliffhanger that makes the reader want to see if the team catches it, but the lack of stakes reduces urgency.
The script so far has built momentum with the team's formation and first successes, but this scene is a minor setback that doesn't significantly advance or hinder the main plot, so the reader is still engaged but not compelled.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a cliffhanger with the vapor charging at Venkman, creating strong suspense that compels the reader to continue to see what happens.
The script has built momentum through the Ghostbusters' formation and previous encounters, and this scene raises the stakes for Venkman personally, keeping the reader invested in the team's success.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels continuation because the ghost escapes and the team's failure creates a need for resolution, plus the open question of what happens if the beams cross.
The script has built momentum through previous scenes (the library, Dana's case, the hotel), and this scene maintains that momentum with a fun but inconclusive action beat. The reader wants to see if they eventually succeed.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a minor cliffhanger (what to do with the trap) and a comedic shrug, which mildly compels continuation but doesn't create strong urgency.
The script has built momentum through the team's expulsion, business startup, and previous failed attempts; this first success is a milestone, but the unresolved trap issue and lack of a clear next mission slightly slow the cumulative pull.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a montage and a front-page photo, creating a sense of closure for this victory. It doesn't leave a cliffhanger, but the montage hints at more jobs to come, making the reader curious about the team's next case.
The script has built momentum through the team's expulsion, startup, and first capture. This scene solidifies their success, and the unresolved threads (Dana's refrigerator entity, the growing ghost activity) keep the reader invested in what happens next.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a punchline (the ticket burning) and a cut to the next location, which is satisfying but doesn't create a strong cliffhanger.
The script so far has built momentum through the Ghostbusters' first capture and growing fame, and this scene maintains that momentum with a fun montage, but the lack of character development or plot advancement may slightly reduce urgency.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a date set, creating mild curiosity about what will happen, but no cliffhanger. It makes the reader want to see the date but doesn't compel immediate continuation.
The script has built momentum through ghost-catching action and the mystery of Dana's experience. This scene slows that momentum for character development, which is necessary but slightly reduces the pull to keep reading immediately.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a setup (EPA visit, Winston's hiring) but no cliffhanger. It compels mild curiosity about the EPA and Winston's integration, but doesn't demand immediate continuation.
The script has built momentum through previous ghost-catching scenes and Dana's storyline. This scene maintains that momentum by introducing new threads (EPA, Winston) but doesn't escalate it.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Peck threatening a court order, creating a mild cliffhanger about future legal trouble, but the lack of immediate action reduces urgency.
The script has built momentum through ghost-catching and Dana's subplot; this scene introduces a new obstacle but doesn't resolve any open threads, so the cumulative pull is moderate.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a grim visual of the storage facility, creating a sense of dread and unanswered questions about what 'something big' means, compelling the reader to see how the team responds.
The script has built momentum through previous ghostbusting jobs and the EPA conflict; this scene deepens the apocalyptic foreshadowing, keeping the reader invested in the escalating crisis.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene strongly compels the reader to continue because it ends on a cliffhanger with Dana being dragged into a fiery kitchen, leaving her fate unknown and the threat escalated.
Given the whole script, the reader is pulled to continue because the Ghostbusters' main client is now in direct danger, the supernatural threat is escalating citywide, and the storage facility is becoming unstable. This scene adds personal stakes to the larger plot.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the Terror Dog chasing Louis into the park, leaving his fate uncertain and creating a cliffhanger that compels the reader to continue to see if he escapes.
The script has built momentum through the Ghostbusters' successful capture and the escalating Dana/Terror Dog plot. This scene adds to the chaos and raises the stakes for Louis, maintaining strong cumulative momentum.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Louis possessed and loping off, creating a strong cliffhanger about what he will do next, compelling the reader to continue.
The script has built momentum through the Ghostbusters' capture of ghosts, Dana's possession, and now Louis's transformation. The Gozer plot is escalating, and the reader is pulled forward by the impending apocalypse.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a cliffhanger with Venkman and Dana heading to the bedroom, leaving the reader wondering what will happen next, compelling continuation.
The script has built momentum through multiple possession and ghost encounters, and this scene raises the stakes for the climax, keeping the reader invested.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a new job setup at the Fort, creating mild curiosity but no strong cliffhanger. The unresolved Dana possession is the main hook.
The script maintains momentum through the Dana/Zuul arc and the growing apocalyptic hints, but the Fort detour slightly dampens the cumulative pull.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a phone call that sets up the Keymaster/Gatekeeper threat, making the reader want to see how the team prevents their meeting.
The script has built strong momentum with the Dana possession and Louis's transformation, and this scene deepens the threat while adding character warmth, keeping the reader invested.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a note of submission and pleasure, which is a cliffhanger of sorts—what happens next to Stantz?—but it feels self-contained and doesn't create a strong pull to the next scene.
Given the whole script, the main plot (Gozer, Dana, Louis) has strong momentum, but this scene is a detour that slows it. The reader may be curious about Stantz's fate but more eager to return to the central conflict.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a cliffhanger with the storage facility exploding, compelling the reader to see the aftermath and how the team responds.
Given the accumulated momentum of Dana's possession, Louis's transformation, and now the containment breach, the script pulls the reader strongly forward toward the climax.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a cliffhanger (the arrest) and an unresolved question (where is Louis going?), which strongly compels the reader to continue. The explosion also creates a sense of urgency that demands resolution.
The script has built strong momentum through the escalating paranormal activity and the personal stakes for Venkman (Dana's possession). This scene raises the stakes further with the explosion and the Keymaster's departure, making the reader eager to see how the team will escape arrest and stop the apocalypse.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene does compel the reader to continue because it raises the question of how the Ghostbusters will handle this escalating chaos, but the lack of a cliffhanger or direct hook weakens the pull.
Given the whole script, the reader is pulled to continue because the main plot (Gozer's arrival, Dana's possession, the storage facility explosion) is unresolved, and this scene shows the city's reaction, adding urgency.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the theater audience applauding, which feels like a conclusion rather than a cliffhanger. It does not create a strong desire to see what happens next, as it is a self-contained vignette. The open question is 'what will Louis do next?' but this is not urgent.
The script has built strong momentum through the explosion of the storage facility and Dana's possession. This scene, while visually interesting, feels like a detour that slows the main plot. The reader is still compelled to see the Ghostbusters' response, but this scene does not add to that urgency.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a summons from the mayor, creating a clear hook and urgency that makes the reader want to see what happens next.
The script has built strong momentum with the explosion, Dana's possession, and Louis's transformation. This scene deepens the mystery and raises stakes, keeping the reader invested.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the mayor asking 'What do you need from me?'—a clear launchpad into the next scene, creating immediate anticipation for the Ghostbusters' plan.
The script has built massive momentum: Dana is possessed, Louis is the Keymaster, the storage facility exploded, and the city is in chaos. This scene adds official sanction, making the final confrontation feel imminent and necessary.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the Ghostbusters gearing up, creating a strong cliffhanger that makes the reader want to see the final confrontation.
The script has built momentum through escalating supernatural events and character arcs; this scene maintains that momentum despite a slight lull in the Mayor corridor.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the Ghostbusters entering the building after the sinkhole, creating a strong cliffhanger about what they will face inside, compelling the reader to continue.
Given the entire script's buildup of Dana's possession, Louis as the Keymaster, and the impending arrival of Gozer, this scene's triumphant arrival and sudden obstacle heighten the momentum and pull the reader toward the final confrontation.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a seismic rumble and the building swaying, creating a cliffhanger that compels the reader to continue to see what happens next.
The script has built strong momentum with escalating chaos, character arcs, and unresolved threats (Dana's possession, the city's destruction), and this scene adds the mystery of Gozer's disappearance, keeping the reader hooked.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because it ends with the Ghostbusters stepping to the edge of the roof, ready to fight—a classic cliffhanger that promises action. The open question is whether they can defeat a giant marshmallow.
Given the whole script, the momentum is high: the apocalypse is manifest, Dana is possessed, and the team is about to face their biggest challenge. The absurd reveal keeps the tone fresh and the reader invested in how the joke will resolve.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene resolves the main conflict, so it doesn't create a strong desire to read the next scene—it feels like an ending. However, the final banter and Louis's line provide a light, satisfying close.
Given this is the climax and resolution of the entire script, the cumulative momentum is high but the story is essentially over. The reader is satisfied and doesn't need to continue.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene does not compel the reader to continue because it is the final scene; the story is complete and all questions are resolved.
Given the whole script, the reader is satisfied and not pulled to keep reading; the story has reached a natural, happy ending.
| Voice Analysis | |
|---|---|
| Summary: | The writer's voice is characterized by witty dialogue, fast-paced action, and a blend of humor and suspense. |
| Voice Contribution | The writer's voice contributes to the script by creating a dynamic and engaging atmosphere. It balances humor with tension and adds depth to the characters and their relationships. |
| Best Representation Scene | 4 - Ghostly Encounter in the Stacks |
| Best Scene Explanation | Scene 4 best showcases the writer's unique voice because it effectively combines humor, suspense, and supernatural elements. The dialogue is witty and engaging, the action is fast-paced, and the overall tone is one of excitement and anticipation. |
The screenplay exhibits a diverse and multifaceted writing style, encompassing elements of humor, supernatural themes, action, suspense, and drama. It blends various genres and narratives, creating a unique and engaging storytelling experience.
Style Similarities:
| Writer | Explanation |
|---|---|
| Dan Aykroyd | His influence is evident throughout the screenplay, particularly in scenes that blend humor and supernatural elements, creating a distinct and memorable tone. |
| Harold Ramis | His comedic sensibilities and penchant for witty dialogue are prominent in several scenes, adding a layer of humor and character development. |
| Joss Whedon | His writing style is discernible in scenes that combine humor, action, and supernatural themes, showcasing his ability to craft engaging and entertaining narratives. |
| Shane Black | Elements of his style, such as fast-paced storytelling and witty banter, can be observed in scenes that blend humor with action and suspense. |
| Guillermo del Toro | His ability to merge supernatural elements with realistic settings and relatable characters is evident in scenes that create a sense of unease and mystery. |
Other Similarities: The screenplay also incorporates the styles of other notable writers, such as Ivan Reitman, Neil Gaiman, and Edgar Wright, contributing to its diverse and rich storytelling landscape.
| Pattern | Explanation |
|---|---|
| Frequent High Tone Scores | Most scenes in this screenplay have a high tone score, indicating a consistent level of suspense, excitement, or humor throughout the narrative. |
| Suspense and Humor | Suspenseful scenes are often complemented by humor, creating a blend of紧张and lighthearted moments. This combination adds depth and keeps the audience engaged. |
| Humor and Character Changes | Scenes with high humor scores tend to have less character changes, suggesting that comedic moments may take precedence over character development in those instances. |
| High Stakes Scenes | High stakes scenes, those with significant consequences for the characters, are often accompanied by intense dialogue and emotional impact, enhancing the overall tension and drama. |
| Mysterious and Suspenseful | Scenes that combine mystery and suspense tend to have higher overall grades, indicating that the combination of intrigue and tension is particularly effective in engaging the audience. |
| Supernatural and Suspenseful | The combination of supernatural elements and suspenseful tones consistently results in high grades, suggesting that this blend of the otherworldly and the thrilling resonates well with the audience. |
| Surrealism and Excitement | Scenes with surreal elements are often accompanied by high excitement scores, indicating that the unexpected and imaginative can effectively elevate the intensity and engagement of the narrative. |
The screenplay demonstrates strong writing craft with a blend of humor, suspense, and supernatural elements. The writer effectively creates engaging narratives, develops compelling characters, and keeps the audience entertained with a unique voice and style. However, there are areas that could benefit from further refinement to elevate the overall impact and consistency of the writing.
| Type | Suggestion | Rationale |
|---|---|---|
| Book | Read 'Save the Cat!' by Blake Snyder to study in-depth character development and story structuring techniques. | This book provides valuable insights into creating compelling characters, building character arcs, and structuring a screenplay for maximum impact. |
| Screenplay | Study screenplays by Aaron Sorkin for exceptional dialogue writing and fast-paced storytelling. | Analyzing Sorkin's screenplays will help improve the writer's ability to create sharp, witty, and engaging dialogue that drives the narrative forward. |
| Video | Watch behind-the-scenes footage of films with similar tone and pacing to understand how directors and writers achieve the desired effect. | Observing how successful films handle tone and rhythm visually can provide valuable practical insights into storytelling techniques. |
| Trope | Trope Details | Trope Explanation |
|---|---|---|
| Damsel in Distress | Dana Barrett is frequently rescued by the Ghostbusters, particularly from Gozer and the Terror Dogs. | A female character who is constantly in need of rescue by a male character, often portrayed as weak and helpless. |
| The Chosen One | The Ghostbusters are tasked with defeating Gozer, an ancient deity, implying that they are the only ones who can save the world. | A character who is destined to save the day, often due to some special power or ability. |
| MacGuffin | The Stay-Puft Marshmallow Man is summoned by Gozer as a physical manifestation of the Ghostbusters' fear, but it ultimately serves no real purpose in the plot. | An object or device that is important to the plot, but has no real value or purpose beyond its symbolic meaning. |
| Supernatural Scare | The film features a number of supernatural scares, including ghosts, demons, and other paranormal entities. | A sudden and unexpected event that is designed to scare the audience. |
| Comic Relief | Winston Zeddemore is often used as a source of comic relief, providing humor and levity in tense situations. | A character who provides humor and lightens the mood in a serious or dramatic situation. |
| The Power of Love | Dana Barrett's love for Peter Venkman helps to save the day, as it weakens Gozer and allows the Ghostbusters to defeat him. | The idea that love can overcome all obstacles, even supernatural ones. |
| The Chosen One | Louis Tully, the Keymaster, and Dana Barrett, the Gatekeeper, are chosen to aid in the summoning of Gozer. They are not necessarily evil, but they are destined to play a role in the apocalypse. | A character who is destined to save the day, often due to some special power or ability. |
| The Hero's Journey | The Ghostbusters go on a journey to defeat Gozer, facing many challenges and obstacles along the way. | A story structure that follows a hero on a journey to achieve a goal, often involving a transformation or growth in character. |
| The Chosen One | The Ghostbusters are the only ones who can defeat Gozer, as they are the only ones with the knowledge and experience to do so. | A character who is destined to save the day, often due to some special power or ability. |
| The Power of Love | Dana Barrett's love for Louis Tully helps to save the day, as it weakens Gozer and allows the Ghostbusters to defeat him. | The idea that love can overcome all obstacles, even supernatural ones. |
| Scene Number | Line |
|---|---|
| 16 | Venkman: He slimed me! He slimed me! |
| 18 | Stantz: We got one! |
| 8 | Stantz: Are you troubled by strange noises in the night? Do you experience feelings of dread in your basement or attic? Have you or your family actually seen a spook, specter or ghost? If the answer is yes, then don't wait another minute. Just pick up the phone and call the professionals -- Ghostbusters. |
| 40 | Stantz: It's the Stay-Puft Marshmallow Man! He was on all the packages we used to buy when I was a kid. We used to roast Stay-Puft marshmallows at Camp Waconda! |
| 38 | Venkman: Ghostbusters! |
| Three parapsychologists lose their university funding and start a ghost-catching business in New York City, only to find themselves facing a supernatural threat of apocalyptic proportions. |
| When ghosts invade Manhattan, a team of eccentric scientists with high-tech gadgets and a knack for the supernatural become the city's only hope. |
| A group of unlikely heroes must overcome their personal differences and bureaucratic obstacles to save New York City from a Sumerian god and his marshmallow minion. |
| A team of eccentric scientists turned ghost hunters face the ultimate supernatural threat in a battle to save New York City from a gooey, gigantic marshmallow man. |
| When ghosts start popping up all over New York, only three professors and a streetwise newcomer can save the day in this supernatural comedy. |
| Science meets the supernatural as a ghost-catching squad wrangles spirits across New York, culminating in a showdown with an ancient deity looking to remodel the city. |
| It's a race against time as four ghostbusters put their paranormal prowess to the test against an apocalyptic threat in the heart of New York City. |
| Who you gonna call? A ragtag team of ghostbusters faces off against a marshmallow mascot turned malevolent god in this action-packed supernatural comedy. |
Got an idea to improve our service? We'd love to hear it!
Brainstorm credits pay for AI generations like Show me how to write this. They auto-refill with each new analysis. Top up here without leaving the page.
No lens is broken, but Design is soft — this reads as a polish pass.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
5/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
5/10 expected
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
Pick a criterion on the left to see its read.
The concept of a haunted library is familiar but executed with a fresh, slow-burn approach that emphasizes atmosphere over jump scares. The use of card catalogues and books as active agents is a nice touch, though the idea of unseen supernatural forces in a quiet public space is not entirely original.
The plot is minimal: a librarian experiences unexplained phenomena. The sequence of events is clear and escalates logically from subtle to overt, but there is no clear narrative progression or change in the situation beyond the Librarian's growing fear.
The haunted library is a familiar trope, but the specific use of card catalogues and books as active agents, combined with the Librarian's obliviousness, feels fresh. The actions and dialogue are authentic to the setting.
Out of step with your script — characters holds up in your other scenes.
The Librarian is a generic 'studious' figure with no distinguishing traits or backstory. Her reactions are believable but shallow; she serves more as a vessel for the audience's fear than as a developed character.
The Librarian goes from calm to frightened, but this is a surface-level emotional shift, not a meaningful character change. She learns nothing and makes no decisions.
The Librarian's internal goal is to maintain order and understand the disturbance, driven by a need for safety and control in her familiar environment.
Out of step with your script — external goal holds up in your other scenes.
The Librarian's external goal is to finish her shelving task and identify the source of the noises.
The conflict is between the Librarian and an unseen supernatural force. It's external and clear, but the Librarian has no agency—she only reacts, which weakens the conflict's dramatic weight.
The opposition is an unseen, malevolent force that is powerful and mysterious. The Librarian has no way to fight back, making the opposition strong but the conflict one-sided.
Stakes are low—the Librarian's safety is threatened, but there's no broader consequence or personal investment established yet.
Out of step with your script — story forward holds up in your other scenes.
The scene introduces a supernatural mystery but does not advance a larger plot or reveal any story direction. It's an opening hook, not a story-moving event.
This scene is unpredictable because the supernatural events are introduced without explanation, and the Librarian's failure to notice them subverts expectations of a typical horror protagonist.
The scene generates mild unease and curiosity but lacks deep emotional resonance because the Librarian is a cipher. The fear is generic, not personal.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
Dialogue is sparse and functional—two short lines that reveal her confusion and fear. It's realistic but does little to develop character or advance plot.
This scene is engaging because it builds suspense through escalating, unexplained phenomena and the Librarian's obliviousness, making the reader want to see what happens next.
The pacing of the scene contributes to its effectiveness because it starts slow and peaceful, then gradually accelerates the frequency and intensity of the supernatural events, creating a rising tension that peaks at the cliffhanger.
Formatting is mostly correct with clear scene headings and action lines. Some action lines are overly descriptive (e.g., 'The Librarian works her way through rows and rows...') and could be more concise. The use of 'POV' as a scene heading is unconventional but clear.
The scene follows a classic horror structure: establish normalcy, introduce subtle anomaly, escalate to overt threat, end on a cliffhanger. It's effective for the genre, though the pacing could be tightened.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a strong cliffhanger with the Librarian about to peek around a corner, creating immediate suspense and a clear question: what will she see? This strongly compels the reader to continue.
As the first scene, the script has established a compelling supernatural mystery and a sympathetic (if thin) protagonist in danger. The unresolved threat and the promise of more revelations create strong momentum to keep reading.
All three lenses are solid — worth protecting as it stands.
HoldingIt commits to one clear thing and holds it.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
8/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
7/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
6/10 expected
It’s a fresh take on this kind of scene
5/10 expected
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
7/10 core
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a cynical professor using fake ESP tests while a real ghost is discovered is fresh and ironic, but the scene leans heavily on familiar tropes (skeptical academic, student volunteers, electric shocks) without fully subverting them.
The plot moves from the library incident to Venkman's test to Stantz's urgent call, creating a clear A-to-B progression. However, the test itself is a static, repetitive gag that delays the plot's forward thrust.
The combination of a fraudulent ESP test with a real ghost sighting is original, but the individual elements (skeptical professor, student volunteers, electric shocks) are familiar. The dialogue feels authentic to the characters.
Venkman is vividly drawn as a charming, unethical, and lazy academic; Stantz is earnest and excited. The coed and sophomore are one-note foils. Venkman's character is the scene's strength, but the others lack depth.
Venkman does not change; he remains the same cynical womanizer. Stantz's excitement is static. No character arc occurs in this scene.
Venkman's internal goal is to maintain his comfortable, manipulative lifestyle—avoiding real work, pursuing attractive women, and preserving his fraudulent reputation. His need is for validation without effort; his fear is being exposed as a fraud.
Venkman's external goal is to finish his ESP test and possibly seduce the coed, then reluctantly respond to Stantz's call about the ghost.
Conflict is moderate: Venkman vs. the sophomore (personal), Venkman vs. Stantz (professional urgency vs. pleasure), and the implied conflict of the supernatural event. None escalate beyond mild tension.
Venkman faces mild opposition from the sophomore (who leaves) and Stantz (who interrupts his fun), but neither is a strong antagonist. The real opposition (the ghost) is off-screen.
Stakes are low: Venkman's test is trivial, and the ghost is only mentioned, not shown. The scene builds curiosity but no immediate danger or consequence.
The scene moves the story forward by introducing the ghost incident and setting up the team's first investigation, but the ESP test is a detour that only serves character introduction.
This scene is unpredictable because the ESP test is revealed as a cruel game, and the sudden shift to a genuine paranormal event subverts expectations, but the overall structure (skeptic gets called to action) is familiar.
The scene generates mild amusement and curiosity but little emotional depth; the librarian's scream is quickly abandoned, and Venkman's test is played for laughs, not empathy.
Dialogue is snappy and reveals character—Venkman's lies, Stantz's urgency, the sophomore's anger. The banter is entertaining, but some lines (e.g., 'You're fantastic!') feel too on-the-nose for the character's manipulation.
This scene is engaging because of Venkman's charismatic, morally gray behavior and the promise of a real ghost investigation, but the extended ESP test loses momentum.
The pacing of the scene contributes to its effectiveness because it starts with a quick hook, slows down for the repetitive test, then picks up again with Stantz's entrance. The middle section drags.
Formatting is professional and clear, with proper scene headings, character cues, and action lines. Minor issue: the parenthetical '(lies)' in Venkman's dialogue is a bit on-the-nose for a screenplay.
The scene follows a classic setup-payoff structure: the library hook, then a comedic interlude (ESP test), then the call to action. The interlude is too long for its payoff, making the structure feel lopsided.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a clear call to action (Venkman leaving with Stantz) and an unresolved question: what is the ghost? This compels the reader to continue to the next scene.
The script so far has established a supernatural threat (the library ghost) and a compelling protagonist (Venkman) with a flawed but entertaining personality. The momentum is building, though the ESP test slowed it slightly.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 core
No page-visible force — antagonist, deadline, need, threat, rule, condition — pushes the beats; the scene proceeds without anything making it happen.
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
4/10 expected
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
5/10 expected
The result doesn’t oblige what comes next
6/10 core
Every beat and line earns its place
5/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
5/10 expected
At the close there is no open question or live threat — no reason to turn the page.
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of skeptical scientists investigating a ghost in a library is strong, but the scene focuses more on character introduction than on the concept's execution.
The plot advances the investigation but is mostly setup and exposition, with no major plot development or obstacle.
The scene offers a fresh take on the ghost-hunting genre by grounding it in academic skepticism and deadpan humor, though the setup is familiar.
Venkman's sarcastic skepticism and Stantz's earnest enthusiasm are well-drawn, but Spengler is underused and the Head Librarian is a flat functionary.
No character changes; Venkman remains skeptical, Stantz remains enthusiastic, and Spengler is barely present.
Venkman's internal goal is to maintain his skeptical, detached persona and avoid being drawn into what he sees as pseudoscience.
Venkman's external goal is to investigate the library disturbance quickly and dismiss it as a non-paranormal event.
Conflict is mild—Venkman's skepticism vs. Stantz's belief, and the librarian's nervousness—but no direct confrontation or high stakes.
Opposition is minimal—the Head Librarian's nervousness and the unseen ghost provide mild resistance, but no active antagonist.
Stakes are low—this is a routine call for the characters, with no personal or immediate danger shown.
The scene moves the story forward by establishing the team's arrival at the library and the beginning of the investigation, but it's mostly setup.
This scene is unpredictable because Venkman's dismissive attitude subverts the expected serious paranormal investigation, but the overall trajectory is predictable.
The scene is light and humorous, with little emotional weight; the librarian's fear is undercut by Venkman's dismissiveness.
The dialogue is sharp and character-revealing, especially Venkman's deadpan lines, but some exchanges (like the rockfall anecdote) feel tangential.
This scene is engaging because of the witty dialogue and the contrast between Venkman's sarcasm and Stantz's earnestness, but the lack of action or tension reduces momentum.
The pacing of the scene contributes to its effectiveness because the dialogue moves briskly, but the extended exposition about the graph and rockfall slows it down.
Formatting is standard and professional, with clear scene headings and action lines. Minor issue: the Head Librarian's dialogue is introduced with a character description that could be integrated more smoothly.
The structure follows a classic setup: arrival, introduction of the location, and initial character dynamics. It lacks a clear inciting incident or turning point within the scene.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the team about to investigate, leaving the reader curious about what they'll find, but the lack of a cliffhanger or strong hook makes it feel self-contained.
The script so far has established a compelling mystery (the library ghost) and a fun character dynamic, but the pacing is slow and the stakes are low, which slightly dampens momentum.
All three lenses are solid — worth protecting as it stands.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
8/10 core
A real force keeps it pushing forward
7/10 core
The situation deepens as it goes
7/10 core
It turns — something is different by the end
6/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
6/10 expected
It’s a fresh take on this kind of scene
7/10 expected
It defeats anticipation fairly
7/10 expected
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a ghost that is both terrifying and mundane (a full-bodied elderly lady) is fresh, and the team's scientific approach to the paranormal is engaging. However, the ghost's final action ('Quiet!') is more comedic than frightening, slightly diluting the horror concept.
The plot moves from investigation to confrontation, with clear beats of discovery and reaction. The team's plan to 'get her' fails humorously, but the plot lacks a clear progression of stakes or a meaningful outcome beyond the ghost's reprimand.
The scene offers a fresh take on ghost hunting by combining scientific jargon with comedic incompetence. The ghost's elderly lady form and her command to be quiet are original twists on typical horror tropes.
Venkman's skepticism, Stantz's enthusiasm, and Spengler's scientific detachment are well-drawn. The librarian's testimony adds color. However, the characters' reactions are somewhat one-note (Venkman's snark, Stantz's excitement) without deeper nuance.
No significant character change occurs; Venkman remains skeptical, Stantz remains excited, and Spengler remains analytical. The ghost's appearance does not alter their perspectives.
Venkman's internal goal is to maintain his skeptical, scientific authority and avoid looking foolish; he fears being wrong or duped.
The team's external goal is to investigate and capture the ghost.
Conflict is primarily external: the team vs. the ghost, with internal tension between Venkman's skepticism and Stantz's belief. The conflict peaks when they try to capture the ghost but fails, resolving anticlimactically.
The ghost is a formidable opponent, but its non-violent response (roaring 'Quiet!') reduces the sense of opposition. The team's failure to capture it shows the ghost's power, but the opposition is not sustained.
Stakes are moderate: the team's credibility and safety are at risk, but the ghost's non-violent response lowers the immediate danger. The scene does not raise stakes significantly.
The scene confirms the existence of the ghost and establishes the team's initial failure to capture it, setting up future attempts. It moves the story forward by validating the paranormal threat.
This scene is unpredictable because the ghost's final action (roaring 'Quiet!') subverts the expected violent confrontation, and the team's plan to 'get her' fails in a comedic way.
The scene generates amusement and mild suspense, but the emotional impact is limited by the comedic tone. The ghost's roar is startling but not deeply affecting.
Dialogue is sharp and character-specific, with Venkman's inappropriate questions ('Are you currently menstruating?') and Stantz's excited 'Arms! Great!' standing out. The ghost's single line 'Quiet!' is memorable but brief.
This scene is engaging because it balances suspense with humor, and the team's bumbling attempt to capture the ghost is entertaining. The ghost's unexpected 'Quiet!' is a memorable payoff.
The pacing of the scene contributes to its effectiveness because it builds tension slowly through the stacks, then accelerates with the ghost's appearance and the team's failed capture, ending with a sudden comedic release.
Formatting is professional and clear, with proper scene headings, action lines, and dialogue. The use of 'HIGH POV' and 'THEIR POV' is innovative but could be confusing without context. Minor issue: 'THE DOOR' as a character heading is unconventional.
The scene follows a classic horror-comedy structure: setup (librarian's testimony), investigation (team enters stacks), discovery (ghost appears), confrontation (attempt to capture), and twist (ghost roars 'Quiet!'). The structure is effective but the climax is deflated by comedy.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the team screaming and falling backwards, leaving the ghost's intentions unclear and the team's next move unknown. This cliffhanger compels the reader to continue to see what happens next.
The script so far has established the ghost as a real threat, the team's dynamic, and their initial failure. The unresolved confrontation and the ghost's mysterious nature create strong momentum to keep reading.
All three lenses are solid — worth protecting as it stands.
An aftermath beat lands the cost of what just happened rather than driving new action.
HoldingWhat happens here obliges what comes next.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
6/10 expected
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
8/10 core
What happens here obliges what comes next
7/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a paranormal research team being fired for being 'bad scientists' right after their first real success is a strong ironic beat, but the execution is straightforward and lacks deeper subversion.
The plot moves from the library escape to the university dismissal, establishing a clear setback that forces the team to regroup. The transition is logical but the dismissal scene feels slightly rushed and expository.
The scene is original in its blend of supernatural adventure and academic satire, with Venkman's sarcastic voice providing a fresh take on the 'scientists vs. the establishment' trope. The dialogue feels authentic to the characters.
Venkman's sarcastic bravado, Stantz's naive excitement, and Spengler's detached scientific focus are all consistent and well-drawn. Dean Yaeger is a functional antagonist but lacks depth beyond being a bureaucratic obstacle.
Venkman shows a slight shift from skepticism to excitement about catching a ghost, but his core personality remains unchanged. No significant character change occurs in this scene.
Venkman's internal goal is to gain recognition and validation for his unorthodox methods, driven by a need for respect and a fear of being seen as a fraud.
Venkman's external goal is to keep the team's research funded and operational, and to catch a ghost to prove their worth.
Conflict is clear: the team vs. the Dean's decision, and internal conflict between Venkman's self-serving attitude and the others' scientific idealism. The external conflict is resolved too quickly, reducing tension.
The opposition is Dean Yaeger, a bureaucratic authority figure who represents institutional resistance. He is a clear obstacle but lacks personal stakes or nuance, making the opposition functional but not compelling.
Stakes are raised: the team loses their lab and funding, threatening their ability to continue their research. However, the stakes feel somewhat abstract as the team quickly pivots to new possibilities.
The scene moves the story forward by establishing the team's loss of university funding, forcing them to consider independent ghost-catching, and setting up the need for a new plan.
This scene is somewhat predictable: after a success, a setback is expected. The specific form (Dean's speech) is a bit cliché, though Venkman's Galileo quip adds a small surprise.
The emotional impact is mixed: the exhilaration of the ghost encounter is undercut by the dismissal, but the scene doesn't dwell on the loss, moving quickly to Venkman's Nobel Prize fantasy, which diffuses the emotional weight.
The dialogue is sharp and character-specific, with Venkman's sarcasm ('They'll probably throw out the entire engineering department') and Stantz's enthusiasm ('kick ass -- in the spiritual sense') landing well. The Dean's speech is a bit too on-the-nose and lacks subtext.
This scene is engaging because of the rapid shifts in tone—from exhilaration to sarcastic banter to sudden defeat—and the promise of a new direction (catching a ghost) keeps interest high.
The pacing of the scene contributes to its effectiveness because it moves quickly from the library to the university, with brisk dialogue and short scenes that maintain energy, though the dismissal scene feels slightly rushed.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
Formatting is professional and standard, with clear scene headings, action lines, and dialogue attribution. No errors or stylistic issues.
The scene follows a classic reversal structure: high from the ghost encounter, then a low from the dismissal, ending with a new goal (catching a ghost). The transitions are clear but the dismissal scene is a bit too expository.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because it ends with the team losing their lab but gaining a new, more ambitious goal (catching a ghost), creating a clear hook for the next scene.
Given the whole script so far, the momentum is strong: the team has had their first real paranormal encounter, been fired, and now have a clear mission. The threads of the ghost at the library and the team's underdog status are gaining steam, pulling the reader forward.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
A transition carries us between beats. It owes less structurally than a scene built to turn.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 expected
No page-visible force — antagonist, deadline, need, threat, rule, condition — pushes the beats; the scene proceeds without anything making it happen.
It leans on mood instead of something actually pushing it
5/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
6/10 core
It turns — something is different by the end
5/10 expected
The result obliges nothing in the next scene — no debt, threat, or changed baseline.
The result doesn’t oblige what comes next
7/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of starting a paranormal investigation business after being fired is strong and original, but the execution in this scene relies on familiar 'starting a business' tropes (mortgage, bank loan, real estate) without adding a fresh twist.
The plot moves the story forward by establishing the team's new direction, but the transitions between locations (bench, bank, firehouse) are abrupt and lack connective tissue, making the sequence feel episodic.
The scene is original in its premise (ghostbusting as a business) but the execution of the 'starting a business' montage is conventional, with dialogue that feels authentic to the characters.
Venkman's visionary optimism and Stantz's pragmatic worry are well-drawn, but Spengler is underutilized (only a calculation line), and the real estate woman is a flat functionary.
Venkman changes from desolate to visionary, but the change is abrupt and not fully earned; Stantz remains worried but goes along.
Venkman's internal goal is to prove he can succeed without the university, driven by a need for validation and fear of failure.
Venkman's external goal is to secure funding and a location for the Ghostbusters business.
The conflict is low—internal disagreement about the mortgage and fear of failure, but no active opposition until the real estate negotiation, which is mild.
The opposition is minimal—Dean Yaeger is gone, the bank manager is unseen, and the real estate woman is cooperative—so there is no strong antagonist.
The stakes are financial and reputational (mortgage, house, career), but they are discussed rather than felt, reducing tension.
The scene moves the story forward significantly by establishing the business foundation, but the lack of a clear obstacle or setback makes it feel like a checklist.
This scene is somewhat predictable—the 'let's start our own business' beat is a classic trope—but the specific details (mortgage at 19%, firehouse with a pole) add freshness.
The emotional impact is moderate: Stantz's worry about his childhood home is touching, but the rapid-fire montage dilutes the feeling.
The dialogue is snappy and character-specific, especially Venkman's 'Einstein did his best stuff while he was working as a patent clerk' and Stantz's 'They expect results.' However, the bank scene lacks memorable banter.
This scene is engaging because of the witty dialogue and the promise of the Ghostbusters' origin, but the rapid location changes and lack of a central conflict reduce sustained interest.
The pacing of the scene contributes to its effectiveness because the bench conversation is slow and reflective, then the bank and firehouse are rushed, creating an uneven rhythm that undercuts the emotional beats.
Formatting is standard and clean, with proper scene headings and character cues, though the transition from EXT. COLUMBIA to EXT. WIDE ANGLE to EXT. AVENUE is a bit jumpy.
The scene uses a three-part structure (despair, decision, action) but the middle part (bank) is too brief to build momentum, and the firehouse scene feels like a coda.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the team securing a firehouse, which creates a sense of forward momentum and curiosity about how they will set up shop, but no cliffhanger or open question compels immediate continuation.
The script so far has built momentum from the library ghost encounter to the firing, and this scene solidifies the new direction, but the lack of a new paranormal threat or personal stake may cause some readers to pause.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
An orientation beat sets up the world. It isn’t expected to carry a big turn, so a lower Design read here is often the shape of the scene, not a fault.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 expected
No page-visible force — antagonist, deadline, need, threat, rule, condition — pushes the beats; the scene proceeds without anything making it happen.
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 expected
It ends about where it started
5/10 expected
The result doesn’t oblige what comes next
6/10 core
Every beat and line earns its place
6/10 core
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The feeling is stated more than felt
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a shy, nerdy neighbor hopelessly in love with the protagonist is a familiar trope, but it's executed with specific, quirky details (the high-speed workout tape, the mineral water) that give it freshness. The juxtaposition of this mundane interaction with the eerie Gothic building and the strange TV image adds a layer of intrigue.
The plot advances minimally: we meet Dana, learn about her neighbor Louis, and get a hint of the supernatural via the TV. The scene is more character-establishing than plot-driving, which is appropriate for an early introduction but slows momentum.
The scene is a fresh take on the 'awkward neighbor' trope, with specific, quirky details that feel authentic. Louis's dialogue is particularly original in its blend of health-consciousness and social ineptitude.
Dana is established as cool, independent, and slightly weary of Louis's advances. Louis is vividly drawn as a well-meaning but socially awkward nerd, with his rambling dialogue and self-lockout perfectly capturing his character. The scene effectively differentiates their personalities.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
Neither character changes significantly. Dana remains aloof, Louis remains awkward. The scene is static in terms of character development.
Dana's internal goal is to maintain her personal space and independence, avoiding unwanted social obligations while managing her fatigue from rehearsal.
Dana's external goal is to get into her apartment, put away her groceries, and turn off the TV.
The conflict is low-level: Dana wants to be left alone, Louis wants her attention. There's no direct confrontation, only a gentle push-and-pull. The real conflict (the supernatural) is only hinted at via the TV.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
The opposition is minimal: Louis's persistence is a minor annoyance, not a true obstacle. Dana easily overcomes it by closing her door.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
The stakes are personal and low: Dana's comfort and Louis's social success. The supernatural stakes are not yet present in this scene.
The scene moves the story forward by introducing Dana and her apartment, which will become a key location. The strange TV image is a small hook, but the scene is primarily setup.
This scene is somewhat predictable in its romantic-comedy beats, but the specific details (the high-speed workout, the self-lockout) add small surprises. The TV image is the main unpredictable element.
The emotional impact is mild amusement and a touch of sympathy for Louis. Dana's weariness is relatable, but the scene doesn't aim for strong emotion.
The dialogue is natural and character-specific. Louis's monologue about his workout and mineral water is both funny and revealing. Dana's polite but firm rejections are realistic. The exchange feels authentic to a neighborly encounter.
This scene is engaging because of the charming awkwardness of Louis's character and the subtle mystery of the TV image. The viewer wants to see what Dana will do next.
The pacing is leisurely, matching the mundane nature of the encounter. The scene takes its time with Louis's rambling, which is appropriate for comedy but may feel slow for viewers eager for the supernatural plot.
The formatting is professional and clear. Scene headings are correct, action lines are descriptive but not overwritten, and dialogue is properly attributed. Minor note: the parentheticals in Dana's dialogue are used effectively.
The scene follows a classic setup: establish location, introduce character, create a minor obstacle (Louis), and end with a hook (the TV). The structure is functional but not innovative.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a small hook (the strange TV image) that makes the reader curious about what Dana will see, but the scene is largely self-contained. The desire to continue is mild.
Given the whole script so far, the supernatural plot has been established and the Ghostbusters are forming their business. This scene introduces a new character and location, adding a romantic subplot and a potential new supernatural incident. The momentum is steady but not urgent.
Design and Read are broken — this reads as a rebuild before polish.
A montage compresses time. It isn’t built to turn on a single thread.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
4/10 expected
No page-visible force — antagonist, deadline, need, threat, rule, condition — pushes the beats; the scene proceeds without anything making it happen.
It leans on mood instead of something actually pushing it
3/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
3/10 expected
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
5/10 light
The result doesn’t oblige what comes next
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
4/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
6/10 core
The reader can follow what matters
3/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
2/10 expected
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
4/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
5/10 expected
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a ghost-hunting service commercial is clever and original, but the execution is straightforward and doesn't explore new territory beyond the parody.
The plot is minimal—a family's ghost problem is solved quickly—serving more as a demonstration than a narrative progression.
The scene is original in its meta-commercial approach, but the ghost-catching itself is a familiar trope executed without fresh twists.
The Ghostbusters are shown in their professional roles but with little depth; the family is generic. Stantz's enthusiasm and Venkman's cheesy smile are the only character beats.
No character changes; the Ghostbusters remain the same, and the family is merely grateful.
Venkman's internal goal is to maintain the Ghostbusters' reputation and success, driven by a desire for validation and profit.
The Ghostbusters' external goal is to catch the ghost in the children's bedroom and satisfy the customer.
Conflict is minimal—the ghost is quickly caught—and the family's mild distress is resolved without tension.
Out of step with your script — opposition holds up in your other scenes.
The opposition (the ghost) is weak and easily overcome, offering no real challenge to the protagonists.
Out of step with your script — stakes holds up in your other scenes.
Stakes are low—a family's ghost problem is solved easily—with no threat to the protagonists or larger world.
Out of step with your script — story forward holds up in your other scenes.
The scene does not advance the main plot (Dana's story or the larger supernatural threat); it serves as a montage of their business success.
This scene is unpredictable because it breaks the fourth wall and turns into a commercial, but the ghost-catching itself is routine.
The emotional impact is light: mild fear from the children, then relief and satisfaction, but no deep engagement.
The dialogue is functional and comedic, with the infomercial lines being catchy, but it lacks natural conversation or subtext.
This scene is engaging because of its humor, catchy lines, and the satisfying resolution of the ghost problem, but it lacks tension or stakes.
The pacing of the scene contributes to its effectiveness because it moves quickly from problem to solution, mimicking a commercial's rhythm, but feels rushed.
Formatting is standard and clear, with proper scene headings and action lines, though the commercial breaks (scenes 39-45) are fragmented.
The structure follows a classic commercial format: problem (ghost), solution (Ghostbusters), testimonial (happy family), and tagline. It's effective for its purpose but not a traditional scene structure.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene is self-contained and resolves the family's story, but the commercial break structure and return to Dana's story create a mild hook to see what happens next.
The script's momentum is maintained by the unresolved Dana plotline (the fridge vision) and the Ghostbusters' growing business, but this scene feels like a detour that slows tension.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
An orientation beat sets up the world. It isn’t expected to carry a big turn, so a lower Design read here is often the shape of the scene, not a fault.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 expected
No page-visible force — antagonist, deadline, need, threat, rule, condition — pushes the beats; the scene proceeds without anything making it happen.
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
4/10 expected
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
5/10 expected
The result doesn’t oblige what comes next
6/10 core
Every beat and line earns its place
5/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
At the close there is no open question or live threat — no reason to turn the page.
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a ghost-catching startup operating from a firehall is inherently fun and original. The scene introduces this with visual gags (the car, the sign) and character quirks, but doesn't deepen the concept beyond what's already established.
The plot advances the Ghostbusters' formation: they get a car, set up the office, hire Janine, and receive their first client. It's functional but feels like a checklist of setup beats rather than a scene with its own rising action.
The scene is original in its specific details (the car, Janine's dialogue, Spengler's hobbies) but follows a familiar 'starting a business' template. The humor feels authentic to the characters.
Venkman's charm, Stantz's enthusiasm, Spengler's deadpan weirdness, and Janine's bored sarcasm are all on display. Dana is introduced as a hesitant but serious client. The characters are distinct and consistent, though Janine's dialogue is the highlight.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
No character undergoes significant change in this scene. Venkman remains the smooth-talking leader, Stantz the eager enthusiast, Spengler the eccentric scientist, and Dana the worried client.
Venkman's internal goal is to prove that his ghost-catching venture is legitimate and to maintain his confident, charming persona despite the recent setback.
Venkman's external goal is to set up the Ghostbusters' operation and secure their first client.
Out of step with your script — conflict holds up in your other scenes.
There is no direct conflict in this scene. Venkman and Dana have a mild tension of her being hesitant to share her story, but it's resolved quickly. The scene is more about setup than confrontation.
Out of step with your script — opposition holds up in your other scenes.
There is no significant opposition in this scene. The only potential opposition is Dana's hesitation, but Venkman easily overcomes it.
The stakes are low here—the Ghostbusters are just starting their business and Dana has a strange story. The scene doesn't raise the stakes significantly.
The scene moves the story forward by establishing the Ghostbusters' base, vehicle, receptionist, and first client. It's a necessary setup beat.
Out of step with your script — unpredictability holds up in your other scenes.
This scene is somewhat predictable as it follows the expected beats of setting up the Ghostbusters' headquarters. Janine's dialogue and the car's condition provide mild surprises.
The emotional impact is low; the scene aims for amusement and curiosity rather than deep feeling. Janine's deadpan and the car's ridiculousness provide mild humor.
The dialogue is sharp and character-specific, especially Janine's 'Remind me not to go to lunch with you' and Spengler's 'Print is dead.' Venkman's 'Hold all my calls, Janine' / 'What calls?' is a classic comedic beat. However, Dana's exposition feels a bit flat.
This scene is engaging because of the character interactions and the promise of Dana's story, but the lack of conflict or tension makes it feel like a checklist.
The pacing is brisk, moving from car to reception to client quickly. However, the transitions feel a bit abrupt, and the scene could benefit from a moment to breathe.
Formatting is standard and professional. Scene headings are clear, action lines are concise, and character cues are correct. One minor note: 'THE DOOR' appears as a character cue, which is unconventional but likely a typo for 'Dana Barrett enters.'
The scene is structured as a series of vignettes: car arrival, reception setup, client entrance. It lacks a clear three-act structure within the scene, but this is appropriate for a montage-like setup sequence.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Dana about to tell her story, creating a clear hook. The reader wants to know what she saw and how the Ghostbusters will react.
The script has built momentum through the library encounter, the expulsion, and the formation of the Ghostbusters. This scene solidifies the new status quo and introduces the first client, maintaining forward momentum.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
8/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
7/10 core
The situation deepens as it goes
7/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
7/10 expected
Every beat and line earns its place
8/10 expected
The parts are ordered and seamed so they build
9/10 core
The reader can follow what matters
6/10 light
It’s a fresh take on this kind of scene
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 expected
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of using a lie detector to verify a supernatural claim is fresh and funny, grounding the paranormal in pseudo-science. However, the scene leans heavily on familiar romantic-comedy beats (the skeptical woman, the smooth-talking man) that feel less original.
The plot moves forward: the team gets a client, investigates, and Venkman's failed seduction sets up future tension. But the scene stalls in the apartment with little new information—the refrigerator is empty, no ghost appears, and the plot relies on Dana's word alone.
The lie-detector interview is a fresh take on the ghost-hunting genre, but the romantic-comedy beats (cello joke, 'spend the night' line) are familiar. Dialogue feels authentic to the characters.
Venkman's charm and opportunism are on full display, and Dana's intelligence and wariness create a strong foil. Stantz and Spengler are underused, serving as exposition machines rather than distinct personalities here.
Dana remains skeptical but slightly more open; Venkman doesn't change—he's consistently opportunistic. No significant character arc occurs here.
Venkman's internal goal is to prove his charm and scientific legitimacy to Dana, driven by a desire for validation and romantic conquest.
Venkman's external goal is to investigate Dana's apartment for paranormal activity and secure her as a client.
Conflict is moderate: Dana resists Venkman's advances and his intrusion, but there's no direct supernatural confrontation. The real conflict is internal—Dana's denial vs. her experience.
Opposition is moderate: Dana resists Venkman's advances and his intrusion, but there's no active antagonist. The ghost is absent, so opposition is purely interpersonal.
Stakes are low—Dana's personal safety is implied but not dramatized, and the Ghostbusters' business is not at risk. The scene feels more like a date than a crisis.
The scene advances the investigation by establishing Dana as a client and setting up the apartment as a location, but the lack of new paranormal evidence makes it feel like a placeholder.
This scene is unpredictable because Venkman's transparent seduction attempts and Dana's sharp rejections keep the audience guessing how she'll respond, but the overall outcome (no ghost, no progress) is expected.
The emotional impact is mild—amusement and mild frustration at Venkman's antics, but no real fear or urgency. Dana's vulnerability is undercut by the comedic tone.
The dialogue is sharp and character-specific—Venkman's 'It's in the stars' and Dana's 'Like a used car salesman' are memorable. However, some exchanges (the cello bit) feel like filler rather than advancing character or plot.
This scene is engaging because of the witty banter and the mystery of Dana's experience, but the lack of supernatural payoff and Venkman's persistent flirtation can feel repetitive.
The pacing of the scene contributes to its effectiveness because the interview is brisk, but the apartment sequence drags with Venkman's cello bit and slow kitchen inspection.
Formatting is professional and clear, with proper scene headings and action lines. Minor issue: the transition from office to apartment could be smoother.
The scene follows a classic three-beat structure: interview (setup), apartment investigation (rising action), rejection (climax/resolution). It's well-paced for a comedy scene but lacks a strong turning point.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Dana slamming the door on Venkman, creating mild curiosity about whether she'll call again, but no cliffhanger. The lack of supernatural action reduces urgency to continue.
The script so far has built momentum through the library ghost, the business setup, and Dana's initial encounter. This scene slows that momentum by focusing on character banter without advancing the supernatural plot, but the unresolved mystery of Zuul and the refrigerator keeps the reader interested.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
HoldingEvery beat and line earns its place.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 expected
No page-visible force — antagonist, deadline, need, threat, rule, condition — pushes the beats; the scene proceeds without anything making it happen.
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 expected
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 expected
What happens here obliges what comes next
7/10 core
Every beat and line earns its place
6/10 core
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a ghostly attack on a honeymoon suite is a fresh take on the haunted hotel trope, blending marital comedy with body horror. The execution is strong, but the scene doesn't advance the central ghostbusting narrative.
The plot is simple: a couple's romantic night is interrupted by a supernatural event. It effectively builds suspense from mundane details, but it's a self-contained set piece that doesn't directly connect to the Ghostbusters' storyline.
The scene is original in its blend of marital comedy and body horror, using the honeymoon suite as a setting for a ghostly attack. The dialogue feels authentic to a bickering couple.
The Bride and Groom are archetypal newlyweds, their dialogue revealing petty frustrations that make them relatable. However, they are thinly sketched and serve primarily as victims for the ghostly attack.
Neither character undergoes meaningful change; they remain static victims of the supernatural event.
The Bride's internal goal is to feel cherished and validated in her marriage, which is thwarted by her husband's indifference and then by the ghost.
The Bride's external goal is to have a romantic wedding night; the Groom's is to sleep. Both are interrupted by the ghost.
The primary conflict is between the couple's romantic expectations and reality, which is then superseded by the external threat of the ghost. The conflict is clear but low-stakes until the horror escalates.
The opposition is the unseen ghost, which is powerful and terrifying but not directly confronted. The couple's lack of agency makes the opposition feel overwhelming.
The stakes are personal for the couple (their safety) but low for the overall narrative. The scene establishes that the supernatural threat is escalating, but without direct connection to the protagonists.
Out of step with your script — story forward holds up in your other scenes.
The scene introduces a new ghostly incident but does not advance the Ghostbusters' plot or character arcs. It functions as a standalone scare.
This scene is unpredictable because the horror emerges from a mundane bathroom visit, and the couple's bickering makes the supernatural intrusion feel jarring and fresh.
The scene generates mild amusement and unease, but the characters are too thinly drawn for strong emotional investment. The horror is more grotesque than terrifying.
The dialogue is sharp and comedic, capturing the couple's bickering with authenticity. The Groom's deadpan 'Nice going, honey' and the Bride's 'Have I done the right thing?' are highlights. However, the scene relies heavily on description for the horror beats.
This scene is engaging because it subverts expectations: a romantic night turns into a comedic argument, then into a grotesque horror. The pacing keeps the reader curious about what the Groom saw.
The pacing of the scene contributes to its effectiveness because it starts slow with romantic sighs, accelerates with the couple's argument, then builds tension with the cracked clock and bathroom noises before the frantic climax.
Formatting is professional and clear, with proper scene headings, character cues, and action lines. The use of 'THE BED', 'THE AIR VENT', 'THE NIGHTSTAND' as sluglines is creative and cinematic.
The scene follows a classic horror structure: establish normalcy (romantic setting), introduce subtle disturbance (cracked clock), escalate (bathroom noises), reveal the monster (the Groom's horror, the Bride's discovery). The comedic dialogue undercuts the tension effectively.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a cliffhanger with the Groom calling for help, creating a strong desire to see what happens next and how the Ghostbusters will respond.
The script has established the Ghostbusters' financial woes and the escalating supernatural threat. This scene adds a new, vivid incident that raises the stakes, but the lack of direct Ghostbusters involvement slightly dilutes the momentum from their storyline.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
5/10 expected
It leans on mood instead of something actually pushing it
4/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
5/10 expected
It ends about where it started
6/10 expected
What happens here obliges what comes next
5/10 core
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
5/10 core
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
3/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
5/10 expected
At the close there is no open question or live threat — no reason to turn the page.
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a paranormal extermination service responding to a hotel ghost call is strong and well-established. The scene reinforces the concept with visual flair (the ambulance, the logo) but doesn't expand it.
The plot moves forward by introducing a new case at the Hotel Sedgwick, but the scene is mostly setup—answering the phone, suiting up, and arriving. No major plot revelations occur.
The scene is not highly original—it's a standard 'heroes get the call' sequence. However, the specific details (the brass pole, the customized ambulance, the logo) are fresh and iconic for this franchise.
Venkman's embarrassment at their outfits and his quick lie to the guest show his charm and improvisation. Stantz's enthusiasm and Spengler's silent efficiency are consistent. Janine's bored professionalism is a nice touch. No character growth, but personalities are clear.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
No character changes occur; everyone behaves consistently with their established traits.
Venkman's internal goal is to maintain a cool, professional image despite feeling embarrassed by their outlandish appearance. He wants to be taken seriously.
The team's external goal is to respond to the hotel's ghost call, investigate, and resolve the disturbance discreetly.
Low conflict; the team works together smoothly. The only mild tension is Venkman's embarrassment and the manager's anxiety, but no opposition arises.
Out of step with your script — opposition holds up in your other scenes.
No opposition is present; the team works cooperatively. The only potential opposition (the ghost) hasn't appeared yet.
Stakes are low—this is a routine job for the Ghostbusters. The manager's concern about guest questions is minor.
The scene moves the story forward by initiating the next ghost call, but it's a transitional sequence that doesn't advance the main plot (Dana's case or the larger threat).
Out of step with your script — unpredictability holds up in your other scenes.
This scene is predictable in structure—a call comes in, they suit up, they go. The only mildly unpredictable element is Venkman's improvised 'exterminators' excuse.
The scene generates mild excitement and anticipation for the upcoming ghost encounter, but no deep emotional engagement. The comedy keeps it light.
The dialogue is functional and comedic, with Venkman's 'exterminators' line being a highlight. The manager's exposition is a bit on-the-nose but serves the scene. Janine's phone call is dry and effective.
This scene is engaging because of its fast pace, comedic beats (Stantz on the pole, Venkman's lie), and the cool visual of the transformed ambulance. It builds anticipation for the ghost encounter.
The pacing is brisk and effective. The phone call, alarm, suit-up montage, and drive are cut together tightly, creating momentum. The brief pause for the guest interaction adds a comedic beat without slowing things down.
Formatting is professional and clear. Scene headings are correct, action lines are vivid but not overwritten, and dialogue is properly attributed. The brass pole description is a bit awkwardly placed as a scene heading but works comedically.
The scene follows a classic call-and-response structure: alarm, suit up, travel, arrival. It's efficient for an action-comedy, with a clear beginning (call), middle (preparation), and end (arrival at hotel).
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the team arriving at the hotel, creating a strong hook to see what happens next. The reader wants to see the ghost encounter.
The script has multiple open threads: Dana's case, the team's new business, and the escalating paranormal activity. This scene adds a new case, maintaining momentum. The reader is pulled forward by the promise of action and comedy.
Read is broken — a load-bearing lens isn’t doing its job yet.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 core
No page-visible force — antagonist, deadline, need, threat, rule, condition — pushes the beats; the scene proceeds without anything making it happen.
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
4/10 expected
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
5/10 expected
The scene delivers information or understanding but no one is forced to decide or act on it.
The result doesn’t oblige what comes next
6/10 expected
Every beat and line earns its place
5/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
5/10 expected
The unit completes its business and ends on a settled beat — no new live question, demand, or expectation is created for the next unit to inherit.
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of ghost hunters with faulty gear and a tendency to overreact is strong, but this scene doesn't introduce new ideas—it recycles the 'nervous team' trope without fresh twists.
The plot stalls here—the team arrives, has a false alarm, and leaves without encountering the ghost. The bellboy incident is a gag, not a plot point.
The scene is moderately original in its specific gags (Spengler's clinical questions to the towel woman) but relies on familiar tropes of incompetent ghost hunters.
Venkman's sarcasm, Stantz's nervous excitement, and Spengler's clinical obliviousness are consistent and funny. However, no character grows or reveals new depth.
No character changes; they remain the same archetypes they entered with.
Venkman's internal goal is to maintain his cool, sarcastic facade despite his fear and lack of confidence in the equipment.
The team's external goal is to investigate and capture the ghost at the Hotel Sedgwick.
Conflict is low—internal team friction is mild, and the only external opposition is a startled bellboy and a dismissive hotel guest.
Opposition is weak—a startled bellboy and a sarcastic hotel guest offer no real resistance to the team's mission.
Stakes are low—the team's reputation isn't on the line here, and the ghost hasn't been encountered yet.
Out of step with your script — story forward holds up in your other scenes.
The scene does not move the story forward—the ghost is not found, no new information is gained, and the plot remains static.
This scene is unpredictable because the bellboy's appearance and the team's overreaction subvert expectations, but the overall beat (nervous team, no ghost) is familiar.
Emotional impact is minimal—the scene aims for laughs, not feels. The team's anxiety is played for comedy, not tension.
Dialogue is sharp and in-character—Venkman's 'unlicensed nuclear accelerator' line and Spengler's awkward questions are highlights. The bellboy exchange feels a bit forced.
This scene is engaging because the characters' banter and the accidental proton blast create comedic tension, but the lack of ghost action reduces momentum.
The pacing of the scene contributes to its effectiveness because it moves quickly from elevator to corridor to room, but the Spengler/woman exchange slows momentum for a joke.
Formatting is clean and professional—action lines are clear, dialogue is properly attributed, and scene headings are correct.
The scene follows a classic setup-punch structure: nervous buildup, false alarm (bellboy), then deflation. It works for comedy but lacks dramatic structure.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the team moving on, but no cliffhanger or open question compels immediate continuation—it feels like a self-contained comedic beat.
The script has built momentum through the team's formation and first client, but this scene stalls that momentum. The unresolved ghost at the hotel and Dana's subplot still pull the reader forward, but weakly.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
5/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
6/10 expected
It turns — something is different by the end
6/10 expected
What happens here obliges what comes next
7/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a ghost that is a slob, feeding on leftovers and wine, is fresh and humorous, but it's a one-note joke that doesn't expand the world or mythology significantly.
The plot advances the ghost hunt with a clear sequence: Stantz finds the ghost, attacks, and it escapes, but the scene is a self-contained chase with no new information or consequences for the larger story.
The scene is original in its depiction of a gluttonous, messy ghost, but the chase and escape are standard genre fare.
Stantz shows bravery and disgust, but his character is not deepened; the ghost is a one-dimensional comic villain. Venkman and Spengler are absent, limiting character interaction.
Stantz shows no change; he starts brave and ends frustrated, but there's no arc or growth.
Stantz's internal goal is to prove himself as a capable ghost hunter, driven by a desire for validation and excitement.
Stantz's external goal is to capture or neutralize the ghost.
Conflict is clear: Stantz vs. the ghost, with a brief chase and the ghost escaping, but the stakes are low and the resolution is anticlimactic.
The ghost offers physical opposition by dodging and escaping, but it is not a formidable threat, making the opposition weak.
Stakes are low: the ghost is a nuisance, not a threat, and the team's failure has no immediate consequences.
The scene moves the story forward by showing the Ghostbusters in action, but the ghost escapes, so no progress is made in capturing it or learning new information.
This scene is unpredictable because the ghost's behavior (feeding on scraps, belching, phasing through walls) subverts typical ghost tropes, but the chase itself is straightforward.
The scene evokes disgust and amusement, but not strong emotional investment; the ghost's escape is frustrating but not moving.
Dialogue is minimal and functional, with Stantz's 'Freeze, Potato-Face' being the standout line, but there's no banter or character-revealing conversation.
This scene is engaging because of the vivid, disgusting description of the ghost's feeding and the chase, but the lack of stakes or character depth reduces sustained interest.
The pacing of the scene contributes to its effectiveness because it moves quickly from discovery to action to escape, but the abrupt ending feels rushed.
Formatting is standard and clear, with proper scene headings, character cues, and action lines, though some descriptions are verbose.
The structure follows a classic horror-comedy beat: setup (Stantz finds ghost), confrontation (attack), and escape (ghost phases through wall), but the ending is abrupt and lacks a punchline.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the ghost escaping through a wall, creating a mild cliffhanger that makes the reader want to see if the team catches it, but the lack of stakes reduces urgency.
The script so far has built momentum with the team's formation and first successes, but this scene is a minor setback that doesn't significantly advance or hinder the main plot, so the reader is still engaged but not compelled.
All three lenses are solid — worth protecting as it stands.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
8/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
6/10 expected
What happens here obliges what comes next
7/10 core
Every beat and line earns its place
7/10 core
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
5/10 expected
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
7/10 core
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a ghost hunt in a hotel with a skeptical protagonist is well-established, but the specific image of a noxious vapor intelligently stalking Venkman adds a fresh, creepy twist.
The plot advances the ghost chase, but the scene is mostly a setup for the confrontation, with little new information or progression beyond Venkman's location.
The scene is original in its blend of mundane hotel setting with a supernatural vapor that has a personality (belching, intelligent movement), and Venkman's self-aware commentary adds authenticity.
Venkman's character is clearly defined through his sarcastic self-doubt and growing fear, but Stantz is reduced to a voice on the radio, limiting depth.
Venkman shows a shift from bored skepticism to genuine fear, but the change is minor and not sustained.
Venkman's internal goal is to maintain his cool, skeptical persona while confronting his own fear and the reality of the supernatural.
Venkman's external goal is to survive the vapor's approach and coordinate with Stantz to capture it.
The conflict is clear: Venkman vs. the vapor, with internal conflict from his fear and disbelief, but it's a straightforward chase without deeper layers.
The opposition is the vapor, which is intelligent, relentless, and visually grotesque, providing a strong physical threat.
The stakes are personal for Venkman (his safety) and professional (the Ghostbusters' credibility), but the scene doesn't raise broader stakes.
The scene moves the story forward by advancing the ghost hunt and putting Venkman in direct danger, but it's a small step in a larger sequence.
This scene is unpredictable because the vapor's intelligent behavior (hovering, looking at Venkman) subverts the typical mindless ghost trope, and Venkman's panic feels fresh.
The scene generates tension and a bit of humor, but the emotional impact is limited by the short duration and lack of a resolution.
The dialogue is sharp and in-character, especially Venkman's muttered complaints and the tense radio exchange, but it's sparse and functional.
This scene is engaging because it combines Venkman's relatable sarcasm with genuine supernatural threat, creating a tense and amusing chase.
The pacing of the scene contributes to its effectiveness because it starts slow with Venkman's muttering, then accelerates rapidly as the vapor appears and approaches, creating a tight rhythm.
Formatting is clean and professional, with clear action lines and proper use of parentheticals and scene headings.
The scene follows a classic horror setup: calm before the storm, threat appears, tension escalates, and ends on a cliffhanger. It's effective for its genre.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a cliffhanger with the vapor charging at Venkman, creating strong suspense that compels the reader to continue to see what happens.
The script has built momentum through the Ghostbusters' formation and previous encounters, and this scene raises the stakes for Venkman personally, keeping the reader invested in the team's success.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
6/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a ghost hunt with a critical rule ('don't cross the beams') is strong, blending sci-fi logic with comedic incompetence. The scene executes this well, though the concept is not entirely new for the genre.
The plot advances the ghost hunt and introduces a key rule, but the action is somewhat muddled by unclear spatial relationships and repetitive firing.
The scene is original in its comedic take on ghost hunting, with the 'don't cross the beams' rule being a fresh twist. The dialogue and actions feel authentic to the characters.
Venkman's cowardly authority, Stantz's enthusiasm, and Spengler's caution are all on display, but the scene relies on established traits rather than deepening them.
Venkman takes charge, but this is a temporary shift rather than a lasting change; no character arc is advanced.
Venkman wants to prove himself as a capable leader and avoid personal harm, driven by fear of failure and physical danger.
Capture the ghost (the vapor) in the banquet room.
The conflict is external (vs. the ghost) and internal (Venkman vs. his own fear/authority), but the internal conflict is underdeveloped.
The ghost is a strong opposition—fast, evasive, and dangerous—but the team's own incompetence is equally oppositional.
The stakes are moderate—failure means the ghost escapes, but the personal stakes for the characters are low.
The scene moves the story forward by showing the Ghostbusters' first real attempt to capture a ghost, but it ends without success, so progress is limited.
This scene is unpredictable because the ghost dodges and the team's incompetence leads to unexpected outcomes, though the 'don't cross the beams' reveal is a known beat.
The scene generates excitement and laughs, but the emotional stakes are low—no one is truly in danger beyond slime.
The dialogue is functional and humorous ('It slimed me!', 'Don't cross the beams'), but much of the scene is action-driven with minimal character interaction.
This scene is engaging because of the comedic tension, the iconic warning, and the visual chaos of the ghost hunt.
The pacing of the scene contributes to its effectiveness because it starts fast (Venkman's scream), slows for the warning, then builds to a chaotic climax. However, the middle section drags slightly with repeated firing.
Formatting is standard and readable, though some action lines are dense and could be broken up for clarity.
The scene follows a classic action-comedy structure: setup (enter room), complication (ghost dodges), revelation (don't cross beams), and climax (attempted capture). The structure is sound but the execution is slightly messy.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels continuation because the ghost escapes and the team's failure creates a need for resolution, plus the open question of what happens if the beams cross.
The script has built momentum through previous scenes (the library, Dana's case, the hotel), and this scene maintains that momentum with a fun but inconclusive action beat. The reader wants to see if they eventually succeed.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
6/10 expected
What happens here obliges what comes next
7/10 core
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 core
The feeling comes off the page
6/10 expected
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of trapping a ghost with proton streams and a foot-pedal trap is inventive and visually distinct, but the execution feels familiar from earlier scenes.
The plot advances the team's first successful capture, but the scene ends without a clear plan for the trap, creating a minor plot hole.
The trap mechanism is original, but the overall ghost-hunting sequence feels familiar from earlier scenes in the script.
Venkman's leadership and Stantz's enthusiasm are clear, but Spengler is mostly silent and the characters don't deepen beyond their established traits.
No character undergoes significant change; they remain in their established roles.
Venkman's internal goal is to prove his worth and validate his risk-taking by succeeding where academia failed him.
The external goal is to capture the ghost in the banquet room.
The conflict is external (vs. the ghost) and resolved, but there is no internal or interpersonal conflict to add depth.
The ghost offers moderate opposition—it dodges and blasts them—but is ultimately outmaneuvered, making the opposition feel manageable.
The stakes are moderate—failure would mean losing the ghost, but the scene lacks broader consequences.
The scene moves the story forward by achieving the first capture, but the lack of a next step slows momentum.
This scene is unpredictable because the trap's mechanism (foot pedal, pyramid of light) is visually surprising, and the anticlimactic ending subverts expectations.
The triumph and relief are genuine, but the emotional impact is undercut by the comedic tone and the unresolved trap issue.
The dialogue is functional and has a few comedic lines, but it lacks the sharp wit or memorable exchanges of the best scenes.
This scene is engaging because the visual spectacle of the trap and the team's coordinated effort create a satisfying payoff, but the flat ending reduces momentum.
The pacing of the scene contributes to its effectiveness because the build-up is tense and the capture is quick, but the final beat drags with the 'what now?' exchange.
Formatting is standard and clear, with proper scene headings and action lines, though some parentheticals could be trimmed.
The scene follows a classic action-comedy structure: setup (cornering the ghost), execution (herding and trapping), and a comedic denouement (the 'what now?' moment).
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a minor cliffhanger (what to do with the trap) and a comedic shrug, which mildly compels continuation but doesn't create strong urgency.
The script has built momentum through the team's expulsion, business startup, and previous failed attempts; this first success is a milestone, but the unresolved trap issue and lack of a clear next mission slightly slow the cumulative pull.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
5/10 expected
It leans on mood instead of something actually pushing it
4/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
5/10 core
It ends about where it started
6/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
The feeling comes off the page
6/10 expected
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of ghost hunters becoming media celebrities after a successful job is strong, and the scene executes it with a fun press conference and a musical number. However, the transition from a tense negotiation to a silly song feels conceptually disjointed.
The plot advances the Ghostbusters from a fledgling operation to a public success, setting up their newfound fame. The scene is straightforward: capture, payment, press, and celebration, but the plot is thin and relies on the montage to carry momentum.
The scene is original in its blend of a ghost capture with a press conference that turns into a musical number, and the street punk's Krypton question adds a fresh, absurdist touch.
Venkman's opportunistic salesmanship, Stantz's earnest enthusiasm, and Spengler's deadpan intellect are all on display. The street punk exchange with Spengler is a highlight, but the characters don't deepen or change here.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
No character undergoes significant change. They are the same people at the end as at the start, just more publicly validated.
Venkman's internal goal is to gain validation and credibility as a serious scientist/entrepreneur, driven by a need to prove his worth after being expelled from academia.
Venkman's external goal is to secure payment from the hotel manager and then manage the press to promote the Ghostbusters brand.
The conflict is low—the hotel manager's resistance is quickly overcome, and the press is friendly. The real tension is external (the crowd) but not adversarial.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
The opposition is minimal—the hotel manager briefly balks at the price, but the real opposition (the ghost) is already defeated. The press and crowd are supportive.
The stakes are low—the team has already succeeded, and the only risk is the hotel manager not paying, which is resolved quickly. The scene is a victory lap.
The scene moves the story forward by establishing the Ghostbusters' public success and setting up their media presence, which will likely lead to more calls and higher stakes.
This scene is unpredictable because the spontaneous singing of the Ghostbusters theme in front of the press is a surprising and comedic choice that subverts the expected serious press conference.
The scene generates excitement and amusement, but the emotional stakes are low. The team's triumph feels earned, but the goofy song undercuts any deeper emotional resonance.
The dialogue is snappy and character-specific, especially Venkman's 'We'll let it go again' threat and Spengler's Krypton line. The song lyrics are fun but feel a bit forced as a spontaneous moment.
This scene is engaging because it delivers a satisfying payoff to the capture setup, with fun character moments and a lively press conference that builds excitement.
The pacing of the scene contributes to its effectiveness because it moves quickly from the hotel lobby to the street to the montage, maintaining energy and momentum without dragging.
Formatting is clean and professional, with clear scene headings and action lines. The montage section is indicated properly with a V.O. announcer.
The scene follows a classic victory-to-celebration structure: capture, payment, press, and a montage. It works for a comedy but feels a bit episodic.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a montage and a front-page photo, creating a sense of closure for this victory. It doesn't leave a cliffhanger, but the montage hints at more jobs to come, making the reader curious about the team's next case.
The script has built momentum through the team's expulsion, startup, and first capture. This scene solidifies their success, and the unresolved threads (Dana's refrigerator entity, the growing ghost activity) keep the reader invested in what happens next.
Design and Read are broken — this reads as a rebuild before polish.
A montage compresses time. It isn’t built to turn on a single thread.
HoldingEvery beat and line earns its place.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
4/10 expected
No page-visible force — antagonist, deadline, need, threat, rule, condition — pushes the beats; the scene proceeds without anything making it happen.
It leans on mood instead of something actually pushing it
3/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
3/10 expected
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
4/10 light
The result doesn’t oblige what comes next
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 core
Every beat and line earns its place
5/10 core
The scene/sequence shifts location, time, POV, mode, or thread without making the causal/spatial/emotional/rhythmic relationship between adjacent chunks legible.
The parts sit side by side rather than building
6/10 core
The reader can follow what matters
3/10 light
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The unit completes its business and ends on a settled beat — no new live question, demand, or expectation is created for the next unit to inherit.
It settles at the exit rather than pulling on
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of showing the Ghostbusters' fame through news reports and a self-aware car that burns parking tickets is fresh and funny, but the scene is more of a montage than a fully realized concept.
The plot advances the timeline and shows the team's growing reputation, but there is no clear plot progression within the scene itself—it's a series of vignettes.
The car burning the parking ticket is a fresh and funny take on the 'car with a mind of its own' trope, but the news montage is familiar.
The Ghostbusters themselves are barely present; the focus is on media and a policeman. The car's personality is the most memorable character moment.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
No character changes occur in this scene.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
No clear internal goal for any protagonist in this scene.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
The Ghostbusters' external goal is to respond to calls and capture ghosts, but in this scene they are not actively pursuing a goal.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
There is no direct conflict in this scene; the policeman's minor confrontation with the car is the closest thing.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
The only opposition is the policeman writing a ticket, which is quickly neutralized by the car's antics.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
Stakes are low; the scene is more about atmosphere and humor than tension.
The scene moves the story forward by showing the team's growing fame and the public's awareness of ghosts, but it's a montage rather than a plot event.
This scene is unpredictable because the car's self-aware behavior (burning the ticket) is a surprising and funny twist.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
The scene is amusing but lacks emotional depth or stakes.
Dialogue is limited to news reporters and a policeman's internal reaction; it's functional but not distinctive.
This scene is engaging because of the humorous car gag and the rapid-fire news montage that shows the team's success.
The pacing of the scene contributes to its effectiveness because the quick cuts between news reports and the car gag keep the energy high, but the lack of a central conflict makes it feel like filler.
Formatting is standard and clear, with proper scene headings and action lines.
The scene is structured as a montage of news clips and a single gag with the car, which works for comedy but lacks a traditional scene structure.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a punchline (the ticket burning) and a cut to the next location, which is satisfying but doesn't create a strong cliffhanger.
The script so far has built momentum through the Ghostbusters' first capture and growing fame, and this scene maintains that momentum with a fun montage, but the lack of character development or plot advancement may slightly reduce urgency.
All three lenses are solid — worth protecting as it stands.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
6/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a romantic date intertwined with ancient Sumerian mythology is fresh and engaging, but the scene leans heavily on exposition of the lore rather than showing it in action.
The plot advances the romantic subplot and reveals key mythological info (Zuul, Gozer), but the scene is mostly setup for a future date, with little immediate plot progression.
The blend of romantic comedy with ancient Sumerian mythology is original, and the dialogue feels authentic to the characters. The 'stiff' and nasal spray bit is a fresh comedic beat.
Venkman's charming, persistent, and witty personality shines through, and Dana is shown as intelligent and skeptical but intrigued. The violinist is a minor jealous foil. Character work is solid but not deeply layered.
Dana softens slightly toward Venkman, agreeing to a date, but neither character undergoes significant change.
Venkman's internal goal is to connect with Dana romantically and prove his worth beyond his goofy exterior, driven by a desire for validation and affection.
Venkman's external goal is to get Dana to agree to a date so he can share information about Zuul and Gozer.
Mild conflict exists between Venkman and Dana (her skepticism, his persistence) and between Dana and the violinist (jealousy), but no high-stakes confrontation.
Opposition comes from Dana's initial reluctance and the jealous violinist, but it's mild and easily overcome.
Stakes are low here—personal and romantic, not life-threatening. The supernatural lore hints at larger stakes but doesn't raise them in this scene.
The scene moves the story forward by setting up the romantic subplot and revealing the name 'Zuul' and 'Gozer,' key to the larger plot.
This scene is somewhat predictable in its romantic-comedy beats, but the specific lore (Zuul, Gozer) adds a fresh twist.
The scene is light and charming, with a hint of romantic tension, but lacks deep emotional resonance or high stakes.
Dialogue is sharp, funny, and reveals character—Venkman's flirty persistence, Dana's dry wit, the violinist's jealousy. The exchange about the 'stiff' and nasal spray is a highlight. However, some exposition feels a bit on-the-nose.
This scene is engaging because of the witty dialogue and the chemistry between Venkman and Dana, plus the tease of supernatural lore.
The pacing of the scene is good—quick banter, a brief interruption from the violinist, and a smooth resolution. It doesn't drag.
Formatting is clean and professional, with clear scene headings and action lines. Minor issue: the transition from the radio studio to Lincoln Center could be clearer.
The scene follows a classic romantic-comedy structure: meet-cute (re-meet), banter, obstacle (violinist), and resolution (date set). It works well for its genre.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a date set, creating mild curiosity about what will happen, but no cliffhanger. It makes the reader want to see the date but doesn't compel immediate continuation.
The script has built momentum through ghost-catching action and the mystery of Dana's experience. This scene slows that momentum for character development, which is necessary but slightly reduces the pull to keep reading immediately.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
An orientation beat sets up the world. It isn’t expected to carry a big turn, so a lower Design read here is often the shape of the scene, not a fault.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 expected
No page-visible force — antagonist, deadline, need, threat, rule, condition — pushes the beats; the scene proceeds without anything making it happen.
It leans on mood instead of something actually pushing it
4/10 light
It restates its note rather than deepening it
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
It ends about where it started
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The result doesn’t oblige what comes next
7/10 core
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
4/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
3/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
5/10 expected
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a ghost-catching business being so successful they're booked a week out is a strong comedic premise, and the job interview with a supernatural-belief questionnaire is a fresh take on hiring. However, the scene doesn't deepen or challenge the concept.
The plot advances minimally: we see the team's busy schedule, meet Winston, and learn of an EPA visit. It's functional setup but lacks a clear plot turn or decision point.
The scene is moderately original in its blend of mundane office comedy with supernatural business, but the 'skeptical applicant' trope is familiar. The questionnaire is a fresh detail.
Janine is stressed and sharp, Venkman is dismissive and surly, Stantz is polite and focused on work, and Winston is pragmatic and witty. The characters are consistent but none undergo change or reveal new depth.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
No character changes; Winston's attitude is consistent from his first line to his last.
Winston's internal goal is to find steady work without compromising his skepticism; Venkman's is to maintain the business's success with minimal effort.
Winston's external goal is to get the job; Venkman's is to handle the workload and the EPA visit.
Low conflict: Janine and Venkman have a minor tension, and Winston's skepticism is mild. No central confrontation or obstacle.
Opposition is minimal: Janine's stress and the EPA visit are minor obstacles. No active antagonist.
Stakes are low: the team is busy but successful, and the EPA visit is a vague threat. No immediate danger or urgent decision.
The scene moves the story forward by introducing Winston and setting up the EPA subplot, but it's mostly status quo reinforcement.
The scene is somewhat predictable: the busy office and skeptical applicant are familiar beats. Winston's final line is a mild surprise but not a twist.
Minimal emotional impact; the scene is functional and comedic but doesn't aim for or achieve emotional resonance.
The dialogue is snappy and character-specific: Janine's phone spiel, Venkman's insult, Winston's dry retort. It serves comedy and exposition well, though some lines feel like setup for a punchline rather than natural conversation.
The scene is engaging because of the brisk pace, witty dialogue, and the intriguing introduction of Winston. However, it lacks a hook or cliffhanger.
The pacing is brisk and effective, moving from phone calls to introductions to the EPA mention without dragging. The rhythm suits the comedic tone.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
Formatting is standard and clean: proper scene headings, character cues, and parentheticals. No errors.
The scene follows a classic sitcom structure: setup (busy office), introduction of new character (Winston), complication (EPA visit), and a comedic button (Winston's final line). It's efficient but formulaic.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a setup (EPA visit, Winston's hiring) but no cliffhanger. It compels mild curiosity about the EPA and Winston's integration, but doesn't demand immediate continuation.
The script has built momentum through previous ghost-catching scenes and Dana's storyline. This scene maintains that momentum by introducing new threads (EPA, Winston) but doesn't escalate it.
All three lenses are solid — worth protecting as it stands.
HoldingEvery beat and line earns its place.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
6/10 expected
It turns — something is different by the end
7/10 core
What happens here obliges what comes next
8/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of an EPA agent investigating ghostbusting is a fresh, satirical take on bureaucracy clashing with the paranormal, but it's executed as a straightforward confrontation without deeper exploration of the environmental angle.
The plot advances the subplot of external pressure on the Ghostbusters, but the scene is largely a standoff with no resolution—Peck leaves without seeing the containment unit, and Venkman's defiance doesn't change the situation.
The EPA vs. ghostbusters premise is original and satirical, but the execution (bureaucrat vs. wisecracker) is a familiar trope. The dialogue feels authentic to Venkman's character.
Venkman's sarcastic, uncooperative personality is on full display, and Peck is a stiff, bureaucratic foil. However, neither character shows depth or change; Venkman's 'save a tree' line is funny but one-note.
Neither Venkman nor Peck undergoes any change; Venkman remains defiant, Peck leaves thwarted. The scene is static in terms of character development.
Venkman's internal goal is to maintain control and autonomy over his operation, driven by a need to avoid being undermined by authority figures he views as petty.
Venkman's external goal is to get rid of Peck without showing him the containment unit.
The conflict is clear: Peck wants access, Venkman refuses. It's a classic bureaucratic standoff with comedic undertones, but the stakes are low—Peck threatens a court order but leaves without escalating.
Peck is a competent but stiff opponent, representing institutional power. Venkman's sarcasm effectively neutralizes him, making the opposition feel weak.
The stakes are moderate: Peck could shut down the operation, but the threat is distant and Venkman's dismissal undercuts the tension.
The scene introduces a new antagonist and a potential future obstacle (court order), but doesn't move the main ghost-hunting plot forward—it's a setup for later conflict.
This scene is somewhat unpredictable because the EPA angle is unexpected, but the beat-by-beat outcome (Peck leaves empty-handed) is predictable once Venkman's attitude is established.
The scene generates mild amusement and frustration (at Peck's officiousness), but no deep emotional engagement—it's a comedic interlude rather than a dramatic moment.
The dialogue is sharp and comedic, with Venkman's 'magic word' bit and 'save a tree' zinger landing well. Peck's lines are functional but dry, serving as a straight man.
This scene is engaging because of Venkman's witty retorts and the novelty of an EPA agent confronting ghostbusters, but the lack of stakes or progression limits sustained interest.
The pacing is brisk, with quick back-and-forth dialogue that maintains energy. The scene doesn't overstay its welcome.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
Formatting is standard and clean, with clear character headings and action lines. No issues.
The scene follows a classic confrontation structure: introduction, request, refusal, escalation (threat of court order), and exit. It's effective for a comedy scene but lacks a twist or reversal.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Peck threatening a court order, creating a mild cliffhanger about future legal trouble, but the lack of immediate action reduces urgency.
The script has built momentum through ghost-catching and Dana's subplot; this scene introduces a new obstacle but doesn't resolve any open threads, so the cumulative pull is moderate.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
An orientation beat sets up the world. It isn’t expected to carry a big turn, so a lower Design read here is often the shape of the scene, not a fault.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 expected
No page-visible force — antagonist, deadline, need, threat, rule, condition — pushes the beats; the scene proceeds without anything making it happen.
It leans on mood instead of something actually pushing it
4/10 light
It restates its note rather than deepening it
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
It ends about where it started
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
What happens here obliges what comes next
7/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
4/10 light
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
6/10 expected
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a ghost storage facility reaching capacity and hinting at a massive supernatural event is strong, and the Twinkie metaphor is inventive and memorable.
The plot advances the overarching threat but does so through dialogue rather than action, making it feel like a pause in the narrative.
The Twinkie metaphor is highly original, and the storage facility as a limbo for ghosts is a fresh take on containment. Dialogue is authentic to the characters.
Spengler's analytical deadpan and Winston's grounded concern are well-drawn, but Venkman's entrance is underutilized—he merely echoes Stantz's question, adding little.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
No character undergoes significant change; they remain in their established roles.
Venkman's internal goal is to maintain control and avoid confronting the scale of the threat, driven by fear of failure and the unknown.
The team's external goal is to monitor and maintain the storage facility while assessing the rising PKE levels.
Conflict is low—internal worry and a vague external threat, but no direct opposition or confrontation.
The opposition is abstract—the accumulating ghosts and the looming PKE surge—rather than a tangible antagonist, reducing tension.
The stakes are high—potential fourfold crossover or dimensional rip—but the scene's static nature reduces urgency.
The scene moves the story forward by raising the stakes and hinting at a coming catastrophe, but it is primarily informational.
This scene is unpredictable because the Twinkie analogy is a fresh, absurd way to convey serious stakes, and the storage facility's appearance is eerie and unexpected.
The scene generates mild unease and concern through Spengler's data, but the humor undercuts any deep emotional resonance.
The dialogue is functional and has a few good lines (the Twinkie exchange), but much of it is technical exposition that lacks the usual snappy banter.
This scene is engaging because the Twinkie metaphor is funny yet ominous, and the glimpse inside the storage facility is visually intriguing.
The pacing of the scene contributes to its effectiveness because it slows down after action-heavy sequences, allowing the audience to absorb the growing threat, but it risks feeling sluggish.
Formatting is clean and professional, with clear action lines and proper scene headings. The use of a monitor zoom is effective.
The scene follows a classic 'calm before the storm' structure: exposition of a growing problem, then a visual reveal of the storage facility to underscore the stakes.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a grim visual of the storage facility, creating a sense of dread and unanswered questions about what 'something big' means, compelling the reader to see how the team responds.
The script has built momentum through previous ghostbusting jobs and the EPA conflict; this scene deepens the apocalyptic foreshadowing, keeping the reader invested in the escalating crisis.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
HoldingThe exit pulls you into the next one.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
7/10 core
A real force keeps it pushing forward
5/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
6/10 core
The plot advances because something external happens, but the unit's own thread doesn't change state — the turn was imported, not made.
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
6/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 core
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a stone gargoyle coming to life and a chair physically attacking Dana is a fresh, inventive take on haunted apartment tropes, blending body horror with domestic invasion. The weakness is that the Terror Dog's awakening is somewhat telegraphed by the earlier fridge scene, reducing surprise.
The plot advances the central threat: the entity is now actively attacking Dana in her home, raising stakes and moving toward a confrontation. The weakness is that Louis's party interruption feels like a detour that dilutes the building tension.
The scene is original in its use of a chair as an attacking entity and the transformation of a kitchen into a fiery portal. The Terror Dog awakening is a familiar trope but executed with strong visual detail. The dialogue is authentic to the characters.
Dana is shown as vulnerable and exhausted, making her victimization effective. Louis's brief appearance reinforces his oblivious comic relief but doesn't deepen his character. The Terror Dog is menacing but lacks distinct personality beyond its physical threat.
Dana does not change in this scene; she remains a victim. The Terror Dog's awakening is a change in the antagonist's state, but no character arc is advanced.
Dana's internal goal is to feel safe and in control of her life after her earlier traumatic experience, but her exhaustion and fear show she is struggling. The scene denies this goal entirely.
Out of step with your script — external goal holds up in your other scenes.
Dana's external goal is to relax and unwind after her dance class, but she is attacked and dragged into the kitchen. She has no active external goal in the scene.
The conflict is clear: Dana vs. the supernatural entity, with her physical struggle against the chair and the Terror Dog. The weakness is that the conflict is one-sided (Dana has no agency or counteraction), reducing dramatic tension.
The opposition is the Terror Dog and the supernatural force, which is overwhelming and inescapable. Dana has no means to fight back, making the opposition strong but the conflict one-sided.
The stakes are high: Dana's life is in immediate danger, and the entity is now actively attacking her in her home. The weakness is that the stakes feel localized to Dana, without broader implications yet.
The scene moves the story forward by escalating the supernatural threat directly to the protagonist, setting up the next confrontation. The weakness is that it doesn't introduce new information or plot twists beyond the expected attack.
This scene is unpredictable because the attack comes from the chair itself, not just the kitchen door, and the Terror Dog's stone statue coming to life is a surprising escalation. The weakness is that the overall trajectory (Dana being attacked) is somewhat expected given the earlier setup.
The scene generates strong fear and dread through visceral imagery (claws ripping through chair, fiery kitchen). The weakness is that the emotional impact is somewhat blunted by the preceding Louis scene, which resets the tone.
The dialogue is minimal but functional: Dana's phone call with her mother feels natural and grounds her character, while Louis's party chatter provides comic relief. The weakness is that the dialogue doesn't reveal new character depth or advance the plot beyond setup.
This scene is engaging because it delivers a visceral, unexpected attack on the protagonist, with strong visual horror (claws, sliding chair, fiery kitchen). The cliffhanger of Dana being dragged into the kitchen compels the reader to continue.
The pacing of the scene contributes to its effectiveness because it starts slow and quiet, then accelerates rapidly with the phone ring, the claws, and the sliding chair, creating a crescendo of horror. The Louis scene before it slows the momentum.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
Formatting is standard and clear, with proper scene headings, action lines, and character cues. The use of bold for 'TERROR DOG' and 'ITS HEAD' is effective for emphasis. No formatting errors.
The scene follows a classic horror structure: calm before the storm (Dana relaxing), a sudden disruption (phone call), a false sense of safety, then a shocking attack (claws, sliding chair, fiery kitchen). The weakness is the tonal interruption of Louis's party scene, which breaks the building tension.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene strongly compels the reader to continue because it ends on a cliffhanger with Dana being dragged into a fiery kitchen, leaving her fate unknown and the threat escalated.
Given the whole script, the reader is pulled to continue because the Ghostbusters' main client is now in direct danger, the supernatural threat is escalating citywide, and the storage facility is becoming unstable. This scene adds personal stakes to the larger plot.
All three lenses are solid — worth protecting as it stands.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
8/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
8/10 core
What happens here obliges what comes next
6/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 expected
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a Terror Dog bursting through a door at a nerdy party is a fresh and effective blend of horror and comedy. The idea of a mundane party being interrupted by a supernatural creature is strong, but the execution here is straightforward chase without much twist.
The plot advances the Terror Dog's rampage and Louis's escape, but it's a simple chase sequence that doesn't introduce new information or complications beyond the creature's presence.
The scene is original in its blend of a mundane party with a monster attack, and the bums' commentary is a fresh take on bystander reactions. The Terror Dog itself is a unique creature design.
Louis is consistent as a neurotic, detail-obsessed accountant, and his panic is in character. The bums provide a comedic contrast, but the other party guests are barely sketched. The Terror Dog is a menacing force but not a character.
Louis does not change; he remains a panicked victim. The bums remain unchanged observers. No character arc is advanced.
Louis's internal goal is to survive and escape the Terror Dog, driven by fear. He has no deeper need or desire in this scene.
Louis's external goal is to run away from the Terror Dog and find safety.
The conflict is clear: Louis vs. the Terror Dog, a life-or-death chase. The opposition is physically overwhelming, creating high tension.
The opposition is the Terror Dog, a powerful, relentless supernatural creature. Louis has no means to fight back, making the opposition strong and the odds heavily against him.
The stakes are life-or-death for Louis, and the Terror Dog's rampage threatens the city, but the comedic tone slightly lowers the perceived stakes.
The scene moves the story forward by escalating the Terror Dog threat and showing it loose in the city, but it's a transitional chase without major plot revelations.
This scene is somewhat unpredictable because the Terror Dog's appearance at a party is surprising, and the bums' deadpan reactions are unexpected. However, the chase itself is a predictable horror trope.
The scene generates fear for Louis and amusement from the bums' reactions, but the emotional impact is somewhat diluted by the comedic tone.
Louis's dialogue about party expenses and generic drugs is perfectly in character and funny. The bums' dialogue is a highlight, especially the 'fighting Spaniel' line. However, much of the scene relies on action rather than dialogue.
This scene is engaging because of the sudden monster attack, Louis's frantic escape, and the humorous contrast with the bums. The pacing keeps the reader turning pages.
The pacing of the scene contributes to its effectiveness because it starts with a slow, mundane party, then accelerates rapidly with the Terror Dog's entrance, maintaining high energy through the chase and ending with a comedic slowdown with the bums.
Formatting is standard and clear. Scene headings, character cues, and action lines are properly formatted. The use of all-caps for character names and sound effects is consistent.
The structure follows a classic chase sequence: setup (party), inciting incident (Terror Dog bursts in), rising action (chase through hall, street, park), and a comedic beat (bums' commentary). It's effective for the genre.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the Terror Dog chasing Louis into the park, leaving his fate uncertain and creating a cliffhanger that compels the reader to continue to see if he escapes.
The script has built momentum through the Ghostbusters' successful capture and the escalating Dana/Terror Dog plot. This scene adds to the chaos and raises the stakes for Louis, maintaining strong cumulative momentum.
All three lenses are solid — worth protecting as it stands.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
8/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
8/10 expected
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 light
It defeats anticipation fairly
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 expected
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a possessed accountant speaking demonic prophecies to a horse is fresh and funny, but the scene relies heavily on the established monster and possession trope without adding new mechanics.
The plot advances the possession storyline and sets up Louis as the Keymaster, but the transition from chase to possession is abrupt and lacks a clear moment of transformation.
The scene is original in its blend of horror and comedy, especially the possessed Louis speaking to a horse. The dialogue is authentic to the film's voice.
Louis's character shifts from terrified to possessed, showing a clear change, but the possessed version is one-note (grandiose demonic speech) and the Coachman is a flat comic foil.
Louis changes from terrified human to possessed demonic servant, a major transformation, but the change happens off-screen between scenes 133 and 135, reducing its impact.
Louis's internal goal is survival and escape from the Terror Dog, driven by primal fear.
Louis's external goal is to find safety inside the restaurant, then to confront the Terror Dog.
The conflict is clear: Louis vs. the Terror Dog, then Louis (possessed) vs. the Coachman. The stakes are life-and-death, but the possession resolves the physical conflict too quickly.
The opposition is the Terror Dog, a powerful supernatural entity. The Coachman provides minor opposition, but the dog is the primary threat.
The stakes are high: Louis's life and the impending apocalypse, but the scene's comedic tone slightly lowers the perceived threat.
The scene moves the story forward by establishing Louis as the Keymaster and showing the Terror Dog's possession, directly advancing the Gozer plot.
This scene is unpredictable because Louis's possession and his subsequent demonic speech to a horse subvert expectations of a typical monster attack.
The scene generates fear for Louis and then unease at his possession, but the comedy undercuts sustained emotional weight.
The dialogue is sharp and funny, especially Louis's possessed lines and the Coachman's deadpan retort, but the muffled 'Help! Help!' through glass is generic.
This scene is engaging because it combines a desperate chase with absurd humor, keeping the reader invested in Louis's fate and the bizarre possession.
The pacing of the scene contributes to its effectiveness because it builds tension quickly (Louis running, pounding on glass) and then releases it into absurd comedy (the possessed dialogue), creating a satisfying rhythm.
Formatting is clean and professional, with clear scene headings and action lines. The use of 'CONT'D' and character cues is standard.
The scene follows a classic horror chase structure: pursuit, failed escape, confrontation, and transformation. The pacing is effective, but the possession happens too quickly without a clear visual or auditory cue.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with Louis possessed and loping off, creating a strong cliffhanger about what he will do next, compelling the reader to continue.
The script has built momentum through the Ghostbusters' capture of ghosts, Dana's possession, and now Louis's transformation. The Gozer plot is escalating, and the reader is pulled forward by the impending apocalypse.
All three lenses are solid — worth protecting as it stands.
HoldingIt commits to one clear thing and holds it.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
8/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
8/10 core
The situation deepens as it goes
8/10 core
It turns — something is different by the end
7/10 core
What happens here obliges what comes next
7/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 light
It defeats anticipation fairly
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 core
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a possessed woman speaking as a demonic gatekeeper while her love interest tries to flirt is fresh and memorable, but the execution leans heavily on familiar possession tropes.
The plot advances the possession storyline and sets up Gozer's arrival, but the scene is more about character reaction than plot mechanics.
The scene is original in its comedic take on possession, with Venkman's flirtation being a fresh angle, but the possession itself is familiar.
Venkman's character is consistent—charming, clueless, and self-serving—but Dana's transformation is sudden and lacks buildup within the scene.
Dana changes from victim to vessel, but Venkman remains unchanged; the transformation is external rather than internal.
Venkman's internal goal is to connect with Dana romantically, driven by his desire for affection and validation.
Venkman's external goal is to get Dana out of the apartment and away from the supernatural threat.
The conflict is clear—Venkman wants to help/rescue Dana, but she is possessed and opposes him—though it's undercut by comedy.
The opposition is strong—Dana as Zuul is a powerful supernatural entity—but Venkman's lack of fear weakens the tension.
The stakes are high—Dana's soul and the world are at risk—but the comedic tone reduces perceived danger.
The scene moves the story forward by revealing Dana's possession and the imminent arrival of Gozer.
This scene is unpredictable because Dana's possession and Venkman's romantic pursuit create an absurd, offbeat dynamic.
The scene generates unease and amusement, but the emotional stakes are diluted by Venkman's flippant attitude.
The dialogue is sharp and funny, especially Venkman's 'Should we make some dip?' line, but Dana's lines are repetitive and expositional.
This scene is engaging because of the unexpected blend of horror and humor, and Venkman's cluelessness creates tension.
The pacing of the scene contributes to its effectiveness because it moves quickly from discovery to confrontation to a surprising turn, maintaining energy.
Formatting is standard and clear, with proper scene headings and action lines, though some parentheticals could be cleaner.
The scene follows a classic three-beat structure: arrival and discovery, confrontation, and a turn toward the bedroom, but the turn feels abrupt.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a cliffhanger with Venkman and Dana heading to the bedroom, leaving the reader wondering what will happen next, compelling continuation.
The script has built momentum through multiple possession and ghost encounters, and this scene raises the stakes for the climax, keeping the reader invested.
No lens is broken, but Execution and Read are soft — this reads as a polish pass.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
7/10 core
A real force keeps it pushing forward
6/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
The situation deepens as it goes
7/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
6/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
Every beat and line earns its place
5/10 expected
The scene/sequence shifts location, time, POV, mode, or thread without making the causal/spatial/emotional/rhythmic relationship between adjacent chunks legible.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
5/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
6/10 expected
It defeats anticipation fairly
6/10 core
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a possessed woman seducing the hero while he tries to exorcise her with humor is fresh and subverts typical horror tropes. However, the scene's concept is somewhat undermined by the abrupt shift to a separate ghostbusting job, which feels like a detour.
The plot advances Venkman's confrontation with Zuul and the looming Gozer threat, but the scene's structure is disrupted by the Fort Detmerring sequence, which introduces a new, unrelated job and slows the main plot's momentum.
The possessed seduction scene is original and authentic, but the Fort setup is a standard ghost-hunting premise.
Venkman's character shines through his comedic, clinical handling of Dana's possession, showing his resourcefulness and charm. Stantz and Winston's exchange in the Ectomobile deepens their personalities, but the Fort scene lacks character development for the new rangers.
Venkman shows no significant change, remaining the same sarcastic, resourceful character. Stantz and Winston's conversation hints at a growing awareness of apocalyptic stakes, but no concrete change occurs.
Venkman's internal goal is to maintain control and humor in the face of the supernatural, driven by a fear of vulnerability and a desire to protect Dana.
Venkman's external goal is to exorcise Zuul from Dana and stop the possession.
The primary conflict is Venkman vs. Zuul's possession of Dana, with a secondary conflict of the Ghostbusters' growing workload and existential dread. The Fort scene introduces a new external conflict but lacks immediate stakes.
Zuul's possession of Dana provides strong opposition, but the Fort's ghost is a vague, off-screen threat with no immediate opposition.
The stakes are high for Dana's safety and the impending Gozer threat, but the Fort scene lowers tension by introducing a routine ghostbusting job.
The scene advances the main plot by showing Dana's possession worsening and the Ghostbusters responding to a new call, but the Fort sequence feels like a side quest that delays the central narrative.
Venkman's refusal to sleep with a possessed woman is unpredictable and refreshing, but the Fort job feels like a predictable 'next call' trope.
The bedroom scene generates unease and humor, but the emotional impact is diluted by the shift to the Fort, which feels like a procedural setup rather than an emotional beat.
The dialogue is sharp and witty, especially Venkman's lines ('I make it a rule never to sleep with possessed people') and Stantz's distracted responses. However, the Fort Detmerring dialogue is functional but less memorable.
The bedroom scene is highly engaging due to its unique blend of horror and comedy, but the Fort sequence loses engagement with exposition-heavy dialogue.
Pacing is uneven: the bedroom scene is tight and rhythmic, but the Ectomobile conversation slows down, and the Fort scene feels like a reset.
Formatting is standard and clear, with proper scene headings and action lines. Minor issue: the transition from 138 to 139 is abrupt but acceptable.
The scene's structure is episodic, moving from a tense bedroom exorcism to a road-trip conversation to a new job setup, which undermines narrative cohesion.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a new job setup at the Fort, creating mild curiosity but no strong cliffhanger. The unresolved Dana possession is the main hook.
The script maintains momentum through the Dana/Zuul arc and the growing apocalyptic hints, but the Fort detour slightly dampens the cumulative pull.
All three lenses are solid — worth protecting as it stands.
HoldingWhat happens here obliges what comes next.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
6/10 core
A real force keeps it pushing forward
5/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
6/10 expected
It turns — something is different by the end
8/10 core
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a possessed man spouting pseudo-mythological nonsense while being interrogated by a scientist is fresh and funny, but the exposition is a bit dense.
The plot advances the Keymaster/Gatekeeper storyline and sets up the climax, but the scene is more about character and setup than plot movement.
The scene is original in its blend of cosmic horror and mundane comedy, with Louis's coffee-eating and Spengler's 'nice clavicles' being fresh moments.
Louis's possessed persona is entertaining, Spengler's deadpan scientific curiosity shines, and Janine's psychic worry adds depth; Venkman's phone call reinforces his concern for Dana.
Spengler shows a rare moment of vulnerability with Janine, but no major character change occurs.
Spengler's internal goal is to understand the supernatural threat while maintaining his scientific detachment, but he also seeks human connection (with Janine).
Spengler's external goal is to keep Louis (Vinz Clortho) contained and prevent him from meeting Dana.
The conflict is low-key: Spengler must keep Louis contained while Venkman deals with Dana; the tension is more about impending doom than direct confrontation.
The opposition is minimal; Louis is cooperative in his possessed state, and the real opposition (the apocalypse) is off-screen.
The stakes are high (apocalypse if Keymaster and Gatekeeper meet), but the scene's comedic tone undercuts the urgency.
The scene reveals the Keymaster's identity and sets up the need to keep him from Dana, moving the plot toward the climax.
This scene is unpredictable because Louis's rambling is absurd and the romantic moment with Spengler is unexpected.
The scene has a mix of humor and mild dread, but the emotional impact is muted by the comedic tone.
The dialogue is witty and character-specific, especially Louis's rambling and Spengler's 'nice clavicles' line, but some of Louis's exposition feels overlong.
This scene is engaging because of the contrast between Louis's bizarre behavior and the mundane setting, plus the romantic tension between Spengler and Janine.
The pacing of the scene contributes to its effectiveness because it alternates between fast, weird dialogue and slower, tender moments, but Louis's monologue drags slightly.
Formatting is standard and clear, with proper scene headings and action lines, though some parentheticals are missing.
The scene has a clear three-part structure: interrogation, phone call, romantic moment, but the transition to the romantic beat feels abrupt.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a phone call that sets up the Keymaster/Gatekeeper threat, making the reader want to see how the team prevents their meeting.
The script has built strong momentum with the Dana possession and Louis's transformation, and this scene deepens the threat while adding character warmth, keeping the reader invested.
No lens is broken, but Read is soft — this reads as a polish pass.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
5/10 expected
The scene delivers information or understanding but no one is forced to decide or act on it.
The result doesn’t oblige what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
7/10 core
The reader can follow what matters
5/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
5/10 expected
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
6/10 core
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a ghost seducing a sleeping Ghostbuster is fresh and subversive, mixing horror with unexpected erotic comedy. However, it feels somewhat disconnected from the main Gozer plot, which limits its integration.
The scene advances Stantz's personal encounter with the supernatural but does little to move the main plot forward. It's a character beat that could be cut without affecting the central story.
The scene is original in its blend of horror and erotic comedy, with a ghost performing a sexual act on a sleeping protagonist. This is a fresh take on ghost encounters, though it risks being gratuitous.
Stantz is shown as vulnerable and curious, adding depth to his usually enthusiastic persona. The ghost is a silent, menacing presence, but lacks dialogue or clear motivation.
Stantz undergoes a subtle shift from fear to submission, but no lasting change is established. He remains essentially the same character afterward.
Stantz's internal goal is to rest and escape the exhaustion of ghostbusting, but his deeper need for connection or curiosity about the supernatural leads him to submit to the ghost's advances.
Out of step with your script — external goal holds up in your other scenes.
Stantz's external goal is to sleep and recover, but he is interrupted by the ghost and passively experiences the encounter.
The conflict is internal for Stantz—fear versus curiosity/pleasure—and external with the ghost. It's low-stakes compared to the main plot, but effectively tense.
The opposition is the ghost, which is a silent, intangible force that Stantz cannot fight or resist. The lack of active opposition makes the conflict one-sided.
The stakes are personal for Stantz (his safety/autonomy) but low for the overall narrative. The ghost is a minor threat compared to Gozer.
Out of step with your script — story forward holds up in your other scenes.
The scene does not advance the main plot of Gozer's arrival or the Ghostbusters' mission. It's a standalone character moment that could be removed without affecting the story.
This scene is unpredictable because the ghost's actions shift from threatening to sexually suggestive, subverting the typical horror trope of a ghostly attack.
The scene evokes a mix of unease and amusement, but the emotional impact is muted by its brevity and the lack of consequence for Stantz.
Out of step with your script — dialogue holds up in your other scenes.
There is no dialogue in the scene, which is a bold choice that relies entirely on visual and physical storytelling. This works for the eerie tone but limits character interaction.
This scene is engaging because of its unexpected and taboo nature—a ghost seducing a sleeping man—which creates a mix of shock, humor, and curiosity.
The pacing of the scene contributes to its effectiveness because it starts slow and quiet, builds tension as the mist appears and descends, then delivers a sudden, surprising climax. The rhythm supports the eerie mood.
Formatting is standard and clear, with proper scene headings, action lines, and character cues. The use of 'MIST' as a character heading is unconventional but works for the ghostly entity.
The scene follows a classic horror structure: setup (Stantz sleeping), inciting incident (mist appears), rising tension (ghost descends), climax (face-to-face encounter), and a surprising resolution (sexual act). It fits the horror-comedy genre.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a note of submission and pleasure, which is a cliffhanger of sorts—what happens next to Stantz?—but it feels self-contained and doesn't create a strong pull to the next scene.
Given the whole script, the main plot (Gozer, Dana, Louis) has strong momentum, but this scene is a detour that slows it. The reader may be curious about Stantz's fate but more eager to return to the central conflict.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
7/10 core
A real force keeps it pushing forward
5/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
6/10 core
The plot advances because something external happens, but the unit's own thread doesn't change state — the turn was imported, not made.
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
5/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
There’s avoidable waste on the page
5/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of an EPA agent shutting down a ghost containment grid as a power play is a fresh, ironic twist on bureaucratic overreach, blending real-world regulation with supernatural consequences.
The plot advances clearly: Peck's legal assault forces a confrontation, Venkman's attempt to reason fails, and the shutdown triggers the explosion, setting up the next crisis.
The scene is original in its use of an EPA agent as antagonist and the ironic 'cease and desist' leading to a ghost explosion, though the 'authority figure ignores warnings' trope is familiar.
Characters are consistent: Peck's smug authoritarianism, Venkman's quick wit and desperation, Spengler's calm technical concern, Janine's feisty resistance, and Louis's silent observation all shine, though Winston is absent.
Venkman shifts from sarcastic to genuinely worried, but no deep change occurs; Peck remains obstinate.
Venkman's internal goal is to maintain control and credibility against authority, driven by fear of losing his operation and pride.
Venkman's external goal is to stop Peck from shutting down the grid.
Conflict is high: Peck vs. Venkman, Janine vs. Peck, and the physical threat of the shutdown create layered tension.
Peck is a strong opposition: armed with legal power, backed by police, and unyielding, making Venkman's struggle feel real.
Stakes are life-and-death: the ghost containment failure threatens the city, and the team's credibility is on the line.
The scene moves the story forward by triggering the containment breach, directly leading to the climax.
This scene is unpredictable because the audience expects a resolution but instead gets a catastrophic failure, subverting the typical hero-wins trope.
The scene generates anxiety and frustration as the audience knows the danger, but the emotional payoff is slightly muted by the quick explosion.
Dialogue is sharp and character-specific: Peck's 'pencil-neck' insult, Venkman's 'Don't be a jerk!', and Janine's 'This is just like Poland' land well, though some lines feel expository.
This scene is engaging because the tension builds from a legal standoff to a physical threat, with witty dialogue and a clear sense of impending doom.
The pacing of the scene contributes to its effectiveness because it starts with brisk entry, slows for argument, then accelerates to the explosion, maintaining urgency.
Formatting is professional with clear scene headings, character cues, and action lines, though some parentheticals are missing and action blocks could be tighter.
The scene follows a classic three-beat structure: confrontation (Peck enters), escalation (argument, orders), and climax (shutdown triggers explosion), fitting the action-comedy genre.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends on a cliffhanger with the storage facility exploding, compelling the reader to see the aftermath and how the team responds.
Given the accumulated momentum of Dana's possession, Louis's transformation, and now the containment breach, the script pulls the reader strongly forward toward the climax.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
An aftermath beat lands the cost of what just happened rather than driving new action.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 core
No page-visible force — antagonist, deadline, need, threat, rule, condition — pushes the beats; the scene proceeds without anything making it happen.
It leans on mood instead of something actually pushing it
4/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
5/10 expected
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 core
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
5/10 expected
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a ghost containment facility exploding and creating a supernatural geyser is strong and visually compelling. However, the scene leans heavily on this spectacle without fully exploring its implications, and the Keymaster thread feels tacked on rather than integrated.
The plot advances the central crisis (the explosion) and introduces the Keymaster's departure, but the transition is abrupt. The scene juggles multiple plot threads (the explosion, the search for Louis, the arrest) without giving any of them full attention, making the plot feel slightly scattered.
The scene is original in its combination of a supernatural disaster with bureaucratic red tape. The image of a ghost containment facility exploding into a geyser is fresh. However, the dialogue and character interactions are familiar from earlier scenes.
Venkman, Spengler, and Stantz are consistent with their established personalities—Venkman is sarcastic and quick to blame, Spengler is analytical and then furious, Stantz is bewildered. However, Louis's character shift from oblivious to zombie-like is too sudden and lacks buildup, and Janine is reduced to a one-liner.
Spengler shows a rare flash of anger, which is a minor change, but no character undergoes a significant transformation. Louis's departure is a plot point, not a character change.
Venkman's internal goal is to maintain control and protect his team, but he is frustrated by external forces (Peck, the police). His need is to be taken seriously as a professional, but his sarcasm undermines him.
Venkman's external goal is to find the Keymaster (Louis) and stop him from reaching Dana, but he is immediately arrested, thwarting this goal.
Conflict is high: the explosion creates immediate physical danger, and the argument between Venkman/Spengler and Peck escalates to threats of arrest. However, the conflict with Peck feels repetitive (he's been obstructive before) and the Keymaster conflict is introduced too late to have weight.
The opposition is strong: Peck and the police actively work against the Ghostbusters, preventing them from pursuing the Keymaster. However, the opposition is one-dimensional—Peck is a bureaucratic villain without nuance.
The stakes are high: the explosion threatens the city, and the Keymaster is now loose, heading toward Dana. However, the scene doesn't fully communicate the scale of the threat—the geyser is described but its danger is not made visceral.
The scene moves the story forward by triggering the main crisis (the explosion) and setting up the Keymaster's journey to Dana. However, the forward momentum is slightly stalled by the repetitive argument with Peck.
This scene is unpredictable because the explosion is a major turning point, and Louis's sudden departure adds a new layer of mystery. However, the argument with Peck feels predictable, as he has been a consistent antagonist.
The explosion and its aftermath generate a sense of panic and urgency, but the emotional impact is muted by the comedic tone and the rapid shift to the Keymaster subplot. The scene doesn't linger on the danger or the characters' fear.
The dialogue has some sharp moments (Spengler's threat to rip out Peck's septum, Janine's 'Going Out Of Business' quip) but also includes clunky exposition ('Where's the Keymaster?') and repetitive bureaucratic back-and-forth that slows the pace.
This scene is engaging because of the visual spectacle of the explosion and the immediate chaos that follows. The rapid-fire dialogue and the threat of arrest keep the tension high, though the Keymaster subplot briefly derails the momentum.
The pacing of the scene is fast and chaotic, matching the disaster. The explosion is immediate, followed by quick cuts to reactions and dialogue. However, the scene slows down during the bureaucratic questioning (the Guy in Suit, the Fire Captain) and the repetitive argument with Peck.
Formatting is standard and clear, with proper scene headings and character cues. The action lines are descriptive but occasionally overwritten (e.g., 'a powerful geyser of irridescent energy'). The use of parentheticals is minimal and effective.
The scene follows a classic disaster structure: cause (explosion), effect (geyser), immediate reaction (characters running, officials questioning), and a new complication (Louis's departure). However, the transition from the explosion to the Keymaster subplot is abrupt, and the scene ends on a cliffhanger (arrest) that feels slightly forced.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a cliffhanger (the arrest) and an unresolved question (where is Louis going?), which strongly compels the reader to continue. The explosion also creates a sense of urgency that demands resolution.
The script has built strong momentum through the escalating paranormal activity and the personal stakes for Venkman (Dana's possession). This scene raises the stakes further with the explosion and the Keymaster's departure, making the reader eager to see how the team will escape arrest and stop the apocalypse.
Design is broken — a load-bearing lens isn’t doing its job yet.
A montage compresses time. It isn’t built to turn on a single thread.
HoldingEvery beat and line earns its place.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
For most of the scene the POV observes activity with no visible intention, scene question, threat, pursuit, or decision organizing what the reader is meant to track.
It isn’t clearly about one thing yet
5/10 expected
It leans on mood instead of something actually pushing it
3/10 expected
Beats restate the same note; the reader’s experience does not change across the scene.
It restates its note rather than deepening it
3/10 expected
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
4/10 light
The result doesn’t oblige what comes next
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 core
Every beat and line earns its place
5/10 expected
The parts sit side by side rather than building
6/10 core
The reader can follow what matters
5/10 expected
It plays close to the version we’ve seen before
5/10 expected
The beats can be called before they land
4/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
5/10 expected
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a city-wide paranormal outbreak is strong, but the execution here is a series of gags rather than a unified idea, diluting its impact.
The plot barely advances; it's a collection of set pieces showing chaos without a clear narrative progression or connection to the main story.
The scene is original in its specific gags (e.g., the onion-headed vapor, the invisible molester), but the concept of a city-wide ghost outbreak is familiar from the genre.
Out of step with your script — characters holds up in your other scenes.
No main characters appear; the vignettes feature anonymous victims, which limits emotional investment and character development.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
No character changes occur; the scene is purely situational with no arc for any individual.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
No protagonist is present; the scene lacks an internal goal.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
No protagonist is present; the scene lacks an external goal.
Conflict is present (humans vs. ghosts) but impersonal and fleeting, with no sustained tension or stakes for known characters.
Opposition is the supernatural entities, but they are faceless and lack personality, reducing the sense of a direct antagonist.
Stakes are high for the city but abstract; without personal stakes for known characters, the tension feels diffuse.
Out of step with your script — story forward holds up in your other scenes.
The scene shows the escalation of paranormal activity but does not move the main plot forward; it's a montage of effects without cause or consequence for the protagonists.
This scene is unpredictable because each vignette introduces a new, bizarre supernatural event (e.g., a possessed hot dog cart, a skeletal cab driver) without warning.
Emotional impact is low due to the lack of character connection; the humor undercuts any horror, leaving a sense of amusement rather than fear.
Dialogue is minimal and functional, mostly used for quick gags (e.g., the businessman's line), but lacks depth or character voice.
This scene is engaging because of its rapid-fire, absurd gags that keep the reader amused and curious about what bizarre event will happen next.
The pacing of the scene contributes to its effectiveness because the quick cuts between vignettes create a sense of escalating chaos and keep the energy high.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
Formatting is standard and clear, with proper scene headings and action lines, though some descriptions are brief.
The structure is a montage of short, disconnected vignettes, which works for a comedy-horror montage but lacks the rising tension or payoff of a traditional scene.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene does compel the reader to continue because it raises the question of how the Ghostbusters will handle this escalating chaos, but the lack of a cliffhanger or direct hook weakens the pull.
Given the whole script, the reader is pulled to continue because the main plot (Gozer's arrival, Dana's possession, the storage facility explosion) is unresolved, and this scene shows the city's reaction, adding urgency.
No lens is broken, but Design is soft — this reads as a polish pass.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
6/10 expected
A real force keeps it pushing forward
5/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
6/10 core
It turns — something is different by the end
5/10 expected
The result obliges nothing in the next scene — no debt, threat, or changed baseline.
The result doesn’t oblige what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
7/10 expected
It’s a fresh take on this kind of scene
7/10 expected
It defeats anticipation fairly
7/10 core
The feeling comes off the page
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a possessed Keymaster confronting muggers with a supernatural roar is inventive and darkly funny. The idea of ghosts emerging from a movie screen to an applauding audience is a clever meta-commentary on horror fandom, but it feels more like a set-piece than a coherent part of the escalating plot.
The plot advances the spread of Gozer's influence through two vignettes, but neither directly involves the main Ghostbusters or Dana, making the scene feel like a detour. The connection between Louis's journey and the theater event is thematic (chaos spreading) but not causal, weakening narrative momentum.
The idea of a possessed man using a supernatural roar to scare muggers is original. The ghost procession from a movie screen to an applauding audience is a fresh take on the 'horror as entertainment' trope. The dialogue is not particularly original.
Louis/Vinz shows a clear, menacing personality shift, but the muggers are one-dimensional obstacles. The theater audience is a collective character, reacting with enthusiasm rather than fear, which is tonally inconsistent with the horror of the event.
Louis/Vinz does not change; he remains a single-minded vessel. The muggers change from aggressors to terrified victims, but this is a superficial shift. No character undergoes meaningful development.
Louis/Vinz's internal goal is to reach the Gatekeeper (Dana/Zuul) to fulfill Gozer's arrival. This is a single-minded, possessed drive, not a personal desire.
Louis/Vinz's external goal is to pass through the tunnel and continue his journey to Dana's building.
There is direct conflict between Louis/Vinz and the muggers, resolved quickly by his supernatural display. The theater scene has no conflict, only a spectacle. The lack of sustained opposition reduces dramatic tension.
The opposition is weak. The muggers are easily dispatched by Louis's roar. The theater has no opposition. The lack of a strong opposing force reduces dramatic tension.
The stakes are high in terms of global supernatural takeover, but this scene feels like a side-show. The muggers' lives are at risk, but the theater audience is unharmed and entertained, which lowers the perceived stakes.
Out of step with your script — story forward holds up in your other scenes.
The scene shows the supernatural chaos spreading, but it does not advance the main plot of the Ghostbusters confronting Gozer. It is a montage of effects rather than a step in the narrative.
This scene is unpredictable because the mugger confrontation takes an unexpected turn (Louis roars instead of paying), and the theater audience's applause is a surprising reaction to a supernatural event. However, the overall structure (montage of chaos) is predictable.
The scene aims for a mix of fear and dark comedy, but the emotional impact is diluted by the abrupt shift from a threatening tunnel to a cheering theater. The muggers' terror is effective, but the audience's applause feels jarring and reduces the sense of genuine threat.
The dialogue is functional but sparse. Louis's repeated 'Do you bar my way?' is effective in establishing his possessed state. The muggers' dialogue is generic street slang. The theater audience has no dialogue, only applause, which limits character development.
This scene is engaging because of its vivid, surreal imagery—Louis's roar and the ghost procession from the screen are memorable. However, the lack of connection to the main characters and the tonal inconsistency reduce sustained engagement.
The pacing of the scene is brisk, moving quickly from the tunnel to the theater. The tunnel scene has a good rhythm (approach, confrontation, climax). The theater scene builds slowly (film break, sound, wind) but the payoff (applause) feels rushed and tonally off.
Formatting is standard and clear. Scene headings are correct. Action lines are descriptive but occasionally overwritten (e.g., 'Irridescent lights pour out of his mouth'). The use of ALL CAPS for character introductions and sounds is appropriate for the genre.
The scene is structured as two parallel vignettes (tunnel, theater) without a clear narrative link. This works for a montage but weakens dramatic structure. The tunnel scene has a clear setup (muggers block path), confrontation, and resolution (roar). The theater scene is a set-piece with no conflict.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the theater audience applauding, which feels like a conclusion rather than a cliffhanger. It does not create a strong desire to see what happens next, as it is a self-contained vignette. The open question is 'what will Louis do next?' but this is not urgent.
The script has built strong momentum through the explosion of the storage facility and Dana's possession. This scene, while visually interesting, feels like a detour that slows the main plot. The reader is still compelled to see the Ghostbusters' response, but this scene does not add to that urgency.
No lens is broken, but Read is soft — this reads as a polish pass.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
6/10 core
A real force keeps it pushing forward
6/10 core
The situation deepens as it goes
7/10 core
It turns — something is different by the end
7/10 core
What happens here obliges what comes next
6/10 expected
Every beat and line earns its place
6/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
5/10 expected
The beats can be called before they land
6/10 expected
The feeling comes off the page
7/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of uncovering a secret society's apocalyptic plan through blueprints and a spirit guide is strong, but it's a familiar reveal in the genre.
The plot advances the mystery of Gozer and the building's purpose, but the scene is mostly exposition with little action.
The scene is original in its use of a jail cell as a setting for supernatural exposition, and the prisoners as an audience adds a fresh comedic layer.
Each Ghostbuster has a distinct voice: Stantz's enthusiasm, Spengler's precision, Venkman's sarcasm, Winston's skepticism. Their dynamic is clear and consistent.
Winston's skepticism remains unchanged; Venkman shows concern but no real change. The scene is more about revelation than transformation.
Venkman's internal goal is to understand the threat to Dana and find a way to save her, driven by concern and a desire to prove himself.
The Ghostbusters' external goal is to decipher the blueprints and figure out how to stop Gozer.
Conflict is low—mostly internal disagreement among the Ghostbusters and Winston's skepticism. The external conflict (mayor's summons) arrives at the end.
Opposition is minimal—Winston's skepticism is the only internal opposition; the external opposition (Peck, the law) is offstage until the end.
Stakes are high—the end of the world—but the scene's focus on exposition reduces immediate tension.
The scene reveals the building's purpose and Gozer's identity, moving the plot toward the climax.
This scene is unpredictable because the revelation of Ivo Shandor and the Sumerian connection comes from a spirit guide, not a typical source.
Emotional impact is moderate; Venkman's worry for Dana adds stakes, but the scene is more cerebral than emotional.
Dialogue is sharp and character-specific, with Venkman's quips and Spengler's corrections adding humor. However, some lines feel like pure info-dump.
This scene is engaging because the exposition is broken up by character humor and the prisoners' reactions, making the info-dump feel organic.
The pacing of the scene contributes to its effectiveness because it starts slow with Winston's complaint, builds through the blueprint discussion, and ends with a sudden summons, creating a rhythm of tension and release.
Formatting is standard and clear, with proper scene headings, character cues, and action lines. The parentheticals are used effectively.
The scene follows a classic exposition structure: setup (Winston's complaint), discovery (blueprint analysis), revelation (Shandor/Gozer), and a turning point (mayor's summons).
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a summons from the mayor, creating a clear hook and urgency that makes the reader want to see what happens next.
The script has built strong momentum with the explosion, Dana's possession, and Louis's transformation. This scene deepens the mystery and raises stakes, keeping the reader invested.
All three lenses are solid — worth protecting as it stands.
HoldingIt commits to one clear thing and holds it.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
8/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
7/10 expected
The situation deepens as it goes
8/10 core
It turns — something is different by the end
7/10 expected
What happens here obliges what comes next
7/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
6/10 light
It’s a fresh take on this kind of scene
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 light
It defeats anticipation fairly
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 expected
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of supernatural crisis management clashing with municipal bureaucracy is strong, and the scene executes it with a parade of officials and Peck's desperate accusations. However, the concept is not pushed further here—it's a familiar 'heroes convince the authorities' beat.
The plot advances cleanly: the Ghostbusters gain official backing, setting up the final act. The weakness is that the mayor's conversion is abrupt, lacking a moment of genuine doubt or a cost.
The scene is original in its blend of bureaucratic comedy and apocalyptic stakes—the Archbishop's 'sign from God' and Venkman's 'registered voters' are fresh takes on familiar tropes.
Venkman's sarcastic charm and Peck's righteous fury are well-drawn. Winston's brief testimony adds grounding. But the mayor is a cipher—he has no distinct personality beyond being 'likeable' and swayed by a punchline.
Venkman gains authority and the mayor shifts from skeptic to ally, but neither change feels earned or transformative—they're functional plot moves.
Venkman's internal goal is to be taken seriously and validated as an expert, driven by a need for respect and a desire to protect Dana and the city.
Venkman's external goal is to convince the mayor to authorize the Ghostbusters to stop Gozer.
The conflict is high: Peck vs. Ghostbusters, and the mayor's decision will determine the city's fate. But the conflict is resolved too quickly, with Peck literally ejected.
Peck is a strong opposition—he has a dossier, official authority, and the ear of the mayor. But his defeat is too swift, reducing his threat level.
The stakes are apocalyptic—the fate of New York and possibly the world. The scene reinforces this with the Archbishop's 'sign from God' and the list of disasters.
The scene moves the story forward decisively: the Ghostbusters get official support and resources, clearing the path to the climax.
This scene is unpredictable because the mayor's decision hinges on Venkman's 'registered voters' joke, which is both surprising and perfectly in character.
The scene generates tension and relief, but the emotional stakes are intellectual rather than visceral—we don't feel the mayor's fear or the Ghostbusters' desperation deeply.
The dialogue is snappy and quotable, especially Venkman's 'registered voters' and the Archbishop's 'sign from God.' The weakness is that Peck's objections are easily dismissed, making the debate feel one-sided.
This scene is engaging because of the rapid-fire debate, the absurdity of the Archbishop's confession, and Venkman's witty one-liners that keep the tone lively despite high stakes.
The pacing of the scene contributes to its effectiveness because it moves quickly from accusation to decision, with each official's testimony adding a beat of escalation before Venkman's punchline.
Formatting is professional: clear scene headings, proper character cues, and parentheticals. The 'MORE' and 'CONT'D' are correctly used.
The scene follows a classic 'heroes convince authority' structure: entrance, accusation, defense, testimony, decision. It's efficient but lacks a twist or reversal.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the mayor asking 'What do you need from me?'—a clear launchpad into the next scene, creating immediate anticipation for the Ghostbusters' plan.
The script has built massive momentum: Dana is possessed, Louis is the Keymaster, the storage facility exploded, and the city is in chaos. This scene adds official sanction, making the final confrontation feel imminent and necessary.
No lens is broken, but Design, Execution and Read are soft — this reads as a polish pass.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
4/10 core
Several candidate threads compete and none governs — the scene splits its focus rather than committing to one determinate spine.
It isn’t clearly about one thing yet
6/10 core
A real force keeps it pushing forward
4/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
5/10 expected
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 expected
What happens here obliges what comes next
6/10 core
Every beat and line earns its place
5/10 expected
The scene/sequence shifts location, time, POV, mode, or thread without making the causal/spatial/emotional/rhythmic relationship between adjacent chunks legible.
The parts sit side by side rather than building
6/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 core
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
6/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of the Gatekeeper and Keymaster uniting is the core mythic payoff, but the execution is brief and the Mayor's scene feels like a detour.
The plot advances the apocalypse but the Mayor's corridor scene is a slow information dump that stalls momentum.
The possessed kiss is a fresh take on the horror trope, but the Mayor scene is a standard bureaucratic obstacle.
Louis and Dana are reduced to possessed archetypes; the Ghostbusters get a nice moment with Janine but little individual characterization.
Louis and Dana change into possessed beings, but the Ghostbusters show no change here.
Venkman wants to save Dana and prove his worth, driven by guilt and affection.
The Ghostbusters must stop the apocalypse by reaching Dana's building.
The central conflict is the Ghostbusters racing to stop the apocalypse, but the scene lacks direct opposition.
The opposition is the possessed Dana and Louis, but they are not actively opposing the Ghostbusters yet.
The stakes are apocalyptic—the world is at risk—but the scene doesn't fully convey the urgency.
The story moves forward with the union of Gatekeeper and Keymaster and the Ghostbusters gearing up, but the Mayor scene slows it.
This scene is unpredictable because Louis's possessed kiss with Dana is a shocking twist, but the Mayor scene is predictable.
Janine's coin gift provides a touching moment, but the horror of Dana's possession is undercut by the absurd kiss.
The dialogue is functional but the Mayor's lines are clunky exposition; Janine's coin exchange is sweet but brief.
This scene is engaging because of the high stakes and the creepy kiss, but the Mayor's corridor scene drags.
The pacing of the scene contributes to its effectiveness because the quick cuts between locations create urgency, but the Mayor scene slows the rhythm.
Formatting is standard but the scene headings are clear; the action lines are functional.
The scene jumps between three locations (Dana's apartment, City Hall, loading dock) without clear transitions, weakening the structure.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the Ghostbusters gearing up, creating a strong cliffhanger that makes the reader want to see the final confrontation.
The script has built momentum through escalating supernatural events and character arcs; this scene maintains that momentum despite a slight lull in the Mayor corridor.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
A transition carries us between beats. It owes less structurally than a scene built to turn.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
6/10 core
It commits to one clear thing and holds it
4/10 expected
No page-visible force — antagonist, deadline, need, threat, rule, condition — pushes the beats; the scene proceeds without anything making it happen.
It leans on mood instead of something actually pushing it
4/10 light
It restates its note rather than deepening it
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
5/10 expected
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
6/10 expected
What happens here obliges what comes next
7/10 core
Every beat and line earns its place
6/10 core
Page space and pacing emphasize the wrong beats — the important turn is rushed/buried while minor business is lingered on.
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
4/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
The feeling comes off the page
7/10 expected
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of the Ghostbusters arriving to a cheering crowd and then immediately falling into a sinkhole is a strong, iconic beat that combines heroism with slapstick. It's a familiar but effective setup for a climax.
The plot advances the Ghostbusters to the final location and introduces a new obstacle (the sinkhole), but the scene is primarily transitional and lacks significant plot development beyond that.
The scene is a fresh take on the familiar 'heroes arrive to save the day' trope by immediately undercutting it with a sinkhole, which feels authentic to the Ghostbusters' comedic tone.
The characters are shown in their archetypal roles: Venkman as the confident leader, Winston as the reluctant realist, and the team as a unified front. However, there is no individual character growth or depth in this scene.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
No character undergoes a meaningful change in this scene; they remain consistent with their established personalities.
Venkman's internal goal is to prove himself as a capable leader and hero, driven by a need for validation and a desire to save Dana.
The Ghostbusters' external goal is to enter Dana's building and stop Gozer.
The conflict is external: the Ghostbusters must overcome the physical obstacle of the sinkhole and the larger threat of the building. There is no internal or interpersonal conflict in this scene.
The opposition is the physical environment (the unstable building and sinkhole) and the larger threat of Gozer, but no direct antagonist appears in this scene.
The stakes are high—the fate of the city and Dana are on the line—but the scene's tone is light and comedic, which slightly undercuts the tension.
The scene moves the story forward by getting the Ghostbusters to the building and introducing the sinkhole as a new complication, but it is a brief transitional moment.
This scene is unpredictable because the sinkhole collapse subverts the expected triumphant entrance, adding a comedic and dangerous twist.
The emotional impact is moderate—there's a sense of triumph from the crowd's cheer and humor from the sinkhole, but no deep emotional engagement with the characters.
The dialogue is functional and includes a few memorable lines (Venkman's 'underground parking' joke, Winston's Australia suggestion), but it is sparse and primarily serves to move the action forward.
This scene is engaging because it delivers a satisfying payoff to the Ghostbusters' journey, with a cheering crowd and a sudden, funny obstacle that keeps the energy high.
The pacing of the scene contributes to its effectiveness because it moves quickly from the motorcade to the crowd reaction to the sinkhole, maintaining momentum and excitement.
Formatting is standard and clear, with proper scene headings, action lines, and dialogue. The use of sub-headings (THE CROWD, THE STREET, etc.) helps organize the chaos.
The scene follows a classic 'hero's arrival' structure: build-up (motorcade, crowd), climax (cheer, flash), and a twist (sinkhole). It works well for an action-comedy genre.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with the Ghostbusters entering the building after the sinkhole, creating a strong cliffhanger about what they will face inside, compelling the reader to continue.
Given the entire script's buildup of Dana's possession, Louis as the Keymaster, and the impending arrival of Gozer, this scene's triumphant arrival and sudden obstacle heighten the momentum and pull the reader toward the final confrontation.
All three lenses are solid — worth protecting as it stands.
HoldingA real force keeps it pushing forward.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
8/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
8/10 core
What happens here obliges what comes next
6/10 expected
The scene reaches its function and keeps going, or carries beats/lines cuttable without losing what it's there to do — waste not explained by the mechanism.
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
5/10 light
It plays close to the version we’ve seen before
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 light
It defeats anticipation fairly
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
7/10 core
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of a rooftop temple, a god manifesting, and the Ghostbusters' absurd legalistic challenge is inventive and fits the franchise's blend of the mundane and supernatural.
The plot advances the climax but the quick defeat of Gozer feels like a false resolution, creating a plot twist that is more confusing than satisfying.
The scene is original in its blend of bureaucratic humor (Stantz's formal declaration) with cosmic horror, and the visual of the Terror Dogs transforming is fresh.
Venkman's sarcasm, Stantz's earnestness, and Winston's pragmatism shine, but the characters react more than drive the action, and the transformation of Dana and Louis into Terror Dogs is visually striking but emotionally distant.
No significant character change occurs; the Ghostbusters remain in their established roles, and Dana/Louis are reduced to monsters.
Venkman's internal goal is to protect Dana and prove his worth, driven by a desire to be taken seriously despite his sarcastic facade.
The Ghostbusters' external goal is to stop Gozer and save the city.
The conflict is clear: Ghostbusters vs. Gozer, but the battle is one-sided and ends abruptly, reducing the sense of struggle.
Gozer is a powerful, godlike opponent, but the opposition is undermined by the ease with which the Ghostbusters seemingly defeat him.
The stakes are cosmic—the fate of the world—but the scene's execution makes them feel less immediate due to the quick defeat.
The scene moves the story forward by introducing Gozer and setting up the next phase, but the false victory stalls momentum.
This scene is unpredictable because Gozer's sudden disappearance after absorbing the proton streams subverts the expected victory, but it feels more confusing than clever.
The emotional impact is mixed—there's awe and humor, but the quick defeat and lack of real danger for the heroes dampens the stakes.
The dialogue is sharp and funny, with Venkman's quips and Stantz's formal declaration standing out, but some lines feel like filler (e.g., 'Well, that ought to do it').
This scene is engaging because of the visual spectacle, the humor, and the anticipation of the final showdown, but the anticlimax reduces engagement.
The pacing of the scene contributes to its effectiveness because it builds tension quickly with the transformation and confrontation, but the rapid defeat and subsequent rumble feel rushed.
Formatting is professional and clear, with proper scene headings, action lines, and dialogue attribution, though some action blocks are dense.
The scene follows a classic three-act structure within itself: setup (arrival, transformation), confrontation (battle), and twist (Gozer's disappearance), but the twist feels unearned.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
The scene ends with a seismic rumble and the building swaying, creating a cliffhanger that compels the reader to continue to see what happens next.
The script has built strong momentum with escalating chaos, character arcs, and unresolved threats (Dana's possession, the city's destruction), and this scene adds the mystery of Gozer's disappearance, keeping the reader hooked.
All three lenses are solid — worth protecting as it stands.
HoldingIt commits to one clear thing and holds it.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
8/10 core
It commits to one clear thing and holds it
7/10 core
A real force keeps it pushing forward
6/10 expected
The situation deepens as it goes
7/10 core
It turns — something is different by the end
8/10 core
What happens here obliges what comes next
7/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
6/10 expected
It’s a fresh take on this kind of scene
7/10 expected
It defeats anticipation fairly
8/10 core
The feeling comes off the page
8/10 core
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of Gozer forcing the heroes to choose their destroyer, and Stantz accidentally summoning the Stay-Puft Marshmallow Man, is brilliantly original and perfectly blends cosmic horror with childhood nostalgia. The weakness is that the logic of 'choose and perish' is explained quickly in dialogue, but the mechanics of how Stantz's thought 'popped in there' and overrode the others' blank minds feels slightly convenient.
The plot moves decisively: Gozer issues the ultimatum, the choice is made, and the monster is revealed, escalating the conflict to its physical manifestation. The weakness is that the scene is largely reactive—the Ghostbusters stand and talk while the threat approaches, with little proactive action until the very end.
The scene is highly original in its fusion of cosmic horror with a childhood brand icon. The dialogue is authentic to the characters, with Venkman's sarcasm and Stantz's guilt feeling true. The weakness is that the 'choose your destroyer' trope is familiar from mythology.
Each Ghostbuster gets a clear moment: Venkman's panicked leadership, Spengler's analytical calm, Winston's blank-minded honesty, and Stantz's guilty confession. The weakness is that their personalities are expressed mostly through one-note reactions (panic, analysis, guilt) rather than deeper conflict or change within the scene.
No character undergoes a meaningful change in this scene; they start as a team facing a god and end as a team facing a giant marshmallow, with the same attitudes. Stantz's guilt is the closest to a shift, but it's played for comedy.
Venkman's internal goal is to protect his team and Dana (though she's absent) while maintaining his cool, sarcastic facade in the face of overwhelming odds. The need is to assert control and find a way out.
The Ghostbusters' external goal is to survive and defeat Gozer by choosing the right form of the Destructor—or, failing that, to fight the Stay-Puft Man.
The conflict is clear: the Ghostbusters must stop Gozer, but they've accidentally empowered him with a giant marshmallow man. The weakness is that the conflict is external and one-sided—Gozer is an offscreen voice, and the Marshmallow Man is a silent, plodding force, so there's no direct back-and-forth struggle.
The opposition is Gozer and the Stay-Puft Man—a god and a giant monster. The weakness is that Gozer is an offscreen voice, so the opposition lacks a personal, interactive presence until the monster arrives.
The stakes are cosmic: the destruction of New York (and possibly the world) by a giant monster. The weakness is that the absurdity of the monster slightly undermines the perceived threat—it's hard to feel genuine dread about a marshmallow.
The scene moves the story forward by introducing the physical form of the apocalypse (the Stay-Puft Man) and setting up the final confrontation. The weakness is that it's a setup scene—the actual battle hasn't begun yet.
This scene is unpredictable because the audience does not expect the Stay-Puft Marshmallow Man—it's a hilarious, left-field choice that subverts the typical 'dark god' climax. The weakness is that once the choice is made, the outcome is telegraphed.
The emotional impact comes from the absurdity and the team's shared moment of 'oh no'—it's funny and tense. The weakness is that there's no deep emotional stake for any individual character; Dana and Louis are absent, and the threat feels cartoonish rather than personally menacing.
The dialogue is sharp and functional, with Venkman's sarcastic 'Great! The marshmallows are about to get their revenge' and Stantz's apologetic rambling about Camp Waconda landing well. The weakness is that Gozer's lines are repetitive ('CHOOSE!!') and the exposition about the choice feels a bit on-the-nose.
This scene is engaging because the absurd premise (a giant marshmallow man) is perfectly timed and the characters' reactions are funny and relatable. The weakness is that the long stretch of dialogue before the reveal can feel static.
The pacing of the scene contributes to its effectiveness because it builds tension through Gozer's booming voice and the team's panicked dialogue, then releases it with the absurd reveal. The weakness is that the middle section (the explanation of the choice) slows the momentum.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
Formatting is professional and clear: scene headings, character cues, and action lines are standard. The use of ALL CAPS for Gozer's voice and the monster's name is effective. No formatting errors.
The scene follows a classic three-beat structure: Gozer's ultimatum (setup), the choice and realization (complication), and the monster's reveal (climax). The weakness is that the beats are dialogue-heavy and the pacing is static until the reveal.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene compels the reader to continue because it ends with the Ghostbusters stepping to the edge of the roof, ready to fight—a classic cliffhanger that promises action. The open question is whether they can defeat a giant marshmallow.
Given the whole script, the momentum is high: the apocalypse is manifest, Dana is possessed, and the team is about to face their biggest challenge. The absurd reveal keeps the tone fresh and the reader invested in how the joke will resolve.
No lens is broken, but Design and Read are soft — this reads as a polish pass.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
7/10 core
It commits to one clear thing and holds it
6/10 core
A real force keeps it pushing forward
5/10 expected
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
6/10 core
It turns — something is different by the end
4/10 expected
A consequence is announced or promised but the world does not change inside the scene.
The result doesn’t oblige what comes next
6/10 expected
Every beat and line earns its place
7/10 expected
The parts are ordered and seamed so they build
8/10 core
The reader can follow what matters
4/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
5/10 expected
The beats can be called before they land
7/10 core
The feeling comes off the page
6/10 expected
The exit pulls you into the next one
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of defeating a giant marshmallow monster by destroying the Terror Dogs and closing the portal is clever and ties back to earlier mythology. However, the 'cross the beams' reversal feels like a deus ex machina rather than a earned solution.
The plot moves from imminent danger to resolution, with clear cause and effect: the Ghostbusters fire at the dogs, the portal closes, the monster is sucked away. The sequence is logical but the key decision (crossing beams) lacks foreshadowing.
The idea of a giant marshmallow man as a destroyer is original and iconic. The method of defeat (destroying the portal) is a fresh take on the 'kill the source' trope. Dialogue feels authentic to the characters.
Venkman shows protective concern for Dana, Spengler has his 'best idea,' and Louis's post-rescue confusion is in character. However, the characters mostly react to the set-piece rather than driving it with distinct agency.
Venkman shows he'll risk Dana's life for the greater good, a slight change from his earlier protectiveness. Spengler has a moment of insight. No major arcs complete here.
Venkman's internal goal is to save Dana without losing her, balancing his desire to protect her with the necessity of defeating Gozer. His fear is losing her permanently.
Venkman's external goal is to destroy the Stay-Puft Man and close the portal, saving the city and rescuing Dana.
The external conflict is high: the Stay-Puft Man is about to kill them. Internal conflict is minimal—Venkman hesitates but quickly agrees. The conflict is resolved by a single action.
The opposition is the Stay-Puft Man, a physically overwhelming force. Peck provides minor opposition but is comically sidelined. The opposition is strong but one-dimensional.
The stakes are life-or-death for the Ghostbusters and the city. The monster is about to kill them. The stakes are very high.
This is the climax and resolution; the story ends here. It moves the story to its conclusion.
This scene is unpredictable because the solution (shooting the Terror Dogs) is a reversal of earlier warnings, and the monster's death via tornado-vacuum is visually surprising.
The scene has emotional beats: Venkman's fear for Dana, the relief of her survival, and the hug. But the comedy undercuts the tension, making the emotional impact moderate.
The dialogue is sharp and funny: 'We're going to be killed by a hundred-foot marshmallow,' 'Life is just a state of mind,' and Louis's 'Somebody must have spiked the egg salad' are memorable. The banter between Venkman and Dana at the end is charming.
This scene is engaging because of the high stakes, the spectacular visual of the burning marshmallow man, and the witty dialogue that keeps the tone light even in danger.
The pacing of the scene contributes to its effectiveness because it moves from tense standoff to rapid action to quiet resolution, with comedic beats (Peck buried in marshmallow) providing rhythm.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
Formatting is standard and clear: scene headings, action lines, character cues. The use of bold for character names and scene numbers is consistent. No errors.
The scene follows a classic three-act structure within itself: setup (monster approaching), confrontation (firing, hesitation, decision), resolution (destruction, rescue, denouement). The pacing is effective for an action climax.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene resolves the main conflict, so it doesn't create a strong desire to read the next scene—it feels like an ending. However, the final banter and Louis's line provide a light, satisfying close.
Given this is the climax and resolution of the entire script, the cumulative momentum is high but the story is essentially over. The reader is satisfied and doesn't need to continue.
Read is broken — a load-bearing lens isn’t doing its job yet.
An aftermath beat lands the cost of what just happened rather than driving new action.
HoldingThe reader can follow what matters.
Craft Read is the familiar battery — concept, plot, characters, dialogue, stakes, pacing.
Scene Mechanics is twelve specific ways a scene stalls — it ends about where it started, nothing is really pushing it, you can call the beats before they land — with about forty finer versions underneath them. So when a scene drags, you find out what's dragging it — not just how much.
5/10 core
It isn’t clearly about one thing yet
3/10 light
It leans on mood instead of something actually pushing it
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 light
The surface is full of events and motion, but the governing thread ends where it started — activity substitutes for evolution. Distinct from beats literally restating the same note.
It restates its note rather than deepening it
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
3/10 light
The unit connects, displays, or frames — it never attempts to change a dramatic condition. Distinct from a turn that is attempted but does not land (unclear_turn). An interlude doing its intended job is a craft choice, not this flaw.
It ends about where it started
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
2/10 light
The result obliges nothing in the next scene — no debt, threat, or changed baseline.
The result doesn’t oblige what comes next
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
6/10 expected
Every beat and line earns its place
5/10 expected
The parts sit side by side rather than building
7/10 core
The reader can follow what matters
3/10 expected
The scene's main situation/image/beat-pattern is recognizable genre convention and the script adds no specific inversion, collision, POV, cost, world-rule, or tonal twist that changes how it plays.
It plays close to the version we’ve seen before
2/10 light
The scene sets up its conflict then plays the most likely version — no turn, reversal, complication, or reveal the reader couldn't call in advance.
The beats can be called before they land
This scene's role doesn't owe this, so a low reading here is neutral rather than a fault.
4/10 expected
The emotion is described on the page rather than produced through the beats.
The feeling is stated more than felt
3/10 expected
The unit completes its business and ends on a settled beat — no new live question, demand, or expectation is created for the next unit to inherit.
It settles at the exit rather than pulling on
This scene has been scored but its written read hasn’t been generated yet — the notes above are derived from the scores.
No explanation provided.
No explanation provided.
Pick a criterion on the left to see its read.
The concept of two bums analyzing a giant marshmallow is a clever, humorous callback that fits the film's tone, but it's a one-joke idea that doesn't deepen the story.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
The plot is resolved; this scene is pure aftermath and celebration, offering no new plot developments or twists.
The bum's marshmallow analysis is a fresh, authentic take on the aftermath of a supernatural battle, but the victory parade is a standard trope.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
The bums are generic comic relief with no distinct personality; the Ghostbusters appear only as a group, with no individual character beats.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
No character changes; everyone is exactly as they were at the end of the climax.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
The Ghostbusters have no internal goal in this scene; they simply bask in victory.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
The Ghostbusters' external goal is to exit the building and drive away, which they accomplish.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
No conflict remains; the scene is purely celebratory.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
No opposition remains; the heroes have won.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
Stakes are zero; the danger has passed.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
The story is over; this scene provides closure but does not move the narrative forward.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
This scene is unpredictable because the bums' philosophical take on the marshmallow is an unexpected comic beat after a high-stakes climax.
The crowd's joy is infectious but shallow; the scene lacks emotional depth or resonance.
The bums' dialogue is amusing but flat, relying on a single joke; the Ghostbusters have no dialogue, missing an opportunity for character closure.
This scene is engaging because the giant marshmallow callback is funny and the crowd's cheer is satisfying, but it's brief and lacks tension.
The pacing of the scene contributes to its effectiveness because it provides a quick, lighthearted release after the intense climax, but it feels rushed and could use more breathing room.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
Formatting is standard and clear, with proper scene headings and action lines, though the bums' dialogue is a bit sparse.
This scene isn't built to carry this, so a low reading here is the shape of the scene rather than a fault.
The scene has a two-part structure: a comic beat with the bums, then a victory procession. It lacks a traditional three-act structure but works as a denouement.
“Grab ‘em by the throat and never let ‘em go.”
The scene level score is the impact on the reader or audience to continue reading.
The Script score is how compelled they are to keep reading based on the rest of the script so far.
This scene does not compel the reader to continue because it is the final scene; the story is complete and all questions are resolved.
Given the whole script, the reader is satisfied and not pulled to keep reading; the story has reached a natural, happy ending.
The screenplay's character development is engaging and effective, with well-defined characters who undergo significant growth and transformation throughout the story. The interplay between character development and the screenplay's themes drives the narrative forward and deepens the emotional resonance of the story.
The screenplay excels in creating a diverse cast of characters, each with their own unique motivations, flaws, and growth arcs. The main characters, such as Venkman, Stantz, and Spengler, are particularly well-developed and their interactions provide both humor and emotional depth. The supporting characters, such as Dana and Louis, also have their own compelling arcs that contribute to the overall narrative.
The screenplay for "Ghostbusters" effectively establishes a compelling and clear premise, blending comedy, science fiction, and horror elements to create a unique and engaging narrative. The initial scenes quickly introduce the core characters, their scientific background, and their skeptical yet humorous approach to the supernatural. The premise's strength lies in its originality, combining elements of ghost hunting with witty dialogue and relatable characters. The clarity of the premise allows the audience to easily understand the central conflict and the Ghostbusters' mission to capture and contain supernatural entities. However, there's room for further exploration of the characters' backstories and motivations, particularly regarding their initial interest in the paranormal, to deepen audience engagement.
The screenplay's premise is highly original, presenting a unique blend of comedy, science fiction, and horror. The concept of a team of scientists using technology to capture ghosts is both intriguing and entertaining. The premise is also clear and easy to understand, with the Ghostbusters' mission and the stakes involved being established early on. The potential for audience engagement is high, thanks to the combination of humor, action, and the supernatural.
The screenplay's structure effectively sets up the premise and character dynamics, leading to a thrilling climax and resolution. However, improvements to pacing and refining certain plot elements could enhance the overall narrative impact.
The screenplay showcases a strong narrative structure with a well-defined beginning, rising action, climax, falling action, and resolution. Each act introduces key plot points and character motivations, building towards a thrilling climax and a satisfying conclusion. The story unfolds at a steady pace, maintaining a balance between action, exposition, and character development.
The screenplay effectively explores and communicates its themes and messages, offering a blend of humor, suspense, and commentary on science versus the supernatural. While some themes are more fully developed and impactful than others, the screenplay manages to convey a coherent and engaging message about the importance of facing one's fears and embracing unconventional approaches to problem-solving.
The screenplay's exploration of themes and messages is commendable, with several key themes woven into the narrative in meaningful ways. The primary theme of the importance of facing one's fears is particularly well-developed through the character arcs of Venkman and Dana, who both grapple with their own fears and ultimately learn to confront them. The screenplay also touches upon the theme of science versus the supernatural, presenting a balanced view that acknowledges the limitations of both approaches while highlighting the potential benefits of combining them. Overall, the screenplay's themes and messages are relevant, clear, and impactful, contributing to its overall success.
The screenplay employs a mix of humor and visual effects, but its descriptions lack vividness and creativity, relying on conventional imagery. Revisiting the screenplay with a focus on crafting unique visual descriptions and incorporating innovative visual storytelling techniques could enhance its cinematic impact.
The screenplay's visual imagery is adequate, providing basic descriptions of scenes and character actions. However, it often lacks vividness and creativity, resulting in a somewhat formulaic visual experience. The screenplay could greatly benefit from enhancing its visual storytelling by incorporating more unique imagery, creating a compelling visual style, and employing a wider range of cinematic techniques.
Examples: Instead of simply describing a room as 'dark', use language that evokes a sense of atmosphere, such as 'The room was bathed in an eerie darkness, the only light coming from the flickering flames of a dying candle.', Instead of describing a character as 'angry', use specific actions and expressions to convey their emotions, such as 'His face was contorted in a mask of rage, his eyes blazing with fury.', Instead of describing a scene as 'chaotic', use vivid verbs and sensory details to create a dynamic and immersive experience, such as 'The crowd surged forward like a tidal wave, their voices a cacophony of screams and shouts.'
Examples: In the library ghost encounter, use a POV shot from the ghost's perspective to create a sense of immediacy and terror., In the final confrontation with the Stay-Puft Marshmallow Man, use a wide-angle lens to capture the scale and grandeur of the battle., In the Dana Barrett possession scene, use color filters and distorted visuals to convey her transformation and the otherworldly presence within her.
Examples: Establish a warm and inviting color palette for scenes set in the Ghostbusters' firehouse to convey a sense of camaraderie and home., Use cool and ethereal lighting in scenes involving supernatural elements to create a sense of mystery and otherworldliness., Incorporate fluid and dynamic camera movements during action sequences to enhance the sense of excitement and danger.
The screenplay effectively elicits emotional responses through witty banter, supernatural tension, and personal growth. To enhance the emotional depth, consider incorporating moments of vulnerability, exploring the fears of secondary characters, and adding scenes that focus on the emotional complexities of the supernatural elements.
The screenplay has a strong foundation for emotional storytelling, with humorous interactions, thrilling supernatural encounters, and compelling character arcs that create an engaging and immersive experience. However, it could benefit from further exploration of emotional vulnerabilities and a deeper dive into the emotional impact of the supernatural phenomena.
The screenplay effectively sets up a central conflict between the Ghostbusters, a group of scientists dedicated to catching and containing ghosts, and various supernatural forces threatening the safety of New York City. The stakes are personal for several characters, especially Dana Barrett, who becomes possessed by an ancient evil entity. While the screenplay succeeds in presenting an engaging conflict and escalating stakes, there are opportunities to deepen the emotional impact and heighten the narrative tension.
The screenplay's conflict and stakes provide a solid foundation for narrative tension and audience engagement. The Ghostbusters' mission to protect the city from ghosts creates a clear goal and establishes the stakes for their actions. The personal stakes for Dana add an emotional layer to the conflict, making it more relatable and compelling.
The screenplay exhibits a delightful blend of nostalgia and innovation, capturing the essence of the original 'Ghostbusters' while introducing fresh elements that keep the story engaging and entertaining. The narrative deftly weaves supernatural thrills with comedic moments, creating a unique and immersive cinematic experience.
The screenplay showcases originality and creativity in its clever reimagining of the 'Ghostbusters' franchise. It successfully captures the spirit of the beloved characters and the supernatural themes of the original while introducing new twists and turns that keep viewers engaged. The screenplay effectively blends comedy, action, and supernatural elements, resulting in a well-crafted and entertaining narrative.
Thank you for your feedback!
Get a comprehensive PDF version of your screenplay analysis
The PDF version is a static summary of your analysis. Due to format and interactivity constraints, the PDF does not include all the data available in the web version.
What's not in the PDF: Interactive charts, expandable sections, full scene-by-scene details, AI chat history, and dynamic filtering options are not available in the PDF format. For the complete analysis experience, use the web interface.
Click below to generate and download your PDF analysis summary
Download PDFPDF generation may take 20-30 seconds
Tip: For sharing purposes, consider using the web link instead. It provides real-time access to all features and updates automatically.
Scene by Scene Emotions