Notes on memory, story, and the table.

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.

Your table’s session has exactly one copy. Six people spent four hours making something that will never happen again, and the only record of it lives inside a bot that promised to be listening. If you’re a GM deciding whether to trust a recording bot with that, you should want to know how these things fail. So here is how ours fails, all thirteen ways, because the day we started paying for traffic we commissioned an adversarial audit of our own recording pipeline …

If you play D&D over Discord, someone at your table has already suggested the Craig bot. They were right to. Craig is the default recording bot for online tabletop, it earned that spot honestly, and if you searched “craig bot dnd” trying to decide whether to use it, my answer is yes. Use Craig. This post is about the question that shows up after you do, the one I built a whole product around: you now have six hours of audio. Who’s going to remember what’s in it?

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 …

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, …

Saturday, 6:04 pm in New York. Your paladin is settling in with a beer. In London it’s 11:04 pm, and your wizard has switched to typing her dialogue because her flatmates are asleep on the other side of a thin wall. In Sydney it’s 8:04 on Sunday morning, and your rogue is eating cereal on camera with sunrise coming through the window behind him.

This is what a D&D game across three time zones looks like when it’s working. The college group scattered, or the forum …

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. …

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 …

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 …

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 …

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 …

Somewhere between “fine, I’ll run it” and the actual Friday, the fear arrives. You said yes because nobody else would, or because you’ve been the note-taking player for a year and everyone just assumed, or because you watched one actual-play episode too many and something in you went I want to do that. And now there’s a date on the calendar and a rulebook on your desk that is 300 pages long, and you are searching “how to DM for beginners” at 11pm with the specific …

The cart has been open in a browser tab for three days. Player’s Handbook, Dungeon Master’s Guide, Monster Manual. Somewhere around a hundred and fifty dollars once shipping shows up, which is a lot of money for a hobby you have played for exactly zero hours. So you do what everyone does: you search “do I need to buy D&D books to start,” and you land here, half hoping someone will talk you into it and half hoping someone will let you off the hook.

Here’s how a campaign actually dies. Session four is scheduled for Thursday. On Tuesday, someone posts in the group chat: “hey, work thing came up, can we push to next week?” Everyone says sure, no problem. Next Thursday, someone else has a birthday dinner. The week after that is fine, you play, it’s great. Then two more reschedules land back to back, a month has passed since anyone rolled a die, and the DM quietly stops prepping because prepping for a game that …

You want to play D&D, and there’s nobody in your immediate circle who already runs a game. Maybe you’ve floated the idea a couple of times and it hasn’t quite stuck. So you google how to find a D&D group, and you get the same advice everyone gets: “ask around, check your local game store, try online!” Cheerful, vague, and completely useless the moment you actually try to follow it.

Here’s the secret about first sessions: at some point during the night, the game you’ve been imagining gets replaced, all at once, by the real one. The real one is better. That moment of magic is what keeps people coming back to D&D for years, and no blog post can spoil it, because it’s built live out of the world you and your friends make together. What a blog post can do is walk you through what actually happens at a first D&D session: the structure, the rhythms, …

Here’s what happens when you google how to start playing D&D.

You get a list. Buy these three books. Consider these seven alternate systems. Here are twelve ways to find a group, four virtual tabletops, a character creation walkthrough, and a paragraph about how the most important thing is to have fun. Somewhere around option thirty you close the tab, and eight months later you still haven’t played.

You have plenty of information. What you’re missing is somebody …

“Remind me,” your player says, leaning in with a grin. “What did Garrick swear he’d do if we ever brought his daughter home?”

Four faces turn to you, waiting. You have no idea who Garrick is.

You invented him three sessions ago—a blacksmith, a grudge, a limp—and the table loved him so much they wrote his daughter into their backstories. He’s the best NPC you never planned. And right now, in front of everyone, you’re about to retcon him into a stranger.

You spent the week building the next arc. The faction politics, the dungeon, the villain’s plan.

Meanwhile, the best hook for that arc has been sitting in a shared doc since session zero. You read it once. You don’t remember what it said.

Every player handed you a backstory. A dead mentor. A sister who vanished. A debt, a betrayal, a home they can’t go back to. Then the campaign started, the dice came out, and those pages went quiet.

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 …

Session forty-seven. You introduce an NPC and a player stops you mid-sentence.

“Wait — that’s the guy from Thornwood. We were supposed to bring his son back.”

You stare at her. You glance at your notes. The name you just said is not the name on the page. She is right. You are wrong.

This used to mortify you. After enough campaigns, it stops.

The myth There’s a fiction at the heart of how DMs talk about the craft. The DM is the keeper of the world. You arrive at the …

Somewhere in my campaign is a promise I made and forgot. My players haven’t.

I don’t know what it was. I don’t know who it was to. I don’t know when they’ll call it in. But I know it’s there—buried somewhere in the hundred-plus hours we’ve spent at the table together, waiting.

Maybe it was something an NPC said in the heat of the moment. Maybe it was a throwaway line that landed harder than I expected. Maybe it was a deal struck in a tavern, a vow made in a dungeon, …

If you’re reading this, you probably already have a system.

Maybe it’s Obsidian with a sprawling vault of linked notes. Maybe it’s Notion with databases for NPCs, locations, and quests. Maybe it’s World Anvil, or a physical notebook with color-coded tabs, or a Google Doc that’s gotten out of control.

You care about your campaign. You put in the work. You take notes.

This post is for you.

The gap between prep and play Your system captures what you build. The …

Ask any DM about their best session ever. The one players still talk about years later.

I’ll bet you anything: it wasn’t the one they prepped the most.

It was the one where everything went sideways. Where the players ignored the dungeon and befriended the monster. Where an NPC invented in desperation became the campaign’s heart. Where the story went somewhere no one—including the DM—expected.

The best sessions emerge. They can’t be planned.

There’s an unspoken rule in the D&D community: good DMs take good notes.

Session logs. NPC lists. Relationship maps. Plot thread trackers. The advice is everywhere—buy a nice notebook, develop a system, write everything down.

And it makes sense. When you’re running a campaign that spans months or years, memory fails. Players ask about the shopkeeper from session 12. They want to know what the prophecy actually said. They remember making a deal with someone, but not …