How to Organize Your D&D Campaign Notes (a System That Survives Session 40)

Session 23 of my longest campaign, a player asked me the name of the fence who owed the party money. We'd met him in session 8. I spent four full minutes flipping through a notebook while my table checked their phones, and when I finally found him, the entry read, in its entirety: 'fence guy, shifty, owes them'. His name was Corvo. The notebook had never known it either.

That night sent me down the long road of learning how to organize DnD campaign notes properly, and this article is the whole system, free, complete, and usable tonight with a pen or any app you already own. We have all lost a Corvo. The fix is smaller than you'd think.

Why Campaign Notes Fall Apart

Every note system I have ever seen failed in one of three ways.

The notebook fills beautifully and becomes unsearchable. Around session 20 it holds everything and retrieves nothing, because the only index is your memory of roughly when something happened, and 'roughly when' is exactly what memory drops first.

The doc graveyard grows one file at a time, each created in a moment of optimism. My worst campaign folder held 31 documents, including one named NPCs FINAL v2 ACTUAL, and the thing I needed was reliably four files deep in a different document than the one I was sure held it.

And the wiki starts as a cathedral and stops getting updated in week three, because a wiki asks for an article when what you have after a session is a tired brain and six scraps. None of these are discipline failures. All three systems ask for more than a weekly game can sustain, and the fix is a system that asks for less.

What to Actually Capture (and What to Let Go)

The instinct after a great session is to write everything down, and the instinct is wrong in a specific way: a good note is written to be read again, and a transcript is written to be filed. I once typed three pages per session for an entire campaign, a beautiful chronicle of who said what to whom. In two years of play I consulted it once, to settle a bet.

Four things earn their place in a campaign journal, because they are the four things a future session will actually ask for:

• NPC names, with one identifying detail and one want. 'Corvo, fence, gold tooth, wants his cousin out of prison' will serve you for years.

• Promises made, by the party and to the party. Promises are the load-bearing beams of long campaigns, and forgotten ones are how trust quietly leaks out of a game.

• Threads dangled, every hook you offered, regardless of whether anyone bit. Players circle back to session-5 mysteries in session 30, and the DM who can answer looks like a genius.

• Consequences owed, what the world will do next because of what just happened. This is the note that writes your next session for you.

Everything else, the blow-by-blow of fights, the verbatim jokes, the marching order, can go. If it mattered, it will have left a mark in one of the four categories above.

A Note Structure That Survives Session 40

Here is the idea this whole article hangs on: organise by threads, and let chronology go. It turns out the best way to organize a DnD campaign follows from one observation about how questions arrive at the table. Nobody mid-session asks what happened on the 14th of March. They ask what we know about the cult, whether the duke still owes us, and who that woman at the funeral was. Questions arrive shaped like storylines, so notes filed by storyline answer them instantly, and notes filed by date answer them after four minutes of flipping while your table checks their phones.

The structure has two layers. Session notes are the inbox: one page per session, quick and disposable, filled in the ten minutes after play. Thread pages are the filing: one page per active storyline, the cult, the debt, the missing sister, and each holds four short sections. Current state. What the party knows. What is actually true. What likely happens next.

The whole trick is a two-minute transfer: after each session, anything on the session page that matters gets one line added to the relevant thread page. The session page can then be forgotten forever, because everything it held now lives where the questions will look for it. Six to eight thread pages cover most campaigns, threads close and new ones open, and page one is always a single index listing the active threads so the entire system stays visible at a glance.

The 10-Minute Post-Session Routine

A system only survives if the upkeep fits inside the tired twenty minutes after your players leave. Here is the whole ritual, and here is the DnD campaign notes template it feeds, five boxes on one page:

The routine, with the kettle on:

• Minutes 1 to 2: write the one-line summary while the session is still warm. If you can't compress the night into a sentence, write the two moments everyone will remember.

• Minutes 3 to 6: fill Threads touched, then walk each line over to its thread page and update Current state. This is the transfer step, and it is the entire reason the system works.

