How to Remember What Happened Last Session (and Rebuild a Campaign You've Lost the Thread Of)

The five things to write down at the end of every session

If you do one thing from this guide, do this. Spend five minutes after everyone logs off and write five things. It takes less time than packing up your dice and it recovers most of what you'll actually need in three weeks.

Write it somewhere you will find it again. The note app on your phone is fine. The point is not the format.

• Where the party is standing right now and what they were in the middle of. "Halfway up the tower stairs, having just heard something move above them" is worth ten times "in the tower."
• Every promise made, in either direction. Debts, oaths, bargains, "we'll come back for you," the price you quoted them.
• What changed in the world because of them. Someone is dead, a gate is open, a faction now knows their names.
• Every NPC name that came out of your mouth, with a two-word tag. "Sera, harbormaster, nervous."
• The one thing the players said they were going to do next.

Why D&D sessions are unusually easy to forget

A session is three or four hours of continuous talk, and the gap before the next one is usually measured in weeks. In between, you have a job. Almost nothing about that is favorable to memory.

The specific failure is worse than general forgetting. Your prepped material survives, because it exists in writing and you read it twice before the game. What evaporates is everything you improvised: the tavernkeeper's name, the rumor you invented on the spot, the number you made up when someone asked what the passage cost. That improvised layer is exactly the part players latch onto, and they will hold you to it.

There's also the arithmetic of a long campaign. Six months of play every other week is a dozen-plus sessions and something like forty hours of table talk. No one holds that. And what happened is distributed across five or six people's memories, none of which is complete and none of which agrees entirely with the others.

What you need to recall exactly versus what you can just rebuild

These are two different jobs and confusing them wastes your prep time.

Facts have to be exact. Names, numbers, who died, what the letter said, what you promised, what the party owes and to whom. Getting these wrong costs you credibility at the table, and a player who catches you contradicting yourself starts treating the world as improvised rather than real. Facts are the thing worth writing down, because they cannot be regenerated.

Motivation can be reconstructed, and often improves in the process. If you can't remember why the party was chasing the duke, you do not need to excavate the original reason. Ask what it cost them to get this far, because cost is what makes people care, and build forward from that. If a player remembers a reason, use theirs.

Practical version: spend your prep recovering facts. Never spend it re-deriving why.

Build a campaign bible one session at a time

Sitting down to write a campaign bible in one go almost never works. It becomes a weekend project, then a guilt object, then nothing. Build it incrementally instead, adding only what actually came up at the table.

Use a promotion rule: something gets its own page the second time it appears. The first appearance is just a name in your session note. The second appearance means it's real and it's going to keep coming back.

Keep the page short and identical every time, so filling it in is mechanical rather than creative work.

On tooling, Obsidian, Notion, or one long Google Doc with headings all work. Pick the one you'll actually open on a Tuesday night. Search matters far more than structure: a single messy document you can find things in beats a beautiful nested vault you never populate.

• Name, and any nicknames the party uses instead.
• What it is, in one sentence.
• First appeared: session number.
• What the party knows.
• What the party doesn't know.
• Current status, updated when it changes.

Keep a state of the world page you rewrite every session

Session logs are append-only history. A state of the world page is different: it is one page, always current, and you overwrite it rather than adding to it. The history lives in the logs; this page only tells you where things stand tonight.

The test for whether it's working: if that page is the only thing you read in the five minutes before the game, you can still run the session.

Rewriting it takes two or three minutes at the end of a session, while it's all still in your head. Doing it a week later takes half an hour and you'll get it wrong.

• In-world date and season, and how long since the last significant event.
• Where the party is and what resources they have left.
• Who is actively hunting or watching them.
• Clocks that are ticking, and how far along each one is.
• Faction standing: who currently likes them, who doesn't, who has changed their mind.
• What your villains accomplished offscreen since last session.

Track unresolved threads as an explicit open list

Plot threads are the first thing to rot across a long gap. A subplot introduced in session nine and untouched through session twelve is functionally gone unless it's written down somewhere you actually look.

Give every dangling thing one line and a status: open, resolved, or abandoned. Include who cares about it, the session you last touched it, and what would move it forward.

This list doubles as prep. Before a session, scan for the thread that's been untouched longest and have it come to the party instead of waiting for them to remember it. A debt collector on the road works better than hoping someone reads their character notes.

Be willing to mark things abandoned. If the party walked past a hook three times, they're not interested. Close it, recycle the material into something they are chasing, and stop carrying it.

Write one line per NPC so you can pick the voice back up

Voice is the hardest thing to recover after a gap, and the most obvious when you lose it. Players notice immediately when the gruff dwarf smith comes back as a completely different person.

Record the mechanical handles, not the vibe. Pitch, pace, an accent you're loosely imitating, one verbal tic, one physical habit. "Sera: clipped, never finishes sentences, taps the counter when she's lying" is reloadable months later. "Sera: mysterious" is not.

Add two more fields while you're there: what they want, and the last thing they said to the party. Those two determine how the NPC opens the next scene, which is the moment you're most likely to fumble.

If you have audio of the session, the fastest way to reload a voice is to jump to the moment you first did it and listen for fifteen seconds.

What to do when you've already lost the thread and have no notes

Ask the players. Their memory is spread across several people, so in aggregate it beats yours, and for continuity purposes it is the authoritative version. What they remember is the campaign they've been playing, regardless of what you originally intended.

Do it a few days ahead in the group chat, and ask specific questions. "What happened last time?" gets you silence. Specific questions get you paragraphs.

Then open the session with a player recap round instead of yours. Each player says one thing their character remembers or is still angry about. You take notes while they talk. It costs ten minutes, it puts everyone back in character, and it hands you your prep for the night.

Where two accounts conflict, take the more interesting one and make it canon on the spot. Nobody is going to audit you.

• What is your character trying to accomplish right now?
• Who does your character owe, and who do they want to hurt?
• What's the last thing an NPC did that made you angry?
• What do you think is really going on with the thing you're currently chasing?
• Is there anything you're waiting for me to follow up on?

How to restart a campaign after a long break without a dull recap session

The instinct after three months off is to spend the first hour recapping. Don't. An hour of summary is the least engaging D&D anyone has ever played, and very little of it sticks. The campaign comes back to people through play far faster than through narration.

Instead, front-load the remembering and start the session already in motion.

Also declare an amnesty. Anything you can't find in your notes didn't happen, and small decisions from the last session can be re-decided. Say it out loud at the top. It removes the pressure on everyone to perform a memory they don't have.

1. Two or three days before, send a one-page written recap. One page maximum. Where you are, what you were doing, who's after you, what's unresolved.
2. Send each player three personalized sentences on what their character has been doing, ending with one thing that's waiting for them.
3. Open the session in the middle of something that forces a decision within ten minutes. Not a tavern. Something arriving.
4. Reintroduce every returning NPC with their relationship attached: "Sera, the harbormaster who lied to you about the manifest, is waiting at the end of the dock."
5. Save the wider political situation for when it becomes relevant in play, not for a briefing at the start.

Capturing the session so next month's version of you has something to work with

All of the above is easier if the session was recorded, because then the raw material still exists and the question is only how to get at it.

Recording is cheap. A phone voice memo in the middle of the table works for in-person games. For Discord, the Craig bot records each speaker to a separate track. OBS captures locally, and Audacity will clean up the result if you need it to.

The honest caveat: raw audio is a burden, not an asset. A four-hour file nobody ever reopens is worse than three bullet points written on the night, because it feels like a safety net that isn't one. Recording only pays off if you can search it, which means turning it into text. Transcription services like Otter will do that, Whisper is open source and can be run on your own hardware, and purpose-built tools exist for tabletop specifically, including DM Scribe, which publishes this guide.

Ask your players before you record anything. Some people play differently on tape. Tell them where the file lives, who can hear it, and that you'll delete it if they'd rather.