How to Take Campaign Notes You Will Actually Use
Why Campaign Notes Fail
Most campaign notes are write-only. They get produced in good faith, session after session, and are never read again, because they were organized for the person writing them (chronologically, as a diary) instead of for the person who needs them: you, mid-session, while four players wait and someone asks what the smuggler promised them in exchange for the ledger.
The other way notes die is over-engineering. Full campaign wikis are magnificent right up until week six, when the maintenance debt exceeds the prep time and the whole structure gets abandoned. The fix for both failures is the same: build notes around retrieval, and keep the system light enough that a tired DM maintains it at midnight.
The Retrieval Test
Hold every note-taking habit against a single standard: if you cannot find a fact within ten seconds at the table, your notes failed that fact. This test is clarifying because it immediately devalues the things note systems overinvest in (polish, completeness, formatting) and elevates the things that matter: names, one-line facts, and a structure you can scan under pressure.
Capture Five Things During Play
During the session, your notes have one job: catch what just became true. Five categories cover it.
- Names dropped: every NPC, place, or thing you improvised a name for. If you do not write it down, the tavern keeper has a different name next visit and the players will notice.
- Promises made: by NPCs to the party and by the party to NPCs. Broken promises are plot; forgotten ones are continuity errors.
- Treasure given: what, to whom, and roughly what it is worth. Loot disputes are the most common table argument that notes can simply delete.
- Threads opened: the hook they ignored, the door they did not open, the letter they did not read. These are your future sessions.
- Facts established: anything you said about the world that players might test later. "The duke has no children" is canon the moment it leaves your mouth.
Each entry is a fragment, not a sentence. "Bell, half-elf fence, docks, owes party" is a complete during-play note.
Organize by Entity, Not by Session
A session log answers "what happened on March 12th?", a question nobody at your table has ever asked. Real questions are entity-shaped: who is this NPC, what do we know about this town, what does this faction want. So the durable home for your notes is one small page per entity, and the session log is just the inbox those pages get updated from.
Link entities to each other as relations, not paragraphs: Bell works for the Grey Quill, the Grey Quill operates out of Millhaven, Millhaven owes fealty to the duke. Three links replace a paragraph and can be followed in either direction at speed.
The Ten-Minute Recap Ritual
Within a day of each session, while it is still cheap to remember, do three things: move the five-category captures from the scratchpad onto their entity pages, write a three-sentence recap of the session, and list the open threads. Ten minutes, then stop. This small ritual is the entire difference between notes that compound and notes that rot; skipping it twice in a row is how every abandoned note system began.
Where the Session Notebook Fits
The tools on this site are built around exactly this workflow. Anything you generate (an NPC, a shop, a settlement, a loot hoard) pins to the Session Notebook in one click, which handles the capture half automatically: the generated details are already on the card, so your note is just why it matters. Entries group into sessions, relations wire NPCs to places and factions, the Campaign Timeline holds event order, and the In-World Calendar tracks fictional dates. The Session Recap Generator turns your session beats into a read-aloud recap, which makes the ten-minute ritual closer to five.
Everything lives in your browser: free, no account, no server copy. That also means your browser storage is the single copy, so treat an export as part of the ritual for any campaign you care about. For how generated content becomes campaign canon in the first place, read How to Use Random Generators in Your D&D Campaign.
Frequently Asked Questions
- Are digital or paper notes better for D&D?
- Whichever you can search mid-session without breaking the scene. Paper wins for capture speed during play; digital wins for retrieval a month later. Many DMs use both: a paper scratchpad at the table, transcribed into a searchable digital home within a day.
- I have three years of messy campaign notes. Should I reorganize them?
- No. Index forward, not backward. Start entity pages today for the NPCs, places, and factions that are currently active, and only mine the old notes when something specific becomes relevant. A retroactive cleanup project is how note systems die.
- How much detail does each NPC note need?
- One line at first: name, role, where met, and the one thing that makes them memorable. Grow the entry only when the NPC recurs. Notes should be paid for by play, not written on speculation.
- Should my players keep their own notes?
- Encourage one shared source of truth instead: a short recap the table can see, with the names spelled correctly. Player memories diverge wildly, and re-litigating what an NPC promised three sessions ago is the exact failure good notes prevent.
- How do I track campaign time and event order?
- Separate the two jobs. A timeline records what happened in play order; an in-world calendar records when it happened in the fiction. Keeping them distinct means you can answer both "when did we meet her?" and "how long has the ritual been running?" without cross-referencing.