• Minutes 7 to 8: Promises made and NPCs met. Names first, always. Future you does not need eloquence, future you needs Corvo.

• Minutes 9 to 10: Consequences now live. Write what the world does next in response to tonight, because this box is half of next week's prep done early. (The other half is the campaign itself, which our guide to writing a D&D campaign covers end to end.)

Ten minutes, once a week. I have kept this routine through two campaigns and a house move, which is more than I can say for any gym habit I've attempted.

Finding Anything Mid-Session

The standard I hold my notes to is the 10-second rule: any fact the table asks for should surface in ten seconds, and if it takes longer, the system failed rather than me. That framing matters. A failed lookup means a page is filed wrong or a thread page has grown bloated, and both are ten-minute fixes, where blaming your own memory fixes nothing.

Three habits keep lookups under the limit. Open the relevant thread pages before the session starts, since you usually know which storylines are in play tonight. Keep a single running names list, every NPC ever, one line each, because half of all mid-session questions are just 'who was that again'. And start each session page by copying forward last week's Consequences box, so the night's most likely callbacks are already sitting at the top of the page in front of you.

Tools Compared Honestly

Paper is fast, personal and pleasant, and it never needs charging. The thread structure works in any notebook with tabs or a few sticky dividers. Its honest limit is search: past a certain campaign length you are trusting your filing absolutely, because there is no ctrl-F to rescue you, and shared access for players means photographing pages.

Google Docs costs nothing and syncs everywhere. One doc per thread plus one per session, all in a folder, gives you the full system with search on top. The trade-off arrives slowly: docs multiply, links between them are manual, and around the thirty-file mark you are maintaining the graveyard from section one, just a searchable one.

Notion and Obsidian reward setup appetite. Both hold the thread structure beautifully, Notion with linked databases and Obsidian with local markdown and backlinks, and both can grow into exactly the tool you want. The cost is the weekend you spend building it and the ongoing temptation to tinker with the system instead of writing the notes.

Dedicated campaign planners trade flexibility for structure that already matches the job. Ours, Dungeon Weave, is built around exactly the thread-first idea in this article, with story nodes as the spine and actions, encounters and consequences attached to them, ahead of time. In fairness, it carries the limitations we've written about before: it is newer than everything above, and there is no worldbuilding wiki. Whichever planner you look at, the test is the same: does it file things the way your table asks questions?

FAQs

What should D&D session notes include?

Five things, matching the template above: a one-line summary, the threads that moved, promises made, NPCs met with a name and a want, and the consequences now in motion. Good DnD session notes fit on one page, and anything longer is usually a transcript wearing a disguise. When in doubt, ask whether a future session could possibly need the fact; if no question at the table would ever retrieve it, it can go.

Should I share notes with my players?

Share a version. A short recap of the one-line summary and the public-facing threads keeps everyone aligned and rescues whoever missed a week, and plenty of tables have a player who loves writing it. Keep the thread pages private, though, since they contain the gap between what the party knows and what is actually true, and that gap is where your campaign's tension lives.

Digital or paper?

Whichever one you will still be using in month six, honestly. Paper wins on speed and feel, digital wins on search and sharing, and the thread structure works identically in both. The only wrong answer is the tool you admire but avoid opening. If you genuinely can't choose, run paper at the table for speed and do the ten-minute routine digitally afterwards, which quietly gives you the best of each.

How do I catch up if my notes are already a mess?

Skip the archaeology. Reconstructing twenty sessions from scraps is a job nobody finishes, so start the system from tonight instead: spend one evening writing thread pages for the storylines currently active, from memory, which is easier than it sounds because you remember more than you think. The old notes stay as an archive to consult when a specific question sends you back. Two sessions from now the new system is carrying everything, and the mess stops mattering.

Or Skip the System-Building

Everything above works with a pen and a Tuesday evening, and it will genuinely carry a campaign for years. If you would rather have the thread-first structure already built, with the transfer step and the consequences tracking done for you, that is the entire design of Dungeon Weave, and it's free to start. Either way, file by threads, keep the ten-minute ritual, and may you never lose another Corvo.