It’s September. The campaign stopped in June, for no reason anyone can name. A wedding, a vacation, two soft cancellations in a row, and then the Thursday slot just quietly stopped being a thing. Last night somebody typed “we should play again” in the group chat, four people reacted with emojis, and now you, the DM, are staring at your notes from three months ago wondering how you get six people back into a story none of them remember. ...
It’s 7:04. You are pulling up the map, muting the guy whose fan sounds like a leaf blower, re-reading the note you left yourself (“they owe Sallow a favor, DO NOT FORGET”), and queuing the tavern playlist. This is, minute for minute, the busiest you will be all night. And by tradition, this is also the exact moment you are supposed to stop everything and deliver a tight, evocative summary of a session that happened nineteen days ago. ...
It has been twenty-three days since the party entered the swamp. Somebody had a work trip, then somebody’s kid got the flu, and tonight, finally, five people are back at the table. Your paladin looks at the map, looks at you, and asks the question with total sincerity: “Why are we in a swamp?” Nobody knows. The rogue thinks it involved a lizard. Your notes say “they follow Meren’s trail south,” which would be useful if anyone at the table, including you, could remember who Meren is. ...
You built a campaign wiki. You did it the ambitious way: a page for the pantheon, a page for each of the five noble houses, a timeline going back eight hundred years, a map with pins. It took most of a weekend. It was genuinely fun. Then session thirty-one happens. Your rogue swears the party still owes the smuggler a favor. Your cleric swears the smuggler owes them, because of the thing with the barge. The argument is entering its fourth minute. You open the wiki, the one you spent a weekend on, and it has a lovingly formatted page about the founding of the kingdom and absolutely nothing about the barge. ...
Your barbarian just proposed marriage to the lich. The whole table is losing it, someone has fallen off their chair, and you missed the exact wording because you were writing down how much the healing potions cost. If you came here searching for a D&D session notes template, you are about to get one. It fits on an index card, it takes five lines, and I want to talk you out of everything beyond it first, because the template only works once you accept what it is for. The person taking thorough notes at a D&D table is playing a worse game than everyone else. They react a beat late. They laugh at the punchline secondhand. They experience the session the way a court stenographer experiences a trial. And here is the part that stings: the notes they sacrifice all that presence for are usually bad, because writing prose in real time while five people talk over each other is a job we pay professionals to do. ...
It’s 10:52. You said you’d wrap at eleven. The party has just kicked in the door to the counting house, the guards are rolling initiative, and your cleric has that look that means she is about to do something expensive with a spell slot. Somebody’s partner has walked past the webcam twice. The bard is on his phone checking what time his train is. And you, the person who is supposed to be steering this thing, are quietly doing the math on whether a six-guard fight can possibly finish in eight minutes, knowing full well it cannot, and knowing that if you push through, the last hour of the session will be played by people who have already left. ...
It’s 10:40 on a Tuesday, the fight has been going for fifty minutes, and your wizard has just asked whether she can cast shape water on the blood pooling under the ogre to freeze it into a blade. Everybody at the table turns to look at you. She has the book open. She’s already found the paragraph that says the spell works on “water,” and she has a very reasonable case that blood is mostly water, and the ogre is at nine hit points, and the whole table wants it to be yes. Somewhere in your head a decade of DM advice is chanting yes, and, and you’re wondering, with the pizza box still on the table, whether saying no to your players makes you the kind of DM people quietly stop showing up for. ...
It’s 6:40 on a Tuesday. The session is at 7:30. You meant to prep on Sunday, and then Sunday happened to you the way Sundays do, and now you’re standing in the kitchen with a laptop balanced on the microwave, opening a notes doc you last touched eight days ago. Somewhere in there is what the party promised the widow. Somewhere in there is the name of the guy with the ledger. You have fifty minutes, dinner is one of them, and you’re searching “how to prep a D&D session fast” with the specific calm of someone who has already accepted the evening will be improvised. ...
It’s the second hour of the session and things are going well, which is exactly when it happens. Your players walk into the smithy you improvised because they turned left instead of right, and the fighter, delighted, asks the one question that costs nothing to ask and everything to answer: “What’s his name?” You know this smith. You invented him nine seconds ago and you already know his forearms, his prices, his opinion of the local guard. But a name requires a specific arrangement of syllables produced on demand, and your brain, which was just fluently narrating a whole world, hands you nothing. So you say “Gareth,” because there is always a Gareth, and you move on. Three sessions later a player says “let’s go back and see Gareth” and you stare at them like they’ve named a stranger. ...
It’s 7:09 on a Tuesday. The pizza’s late, somebody’s dog is barking on the call, and your rogue is asking — completely sincerely — whether they still have the cursed amulet. They do. They’ve had it for four sessions. They were there when they picked it up. This is the moment the recap was invented for. Not the wiki, not the binder, not the forty-page campaign bible nobody reads. The two minutes at the top of the night where five distracted adults put down their phones, climb back into people who can cast spells, and remember that last week they swore a blood oath to a goose. ...