It’s 7:04. You are pulling up the map, muting the guy whose fan sounds like a leaf blower, re-reading the note you left yourself (“they owe Sallow a favor, DO NOT FORGET”), and queuing the tavern playlist. This is, minute for minute, the busiest you will be all night. And by tradition, this is also the exact moment you are supposed to stop everything and deliver a tight, evocative summary of a session that happened nineteen days ago.

I think the tradition is wrong. The DM is the worst-positioned person at the table to give the opening recap, and handing that job to your players makes the whole session better within a week of trying it. If you searched “how to start a D&D session,” this is my answer: start with your players’ voices, one sentence each, before yours.

Why the DM’s recap falls flat

I wrote a whole field guide to recaps, and player-led recapping appears in it as one option on a long menu. This post is me promoting it to the default, because of three things I kept noticing at my own table.

First, your recap is a rerun. You wrote the session, ran the session, and took the notes. When you summarize it, you tell the players what you already decided was important, in the order you decided it, and they receive it the way people receive any rerun: politely, phones within reach. An announcement is happening. Remembering, the thing the recap exists for, is happening to exactly one person in the room, and it’s you.

Second, you will accidentally spoil your own game. The DM knows which of last session’s forty details is about to matter, and DM recaps drift toward those details like water finding a drain. The moment you say “and you also met a fisherman named Orel,” every player at the table writes THE FISHERMAN IS IMPORTANT in their notes. Your foreshadowing budget just got spent on the recap.

Third, and this is the one that converted me: when you give the recap, you learn nothing. When your players give it, you get a live reading of what actually landed. The dramatic reveal you built the whole night around goes unmentioned, and three players independently bring up the goose. That information is worth more than any prep, and the DM recap throws it away every single week.

The round: one thing you remember, one thing you want

Here is the whole mechanic. Go around the table. Each player gives two sentences:

  1. One thing you remember. Any true thing from last session, big or small, in character or out.
  2. One thing you want. What their character is trying to get, avoid, or find out, right now.

That’s it. No narrating, no chronology, no pressure to be complete. Five players, two sentences each, and you’re done in about ninety seconds. Keep it capped there. The moment a recap round turns into a retelling, you’ve traded the snap of an opening for a group essay, and next week people will dread their turn.

Notice what the two prompts are doing. “One thing you remember” is memory. “One thing you want” is intent, and intent is the part of a session that actually survives a three-week gap. In the post about tables that remember nothing, I argued that memory keeps stakes and feelings and discards logistics. This round is built on that grain. You are collecting the ten things the table still holds and skipping the thirty it never will, and it turns out the ten are enough to start a session. The recap that recaps wants beats the recap that recaps events, every time, because wants point forward. An event summary ends with everyone looking at you. A round of wants ends with everyone leaning toward the door of the counting house.

There is a quieter benefit too. The player whose week was terrible, who barely remembers there was a lizard, gets to say “I remember the lizard. I want to never see it again,” and the table laughs, and they are in. Two sentences is an on-ramp anyone can take. A DM monologue, however lovely, asks them to sit still for one more minute of their own distraction.

The gaps are your first scene

Run the round for a few weeks and you’ll notice the same thing every time: the table’s collective memory has holes, and the holes are not random. Nobody mentions the debt to Sallow. Nobody remembers the sealed letter. The name of the town they’re defending has fully evaporated.

Do nothing about this during the round. No corrections, no “actually,” no gentle reminder about the letter. Let the recap be wrong in exactly the ways it wants to be wrong. Then open your first scene inside the biggest hole. The party forgot they owe Sallow a favor? The first knock on the door tonight is Sallow’s courier, smiling, here to collect. The letter went unmentioned three weeks running? Tonight someone else asks about the letter, someone who should never have known it exists.

This is the move that turns the recap from housekeeping into play. The round tells you precisely what the table has lost track of, which means it tells you precisely where surprise is cheapest. You get dramatic irony delivered to your doorstep, free, at 7:05, and all you had to do was listen. When I said the DM recap teaches you nothing, this is the flip side: the player recap is a diagnostic, and a good first scene is just the diagnostic weaponized.

What the table holds, what the record holds

A fair objection: if the players run the recap and the recap is allowed to be wrong, who is keeping the campaign true? Someone sincerely misremembers the deal with the duke, it goes uncorrected in the round, and four sessions later that misremembering has hardened into a dispute.

The answer is to split the job cleanly. The table holds intent. The record holds truth. The recap round is for wants, feelings, and the shape of the story in the group’s head, and it never needs to be accurate to do that job. Accuracy belongs to a written record that exists outside anyone’s memory: your closing note, a player’s index card, whatever your table keeps. When a real dispute shows up mid-scene, you consult the record, settle it in twenty seconds, and play on. The round opens the night; the record referees it. Neither can do the other’s job, and most recap advice fails by asking one instrument to do both.

This is where I’ll mention what we build, briefly. Loracle sits in your Discord voice channel, records the session, and turns it into a recap and a searchable record. When the duke dispute happens, someone asks the bot and gets the actual scene back. Which means the humans at your table are freed to do the thing only humans can do in a recap: be wrong in interesting ways, want things, and lean toward the door.

Start next week

You don’t need buy-in, a rules discussion, or a session zero amendment. Next session, at the top of the night, say: “Before I say anything: around the table. One thing you remember from last time, one thing your character wants right now. Two sentences.” Then be quiet, listen for the holes, and start your first scene inside the biggest one.

Your recap was never supposed to be a performance you deliver to an audience. It’s the sound of five people climbing back into a story, and it works best in their voices, at 7:04, while you sit there taking notes for once.