How to Write a D&D Session Recap Your Players Will Actually Read

Every GM has sent a session recap into the void.

You spent 20 minutes writing up what happened last session. You dropped it in Discord. Three people reacted with 👍. Nobody read it.

The problem usually isn't motivation — it's format. A wall of text recapping everything that happened in chronological order is homework. Nobody does homework before game night.

Here's how to write session recaps that players actually open, read, and reference.

Why Session Recaps Matter (When They Work)

A good recap does three things:

• Reduces the "wait, what happened last time?" spiral that eats the first 15 minutes of every session
• Keeps absent players from falling behind without a 10-minute catch-up conversation
• Creates a living campaign history you can reference months later when a plot thread resurfaces

The key word is living. A recap buried in Discord is gone in 48 hours. A recap that lives at a permanent URL — one your players bookmark — is something they'll actually check before session.

The Format That Works

Forget prose. Players don't want to read a short story about what they already did. They want to remember the important stuff fast.

Use this structure every time:

⚡ The One-Liner

One sentence. What was this session about?

"The party broke into a Covenant warehouse, found prisoners, and accidentally became leverage against the city council."

This is the hook. It goes at the top. It tells players immediately whether they remember this session.

🎯 What Actually Happened (5–8 bullets)

Not everything. The things that matter going forward.

• Accepted the warehouse job from Maren — retrieve a stolen ledger
• Discovered the warehouse held three Warden prisoners being held without charge
• Chose to free the prisoners, blowing their cover in the process
• Commander Fell arrived — let the party go, issued a formal warning
• The ledger contained names of city council members on Covenant payroll
• Party now holds the ledger

One bullet per meaningful event. If you can't say it in one line, it's two bullets.

🔮 Threads Still Open

What's unresolved? What's coming?

• Maren wants the ledger back — or does she?
• The three Wardens are free. They owe the party. Where did they go?
• Commander Fell let them go this time. Why?

This is the section players actually reread before next session. It's the cliffhanger in text form.

💀 Notable Moments

One or two moments worth remembering. Funny, heroic, disastrous — whatever made the table laugh or gasp.

Aldric attempted to bluff his way past two guards by claiming to be a "Covenant cheese inspector." Rolled a 19. It worked.

This is the part that gets shared. It's also what makes players feel like the campaign is worth documenting.

Where to Store Your Recaps

Here's the thing most GMs get wrong: recaps should be in one place, not scattered across Discord messages.

A single Folio with all your session recaps — newest at the top — means:

• New players can catch up instantly
• You can search the whole campaign history
• The link never dies between sessions

The D&D Campaign Starter Kit includes a session recap section built exactly this way. Fork it and start adding recaps after each session — it takes less than 10 minutes per session once you have the format down.

The 10-Minute Recap Workflow

1. Right after session ends — jot 5–8 bullet points while it's fresh. Don't write prose yet, just events.
2. Next day — take those bullets, add the one-liner and open threads. 10 minutes max.
3. Publish to your campaign Folio — newest recap at the top.
4. Share the Folio link (not the individual recap) so players have one bookmark that always works.

Do this for three sessions in a row and your players will start asking for the recap before the next session. That's when you know it's working.

📂 Free template → D&D Campaign Starter Kit — session recap section included, ready to use.