How to Take Notes During a D&D Session Without Wrecking the Game

Why you can't run the game and take good notes at the same time

The problem is not discipline. It is attention. While you are composing a sentence you are not reading the table, not tracking initiative, not hearing the quiet player finally say something. Every second your eyes are on the page is a second the game is running without you.

Trying to do both badly is worse than picking one. You end up with half-legible fragments you cannot decode a week later, plus a session where you kept losing the thread. If you have ever stared at the line "guard — the thing?? maybe not" and felt nothing, you have already paid this cost.

So set the rule now: at the table, your job is running the game. Notes are a background process that takes under five seconds at a time. Anything that takes longer waits.

Everything below is built in three layers. Capture during play, measured in seconds. A ten-minute dump right after everyone leaves. A short review before the next game. The middle layer does most of the work, which is why the first layer can be so thin.

What is actually worth writing down mid-session

Capture only things that will be gone if you don't. Six categories cover almost all of it:

• Names you improvised. This is the highest-value item on the list. The moment you say "the barkeep is... Merrin," write Merrin down, or he will be Marlon next month and your players will notice.
• Promises the party made. "We'll come back for the kid." "We'll pay you when we're through." Debts are plot, and players remember the ones that favor them.
• Threads you opened and nobody closed. The door you described that they walked past. The letter they never read. The bandit who fled at 4 hit points.
• What the party believes that is wrong. They think the duke ordered the killing. He didn't. Write "party thinks duke ordered it — wrong." That single line is a whole future session.
• Rulings you made on the fly, so you can be consistent next time instead of relitigating it.
• Persistent numbers: gold, remaining charges, days elapsed, how hurt the recurring villain was when he ran.

What can wait until after the session

Anything already written somewhere else does not need a note. Stat blocks, prepped location descriptions, module loot tables, the map, the NPC you wrote a page about last week. You are not making a duplicate copy of your prep.

Skip the combat blow-by-blow. Nobody has ever reread "Kira hit for 9, then 12, then missed" and gotten value from it.

Skip verbatim dialogue. Reaching for the exact words is what pulls you out of the scene hardest, and the shape of a conversation is recoverable from a five-word note about what changed in it.

Skip anything you are about to resolve in the next ten minutes. If they open the chest before the scene ends, the chest never needed a line.

The one-line-per-beat technique

Write one line per beat, never a paragraph. A beat is a thing that changed: someone was named, someone promised something, someone learned something, someone left.

Keep each line under about eight words, noun then verb. "Merrin the barkeep owes the Ash Guild." "Party promised to return for Tam." Ignore capitals, punctuation and grammar entirely. You are leaving yourself a handle, not a record.

Use single-character prefixes so you never have to think about where a line goes. N for a new name, P for a promise, ? for an open thread, X for a wrong belief, R for a ruling. One keystroke, no decision.

Write strictly top to bottom in one file or on one page per session. Do not sort things into categories while the game is running — sorting is where the attention goes. Organizing happens later, when it is free.

Aim for twenty to forty lines out of a four-hour session. If you have two hundred you are transcribing and the game is suffering. If you have five you are not capturing.

Anchor your notes with scene breaks, round numbers, or a timer

Notes without position are hard to reconstruct. Give every line a rough anchor and future-you can rebuild the order of events in a minute instead of twenty.

Draw a line across the page every time the scene or location changes and label it: "— docks, after dark." That is usually enough structure for a whole session.

In combat, write the round number instead. "R3 — hag teleports out, wounded" tells you more than the same note with no marker.

If you are recording the session, write the clock time next to any line you might want to hear again. A timestamp turns four hours of audio into a ten-second jump.

A quiet timer at thirty-minute intervals is a useful check, not an interrupt. When it goes, glance at the page. If nothing is written since the last chime, decide whether genuinely nothing happened or whether you got absorbed and lost twenty minutes of names.

Index cards for NPCs you invent on the spot

Keep a stack of blank index cards next to your screen. When you improvise an NPC, they get a card: name, one physical detail, one verbal tic, what they want, where the party met them.

Write the name the instant you say it out loud. The other four fields can be filled in during the next break — they are cheap to reconstruct, the name is not.

The verbal tic is the load-bearing detail. It is what makes an NPC recognizably the same person when they turn up six weeks later, far more than the description of their coat.

Cards beat a notebook here because they are physical and sortable. You can spread the relevant ones in front of you at the start of next session, hand one to the player who keeps talking to that NPC, and pull the whole tavern's staff out as a group.

After the session, the NPCs who mattered get typed into wherever your campaign lives. The rest go in a box, which is exactly where an unused innkeeper belongs.

Note-taking during combat versus roleplay

These are two different jobs and treating them the same is why most systems collapse.

