Cliffhanger Template 1
Reveal ending: [expected result]. Then [specific contradictory fact].
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.
A strong cliffhanger gives readers the information the viewpoint has earned, stops after a real turn, creates a precise continuation question, and receives timely progress or payoff instead of relying on arbitrary interruption.
Reveal ending: [expected result]. Then [specific contradictory fact].
Decision ending: [Character] must choose between [option A] and [option B] before [deadline/consequence].
Arrival ending: [Character reaches goal/location] and discovers [new condition that changes the objective].
Question ending: Provide enough evidence to make readers ask one precise question, not a vague “what happens?”
Source-ledger and revision-history audit for Cliffhanger: 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 → [ ].
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].
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].
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 → [ ].
Cliffhanger boundary card Unit ending: [scene/chapter/installment] Changed state earned before cut: [ ] Concrete unresolved pressure: [ ] What the viewpoint legitimately knows: [ ] What remains unknown: [ ]
Payoff-before-pivot check Question resolved in this unit: [ ] New question created by that answer: [ ] Why the new question matters: [ ] Is the cut after meaningful progress?: [ ]
Withholding fairness test Information character currently perceives: [ ] Information narration reveals: [ ] Information delayed: [ ] Causal reason for delay: [ ] Artificial concealment present?: [ ]
Ending-shape variation map Previous chapter ending: [ ] Current ending shape: [revelation/decision/danger/contradiction/cost] Next planned ending: [ ] Repeated pattern to avoid: [ ]
Cliffhanger payoff distance Promise created: [ ] First progress toward answer: [ ] Full/partial payoff location: [ ] What readers receive before another delay: [ ]
Final-book cliffhanger audit Current-book core promise: [ ] Paid in full?: [ ] Series question left open: [ ] Does the open thread cancel closure?: [ ] Revision if trust cost is too high: [ ]
Scene-structure prerequisite Immediate goal: [ ] Resistance: [ ] Turn: [ ] Changed exit state: [ ] Exact stopping point after the turn: [ ]
Quiet cliffhanger design Relationship/decision/question under pressure: [ ] Small but consequential change: [ ] Why continuation matters without physical danger: [ ] Last concrete beat: [ ]