Reusable frameworks

13 Reunion 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 reunion scene does not assume every reunion is joyful or cathartic. It establishes the separation, stakes, current relationship, recognition beat, first exchange, conflicting expectations, and an exit condition that changes the story.

  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.
Reunion Scene Template 1
Reunion beat map\nSeparation: [x]\nExpectation A/B: [x]\nRecognition: [x]\nFirst exchange: [x]\nMismatch: [x]\nChanged condition: [x]
Reunion Scene Template 2
History without dump\nShared past detail: [x]\nPresent trigger: [x]\nAction/dialogue reveal: [x]\nWhat remains unsaid: [x]
Reunion Scene Template 3
Generic reunion → specific\nGeneric: They hugged emotionally.\nRelationship history: [x]\nPresent constraint: [x]\nRevision: [x]
Reunion Scene Template 4
Boundary check\nExpected contact: [x]\nActual response: [x]\nConsent/comfort cue: [x]\nNext beat: [x]
Reunion Scene Template 5
Certainty and expert-exception audit for Reunion 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 → [ ].
Reunion Scene Template 6
Purpose-and-verification decision audit for Reunion 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 → [ ].
Reunion Scene Template 7
Publication-readiness audit for Reunion 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 → [ ].
Reunion Scene Template 8
Provenance and classification audit for Reunion 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 → [ ].
Reunion Scene Template 9
Source-record and update audit for Reunion 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 → [ ].
Reunion Scene Template 10
Source-ledger and revision-history audit for Reunion 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 → [ ].
Reunion Scene Template 11
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].
Reunion Scene Template 12
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].
Reunion Scene Template 13
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 → [ ].