Reusable frameworks

14 Chase Scene Templates

Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.

Use the framework

How to personalize a template

A strong chase scene lets readers track who is pursuing whom, why the pursuit matters, how the environment changes available options, and what each turn costs. The scene ends with a meaningful capture, escape, reversal, loss, or new problem.

  1. 1
    Choose the template closest to your actual purpose.
  2. 2
    Replace every bracketed field with specific information.
  3. 3
    Delete any sentence that does not belong in your situation.
  4. 4
    Read the result aloud for unnatural transitions or repeated phrasing.
  5. 5
    Verify names, dates, links, facts, and promises before sending or publishing.
Chase Scene Template 1
Chase map
Pursuer: [x]
Pursued: [x]
Starting positions: [x]
Exit/end condition: [x]
Key obstacles: [x]
Result: [x]
Chase Scene Template 2
Chase escalation
Beat 1 option: [x]
Obstacle/change: [x]
Beat 2 option: [x]
Cost: [x]
Reversal: [x]
Chase Scene Template 3
Continuity check
Distance: [x]
Direction: [x]
Injuries/resources: [x]
Who can see whom: [x]
Available exits: [x]
Chase Scene Template 4
Generic → specific chase
Generic line: [x]
Specific terrain: [x]
Specific tactic: [x]
Consequence: [x]
Revised beat: [x]
Chase Scene Template 5
Evidence/support and mastery ladder for Chase Scene: minimum acceptable → [ ]; strong → [ ]; expert → [ ]; audience/genre constraint → [ ]; evidence or story support → [ ]; boundary that would require a different technique → [ ].
Chase Scene Template 6
Certainty and expert-exception audit for Chase Scene: statement or choice → [ ]; evidence/canon/authority supporting it → [ ]; confidence level → [ ]; uncertainty that must be named → [ ]; expert exception → [ ]; nearest alternative technique → [ ]; why the final choice fits better → [ ].
Chase Scene Template 7
Purpose-and-verification decision audit for Chase Scene: real writing job → [ ]; plausible choice A → [ ]; plausible choice B → [ ]; downstream consequence of each → [ ]; facts/evidence/canon to verify → [ ]; reader or genre boundary → [ ]; final purpose-fit reason → [ ].
Chase Scene Template 8
Publication-readiness audit for Chase Scene: claim/advice/example → [ ]; strongest available source tier → [ ]; important disagreement or uncertainty → [ ]; what would change the conclusion → [ ]; publish now / qualify / revise / hold → [ ]; final verifier or source of truth → [ ].
Chase Scene Template 9
Provenance and classification audit for Chase Scene: draft statement/example → [ ]; classify as fact / interpretation / recommendation / convention / original example → [ ]; source or internal provenance → [ ]; source date / version / checked date → [ ]; attribution needed → [ ]; recency risk → [ ]; final publishable wording → [ ].
Chase Scene Template 10
Source-record and update audit for Chase Scene: statement / example → [ ]; external fact, project fact, interpretation, recommendation, convention, or original example → [ ]; controlling first-party / primary source → [ ]; secondary source if used → [ ]; source record / locator → [ ]; date or version checked → [ ]; update trigger → [ ]; publish / qualify / revise / hold → [ ].
Chase Scene Template 11
Source-ledger and revision-history audit for Chase Scene: claim / recommendation / example → [ ]; source or project record ID → [ ]; source status active / superseded / corrected / retracted / retired → [ ]; claim-level last verified date/version → [ ]; event that triggered recheck → [ ]; correction / withdrawal action → [ ]; reader-facing disclosure needed? → [ ]; what changed and why → [ ]; prior wording/version retained at → [ ].
Chase Scene Template 12
Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].
Chase Scene Template 13
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
Chase Scene Template 14
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].