Multiple-Locations Scene Template 1
Location chain\nStart: [x]\nObjective: [x]\nLocation 1 → reason to leave: [x]\nLocation 2 → new constraint: [x]\nLocation 3 → new opportunity: [x]\nEnd-state: [x]
12 Multiple-Locations 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 multi-location scene treats movement as part of the scene rather than a series of unexplained teleports. The reader can identify the current location, what changed during the transition, how much travel matters, and why the next place creates a new opportunity, constraint, audience, or consequence.
- 1Choose the template closest to your actual purpose.
- 2Replace every bracketed field with specific information.
- 3Delete any sentence that does not belong in your situation.
- 4Read the result aloud for unnatural transitions or repeated phrasing.
- 5Verify names, dates, links, facts, and promises before sending or publishing.
Multiple-Locations Scene Template 2
Continuity anchor\nObject/information/deadline: [x]\nWho carries/knows it?: [x]\nWhat changes in transit?: [x]\nWhat must remain consistent?: [x]
Multiple-Locations Scene Template 3
Travel compression\nDeparture cue: [x]\nEssential transit detail: [x]\nElapsed-time cue: [x]\nArrival consequence: [x]
Multiple-Locations Scene Template 4
Location audit\nCurrent place always clear? [ ]\nTravel plausible? [ ]\nCharacter positions tracked? [ ]\nWeather/time continuity checked? [ ]\nEach place changes the scene? [ ]
Multiple-Locations Scene Template 5
Purpose-and-verification decision audit for Multiple-Locations 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 → [ ].
Multiple-Locations Scene Template 6
Publication-readiness audit for Multiple-Locations 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 → [ ].
Multiple-Locations Scene Template 7
Provenance and classification audit for Multiple-Locations 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 → [ ].
Multiple-Locations Scene Template 8
Source-record and update audit for Multiple-Locations 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 → [ ].
Multiple-Locations Scene Template 9
Source-ledger and revision-history audit for Multiple-Locations 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 → [ ].
Multiple-Locations Scene Template 10
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].
Multiple-Locations Scene Template 11
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].
Multiple-Locations Scene Template 12
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 → [ ].