The Lazy DM's Guide to Campaign Documentation

The Problem: You Can't DM and Take Notes at the Same Time

We've all been there: mid-combat, a player asks about an NPC from session 4, and you're frantically flipping through notes that don't exist. Or worse — you're trying to scribble something down about a brilliant improvised plot twist while simultaneously describing a dragon's lair and tracking initiative order. Something's gotta give, and it's usually the notes.

Here's a truth that doesn't get said enough: the act of running the game and the act of documenting the game are fundamentally at odds. DMing demands presence. You're voicing NPCs, tracking hit points, reading the table's energy, improvising when players go wildly off-script — which they always do. Note-taking demands stepping out of that flow, switching from performer to secretary, and hoping you can jump back in without losing the thread. Cognitive psychology calls this "task switching," and research consistently shows it degrades performance on both tasks. You're not bad at note-taking. You're just being asked to do two jobs at once.

The numbers tell the story. According to Sly Flourish's DM survey of over 6,600 dungeon masters, 69% of DMs spend fewer than three hours prepping each week. About a third spend three hours or more preparing for a single four-hour session. That prep time goes to maps, encounters, NPCs, and plot hooks — not post-session documentation. After pouring that much energy into the game itself, asking DMs to also maintain a meticulous campaign log is how you get burnout.

And burnout is everywhere. Browse any D&D community — Reddit, D&D Beyond forums, Discord servers — and you'll find a new "I'm burning out" post practically every day. DungeonSolvers puts it bluntly: if you DM long enough, you will almost certainly experience burnout at some point. Over-preparation is one of the most commonly cited triggers, and documentation guilt — the nagging feeling that you should be writing things down but aren't — is a sneaky contributor. The game is supposed to be fun. The paperwork is the part nobody signed up for.

So what's the move? You do less. You do it smarter. And you stop feeling guilty about the notes you're not taking during the game.

The Lazy DM's Principles

If you've read Mike Shea's Return of the Lazy Dungeon Master, you already know the philosophy: focus on what matters, omit what doesn't. Shea's eight-step prep method is designed to get you ready for a session in about 30 minutes, focusing on improvisation fuel rather than scripted plans. The same mindset applies to documentation. You don't need a transcript. You don't need a blow-by-blow combat recap. You need the stuff that will matter next session.

Three core principles underpin every method in this guide:

1. Less is more. A five-bullet summary beats a five-page session log. You'll actually read the bullets. You'll never re-read the log.
2. Delegate. You are not the only person at the table. Players can — and should — share the documentation load. As The Angry GM argues, having players do the recap isn't laziness; it's smart design that also reveals what your table actually remembers and cares about.
3. Automate where it makes sense. If a tool can handle the grunt work, let it. Your creative energy is better spent on the game.

Here are five methods, from lowest-effort to most automated. You don't need all five. Pick one or two that fit how your table plays.

Method 1: The 10-Minute Post-Session Dump

The single best habit you can build as a DM is spending ten minutes after the session — not during — writing down what happened. Close the books, say goodnight to the players, and before you do anything else, open a doc or grab a notebook and dump everything you remember.

This works because of how memory consolidation functions. Psychologist Hermann Ebbinghaus demonstrated that people forget roughly 70% of new information within 24 hours if they don't actively review it. But the flip side is powerful: even a brief review immediately after the experience dramatically improves retention. Those ten minutes right after the session are worth more than an hour of note-taking the next day.

Keep it to bullet points. You're not writing prose. You're jotting down:

