Guides
How to Write a D&D Session Recap
Learn how to write a D&D session recap players actually read: what to include, a copy-ready template, and whether the GM or a rotating player should write it.
By Mythical AtlasLast updated
A good D&D session recap is a short, player-facing summary that tells everyone what happened last time, what changed in the world, and what the party is chasing next. Aim for 150 to 300 words, post it within a day or two of the session, and keep every GM secret out of it. That's the whole recipe. The rest of this guide covers what to include, a template you can copy, and who should write the recap.
A recap isn't a record of everything that happened. It's a memory aid for a group that might not play again for a week or two, and it works just as well for Pathfinder, OSR games or homebrew systems as it does for D&D 5e.
Why session recaps are worth the effort
Most tables meet every week or two, and a lot happens in between: work, family, other games. By the time you sit down again, the party's memory of the cultist in the tavern has faded into "some guy, I think?"
A recap fixes this in a few ways:
- Players re-enter the story quickly, so you don't spend the first half hour on "wait, where were we?"
- Absent players catch up without asking the GM to retell the whole session.
- You get a campaign diary. Months later the table can scroll back and remember which decision led to which consequence.
- The recap is a prompt for you, too. Writing it shows you which threads you've left dangling.
What to include in a session recap
Lead with consequences, not a play-by-play. "We went to the docks, then the warehouse, then fought four thugs" is a log. "The smugglers know the party is hunting them" is a recap. Cover these pieces:
- The session in one line. If someone reads only this sentence, they should still know the headline.
- Three to five key scenes. Only the scenes that changed something: a deal struck, a fight that went badly, a secret learned.
- What changed in the world. Who is angry, who owes the party a favor, which door is now locked. Include what will still be true next session and skip what only mattered in the moment.
- Named NPCs and places. Nobody remembers the innkeeper unless the recap uses the name. A short list of who the party met and where they went is enough.
- Loot and rewards, briefly. Loot belongs on character sheets or a party inventory more than in the story, so one line is plenty.
- Open threads. The questions the party hasn't answered, the promises they've made, the deadlines that are ticking.
- A hook for next time. End on the first pressure of the next session: an arriving ship, a letter, a locked vault.
What to leave out
- Anything the characters didn't see or learn. A recap is player-facing. If the villain's plan was explained only in your notes, it stays in your notes.
- Rules discussions and out-of-game chat.
- Combat blow-by-blow, unless one moment was legendary and deserves a line.
- Long lore dumps. Put reference material somewhere players can look it up instead.
A reusable recap template
Copy this skeleton and fill it in. Each part can be a sentence or two.
Session [#]: [Title]
In one line:
What happened:
- Scene 1
- Scene 2
- Scene 3
What changed:
People and places:
Loot:
Open threads:
Next time:
A filled-in example might read: "Session 7: The Flooded Archive. The party recovered the tide-priest's ledger but alerted the Harbor Guild. The Guild now knows Mira carries it. Captain Orsk offered passage upriver in exchange for a favor. Open threads: who forged the ledger's last page? Next time: the Guild's enforcers arrive at dawn."
Who should write the recap?
There are three common approaches, and each suits a different table.
| Approach | Strengths | Watch out for |
|---|---|---|
| GM writes it | Accurate, consistent, and you control the spoilers | It's one more task on a GM's plate |
| One player writes it, rotating | Shows what players found memorable, shares the workload, and gives you feedback on what landed | Quality varies, and details can be wrong or missing |
| Group writes it together | Everyone can add the moment they cared about | Needs a bit of structure, or it turns into a long list |
A popular middle path: a rotating player writes the first draft in their own voice, and the GM corrects any facts and adds the hook. Player recaps also tell you what stuck with the table, which is useful for planning. If you'd like a regular player in the rotation, ask them to write in character, and treat it as a bonus rather than a chore.
If the GM writes it, keep it short. A recap you can finish in ten minutes is one you'll keep writing in month six.
Keeping recaps where the table can find them
The best recap is useless if it's buried in a chat scroll. Pick one home for recaps and use it every time, so players know where to look.
In Mythical Atlas, there are two natural places:
- Updates is the campaign's announcement board, and the first thing players see. Only the GM can post, each update has a title of up to 100 characters and up to 2,000 characters of content, and everything shows newest first. The template above fits comfortably. Players have read-only access, so if they spot a mistake they tell you and you edit it.
- Notes let any campaign member write. A player can post a shared recap and tag it with something like "recap" and the session number, so the table can filter all recaps later. Notes are readable by every member, so they're not the place for GM secrets.
Whichever tool you use, the habit matters more than the app: same place, same format, within a day or two.
Make the recap work at the table
A written recap does its best work when you also use it out loud. Before play starts, read the "In one line" and "Next time" parts, or ask a player to read their version. Two minutes is enough to pull everyone back into the scene. For keeping the rest of your campaign material tidy, see our guide to organizing a D&D campaign, and use the session zero checklist to agree on habits like recaps at the very start.
Quick recap checklist
- One-line headline at the top
- Three to five scenes that changed something
- NPCs and places named
- Open threads listed
- A hook for next session
- No GM secrets
- Posted within a day or two, in the same place every time
Start with the template next session, even if it's rough. A mediocre recap posted this week beats a perfect one that never gets written.
