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

How long a session recap should be

Five to ten sentences. Roughly 120 to 200 words. That is about thirty seconds to read on a phone, and about a minute to read aloud at the table.

A full page of prose loses to everything else in the channel. Long recaps get skimmed and abandoned, so the opening lines end up doing all the work anyway. Write only the lines that would survive the skim.

The constraint is the useful part. When you only get a handful of sentences, you are forced to decide what actually mattered, and that decision is the recap. A four-hour session usually comes down to three or four things that changed the party's situation. Everything else was texture, and texture does not need to be remembered — it needs to be re-created at the table.

Why the previously-on framing beats a minutes-of-the-meeting log

A blow-by-blow log is written for the archive. A recap is written for the people who are about to play, some of whom have not thought about the campaign since the last session — which may have been three weeks ago.

Television has the useful version of this. A previously-on segment is not a summary of last week's episode. It is a selection of the specific moments the upcoming episode needs you to have loaded. If tonight's episode turns on a debt, the previously-on shows the debt being incurred and nothing else.

Do the same thing. Write your recap after you know what next session is likely to touch. Ask: what does the table need to be holding in their heads when we start? Include that. The rest can live in the campaign log, where nobody has to read it under time pressure.

Lead with the consequence, not the chronology

The most common recap mistake is starting where the session started. Chronological order buries the point three sentences deep, and by then half the readers are gone.

Open with the sentence that describes how the party's situation is different now. Then, if you need it, give the one line of context that explains how they got there.

Chronological version: The party left the inn at dawn, traveled two days along the river road, met a toll clerk at the county line, and after some discussion Bram burned the writ.

Consequence-first version: The party are fugitives in Harrow County — Bram burned the Duskwarden's writ in front of the toll clerk rather than pay.

Same facts, fewer words, and the reader gets the stake in the first line. Apply the same test to every sentence: does this tell them something is now different, or is it stage direction?

What to include in a session recap, and what to cut

Include the things that will still be true when you sit down to play, and cut the things that only existed during play.

Cut initiative order, round-by-round combat, damage numbers, individual dice rolls, every skill check that succeeded, the exact loot list, and the shopping trip. Nobody rereads a recap to find out how much damage the fireball did, and loot belongs on the character sheets rather than in the story.

What survives is roughly this:

• What changed — the state of the world that is different now than it was last session
• What the party decided, especially decisions that were argued over and are not fully settled
• What is now owed, promised, or threatened, and by when — debts, deadlines, and anyone newly hostile
• What is still unexplained that they are carrying: the key nobody has matched to a lock, the letter nobody has opened
• The cliffhanger — the exact image or moment the session ended on, written as if the camera is still on it

Write it in your players' language, with their characters' names

Use character names, not classes or player names. Kest, not the rogue. If the table has invented shorthand for something — the vault job, the goblin sommelier, Tuesday the mule — use their words, exactly as they say them. A recap written in the table's own vocabulary reads like their story instead of your notes about their story.

Addressing the party as you works well. You rode north without paying. It puts the reader in the scene rather than reading a report about people they know.

Keep the tense consistent — past tense for what happened, present tense for the cliffhanger, so the ending feels live. Do not write in the voice of a chronicler unless your table genuinely enjoys that, in which case commit to it and keep it short anyway.

How to keep GM secrets out of a player-facing recap

Write the recap from what the characters observed, not from what you know. That single rule handles most of it. If the party did not learn that the abbot is the one funding the plague, your recap describes a man in a good coat leaving the abbey at night, because that is what Sela saw from the ridge.

Never write something false to protect a reveal. Your recap becomes canon the moment you post it, and your players will quote it back to you six sessions later. A false detail in a pinned message is a trap you built for yourself. Omit instead of lying.

Two techniques worth having. First, attribute uncertainty to the characters: as far as you could tell, the seal was Duskwarden. That is honest, keeps the reveal live, and quietly flags to the table that they should not be certain either. Second, describe the observable and stop: the letter is sealed with green wax and Wend did not say what is in it. You have recorded the fact without narrating the secret.

