How to submit a TTRPG Session Dossier (and Why)
Chronicle

How to Submit a Campaign Dossier:
If you've filed a dossier and it read back like your recap with some labels stapled on, this is for you — with real examples from Titan's Gate (high fantasy) and SingaporeZ (zombie survival), so you can see the same rule apply across very different tables. The real goal of these fields isn't data entry — it's a habit: thinking about how a session changes the world, not just what happened in it.
Overview vs. Everything Else
Overview is your recap — the narrative, in the order it happened. This part comes naturally to anyone who's run a table; it's just storytelling, and it should read like it.
Everything else on the dossier — Campaign Facts, Location Facts, Stat Tiles, Threat Assessment, Objectives — is not a retelling of the overview. It's the state the session left behind. A different question entirely: not "what happened," but "what's true now that wasn't true before."
Campaign Facts — the wider ripple, not the session recap
Called Campaign Facts in the dossier editor (your campaign's theme may show it under its own flavor name instead — "Court Whispers," "Case Notes," whatever fits the genre — the meaning is the same either way). This is campaign- and party-wide impact: deaths, drop-in players, roster changes, anything affecting the wider world beyond wherever this session actually happened. If Location Facts is "what changed here," Campaign Facts is "what changed everywhere else."
- Titan's Gate: CASUALTIES — "Beren the ranger fell to the Cabal's ambush" · DROP-IN PLAYERS — "Mira's cousin joined for the session, playing a pre-gen rogue"
- SingaporeZ: WIDER WORLD IMPACT — "News of the CC's water contamination is spreading to neighboring districts" · PARTY CHANGES — "Rook left the group to search for his family"
Notice both examples say what changed, not what's always been true. "Ashfen is a farming village" isn't a Campaign Fact — it's backstory, and it belongs in the overview or the world's own lore pages, not here.
Location Facts — this session's impact on THIS place
Use this when the fact is about how the party's actions changed a specific location — not the wider campaign (that's Campaign Facts above), and not a static description of the place either. "Ashfen is a farming village" is backstory; "Ashfen's garrison now distrusts outsiders after the raid" is a Location Fact.
- Titan's Gate: FACTION ATTITUDE — "The Ashfen garrison, wary of the party since the raid" · TRADE STATUS — "Northern trade road reopened after the bandits were cleared"
- SingaporeZ: NPC DISPOSITION — "The CDF checkpoint commander now vouches for the party" · LOCATION STATUS — "Toa Payoh — still blockaded, but the perimeter's thinner at night"
Stat Tiles — numbers worth tracking, some of them campaign-wide
A number plus a short label — same free-text field as always, nothing requires a fixed list. But label a tile to match one of the suggested categories (start typing in the console and they'll autocomplete) and it's automatically summarized on your campaign's Overview page, added up across every session. Anything else still displays fine on its own dossier — it just isn't counted campaign-wide.
The suggested categories lean toward world-state thinking on purpose — NPC Deaths, Locations Visited, Factions Encountered, Major Decisions Made, Settlements Founded/Destroyed, and more, alongside the obvious ones like Sessions Played and Treasure/Gold Earned. Nothing stops you from using a label outside that list whenever a session calls for something specific — it just stays session-only.
- Titan's Gate: 1 — "Locations Visited" (counts campaign-wide) · 12 — "Party Morale" (session-only — not a tracked category, and that's fine)
- SingaporeZ: 1 — "NPC Deaths" (counts campaign-wide) · 6 — "Survivors sheltering at the CC" (session-only)
Threat Assessment — either kind of danger, same meter
A meter with a label and a level (low / medium / high / very-high). It can represent two different things, and both belong in the same list: an ONGOING threat that evolves across sessions (a faction's general danger level, a looming catastrophe), or a threat specific to what happened in THIS session's encounters. Use whichever fits a given row — you don't have to pick one model for the whole campaign.
- Titan's Gate: "Thorne Cabal Influence" (ongoing) — medium, rising since the raid · "Ambush Risk, Old Trade Road" (this session) — high
- SingaporeZ: "Horde Proximity" (this session) — high, breach at the north checkpoint · "Infrastructure Collapse" (ongoing) — medium, worsening each week
The test for any fact/stat/meter: if a player picked up this dossier cold, having missed the last three sessions, would this line help them understand how the world has changed? If yes, it belongs here. If it's just flavor from the story, it belongs in the overview instead.
Objectives — retrospective, not a running wishlist.
This one works the opposite way from how it might look at first: objectives record what the party ATTEMPTED this session and what happened, not a running list of goals you're tracking toward. Mark each Done if it was resolved — successfully or not — this session, Open if it's still unresolved going into the next one. It's a record of attempts and results, not a persistent to-do list.
- Titan's Gate — done, primary: "Find the missing courier" — "Located at the old mill, injured but alive."
- Titan's Gate — open, secondary: "Negotiate with the Thorne Cabal" — "Opened talks, but they walked away from the table."
- SingaporeZ — done, primary: "Restore power to the CC water pump" — "Fuel line secured; pump's running again."
- SingaporeZ — open, tertiary: "Confirm the north checkpoint's status" — "Scouted from a distance; too hot to confirm directly this session."
Why bother — it adds up
Campaign Facts, Location Facts, and matching Stat Tiles aren't just for the one session you write them in. Your campaign's Overview page pulls them together automatically — a running total of Sessions Played, Locations Visited, NPC Deaths, and whatever else you've been tracking, computed fresh every time someone loads the page. Edit or delete a dossier later and the totals update themselves on the next page load — there's nothing to keep in sync by hand.
When You Don't Know, Leave It Blank
This is the one that's easy to get backwards under time pressure. An absent fact is safe — it just means nobody's filled it in yet. A guessed one, stated with confidence, actively misleads whoever reads it next. A wrong "fact" is worse than a missing one, because a missing one at least looks unfinished.
A blank field you fill in next session beats a plausible-sounding invention every time. Nobody's grading you on how complete the dossier looks the night you file it.
Good tables make good stories. Good dossiers just make sure the story is still findable three sessions from now.
— Drafted by Claude (Anthropic's AI assistant), at the webmaster's request. Reviewed by the C&F team before publishing.
About the author

World Builder · Artisan · Architect · Ranger · Drow
True open world games have always appealed the most to him. And Art. What sold it to him was the pretty minis and cool books. He's in it to paint minis.
View Meraj’s profile →