In combat your attention is fully committed to the map, initiative, and stat blocks. Record almost nothing. The exceptions: what an enemy revealed about itself, who fled and how badly hurt, anything expensive the party burned that will hurt later, and consequences that leave the room — a building on fire, a witness who got away.

Roleplay is where the durable information lives, and it is harder to write during because you are the one talking. Never write while an NPC you are playing has just been asked a question. Answer first.

Capture at the break instead. The moment a scene ends and the party turns to argue among themselves about what to do next, that is fifteen to thirty seconds of free time that recurs constantly. Use it deliberately rather than sitting there watching them deliberate.

If a scene produces something you absolutely must not lose and you cannot break away, say it back in character. "So you want me to bring you the seal by the new moon." The party confirms, you have bought yourself a memory hook and made the promise explicit at the same time.

How to hand note-taking to a player without it becoming a chore

The usual failure is predictable. You ask for a scribe, one enthusiastic player volunteers, they do it beautifully for three sessions, it turns into homework, and then nobody has notes for sessions four through nine.

Rotate it. If it moves around a table of five, each person does it once every five games and it never becomes an identity or an obligation.

Give them a template so they are not facing a blank page. Four prompts, five bullets each, maximum: what we did, who we met, what we promised, what we still want to know. That last one is the prompt that produces the useful stuff.

Make the deadline "before we leave the table." Notes that go home do not come back. Ten minutes of everyone packing up is enough time to finish five bullets.

Pay for it. Inspiration, a small bonus, or simply posting the recap to the group chat with their name on it. Unpaid recurring labor at a hobby table ends the way you expect.

Accept that a player's notes record what the party thinks happened. That is not a defect, it is a second useful document: it shows you exactly where their understanding has drifted from yours. Do not ask a scribe to track secrets. They record what the party saw, and nothing else.

Put the scribe's notes and yours in the same place — any shared document the whole table can edit will do — so nobody has to email anything and nothing lives only on one person's laptop.

The 10-minute brain dump right after the session

This is the layer that makes thin in-game notes work, and it is the one people skip. Do it before you get in the car, or in the five minutes after everyone logs off. Not tomorrow. Detail fades fast, and it is the difference between a note you can use and a note you can only stare at.

Set a timer for ten minutes and expand your one-liners into sentences a stranger could follow. Do not polish. Nobody is reading this but you.

Four headings cover it: what happened, what changed in the world, what the party said they will do next, and what you owe them — a ruling to confirm, an answer you promised, an item you need to price.

Then add the single most valuable line in the whole system: what you want to happen next session. Not what will happen. What you want. That is the seed of your prep and it is only available while the session is still warm.

Also record anything you invented on the spot and are now committed to, and anything the party currently believes that is not true. Both of those are invisible by Wednesday.

If typing feels like too much, talk instead. Five minutes into a phone voice memo on the drive home captures more than twenty minutes of typing three days later. You can transcribe it later or never — even listening back beats reconstructing from nothing.

Reviewing your notes before the next game

Give it ten to fifteen minutes the day before, not five minutes before the players arrive. You want time to react to what you find.

Read three things: last session's dump, your running list of open threads, and the index cards for anyone likely to show up.

Keep that open-threads list as a single living document. One line per thread, dated, deleted when resolved. Sessions have a way of opening four threads and closing none, and the drift is invisible until you have a list.

Write a recap of five to eight sentences and read it aloud at the start of the session. It does three jobs at once: it reloads your own memory, it syncs the party, and it surfaces the moments where they remember events differently than you do. When someone objects, stop and listen — that gap is worth more than the recap.

Occasionally ask a player to give the recap instead. What they leave out tells you precisely what did not land.

Recording the session, and what it changes

If you record, most of this tension disappears. You stop trying to be a stenographer and start marking a record you already have. If you have the option, it changes the job more than any other single thing on this page.

In person, a phone lying face-up in the middle of the table will capture a whole session well enough. A cheap USB mic in the center is better. On Discord, the Craig bot records each speaker to a separate track, which matters a lot if you ever want the audio transcribed. OBS and Audacity both handle local capture without fuss.

Then decide what the audio is for. It can be nothing more than a safety net for arguments about what was said. General-purpose transcription services like Otter will turn it into text, and Whisper, the open-source speech model, runs locally for free if you are comfortable with the tooling. Purpose-built options exist too, including DM Scribe, which is built specifically to turn session audio into a campaign wiki and recaps.

The honest caveats. Get consent from everyone at the table, every time, and stop if anyone is uncomfortable. Four hours of unstructured audio is not notes — a recording you never open is worth nothing, which is why the in-game one-liners still earn their place as an index. And transcription tools struggle with invented fantasy names, so expect to fix spellings.

Even with a recording, still do the ten-minute dump. The recording tells you what happened. The dump tells you what you thought about it, and that is the part that actually drives the next session.