Be careful about the silence you leave. If every recap mentions the NPC you are protecting and one recap conspicuously does not, that is a signal. Either mention them normally or keep them out of several recaps in a row.

A worked example of a short session recap

Everything below is invented for the purpose of this example — the campaign, the characters, and the events are not from a real table. It runs about 130 words, which is roughly thirty seconds of reading and just under a minute aloud.

Previously on The Ninefold Road, session 12:

The party are fugitives in Harrow County. Bram burned the Duskwarden's writ in front of the toll clerk rather than pay, and you rode north without looking back.

Sela agreed to carry Old Mother Wend's sealed letter to the abbey at Grieve. She has not opened it. Wend was clear that the debt is settled when the letter is delivered, not before.

The rust-plague in Tanner's Row is spreading faster than Doctor Aldis said it would. Two more doors were marked while you were still arguing about the writ.

Kest still has the iron key off the barge. Nobody has found what it opens.

We open on the ridge above Grieve at dusk, watching a column of smoke come up from the abbey's side of the valley.

Notice what it does. Four of the five paragraphs state a consequence, not an event. There is no combat in it even though there was a fight. It names characters, not classes. And it ends exactly where the next session begins, so the first thing you say at the table is a continuation rather than a restart.

A D&D session recap template you can copy

Answer the seven prompts in one or two sentences each, then delete any that came out empty. What remains is your recap, roughly in order: the first prompt usually becomes your consequence-first opening, and the last is always the cliffhanger. The edit check at the bottom is the eighth step, and the one that tells you when to stop writing.

It is plain text, so it pastes into a Discord message, a shared doc or a notes app without losing its shape. Keep a blank copy pinned and duplicate it each week.

It is also the player-facing half of a pair. The post-session summary sheet in the session notes templates is the record you keep for yourself; this is the part that gets read aloud. Write the summary first and this takes five minutes, because most of the prompts here are already answered somewhere in it.

And when someone really has missed the session, the missed-session guide covers the part the recap cannot do — their character, and the five minutes before the session.

SESSION RECAP
Campaign: ______________   Session #: ____
One or two sentences per prompt. Delete any that come
out empty. What is left, in order, is the recap.

WHERE IS THE PARTY STANDING, AND WHEN?


WHAT IS DIFFERENT IN THE WORLD SINCE LAST SESSION?


WHAT DID THE PARTY DECIDE, IN THEIR OWN WORDS -
AND WHICH DECISION IS STILL BEING ARGUED ABOUT?


WHAT IS NOW OWED, PROMISED OR THREATENED, AND BY WHEN?


WHAT ARE THEY CARRYING THAT THEY DO NOT UNDERSTAND YET?


WHO IS ANGRY AT THEM WHO WAS NOT BEFORE?


WHAT IS ON SCREEN AS WE OPEN TONIGHT?
(present tense - this is always the last line)


EDIT CHECK
Could a player who missed the session play tonight
after reading this? If yes, stop writing.
Aim for 5-10 sentences, 120-200 words.
Cut: initiative, damage, dice, loot lists, shopping.
Never write something false to protect a reveal - omit.

What to do when you cannot remember what happened

The recap is only hard when the session has gone fuzzy. The fix is capture, and capture can be nearly free.

It is worth noticing how much this costs you elsewhere. Reconstructing a fuzzy session is the same work whether you are writing a recap or preparing the next game, and in prep it is pure overhead — you finish it knowing exactly what you knew before, with the useful part not yet started. How long D&D prep takes pulls that apart against the survey data.

A phone lying face up in the middle of the table with the stock voice recorder running is genuinely enough for an in-person game. For Discord games, recorder bots such as Craig can capture a separate track per speaker, which makes a crowded table far easier to follow later. OBS will record your desktop and microphone audio, and Audacity is fine for a local recording you just want to scrub through afterwards. Otter and similar services will give you a rough searchable transcript, and Whisper, OpenAI's open-source speech model, will do the same on your own machine at no cost if you are comfortable on a command line.

