Session six. You open your notes and start reading: "Okay, so round one, Brannoc rolled a 14 on initiative, the bandit went first, missed, then Sel cast a spell..." Around round three of the retelling, two players get up for snacks and a third is scrolling under the table. You can't blame them. You've told them what happened. You haven't told them why any of it matters tonight.
Why the blow-by-blow recap kills momentum
Reading your notes in order feels diligent. You wrote them in order, so you read them in order. But sequence is the least useful thing about last session. The players already sat through it once, and they don't need a replay. They need to know where they're standing.
The recap's only job is to drop the table back into the situation with their hands on the controls. For that you need three facts and nothing more:
- Who the party is trying to stop or help.
- What happens if they fail.
- How long they have.
The rest can stay in your notebook. That includes the exact damage on the killing blow, the shop where the wizard bought rope, and the running joke about the goat. Keep all of it out of the first minute of play.
Set a ceiling of two minutes. Past that, the recap stops pulling the table forward and starts dragging it backward. You end up holding a memorial for last week when you should be starting this one.
A short recap is also a quiet reset. Say last session drifted because the party spent two hours trying to buy a tavern. You don't need to scold anyone for the detour. Restate the goal and the clock, and the tavern shrinks back to the side errand it always was. (For handling the detour itself, see what to do when players derail the plot.)
The 90-second last-time-on format
A TV "previously on" segment doesn't rerun the episode. It cuts straight to the handful of moments that set up tonight. Borrow that structure. Here's a four-beat skeleton you can reuse every week:
- Name the goal. What were they trying to do?
- Name the obstacle or reversal. What went wrong, or what surprised them?
- Name the clock. What happens if they wait?
- Ask the table a direct question.
All four in one breath sound like this:
"Last time, you broke into the baron's wine cellar looking for the ledger. Instead you found blood on the floor and no ledger. The guards change shift at dawn. What do you do?"
About fifteen seconds. The question is the part to protect. It hands control to the players before anyone's attention wanders off. If you close with "...and that's where we left off," you get a pause while everyone waits for someone else to speak. Close with a question and somebody answers it.
The skeleton works outside combat too. In a social session, the goal could be "win the guild vote," the reversal "the treasurer switched sides," and the clock "the vote is at the next bell." In a dungeon crawl the clock can be tiny: "your torches have maybe an hour left."
And if you sit down to write the recap and can't find a clock at all, pay attention to that. The adventure probably needs some pressure, and you've just spotted the gap before the session started.
Hand recap duty to a rotating player
You don't have to deliver the recap yourself. We prefer handing it off.
Each session, pick a different player and give them a title: Keeper of the Last Session. Just before play, slide them an index card with three short lines:
- Goal: find the baron's ledger
- Obstacle: cellar empty, blood on the floor
- Clock: guards change at dawn
They get two minutes to turn that into a recap in their own words. Then you take over.
The first payoff is investment. A player who says the summary out loud owns it in a way a listener doesn't. Suppose the rogue's player recaps the cellar break-in. By the second sentence they're already thinking about the cellar again, maybe half in character. That warms up the table faster than your voice can.
The second payoff is stranger. Players misremember, and you can use that. Say the Keeper announces, "Mayor Hale was on our side, he basically gave us the key." He didn't. Hale stalled them for an hour and pointed them at the wrong door. You could correct the record. Or you could let it stand. Maybe Hale wants them to believe he helped. Maybe another player pipes up with a different memory, and now the table is arguing about whether the mayor can be trusted. You didn't prep that argument, and it's better than most of what you did prep. The mistake also shows you exactly what the players believe, which is hard to find out any other way.
The cost is that some people freeze when you put them on the spot. Let them pass, no penalty, or pair them with a co-recapper. The card does a lot of the work here, since nobody has to build a summary out of thin air.
The card works better still if the Keeper has something to check against. Even a rough written record of last session lets them confirm a name before they say it. Session transcripts posted to your Discord give you that record without anyone scribbling notes during play.
One image beats ten facts
You can push this further and drop chronology entirely. Skip the list of events. Pick the single sharpest image from last session and open on it:
"You're staring at a letter burning in the hearth, the wax seal still unbroken enough to read one word: Hollow."
Then stop talking for a second. Add the clock and the question afterward if you need them. Most of the time the image has already done the heavy lifting.
People remember moments, not itineraries. A player who couldn't tell you what happened in the second fight will still remember that letter curling in the flames, and that one memory pulls the rest of the session back with it. Ten facts ask the table to rebuild last week from parts. One image gives it to them whole.
The image also sets the mood before anyone touches a die. A burning letter means dread. A goblin wearing the paladin's helmet backwards means the night is going to be silly. You choose the tone of the opening scene when you choose the picture.
The best pictures usually come from the villain, specifically from a villain's visible want. Think of the cult leader pressing her palm against the sealed door, or the usurper trying on a crown that doesn't fit him yet. A villain whose desire the players have actually watched gives you an opening image every week. If your recaps keep sliding into "and then you fought some guys," take that as a sign the villain is too far offstage.
Fold foreshadowing into the recap instead of a separate reminder
Plants wither. You set up an ominous letter three sessions ago, or a stranger who knew the fighter's real name. Then two sessions of other business piled on top, and now the payoff is close and nobody remembers the setup.
The clumsy fix is the aside: "Oh, and remember that letter? You still have it." Players hear a siren. You've told them the letter matters, and you've stopped the game to do it.
The cleaner fix is to fold a plant from three sessions back into this week's recap, where it travels alongside material the players already treat as relevant. Take the cellar recap and add one sentence:
"Last time, you broke into the baron's wine cellar looking for the ledger. Instead you found blood on the floor and no ledger. The blood pattern matches the ink on that ominous letter you still haven't opened. The guards change shift at dawn. What do you do?"
That one line recaps the cellar and replants the letter at once. The letter now feels tied to the current problem. Nobody dragged it in from nowhere. And since the recap is the part of the night where you're stating plain facts about the world, players file the detail as part of the situation. It doesn't register as a hint.
Watch the dose. One folded plant per recap, two at the very most. Load three callbacks into every recap and players start reading it like a clue sheet, weighing every word. In a heavy mystery campaign that can be fun. Elsewhere it turns orientation into homework, and you lose the momentum you wanted.
Investigations benefit most. A mystery can have every clue it needs and still stall because the players forgot half of them. The weekly recap is your one chance to restate evidence without anyone feeling hand-held, so a lot of clue retention happens right there. For building the clue structure itself, see how to run a mystery your players can actually solve.
Sample scripts: combat session vs investigation session
Here are two full scripts, each 60 to 90 seconds spoken. Read them aloud once to check the timing.
Combat-heavy session
"Last time, the warband cornered you on the bridge over the Greywater. Thirty of them, and you were four. You dropped the bridge support to buy time, and half of them went into the river with it. Their leader didn't. Captain Rhessa Vane pulled herself up the far bank, looked straight at you across the gap, and swore she'd hunt each of you by name. She knows your faces now. Sel, she watched you cut the rope. The nearest town is a day's walk east, and the warband has horses. Where are you headed to lay low?"
There's no initiative order in there, no damage totals, no tally of who hit whom. The script is built around a threat and a grudge. Rhessa is the face of the danger, and calling out Sel by name makes one player feel the target on their back. Think of it as the other half of ending a session on a cliffhanger. The cliffhanger leaves the threat hanging. The recap picks it up and hands it back to the players.
Investigation-heavy session
"Last time, you learned the missing merchant, Dorran Pell, wasn't kidnapped. He vanished the same night three other debts in town went unpaid, all owed to the same lender. Mags at the Copper Kettle told you he left 'after the second bell, swear on the Kettle.' But the stablehand saw his cart gone before sundown. Mags lied about the time he left. You still don't know why. The lender's collectors come back to town in two days. What's your next move?"
The combat script hangs on a threat. This one hangs on a contradiction. Mags said one thing, the stablehand said another, and the gap between them is the hook. Don't explain it. State both sides plainly and let the players feel the itch.
This script is also where recaps tend to go soft. Everything rests on what Mags actually said. If the Keeper paraphrases it as "Mags said he left late," the contradiction blurs and the clue goes dull. Memory flattens exact wording first, and in a mystery the exact wording is often the clue.
So have the Keeper check the record before they pick up the card. With a session transcript in your group's Discord channel, they can quote Mags word for word instead of guessing. LorePanic can post those transcripts for you after each session. Whatever your source, copy Mags's line onto the card inside quotation marks: "after the second bell, swear on the Kettle." When the Keeper reads it aloud, the table hears the lie exactly as it was told.