• NPCs introduced or referenced (names and one-line descriptions)
• Key decisions the party made
• Plot hooks planted or followed up on
• Unresolved threads and loose ends
• Anything you improvised that you need to remember (a shop name, a guard's accent, a promise an NPC made)

The Angry GM's "Post-Play Pre-Prep" method follows this exact philosophy. He starts his prep the day after the game session, and the first step is always making a short list of what actually happened — rarely more than a few bullet points. At most game sessions, there are only one or two events worth actually retaining. Everything else is atmosphere, combat rounds, and jokes about the bard's poor decisions.

Time cost: 10 minutes, once per session. No effort during the game.

Method 2: The Player Recap Rotation

You know what's better than taking notes yourself? Making someone else do it. Specifically, your players. The Player Recap Rotation means each session starts with a different player summarizing what happened last time — the "Previously on..." moment — and that player rotates every session.

This does three things at once. First, it takes documentation off your plate entirely. Second, it reveals what the players actually remember and care about, which is invaluable intel for your prep. If nobody remembers the political intrigue subplot but everyone remembers the talking cat, that tells you something. Third, it's genuinely good for memory. Research in cognitive psychology shows that active recall — forcing yourself to retrieve information from memory rather than passively rereading it — strengthens retention significantly.

Many DMs sweeten the deal with a small reward. Hand out Inspiration to whoever volunteers for the recap. It's one of the most commonly cited engagement tricks in DM communities, and it works: a tiny mechanical incentive turns a chore into a mini-competition. "I'll do the recap!" becomes something players actually say.

A variation that works for longer campaigns is the written recap. Instead of a verbal summary at the table, the designated player posts a short write-up in your group's Discord channel or shared doc before the next session. Some groups turn this into an in-character journal entry — the rogue's field notes, the cleric's prayers, the bard's tavern song — which adds flavor while still serving as documentation. The Friendly Bard recommends keeping these "short and sweet" — a few lines covering who you talked to, what you agreed to do, and any unresolved questions.

Time cost for the DM: Zero. Time cost per player: 10-15 minutes every few sessions.

Method 3: The Living Bullet Journal

Some DMs don't want a session-by-session log — they want a running reference document they can ctrl+F when they need to remember something. The Living Bullet Journal is a single, evolving document organized not by session, but by category: NPCs, locations, factions, decisions, and open hooks.

Think of it as the world's simplest campaign wiki, maintained in a Google Doc or Notion page. Every time something new enters the campaign — a new NPC, a new location, a faction reveal — it goes into the appropriate section. Not a paragraph. A line. "Marta — halfling innkeeper in Greyhaven, knows about the catacombs, owes the party a favor." That's enough.

The beauty of this approach is that it's cumulative, not repetitive. Session notes make you write "the party traveled to Greyhaven" in session 5 and then reference it again in session 8. A living doc just has Greyhaven in the Locations section with everything you need to know about it in one place. When a player says, "What was the name of that innkeeper?" you don't scroll through five session logs. You check the NPC section.

DM Lair's "8 Types of Notes Every Dungeon Master Should Take" recommends organizing your notes into categories like important NPCs, quests, player decisions, and world details. The Living Bullet Journal follows that logic but strips it down to the bare minimum — one line per entry, updated only when something changes.

Time cost: 5-10 minutes after each session (adding new entries). Cumulative time pays off — by session 20, this document is a goldmine.

Method 4: The Voice Memo Method

Here's one for the DMs who hate writing: after the session ends, pull out your phone and record a five-minute voice memo summarizing what happened. Talk to yourself. Hit the highlights. Mention the NPC names, the big decisions, the hooks you planted. Done.

This works because speaking is faster than writing, and you're already in "storytelling mode" after a session. You've been narrating for three or four hours — five more minutes of talking is nothing. The barrier to entry is essentially zero: open your phone's voice recorder, hit the red button, talk, stop.

The research supports this approach, too. Dual-coding theory in cognitive psychology suggests that information encoded through multiple channels — hearing yourself say it, on top of having experienced it — is retained significantly better than information processed through a single channel. You're reinforcing the memory while also creating a reference you can listen back to later.

Some DMs take this one step further and use a transcription app — like Otter, Whisper, or even the built-in transcription on modern phones — to turn that five-minute audio note into searchable text. Now you've got a written record without ever having typed a word.

A twist on this method: record the voice memo while driving home from an in-person session (hands-free, of course). The commute becomes your documentation window, and you arrive home with the session already captured.

Time cost: 5 minutes of talking. No writing required unless you want a transcript.

Method 5: Let the Robots Handle It

If your group plays on Discord, a recording bot can take notes for you while you focus on running the game. This is the "laziest" method in the best sense of the word — zero effort during or after the session, because the tool captures everything automatically.

The landscape of TTRPG recording and documentation tools has grown significantly. Here's what's out there:

• Craig Bot is the gold standard for Discord voice recording — free, open-source, multi-track audio with up to 6 hours of recording time. It captures everything, but you'll need to handle transcription and note-taking separately.
• Scribble is an open-source project that watches for new Craig recordings and processes them into narrative recaps automatically.
• Kazkar is a Discord bot that records your session, transcribes it, and auto-generates session chronicles plus a lore wiki with NPCs, locations, and factions — browsable on a web dashboard (free tier includes 10 hours of recording).
• SessionKeeper offers session note-taking and campaign wiki features.
• World Anvil and LegendKeeper aren't recording tools, but they provide manual campaign wiki platforms that pair well with any of the above.

The honest pitch for automated tools is simple: they remove the entire documentation burden from human hands. Nobody has to volunteer for recap duty. Nobody has to spend ten minutes after the session writing bullets. The bot records, transcribes, and organizes — and your group gets a searchable record of the campaign that grows every session.

This approach is especially valuable for groups that play infrequently. If you're on a biweekly or monthly schedule — and remember, about 42% of groups play less than weekly according to Sly Flourish's survey — the gap between sessions is long enough that even good notes can struggle to bridge the memory gap. An automated chronicle gives everyone something to reference before the next game.

Time cost: Near zero. Add the bot once, summon it each session, and everything else happens automatically.

What to Actually Document (and What to Skip)

Here's the dirty secret of campaign documentation: most of what happens in a session doesn't matter for the campaign record. The third round of combat where the fighter missed three attacks in a row? Irrelevant to future sessions. The ten-minute argument about whether to take the left or right corridor? Not worth preserving.

Focus on these five categories and ignore everything else:

1. Decisions. What did the party choose, and what did they turn down? "We sided with the rebels over the crown" matters. "We fought six goblins" doesn't.
2. NPC introductions and developments. New NPCs, NPCs who revealed something important, NPCs the party made promises to or enemies of.
3. Unresolved hooks. Anything that's dangling — quests accepted but not completed, rumors heard but not investigated, doors opened but not walked through.
4. World changes. If the party's actions changed the state of the world — burned down a building, freed a prisoner, crashed an economy — document the new status quo.
5. Player-driven moments. The things your players will remember because they were emotional, funny, or dramatic. The oath the paladin swore. The betrayal. The natural 20 that saved the party.

Everything else — tactical combat details, shopping trips, rules discussions, scheduling chatter — can be safely forgotten. If your campaign were a TV show, you'd only put the plot-relevant moments in the "Previously on..." montage. Apply the same filter.

For a deeper look at building a permanent record of your campaign's lore, our guide on building a campaign wiki goes into the how and why of wiki-style documentation.

Comparison Table: All Methods at a Glance

A few honest observations. The Post-Session Dump is the most universal — it works for online and in-person groups, requires no buy-in from players, and takes ten minutes. The Player Recap Rotation is the most community-building — it gets everyone invested in the campaign's continuity. And automated tools are the most complete but only work if your group plays on a platform that supports them.

Most groups will benefit from combining two methods. The Post-Session Dump plus a Player Recap Rotation covers both the DM's and the players' perspectives. Or a Living Bullet Journal plus an automated recording bot gives you both a quick-reference document and a full archive. Experiment, find what sticks, and — this is the important part — don't let documentation become another source of stress.

FAQ

How do I take notes while DMing without breaking the flow?

The short answer: don't. Trying to take detailed notes while running the game splits your attention and degrades both the notes and the DMing. Instead, focus entirely on the game during the session and use a post-session method — a 10-minute bullet dump, a voice memo, or an automated recording tool — to capture what happened afterward. If you absolutely need to jot something during the session, limit yourself to single words or very short phrases (an NPC name, a plot point) that serve as memory triggers for later. Anything more than that pulls you out of the moment.

How much time should DMs spend on session prep and documentation?

As little as possible while still feeling prepared. Sly Flourish's eight-step Lazy DM method is designed to get you ready in about 30 minutes. His survey data shows that 69% of DMs spend fewer than three hours per week on prep, and there's no correlation between longer prep times and better games. For documentation specifically, ten minutes after the session is plenty. If your total prep-plus-documentation time regularly exceeds your actual play time, something needs to change.

Should I record my D&D sessions?

If your group plays on Discord, absolutely give it a try. Tools like Craig Bot (free, open-source) make recording effortless, and having a recording means you never lose a detail. The main trade-off is that raw recordings are time-consuming to review — a four-hour session is a four-hour recording. That's why transcription and summarization tools are gaining popularity: they turn hours of audio into searchable, skimmable text. For in-person groups, a phone or USB mic at the center of the table works too, though audio quality varies.

What's the minimum I need to document after a D&D session?

Names, decisions, and hooks. If you write down every new NPC name (with a one-line description), every meaningful decision the party made, and every unresolved plot thread, you have enough to prep the next session and run a recap. Everything else — combat play-by-play, exact dialogue, shopping lists — is optional. Most experienced DMs find that 5-10 bullet points per session is sufficient, even for plot-heavy campaigns.

How do I get my players to help with campaign documentation?

Make it easy, make it rewarding, and make it optional. Start a shared Discord channel or Google Doc where anyone can drop notes. Offer Inspiration (or a similar small in-game reward) for writing session recaps. Frame it as a contribution to the group, not a chore — some players genuinely enjoy writing in-character journal entries or drawing session art. The key insight from The Angry GM is that player recaps also benefit the DM: they reveal what players remember and care about, which is free prep intel. Not every player will participate, and that's fine. Even one consistent contributor transforms the group's ability to stay connected to the story, especially when it comes tohelping players remember what happened between sessions.

Your campaign's story is worth remembering — but remembering it shouldn't feel like a second job. Pick the method that matches your table's energy, spend ten minutes or less after each session, and trust that good-enough documentation beats perfect documentation every single time. The goal isn't to write a novel. It's to make sure that when a player asks, "Wait, who was that NPC again?" — somebody has the answer.