Tell your players you are recording, and tell them where the file lives. Nobody enjoys discovering it afterwards, and it takes one sentence at the top of session one — consent and the law covers the version of that conversation worth having. If you go the Whisper route, what works and what does not is worth reading first.

For the notes themselves, a plain document is fine. Obsidian and Notion are both good homes for a campaign log, and a single running Google Doc with a heading per session beats an elaborate system you abandon in March.

If the recording piles up faster than you can listen to it, that is the specific problem DM Scribe was built for — it transcribes the session and drafts a structured recap you edit, rather than you scrubbing four hours of audio.

Whatever you use, write two or three lines during play, at the moment something changes. A recap assembled from four in-session scribbles is faster and better than one reconstructed from memory a week later.

And if those scribbles are all you have, you can paste them into the free session recap generator and get a first draft back without an account. It only knows what you wrote down, which is the honest limit of working from notes rather than a recording.

Where to post the recap, and reading it aloud at the table

Post within forty-eight hours, while you still remember the tone of the session and while the players still care. A recap that lands the night before the next game is a reminder; a recap that lands two days after the session is a small piece of the campaign continuing to exist during the week.

Pick one home and never move it. A pinned message in the Discord channel is the most reliable option for most groups — pin the newest one, unpin the last. If your group does not live in Discord, an email to the table works fine and has the advantage of arriving whether or not people open the app. Keep the full archive somewhere separate and stable, a shared doc or a wiki, and link to it from the pinned post so the short recap stays short. (That archive earns its keep years later, too — it is the raw material if the campaign ever becomes a novel.)

Then read it out at the table. Under a minute, out loud, before anyone touches a die. Hand it to a player and let them read it if you want the table to hear it in a voice that is not yours.

End by going straight into the cliffhanger line — we open on the ridge above Grieve, the smoke is coming up from the abbey, what do you do — with no gap between the recap and play. That transition is the entire reason to write the thing.

D&D recap ideas: five ways to run the recap at the table

The written recap is one format. The job underneath it — everyone holding the same three or four facts before the first die is rolled — can be done at the table five ways, and rotating between them keeps the ritual from going stale.

• A player-led recap, rotating each week. A different player opens the session with what they remember, in under a minute, and you correct only what would break the game. What they leave out tells you what did not land. Rotate it so it stays a turn rather than becoming a job.
• An in-character journal recap. One player writes the session up as their character's diary entry or letter home and reads it aloud. It carries the character's biases, which is the fun of it — let the opinions stand and correct only the facts that matter. The player scribe sheet in the session notes templates gives them four prompts to write it from.
• A previously-on read-aloud with a music cue. Pick a short theme the table will learn to recognise, let it play for a few seconds, and stop it on your first line. If you record your sessions, keep the music out from under the words: music underneath dialogue cannot be cleanly removed from a recording afterwards.
• A three-question quiz round. Before anyone touches a die, ask three questions — who do we owe, what are we carrying that we do not understand, where are we standing. Players answer out loud and you fill the gaps. Keep the stakes friendly: a small reward for the table if you like, never a penalty for forgetting.
• The written recap, sent two days ahead. For a group that meets every two or three weeks, a recap posted the night of the session is long forgotten by the next one. Send it, or send it again, two days before the next game, when people have time to read it and the session is close enough to care about. The version you read aloud at the table then becomes a thirty-second reminder rather than the first time anyone has thought about the campaign since.

If you would rather not start from a blank page

The template above is the blank-page fix. If even that stalls, answer only its first and last prompts — where things stand, and what is on screen as you open — and you have a two-sentence recap that does most of the job.

If you have rough notes, there is a free recap generator here that takes the scrappy bullet list you kept during the session and returns a "previously on" draft plus a short list of key events — no account, no email. It writes the session as a story, so expect it to run longer than the five to ten sentences above and to need its consequence moved to the front. If you have a transcript, a general-purpose AI assistant will draft from it, and the NotebookLM guide walks through that route and where it goes wrong. Treat anything generated as a first draft, not a finished recap. A tool cannot know which reveal you are holding back, so re-read the draft against the "what to cut" section and the secrets section before you post it.