Jess missed last week. Work thing, totally fine, everyone said “no worries!” in the group chat. And now it’s game night, the table is settled, and you hear yourself begin the sentence that eats the next ten minutes: “Okay, so, for Jess’s benefit…”

You know how this goes, because you’ve sat through it from both chairs. The DM summarizes, badly, in the wrong order. Two players interrupt to correct details that don’t matter. Somebody checks their phone, then somebody else does, and the energy you need for the opening scene quietly leaves the room. Jess nods along and retains maybe a third of it. Searches for “missed dnd session catch up” spike for a reason: every group hits this, and almost every group solves it the same bad way, live, at the table, on everyone’s time.

Here’s the fix in one line: catch the player up before game night, in writing, stakes-first, and give them one free question per scene once play starts. The rest of this post is how to do that in about two minutes a week.

The monologue pays one person’s debt with six people’s attention

Do the math on the table-side catch-up. One player missed three hours of game. To patch that gap, you spend ten minutes of a session that seven people showed up for, which is over an hour of collective attention, at the exact moment of the night when enthusiasm is highest and most worth spending. You are paying off one person’s debt with the whole table’s best currency.

And the product is bad. A live monologue is events-first by nature (“you fought the cultists, then you found the ledger, then you went to the docks”) because that’s how memory serializes under pressure. But the returning player doesn’t need the sequence of events. They need to know what their character is walking into: what’s at stake, what the party owes, what’s about to go wrong. Facts without stakes don’t stick, which is the same reason nobody remembers last session even when everyone attended.

So move the catch-up off the table entirely. Game night is for playing. The gap gets closed before anyone sits down.

The two-minute brief: what you missed, what you owe, what’s about to matter

The day before the session, post three short paragraphs in your campaign channel, addressed to the player who missed. Write it in this order, and keep the whole thing under 150 words:

What you missed, as it affects you. One or two sentences of events, filtered hard through their character. Skip everything their PC wouldn’t care about. “The party took the smuggler’s job. Your contact Veska vouched for you to get it, which means your name is on this now.”

What you owe. Promises, debts, and plans the party made while they were gone, because these are the things that will ambush them mid-scene. “Everyone agreed to split the ledger money with the dockworkers. Also Bram told the captain you’d handle the manifest, so that’s yours.”

What’s about to matter. One line of looming stakes, phrased as pressure, with the mystery intact. “The handoff is at midnight tomorrow, and nobody has told Veska about the second buyer.”

Stakes-first, second person, their character at the center of every sentence. You’ll notice this is the same shape as a good opening recap, and that’s the point: you’re writing a private “previously on” for an audience of one, tuned to the seat that was empty.

What to leave out, on purpose

Leave out the loot ledger. Leave out travel. Leave out the forty-minute shopping scene. If they need a number, it’s in the party notes; the brief is for stakes, and padding it with inventory teaches the player to skim it.

Leave out the jokes, too, even the great ones. “You had to be there” is an acceptable answer at a table, and honestly a healthy one. The returning player will hear the goose story retold at the table anyway, with better delivery, and the retelling is a bonding moment you’d be stealing by summarizing it.

And keep your secrets. A brief is written by the DM, so write around the mystery the same way you’d narrate around it. “You don’t know who the second buyer is” is a perfectly good sentence. Some DMs panic here and over-share to compensate for the absence. The absent player is owed the party’s knowledge, never the DM’s.

At the table: one free “wait, what?” per scene

However good the brief is, gaps will surface mid-play. So make the patch mechanic explicit at the top of the night: the returning player gets one free “wait, what?” per scene. They ask, anyone at the table answers in one sentence, play continues, zero judgment attached.

Saying this out loud sounds like a small thing. It changes the night. The free question converts the returning player’s confusion from a private embarrassment into a table mechanic, which means they actually use it, which means they stop bluffing through scenes they only half-understand. The player who pretends to be caught up is the one who derails act three by cheerfully betraying a plan they never heard about.

Make missing a session cheap, because someone always will

Zoom out and this is a design problem, the same one you solve when you run a game across time zones: over a long campaign, absence is weather. Someone will miss. The campaigns that survive treat a missed session as a routine event with a routine cost, close to zero, for both the character and the player. The absent PC fades into the background and comes back without punishment. The returning player gets the brief, gets the free question, and gets their opening scene like everyone else.

Groups that handle absence punitively, with in-game penalties or a social expectation of apology, teach players a darker lesson: that falling behind feels bad. Players who feel behind start finding reasons to skip, and skipping compounds. Most campaigns end the same quiet way: attendance frays, one missed week at a time.

The brief writes itself if the session was recorded

The honest objection to all of this: it’s one more thing the DM writes, every week somebody misses, from notes the DM may never have taken. That objection is why we built Loracle the way we did. It sits in your Discord call while you play, and afterwards the recap is just there in the channel, stakes and promises included, in whatever language your table plays in. The player who missed reads it the next morning without anyone writing a word. You add one line about what they personally owe, and your two-minute brief took thirty seconds.

Either way, with a bot or a pen: write the catch-up before game night, keep it to stakes, grant the free question, and let the table spend its best ten minutes playing. Jess missed one session. There’s no reason the other six of you should miss the start of this one.