Campaign continuity guide · July 15, 2026

How to turn a TTRPG recording into a campaign wiki

The useful workflow is not “record, summarize, done.” A long-running campaign needs a trustworthy path from raw conversation to reviewed chronicle, persistent entities, source-linked facts, and portable campaign memory.

The short version

Record with consent, produce a speaker-labeled transcript, create a chronological recap, extract persistent campaign records, resolve uncertain identities, review every canon-changing proposal, and export the approved result in a portable format.

Step by step

A practical session-to-wiki workflow

  1. 01

    Get the table's consent

    Tell every participant what will be recorded, why it is being processed, who can access the result, and when the audio will be deleted. Make it easy for anyone to decline.

  2. 02

    Capture clear audio

    Place one microphone near the center for an in-person game, or record separate aligned tracks online when your tools allow it. Reduce music bleed and overlapping side conversations.

  3. 03

    Create a speaker-labeled transcript

    A useful transcript keeps utterances in order and identifies speakers consistently. Do not worry about correcting every word before analysis; prioritize names and consequential facts.

  4. 04

    Generate a session chronicle

    Summarize events in sequence, including decisions, discoveries, consequences, unresolved threads, and the state of the party at the end.

  5. 05

    Extract persistent campaign records

    Identify recurring people, places, items, factions, lore, quests, events, and mysteries that should remain useful after the recap is forgotten.

  6. 06

    Resolve identities before merging

    Compare new names and aliases with the existing wiki. A similar spelling is evidence for review, not permission to merge two characters automatically.

  7. 07

    Review proposed canon

    Show the current page, proposed change, source session, and reason for the update. Let the game master accept, reject, create a new page, or keep identities separate.

  8. 08

    Export and back up

    Keep the approved campaign in a portable format such as Markdown with stable links and structured metadata. Test the export before depending on it.

Quality control

What should never happen silently

  • A low-confidence name becomes a new NPC automatically.
  • Two similar characters merge without review.
  • A generated inference is presented as transcript evidence.
  • Manual campaign writing is overwritten by an AI update.
  • A partial analysis looks like a complete result.
  • A destructive change has no recovery path.

Recap versus memory

Do not force one document to do every job.

A recap should be enjoyable to read. A campaign wiki should be easy to query and maintain. A transcript should preserve evidence. A review should expose uncertainty. Keeping those jobs connected but distinct makes the system more trustworthy.

The resulting campaign should answer:

  • What happened last time?
  • What is true now?
  • What changed and when?
  • Which source supports it?
  • What remains unresolved?

Where Everlore fits

Everlore is being built around this session-to-canon workflow: audio or transcript in, readable chronicle and campaign discoveries out, followed by game-master review and portable Markdown export.

Explore Everlore's campaign-memory workflow

Your table plays. Everlore remembers.

Turn the next session into useful campaign memory.

Join the private-beta waitlist