A working glossary of the craft terms that come up most often in coverage, notes, and rewrites — with plain-English definitions and examples for beginner and intermediate writers.
Every term below has its own anchor link, so you can jump straight to a definition or share one with a collaborator. For example, /terms#notebehindthenote will take you right to "The Note Behind the Note."
Meta-vocabulary for reading notes on your own work.
Also called: the real note, the underlying note, the diagnosis vs. the symptom.
The deeper, structural issue that a piece of surface feedback is really pointing at. When a reader says "this dialogue feels off," the note behind the note might be "I don't believe this character wants what you're telling me they want." The surface note is a symptom; the note behind the note is the diagnosis.
Learning to hear past the literal words of a note is the single biggest leap a writer can make in using coverage effectively. Two different readers will often describe the same underlying problem with wildly different surface notes — "pacing is slow," "I didn't care about the protagonist," "the second act drags" — and a writer who fixes the literal note without finding the real one will keep getting versions of that feedback forever.
When reading coverage, ask: "If this reader is right, what would have to be true about the script?" That question surfaces the note behind the note.
The skeleton of the script — premise, plot shape, and the big beats.
Also called: pitch, one-liner, (loosely) premise.
A one-sentence description of your story's engine: who wants what, and what's in their way. A good logline tells a reader the protagonist, their concrete goal, the opposing force, and often a ticking clock or an ironic hook. It's the hardest sentence in screenwriting, because it forces you to know what your movie is actually about.
Coverage almost always opens with logline feedback, because if the logline is fuzzy the script usually is too. Beginners often confuse a logline with a premise ("What if a shark attacked a small town?") or a synopsis (the whole plot). The logline is the intersection: premise + specific character + engine of conflict.
Notice the second version has irony built in — Blake Snyder called this "the promise of the premise." A good logline already makes the movie.
A story whose premise can be communicated in a single striking sentence that immediately suggests a movie — and that most listeners would pay to see. Classic examples: Jaws ("a shark terrorizes a beach town"), Groundhog Day ("a man relives the same day forever"), Liar Liar ("a lawyer can't lie for 24 hours"). High-concept scripts sell themselves on premise alone.
The opposite is sometimes called "low-concept" or "character-driven" — stories that rely on execution, voice, and character over premise (Manchester by the Sea, Marriage Story). Neither is better; they're different sales strategies and they attract different readers.
Coverage will call a script "under-conceptualized" when the premise isn't doing enough work to hook a reader in a single line. If your logline isn't landing, the note behind the note may be that the concept itself isn't high enough to carry the kind of movie you're pitching.
Also called: the call to adventure, the catalyst, the disturbance.
The event that disrupts the protagonist's status quo and forces the story into motion. Luke finds Leia's message. Neo takes the red pill. The letter from Hogwarts arrives. Before the inciting incident the protagonist could plausibly have stayed where they were forever; after it, the old life is no longer an option.
Most feature specs want the inciting incident somewhere between page 10 and page 17 — early enough that the audience isn't waiting, late enough that the "ordinary world" has been established. TV pilots usually land it faster.
Notes that trace back to a weak inciting incident: "the story takes too long to start," "the protagonist feels passive," "I wasn't sure what the movie was about until page 30." When the first act drags, this is the first thing to examine.
Also called: plot point, act turn, major beat.
The structural hinge where the story changes direction — a moment of no return that locks the protagonist into a new phase. In three-act structure, the two big ones are the Act One break (the protagonist commits to the adventure) and the Act Two break (all is lost; the old strategy has failed and a new one is needed).
A true turning point reframes everything. Before the Act One break of Die Hard, John McClane is a cop visiting his estranged wife. After it — terrorists seize the building — he's a lone fighter trapped in an enemy fortress. The goal, the stakes, and the rules all shift.
Common coverage notes that trace here: "the second act drifts," "there's no clear turn into Act Two," "the ending feels unearned." The third-act ending always feels unearned when the second-act turn didn't put the protagonist in real trouble.
The big pivot at roughly the 50% mark — where the protagonist flips from reactive to proactive, where a false victory becomes a real defeat (or vice versa), where a secret is revealed, or where the mission itself changes. Silence of the Lambs: Clarice's second interview with Lecter gets her the real clue. Toy Story: Woody and Buzz end up trapped at Sid's house — the world turns hostile.
Midpoints exist because audience attention struggles across 60 straight pages of Act Two. Without a major pivot the second act sags — and "the second act drags" is probably the single most common structural note in all of coverage.
If your script feels slow in the middle and you don't know why, the midpoint is the first place to look. Ask: does the protagonist's strategy change here? Do the stakes escalate? If neither, you don't have a midpoint yet.
A scene-by-scene (or beat-by-beat) outline of a screenplay, used for planning before drafting or diagnosing a finished draft. The most famous template is Blake Snyder's Save the Cat beat sheet — 15 named beats with target page numbers — but every working writer has their own version: John Truby's 22 steps, Dan Harmon's story circle, the classic three-act sheet, or index cards on a corkboard.
Beat sheets aren't formulas. They're diagnostic tools. When coverage says "the structure feels off," it often means specific beats are missing, out of order, or landing at the wrong page. Writing a beat sheet after a draft is often more useful than writing one before — it shows you the shape of what you actually wrote.
A common intermediate mistake: treating beat sheets as a checklist rather than a map of emotional turns. The midpoint doesn't have to land exactly on page 55 — it has to feel like a midpoint.
Also called: planting and harvesting, foreshadowing, Chekhov's gun.
The principle that anything important in a story's climax must be established earlier (the set-up), and anything established earlier should eventually matter (the payoff). Chekhov: "If in the first act you hang a pistol on the wall, in the next one it should be fired."
Good set-up is invisible on first viewing and inevitable on second. The ending of The Sixth Sense works because the clues are planted so precisely you don't notice them. The climax of Back to the Future — Marty playing "Johnny B. Goode" — is set up by Marty's band audition in the first act.
Coverage notes here are usually one of two kinds: "the payoff feels random" (under-planted) or "you keep telling me things I already know" (over-planted, usually meaning the foreshadowing is too obvious). The trick is planting just enough that the audience can retrieve it later without consciously remembering the plant.
What the protagonist stands to lose if they fail. Stakes can be external (death, prison, the world ending) or internal (a marriage collapses, an identity shatters, a last chance at redemption disappears). Great scripts operate on both levels at once.
Writers routinely confuse stakes with consequences (what has already happened) or urgency (time pressure). Stakes are a future loss the audience can feel. If the worst-case outcome isn't clear, or if it doesn't matter to the protagonist, the script has a stakes problem.
"Raise the stakes" is one of the three most common notes in all of coverage. It almost never means "add a bigger explosion." It usually means: make the loss more personal, make the protagonist more invested, or close an off-ramp so the protagonist can't simply walk away from the problem.
A scene (usually 1–5 pages) that plays before the main title or the main story begins — designed to hook the audience before they've had a chance to reach for the remote. Common in TV; increasingly common in features.
Cold opens take a few shapes. The in-medias-res hook (Breaking Bad pilot: Walt in the desert in his underwear, then flash back six weeks). The case-of-the-week opener (Law & Order's two joggers finding a body). The standalone mini-movie (Bond's pre-title sequences). The thematic prologue (the silent opening of Up).
A strong cold open promises what the show or film will deliver every time out. Coverage will flag a cold open that's disconnected from the rest of the story — it has to earn the hook by paying off a promise later, or it reads as a gimmick.
Who the protagonist is, what they want, and why they can't simply walk away.
Also called: external goal vs. internal need, conscious vs. unconscious desire, the two-want structure.
The want is what the protagonist thinks will make them happy — a concrete, external goal they pursue throughout the story (win the tournament, solve the case, get the promotion). The need is what they actually have to learn, change, or accept in order to be whole — usually the opposite of what they think they want.
This structural split is the engine of almost every character-driven screenplay. Luke wants to become a Jedi hero; he needs to trust the Force. Woody wants to remain Andy's favorite toy; he needs to accept that his worth isn't conditional on being #1. Michael Corleone wants to protect his family; he needs to not become his father (and fails — a negative arc).
Coverage that calls a protagonist "flat" or "unsympathetic" is often really pointing at a missing or unclear need. A want alone makes a plot. A want plus a need makes a story.
See also: Character Arc, Wound / Ghost / Flaw.
The internal change a character undergoes from beginning to end. Classic arcs come in three flavors. The change arc: character overcomes a flaw and becomes better (Groundhog Day, most Pixar). The flat arc: character stays steadfast and changes the world around them (Paddington, most Captain America). The negative arc or corruption arc: character resists change and is destroyed (Macbeth, Walter White in Breaking Bad).
A clear arc requires a starting state (a flawed or fixed belief), a disturbance (pressure the belief can't handle), a dark moment (the old belief fails completely), and a new state (proven by action, not dialogue).
Coverage note: "the arc isn't clear" almost always means one of three things — we never knew what the character believed at the start, we didn't see the belief tested, or the change was told to us instead of shown through choice.
See also: Want vs. Need, Theme.
Also called: the backstory wound, the ghost (Truby), the lie the character believes (K.M. Weiland).
The formative event in the protagonist's past that produced the flaw they carry into the story. The wound is what happened (a parent left, a friend died, a betrayal); the flaw is the broken belief or behavior that resulted ("people can't be trusted," "love is weakness," "I'm only valuable when I'm useful"). Together they form the emotional pressure point the plot will eventually press on.
You don't need to show the wound on screen. Doing it too explicitly — a flashback in Act One — often flattens the character. The wound lives in behavior: the way they flinch, the things they won't say, the relationships they sabotage.
When coverage says "I don't know why this character is like this" or "the flaw doesn't cost them anything," the wound is usually underbaked. Readers don't need the literal backstory — they need to feel that there is one.
See also: Want vs. Need, Character Arc.
A moment in the early pages of a screenplay — often the protagonist's introduction — in which the protagonist does something small, kind, or principled that earns the audience's rooting interest. Blake Snyder popularized the name in his 2005 book of the same title. It doesn't have to involve an actual cat (though Alien's Ripley does rescue one).
The misread: "make the protagonist likable." That's not quite right. A Save the Cat moment makes the protagonist interesting enough to follow, which usually means showing something admirable in context of their flaw. Michael Clayton quietly defending his son. Walter White patiently teaching chemistry. Deadpool sparing an old man in traffic.
The moment matters because audiences decide within minutes whether to invest. A protagonist introduced only through their flaws — no matter how fascinating — forces readers to reserve judgment, which reads as distance.
Three roles that overlap so often writers treat them as synonyms — but they aren't, and the distinction clarifies a lot of coverage confusion.
The protagonist is the character whose pursuit drives the plot — the engine of want. The main character is the one whose inner journey the story is about — the one the audience emotionally lives inside. The POV character is the lens through which the story is shown.
In most movies, one character is all three. But The Great Gatsby has a clear split: Gatsby is the protagonist (driving the plot); Nick Carraway is the main character and POV (having the emotional experience of watching Gatsby). To Kill a Mockingbird: Atticus is the protagonist; Scout is the main character and POV. Forrest Gump: Forrest is all three; Jenny runs her own protagonist-arc in the background.
When coverage says "I'm not sure whose story this is," the note behind the note is often that these three roles haven't been clearly assigned.
How characters talk, how scenes end, and where meaning actually lives.
Also called: on-the-nose, telling not showing, saying the subtext out loud.
Dialogue where characters say exactly what they mean — explicitly stating their feelings, motivations, or the thematic point the audience should be inferring. The craft goal is usually the opposite: characters talking around what they feel, trusting the audience to read the subtext.
"On-the-nose" is one of the most common notes in professional coverage because it's easy to diagnose and almost always a symptom of a deeper trust issue — the writer doesn't yet trust the scene, the actor, or the audience to carry the meaning without spelling it out.
A useful test: if you can delete a line and the scene still works emotionally, the line was probably on the nose. If you can delete it and the scene falls apart, either the line is load-bearing or the scene is doing the work elsewhere — which is often where the note behind the note is hiding.
See also: Subtext, Exposition.
The meaning underneath the dialogue — what a character really feels, wants, or fears, expressed through what they don't say. Subtext is the opposite of on-the-nose dialogue: rather than announcing the emotional content, the scene conveys it through deflection, misdirection, silence, and behavior.
The classic example: in Casablanca, Rick and Ilsa don't say "I still love you" — they talk about Paris, the rain, a song. In The Social Network, Mark and Erica's breakup scene is ostensibly about rowing crew and Final Clubs. It's entirely about class, shame, and ambition.
Subtext is created by pressure: a character wants to say something but can't — because of propriety, status, self-protection, or the presence of a third party. If nothing stops a character from saying what they mean, they'll say it, and the scene goes on the nose.
When coverage praises dialogue as "crackling" or "alive," it's almost always responding to subtext. When it flags dialogue as on-the-nose, subtext is what's missing.
Information the audience needs to understand the story — who these people are, what the world is, what's already happened, what's at stake. Exposition is unavoidable. Bad exposition is the problem: when a character tells another character something they both already know, purely to inform the audience.
Good exposition hides inside conflict. Two characters arguing can reveal everything about their relationship while ostensibly fighting about dinner. A teacher explaining physics to a student feels natural; two physicists explaining physics to each other is a red flag.
Common tools for handling exposition gracefully: make someone resist it (one character doesn't want to reveal the thing), make it cost something (the reveal damages a relationship), delay it (let the audience feel the gap), or externalize it (show the evidence instead of stating the fact).
Coverage notes like "expository dialogue," "info-dump," or "feels like we're being told, not shown" usually mean the exposition hasn't been hidden inside something that would be happening anyway.
See also: On-the-Nose Dialogue.
When the audience knows something a character doesn't — and the tension comes from watching the character operate without that information. The term goes back to ancient Greek theater (Oedipus doesn't know he's hunting himself; we do). It is one of the most powerful tension-generating tools in screenwriting, and the one beginners are most likely to under-use.
Three common modes. Suspense: we see the bomb under the table; the characters don't (Hitchcock's famous example). Comedy: we know the woman in the disguise is the lead; the other characters don't (Some Like It Hot, Mrs. Doubtfire). Tragedy: we know the romance is doomed before the characters do (Romeo and Juliet, Titanic).
If a scene feels inert, try giving the audience one piece of information the character is missing. Watch tension appear for free.
Coverage note: "the scene has no tension" is often really "the audience is in the same epistemic position as the character." Creating an asymmetry fixes it.
Also called: V.O., off-screen narration.
Voice-over (V.O.) is dialogue or commentary heard over action, with the speaker not physically present in the scene — a character narrating their own past (Goodfellas), an omniscient outsider (Amélie), or an internal monologue (Fight Club). Narration is the broader concept: V.O., on-screen text, or direct address.
V.O. has a bad reputation in some screenwriting circles, largely because of a famous scene in Adaptation where Robert McKee (playing himself) tells Charlie Kaufman that V.O. is for lazy writers. Taken literally, that advice is wrong — Goodfellas, Sunset Boulevard, Arrested Development, and Fleabag are all unimaginable without it. What McKee really meant: don't use V.O. to paper over storytelling you haven't figured out how to dramatize.
The question to ask: does the voice-over add a perspective the images alone can't carry? If yes, it's earning its page. If the V.O. is just describing what we can already see, cut it.
What the story is really about — and the tools that power the plot without being it.
What the story is about underneath the plot — the argument the movie is making about human experience. Love requires risking loss (Up). Obsession consumes (There Will Be Blood). You can't outrun the past (Manchester by the Sea). Theme is expressed through the whole of the story, especially through what choice the protagonist makes at the climax.
Beginners often confuse theme with subject ("this movie is about war") or moral ("the lesson is: war is bad"). Theme isn't a topic or a slogan. It's a position the story takes, usually in dialogue with a counter-position the antagonist represents. Dead Poets Society argues for seizing the day; Mr. Perry argues for duty. The film takes a side.
When coverage asks "what is this really about?" and the writer can't answer in a sentence, the theme probably isn't doing work yet. When every scene pulls in a slightly different thematic direction, the story feels unfocused for reasons readers can't name. Theme is often the deepest note behind the note.
An object, goal, or plot device that drives the characters' actions but whose specific nature doesn't matter to the audience. Hitchcock coined the term: the briefcase in Pulp Fiction, the microfilm in North by Northwest, the Ark in Raiders of the Lost Ark, the Rabbit's Foot in Mission: Impossible III. What's inside is irrelevant; what matters is everyone wants it.
A MacGuffin is a tool, not a flaw. It's a perfectly legitimate way to get characters into motion and into conflict with each other. The problem arises when a writer mistakes a MacGuffin for a theme or a stakes generator — it isn't either. If the audience doesn't care about the people chasing the MacGuffin, making the MacGuffin cooler won't save the script.
Common misuse: writers assume the term means "plot hole" or "lazy device." It doesn't. A well-used MacGuffin is invisible. A badly used one exposes the seams because the chase isn't about anything.
A clue or piece of information that points toward a false conclusion, designed to misdirect the audience. Most common in mysteries and thrillers (the suspicious neighbor who turns out to be innocent), but the technique appears anywhere the writer wants to manage the audience's expectations — romance (the obvious love interest who isn't), horror (the "scary" stranger who turns out to be helpful).
A good red herring has to satisfy two conditions. It has to be plausible enough that the audience genuinely entertains it, and the real answer has to be more satisfying in retrospect. If the red herring is more interesting than the truth, the reveal disappoints. If the red herring isn't convincing, it doesn't misdirect.
Coverage note on mysteries: "I guessed the twist on page 30" usually means the red herrings weren't pulling enough weight — not that the twist itself was weak.
Vocabulary you'll hear from managers, producers, and fellow writers.
A screenplay written on speculation — without a commissioning deal, studio assignment, or prior payment — in the hope that it will sell or serve as a writing sample. Most screenplays a new writer writes are specs, by definition. The opposite is an assignment or open writing assignment (OWA), where a producer pays a writer to draft a project they already own.
Two subcategories worth knowing. A sample spec (sometimes "calling card") is written to showcase voice and craft — it may never sell, but it lands the writer meetings, rooms, or assignment work. A market spec is written to sell — usually higher-concept, more genre-forward, built around a premise that can be pitched in a sentence.
Coverage doesn't usually flag this as a note, but the distinction changes how you should read your own script. A beautifully written character piece is a great sample and a tough sell. Knowing which you're writing helps you know whose notes to take.
A rewrite that discards the existing draft's structure and rebuilds the script from scratch — as opposed to a polish (line-level changes) or a production rewrite (targeted fixes for budget, casting, or location reasons). Page one rewrites are the heavy artillery of development: expensive, painful, and usually a sign that earlier passes didn't solve the fundamental problem.
Writers often resist the page one because it feels like throwing away work. In practice what gets thrown away is usually fewer pages than you think — most of the characters, many of the scenes, and almost all of what you learned writing the first draft come with you into the second.
Rule of thumb: if the note you keep getting is about a premise, a protagonist, or a deep structural beat, you probably need a page one — no amount of line-level polishing will get you there. If the notes are about dialogue, pacing, or specific scenes, a polish will do.
The vocabulary the script overview and per-scene diagnostic use. Two craft layers (Design and Execution), four scene types, and the dimensions each gets scored on.
The structural side of a scene.
The choices behind the scene — what it's trying to do, who wants what, who blocks, what changes by the end. Design lives before the page: it's the engineering of cause and consequence, of contest and payoff, of why the scene needs to exist at all. A well-designed scene moves the story forward whether the prose is brilliant or workmanlike.
Design problems require restructuring. You can't fix a design problem by rewriting prose. If a scene's want isn't legible, or its opposition can't enforce, or nothing changes by the end, polishing the dialogue won't help — you have to rebuild what the scene is trying to do.
Design splits two ways depending on the scene type. Conflict scenes are scored on the seven Conflict axes (Clear Want through Audience Awareness). Moment scenes are scored on the four Moment axes (Clear Job through Anchored). Conflict + Moment scenes get both. Bridge scenes aren't scored on Design at all — they exist to move us between contexts, not to build structure.
The on-page side of a scene.
How the scene's structural choices land on the page — beat clarity, dialogue function, pressure, economy. Execution is the craft of making sure what you intended actually arrives. A well-executed scene reads the way you wrote it: turns turn, lines do work, pressure registers, runtime is earned.
Execution problems can usually be fixed in a polish pass without touching structure. A scene with strong Design but weak Execution is a scene that's doing the right thing but not landing it — the fix is rewriting prose, not rebuilding the scene's job.
Execution applies the same way to every scene, regardless of type. The four execution axes (Beat Clarity, Active Dialogue, Pressure on Page, Economy & Flow) are scored on every Conflict, Moment, Conflict + Moment, and Bridge scene.
Engine scenes. Contest scenes. The fights.
Scenes built around a contest between characters. Someone wants something; someone (or something) is in their way; the scene tracks how that pressure plays out. The audience reads the scene as a contest: who's going to win, what's it going to cost, what does it leave behind?
Conflict scenes are scored on seven design dimensions: Clear Want, Real Opposition, Shared Contest, Cost Lands, What Changes, Tactical Shift, Audience Awareness. Plus the four execution dimensions every scene gets.
Sub-types include confrontation, negotiation, interrogation, debate, chase, battle, and ambush. The system tracks the sub-type but scores them all on the same engine axes — what changes is the texture, not the architecture.
Payload scenes. Experiential scenes. The breath beats.
Scenes whose primary job is to deliver an experience — not to run a contest. A reveal, a processing beat, a moment of dread, a bonding scene, an orientation, a plant. The audience reads the scene as something landing: a feeling, an understanding, a relationship shift, a piece of information.
Moment scenes are scored on four design dimensions: Clear Job, Payload Progression, Runtime Justification (Earned Length), Payload Anchoring. Plus the four execution dimensions.
A common revision question for Moment scenes is whether they alter later behavior or just deliver an experience and move on. A Moment that lands beautifully but doesn't change the next contest's baseline is sometimes called unanchored — pretty but skippable.
Both at once. A contest runs while a moment lands.
Scenes where a contest runs and an independent moment lands at the same time. The test: would the moment still land if the contest outcome were reversed? If yes, the scene is a Conflict + Moment scene. If the moment depends on the contest result, it's a Conflict scene with texture, not a Conflict + Moment.
Conflict + Moment scenes get scored on both the seven Conflict axes and the four Moment axes. They're often a script's most ambitious scenes — and the hardest to write — because they have to do two jobs at once without either feeling subordinate to the other.
The most common Conflict + Moment failure: hedging. The scene tries to be both but lands neither cleanly. The diagnostic question is which job is primary? Once the writer commits, the other job either intertwines naturally or it doesn't — and if it doesn't, the scene wants to be one type, not both.
Bridge scenes. The in-between.
Scenes whose job is to move us between contexts — locations, time periods, emotional states. They don't carry a contest, and they don't deliver a primary experiential beat; they exist for continuity.
Transition scenes are scored only on Execution — the four execution axes, and that's it. They don't carry a Design score because Design is about what the scene is trying to do, and a transition's job is just to get us cleanly to the next context. The most common Transition diagnostic is whether the scene runs longer than its job justifies.
A well-used transition can plant a story seed for later or set a tonal contrast that pays off in the next beat. But the bar is low: do the work and get out.
A1 — a Conflict design dimension (Conflict and Conflict + Moment scenes).
Whether the scene makes it trackable what the center of the scene wants now. Not their general life goal — their specific aim within this scene's first 10–15%. A high score means the audience can name what the character is going after; a low score means we're watching behavior without knowing what to root for or against.
Without a legible want, a scene can't read as a contest — it just reads as people doing things. The fix is almost always the same: make the want visible earlier and more concretely. A character ordering coffee might be wanting "coffee," "to delay this conversation," or "to feel normal again" — the scene works once the audience can name which.
A2 — an engine design dimension.
Whether the opposition has teeth — whether the blocker can credibly enforce a "no" or extract a "yes-but-pay." A high score means the obstacle has authority, leverage, gates, or environment behind it. A low score means the threat exists in dialogue but doesn't change anything (sometimes called "threats without enforcement").
The diagnostic question: what would happen if the protagonist just walked past the opposition? If the answer is "nothing structural," the opposition isn't real — it's set dressing. Strong opposition makes contest scenes pop; weak opposition makes them feel like conversations with extra steps.
A4 — an engine design dimension.
Whether in-scene consequences actually land — options narrow, leverage shifts, costs are paid inside the scene, not deferred to later. A high score means something becomes harder or impossible by the end of the scene that wasn't at the start. A low score means threats are made and pages heat up, but nothing structural changes.
Receipts are how the audience trusts that stakes are real. A scene that promises consequences and never pays them teaches the reader to discount future threats. The fix is to make at least one cost land before the scene ends — a door closes, a relationship shifts, a piece of information becomes public.
A5 — an engine design dimension. The "skip test."
Whether the scene shifts state for the next scene. The diagnostic is the skip test: if you removed this scene, would the next one start differently? If yes, the scene updates. If no, it's removable.
High-update scenes carry forward a binding fact, a commitment, a capability, or a value polarity. Low-update scenes are ornamental — the story would proceed identically without them. The fix isn't always to add an update; sometimes the right answer is to cut or combine scenes that don't earn their slot.
A6 — an engine design dimension. Sometimes called "Strategy Shift."
Whether the center's approach changes in response to pressure. When the first tactic fails, does the character adapt — pivot to a different strategy, escalate, reframe? A high score means visible adaptation under pressure; a low score means one tactic the whole way through, which tends to read as static or passive.
Static centers under pressure are a common diagnostic for first drafts. The character "tries" something for ten pages but doesn't change shape when it doesn't work. The fix is usually a small one: let the first move fail visibly, then let the character try something else.
Note on intentional stuckness. Some scenes deliberately keep the center static — comic stuckness, principled refusal, trauma freeze, character flaw patterns. The system flags these as possible craft bets rather than auto-flagging them as failures.
A7 — an engine design dimension. Sometimes called "Audience Position."
The audience's relation to what's known and unknown in the scene — aligned with the protagonist's POV, ahead of them (dramatic irony), or behind them (mystery). A high score means the audience knows what they're tracking; a low score is "behind-confusion" — the reader can't name what to follow or hope for.
Confusion disengages; named mystery engages. The difference between the two is whether the gap in knowledge is visible. The fix when this is weak is usually to give the reader a question to track even if you're withholding the answer.
P1 — a Moment design dimension (Moment and Conflict + Moment scenes).
Whether the Moment scene's experiential job can be named in one phrase. Reveal, processing, dread, bonding, orientation, plant, tonal contract. A high score means the scene has a single clear intent; a low score means it's doing several weak jobs at once with no anchor.
A Moment scene without a named job tends to dilute everything it touches. The diagnostic question: if you had to describe what this scene does in five words, could you? If the answer takes a paragraph, the scene probably wants a sharper job.
P2 — a payload design dimension. Sometimes called "Builds."
Whether the payload advances rather than repeating the same note. Each beat should change the audience's "what now?" — even when the change is small. A high score means the scene moves; a low score means it cycles, reinforcing what we already know without escalating or shifting.
Atmosphere without progression reads as the scene running in place. Note: progression doesn't have to mean escalation. Baseline-building — making a normalcy specific and usable so later pressure can violate it — counts as legitimate progression too. A calm-before-the-storm beat that anchors a relationship clearly is doing its job, even though nothing dramatic happens within it.
P3 — a payload design dimension. Sometimes called "Earned Length."
Whether the Moment scene's runtime is proportionate to the payload it delivers. A high score means every beat earns its place — you couldn't cut 20% without losing something. A low score means the scene runs longer than the payoff justifies and could be tightened.
Moment scenes that overstay drag the script's pace and make readers stop trusting the writer's economy. The diagnostic is simple: if you cut the middle 30% of the scene, would you lose any of the payload? If no, the scene wants to be shorter.
P4 — a payload design dimension. Sometimes called "Anchored."
Whether the payload alters the baseline for the next time a contest occurs. A high score means characters enter the next Conflict scene differently because of what landed in this Moment. A low score means the payload was atmospheric — nothing carries forward into the next page.
Unanchored payloads are pretty but disposable. They feel like the script took a breath rather than a step. The fix is to make the payload do work for a later scene — change a relationship, plant a fact, shift a posture — so its absence would be visible later.
E8 — an execution dimension.
Whether the page makes important turns read as important — placement, emphasis, compression, white space, reaction beats. A high score means the eye lands on the turns; a low score means the turns are buried in dense blocks or unmarked transitions.
A beat the writer staged but didn't mark on the page is a beat the reader misses. The fix is mechanical: line breaks, isolation, reaction shots, or a single line on its own. The page's typography is doing real work; treat it that way.
E9 — an execution dimension. Sometimes called "Character Expression."
Whether dialogue (or the scene's expressive channel more broadly) performs moves — probe, threaten, concede, deflect, withhold — and carries distinct character voice. A high score means every line is doing tactical work and sounds like its character; a low score means dialogue talks about things rather than doing things.
Note on silent and nonverbal scenes. Active Dialogue is not strictly about speech. Silence, gesture, blocking, behavior, sound discipline, action-as-expression all count as expressive channels. A scene without spoken dialogue can score high if its nonverbal channels carry the work; conversely, a wall of text doesn't score high just because there are lines on the page.
E10 — an execution dimension.
Whether the structural pressure that the scene's design implies actually registers continuously on the page — through proximity, micro-reactions, consequence adjacency, withheld moments. A high score means the reader feels the constraint beat-to-beat; a low score means the page buffers the pressure with safety prose, paragraphing, or stage-direction bloat.
Structural pressure that doesn't register is invisible to the reader. The page craft has to deliver what the design promises. Common fixes: tighten reaction beats, cut buffer prose, move consequences closer to provocations.
E11 — an execution dimension.
Whether the scene uses its runtime efficiently — enters late, exits early, no redundant beats, clean rhythm. A high score means you couldn't cut 20–30% without losing something; a low score means the scene could be tightened by a third without losing state or progression.
Economy is the easiest axis to fix and the most visible to the reader. Most first drafts gain pace from a pure tightening pass that doesn't restructure anything — just trims openings, exits, and middle redundancies.
Missing a term? This page is a living glossary. If there's craft vocabulary you keep running into in coverage or in notes that isn't defined here yet, let us know — we add the ones writers ask about most.