How to take D&D session notes your players will actually read
A short, repeatable structure for session logs — what to record, what to leave out, and how to stop note-taking from competing with playing.
Most session notes die for one of two reasons. Either they are so thin that they answer nothing later — "fought goblins, went north, Dave levelled" — or they are so thorough that writing them stops being worth it, and the run ends after three weeks.
The version that survives a campaign is short, structured identically every time, and written somewhere the whole table can see. Structure is what does the work: when every log has the same shape, writing one becomes filling in a form rather than composing an essay, and reading thirty of them becomes possible.
Write five things, not everything
You are not producing a transcript. You are leaving your future self, and everyone else at the table, enough to reconstruct the state of the world.
Who they met, and what those people wanted. Names are the highest-value thing in any session log. They are what people search for months later and the first detail everyone forgets. A name with a one-line motive attached is worth a paragraph of description.
What the party promised or owes. Debts, favours, threats and bargains are what make a campaign feel continuous rather than episodic. They are also the first things to quietly evaporate if nobody writes them down, usually at the exact moment they would have been most satisfying to call back to.
Where they went, and what changed there. A location that is different from the last time the party saw it is a plot hook you have already paid for.
What is still open. End every log with a short list of unresolved questions. This is the single most useful thing you can hand yourself at the start of the next prep session, and it takes about ninety seconds.
What the players believe. Not what is true — what they currently think is true. The gap between those two is where most of the interesting play lives, and tracking it deliberately is how you notice when a reveal has stopped landing or a red herring has taken over the campaign.
Stop making it one person's job
The most reliable fix for session notes is structural rather than motivational: share the work.
When the log is a note the whole table can edit, people specialise without being asked. Someone catches names, someone tracks loot and money, someone remembers the exact wording of the promise the party made. Nobody has to choose between playing the game and transcribing it, which is the trade that kills most note-taking habits.
This is also the argument for writing the log during the session rather than afterwards. Reconstructing four hours from memory the next day is a real chore. Adding a line as it happens is nearly free — but only if everyone can write into the same place at once and see each other's additions.
Keep the secrets in the same file
The usual reason a DM does not simply share their notes is that the notes contain the answers. So the group ends up with a public log and a private one, and the moment those two drift apart the shared one stops being trustworthy.
The better arrangement is one log where visibility is set per note. The parts that describe what happened are shared with the table; the parts that explain what was actually going on are DM-only, sitting in the same structure, revealed when the reveal happens.
In Dungeon Ledger that filtering happens on the server, so a player's browser never receives the content of a hidden note. You are not managing a risk — the hidden part is genuinely not there until you change one setting.
Link the log to the things it mentions
A pile of session logs is an archive. A pile of session logs that link to the NPCs, locations and quests they mention is a reference.
The difference shows up around session fifteen, when someone asks who the party met in the port town and you can open the note for that town and see every session it appeared in. Making the link takes a second while writing; recovering the connection later without it takes ten minutes of scrolling.
That is also what turns a run of logs into a campaign wiki without anyone ever sitting down to build one.
A template worth reusing
Something close to this, every week:
- Present: who played
- Recap: two sentences, no more
- Met: names, with a clause each
- Did: what actually happened, in bullets
- Owe / owed: promises, debts, threats
- Changed: anything different about the world
- Open: unresolved questions for next time
- DM only: what the players got wrong, and what is coming
The last line is the one that makes the whole thing work. It is also the one you should never keep in a document your players can open.