Audit what the scene does, not whether it resembles a preferred formula.
A scene can be quiet, atmospheric, comic, exploratory, or reflective and still be functional. The target is unproductive narrative time, not low action.
Core Questions
For the supplied scene determine:
- Why does this scene exist?
- Who wants what during it?
- What prevents immediate success?
- What changes because the scene occurs?
- What would be lost if the scene were removed?
Function Categories
Tag all relevant functions, then identify the primary one:
- plot advancement
- character revelation
- relationship development
- setup
- payoff
- revelation
- choice
- consequence
- worldbuilding
- tutorial
- mood / atmosphere
- pacing relief
- escalation
- transition
A scene with many claimed functions may still have no dominant dramatic purpose.
Entry / Exit Audit
Describe the meaningful state before and after.
Track when relevant:
- goal
- relationship
- trust
- power
- knowledge
- danger
- commitment
- resources
- location
- quest state
- emotional state
If entry and exit are materially identical, ask whether atmosphere, characterization, or pacing value justifies the scene.
Dramatic Engine Audit
Check:
- clear local objective
- credible resistance
- changing tactics
- increasing or transforming pressure
- turn or decisive beat
- outcome
Do not require every scene to contain every element. Flag only missing elements that make the scene feel inert or redundant.
Exposition Audit
Identify information delivered in the scene and ask:
- Does a participant have a reason to say it?
- Does the audience need it now?
- Is it new?
- Is it dramatized through conflict, choice, discovery, or consequence?
- Is the same information already available elsewhere?
Classify exposition as:
- necessary and active
- necessary but inert
- premature
- redundant
- implausibly delivered
Redundancy Audit
Look for repeated functions across nearby scenes.
Examples:
- three scenes establishing the same mistrust
- repeated reminders of a known goal
- multiple conversations that all resolve to “we must go there”
- a cutscene restating information the player just learned through play
Suggest consolidation only when it preserves needed pacing and characterization.
Scene Economy
Estimate what the scene costs in:
- writing
- VO
- cinematics
- animation
- unique location / staging
- branching variants
- quest implementation
A high-cost scene should generally carry proportionate narrative or experiential value.
Do not reduce narrative worth to production efficiency; expose the tradeoff.
Finding Types
Use:
- No clear primary function
- Weak or absent state change
- Passive protagonist
- Soft resistance
- Repeated tactic
- Flat escalation
- Unclear turn
- Exposition overload
- Redundant information
- Redundant neighboring function
- Unearned reversal
- Missing consequence
- High production cost / low unique value
- Strong quiet scene — explicitly recognize when low-action content is doing useful work
Severity
- High — scene's purpose or causal role is unclear; likely produces pacing or comprehension problems.
- Medium — scene works but contains structural drag or a missing beat.
- Low — optimization opportunity, not a failure.
Report confidence separately.
Audit Procedure
- Summarize the scene literally in 1–3 sentences.
- Identify claimed and actual functions.
- Establish entry and exit states.
- Identify the local goal and resistance.
- Locate tactic changes and escalation.
- Identify the turn and outcome.
- Audit exposition and redundancy.
- Consider production cost if relevant.
- Rank only material findings.
- Suggest the smallest repair category instead of rewriting.
Repair Categories
- sharpen objective
- strengthen resistance
- change tactic
- add pressure
- move revelation
- create a turn
- add consequence
- remove repeated exposition
- combine scenes
- relocate setup
- convert exposition into discovery or action
- cut scene
- keep scene; function is already strong
Output
Begin with:
Scene verdict: strong / functional with issues / weak / probably redundant
Then report:
Primary function
Entry → exit state
Dramatic engine
Material findings
| Location / beat | Finding | Why it matters | Severity | Confidence | Smallest fix |
|---|
Cut test
What specifically disappears if this scene is removed?
Strong elements
Call out useful structural work, especially quiet characterization or setup that could be mistaken for inactivity.
Failure Modes
Avoid:
- demanding action in every scene
- assuming every scene needs a twist
- treating exposition as inherently bad
- optimizing away emotional breathing room
- rewriting before diagnosing
- flagging stylistic taste as structural failure
- evaluating a scene without surrounding context when the user supplied it
Final Quality Check
Verify that every finding is tied to function, causality, state change, pacing, comprehension, or production cost rather than personal taste.