Session notes that survive twenty sessions
Campaign notes fail in a predictable way. For ten sessions everything is findable because you remember it. Around session twelve memory stops covering, you search for the innkeeper, and get forty hits because every session log mentions an inn. The fix is separating capture from structure, rather than taking more notes.
Why the session log stops working
A chronological log is a record of events. That is the wrong shape for the question you actually ask at the table.
You never ask “what happened in session nine”. You ask “who was that merchant”, “what did we agree with the guild”, “has the party been to this city before”. Those are questions about things, and a log is organised by time.
Both are worth having. The mistake is expecting the log to answer the second kind of question.
The two-step loop
Step one, at the table: capture. One line per named thing. A name, three words of context, nothing else.
Brannoc. Fence, Lower Market, owes party a favour
That is the whole note. Writing a proper entry during play costs you the session, and a DM who is typing is not running a game.
Step two, after the session: promote. Fifteen minutes. Anything mentioned twice becomes a real entry. Anything mentioned once stays a line in the log.
The “twice” rule is what keeps the wiki searchable. A campaign wiki with 400 entries where 300 appeared once is functionally identical to no wiki, because search stops discriminating between signal and noise.
What a promoted entry contains
Three fields. Not more.
| Field | Why |
|---|---|
| What they want | Drives every improvised scene they appear in |
| Who they are linked to | The only thing a folder cannot express |
| What the party knows | Prevents you acting on facts nobody was told |
That third field is the one most often skipped and most often needed. Most table confusion comes from the DM treating something as known when the party never heard it, and a “party knows” line heads that off.
Keep three records, not one
The log. Chronological, one entry per session, written for future you. What happened, what changed, what is now owed.
The entries. One per named thing, linked to each other. This is what you search at the table.
The open threads list. A single page of unresolved promises: the favour owed, the letter undelivered, the NPC last seen fleeing. This page is worth more than any other artefact in a long campaign, because it is the one that turns improvisation into a plot.
Most DMs keep the first and skip the third. The open threads list takes one line per thread and is the difference between a campaign that pays things off and one that forgets them.
Where to keep it
The requirement is entries that link and search that works offline or fast. Options are compared in the best D&D campaign management software.
For this specific job:
- Obsidian: best for capture speed and offline use at a physical table. Free for personal use.
- vvd or Kanka: best if the entries should link to a map and be shareable with players. Both have free tiers.
- A notebook: genuinely fine for capture. The promote step still has to happen somewhere searchable.
The test
At session twenty, from a cold start, answer in under a minute:
- Who is Brannoc and what does he want?
- What has the party promised and not delivered?
- Which of the three factions currently believes the party is hostile?
If any of those takes longer than a minute, the promote step is not happening. That step, rather than the capture, is what has failed.
Frequently asked
How should I take notes during a session?
One line per named thing, nothing more. Full entries written at the table cost you the game. Capture names and outcomes; do the structuring afterwards, or the notes will stop happening entirely.
Should players take the session notes?
A rotating player scribe works well and gives you their perspective on what mattered, which is often not what you expected. Keep your own one-line capture alongside it, since the two records answer different questions.
How long should note-keeping take after a session?
Fifteen minutes. If your promote step takes an hour you will skip it, and a loop you skip twice is a loop you have abandoned. Structure the system so fifteen minutes is genuinely enough.
What is the most useful thing to record?
What the players believe, as distinct from what is true. Most table confusion comes from a DM acting on facts the party was never told, and no other note prevents that.