How to Recap a D&D Session (And Why It Transforms Your Campaign)

Every DM knows the feeling: it's three days after a great session, someone asks "wait, what was the name of that NPC we met at the docks?" and the whole table goes silent.

A solid session recap fixes that. More than just a summary of what happened, a great recap becomes a living artifact of your campaign — something players actually read, that sharpens your next session, and that keeps the story coherent across months of play.

Here's how to write one, and why the habit compounds over time.

What a Good Session Recap Actually Does

Before diving into how to write one, it helps to understand what you're trying to accomplish. A session recap serves three distinct audiences at once:

Your players — they want to relive the highlights, catch anything they missed mid-session, and stay emotionally connected to the story between sessions. A recap that hits those emotional beats ("Kira's bluff to the duke ended up changing everything") is one they'll actually read.

You, the DM — you're extracting loose threads, tracking NPC states, and reminding yourself what you set up. A good recap is your best prep tool for next session.

Your future table — a campaign that runs a year or two will have dozens of sessions. The recap is the institutional memory of your story.

The Core Elements of a Strong Recap

1. A Narrative Opening (2-4 sentences)

Don't start with a bullet list. Open with a short paragraph that sets tone and reminds people why they showed up. Something like:

"Session 14 picked up exactly where 13 left off: the party crouched in the ruins of the Ashen Keep with three dead guards at their feet and a very nervous informant who still hadn't told them why the Duke's seal was on a crate headed for Undercity docks."

This does more for player engagement than any bullet point.

2. The Highlights — What Actually Happened

Cover the major beats of the session in 3-5 bullet points or short paragraphs. Focus on:

• Decisions the party made (not just what happened to them)
• NPC interactions that moved the story forward
• Combat outcomes that matter to the plot (skip the rolls, keep the stakes)
• Revelations and information gained

What you leave out matters as much as what you include. If an encounter didn't affect the story, it probably doesn't need its own paragraph.

3. Loose Threads and Open Questions

This is the most useful section for your prep. What did the party NOT resolve? What questions did they ask that you haven't answered yet? What did they do that will have consequences?

Examples:

• The informant is still alive and knows the party's faces
• Three players voted to go to the Docks; one wanted the Undercroft — that tension isn't resolved
• Mira made a promise to the merchant guild she probably can't keep

Keep this honest. If something is hanging, name it here. It becomes your prep list.

4. NPC and World Updates

Briefly note any changes to named NPCs or locations your party cares about:

• Who did they befriend, offend, or kill?
• Did anything change in the world they can observe?
• What do key NPCs now know about the party?

5. Loot and Mechanical Notes (if your table tracks this)

If your group cares about inventory, XP, or item states, a quick bullet list at the bottom handles it cleanly without polluting the narrative sections.

6. A Hook for Next Time

End the recap with a line or two that creates anticipation for next session. It doesn't have to be a cliffhanger — it can be as simple as naming what's at stake:

"Next session: the docks at midnight, a ship that shouldn't be there, and a crate the Duke doesn't want anyone opening."

That's what they'll be thinking about until they sit back down at your table.

Practical Tips for Writing Recaps

Write it within 48 hours. The emotional texture fades fast. The table energy you remember on Sunday is much harder to capture on Thursday.

Take 5 minutes of notes mid-session. You don't need transcription. Just: NPC names, any promises made, any major decisions, any revelations. Three bullet points on your phone during a break is enough to anchor your recap later.

Write it for the players who were absent. One or two players will miss sessions. A good recap brings them back up to speed without requiring another player to explain it badly.

Don't recap the dice. Nobody cares that Theron rolled a 7 on his Insight check except Theron. What they care about is that Theron didn't notice the merchant was lying. Keep it story, not mechanics.

Keep it readable in 3-5 minutes. Players are busy. A 500-word recap gets read; a 2,000-word wall of text gets skimmed. Be ruthless about what earns its place.

Using Tools to Make Recaps Easier

Manual recaps take time — often 30-60 minutes if you're writing from scratch. A few approaches that help:

Record your sessions. Even a phone on the table captures enough. You can skip to key moments instead of reconstructing from memory.

Use a consistent template. Having a standard structure (narrative opening → highlights → threads → NPC notes → hook) means you're filling in blanks, not staring at a blank page.

Tools like Epicly can take your session audio and generate a structured first draft — plot threads, NPC interactions, loot, and open questions — so you're editing and adding personality rather than building from zero. The Lorekeeper AI then keeps all of that in your campaign's memory so you can ask "what do we know about the duke?" anytime.

The Long Game: Why Recaps Compound

Here's the thing that takes a while to appreciate: session recaps are a compound investment.

Early in a campaign, they feel like overhead. By session 20, they're the backbone of your world. Players reference them. You mine them for callbacks. The shopkeeper mentioned offhand in session 3 who became a recurring character because someone read the recap and asked about her — that only happens because someone wrote her down.

The campaigns that people talk about for years are the ones where the story felt continuous, where the world remembered what the party did, where choices had weight. Recaps are how you build that.

The table that takes notes tells better stories. Start with one session. Write the recap this week. See what it does for next session's prep.