How to Write a Useful Recap for a Player Who Missed the Last RPG Scene

Start with the player’s immediate question

The returning player usually needs to know: Where is the group now? What happened while I was away? What does my character know? What can I do next? Shape the recap around those questions instead of writing a transcript or a chapter of campaign fiction.

A practical target is a few concise paragraphs or a short bullet list. There is no universal ideal length: a travel scene with one decision may need only a few sentences, while a session with several locations, clues, and lasting consequences needs more. The test is whether the player can rejoin without asking the group to reconstruct every moment.

A strong recap distinguishes the session’s events from the scene the player missed. Open with a one-sentence status update, then summarize the missed scene, and finish with where the party stands now. This gives the reader an anchor before introducing new names and details.

Reconstruct the scene from reliable notes

Write soon after the session, while the sequence is fresh. Use your notes, shared campaign log, or a quick check with someone who attended. D&D’s 2024 Basic Rules recommend taking notes on what happened and the end-of-session situation so the game master can refer to them when preparing the next session. The same source says a session recap can come from the GM or players, with different advantages for each approach. D&D Beyond, “The Basics”

Capture the scene in this order:

This sequence helps prevent a recap from turning into disconnected lore. For example: “At the observatory, the group found the brass door sealed and heard the archivist arguing with someone inside. Mara traded the moon map for the archivist’s key. The party opened the door, but the archivist had already left; a fresh trail of blue chalk led downstairs. The group is now at the top of the stairwell.”

Separate facts, clues, and guesses

A recap should not quietly turn an interpretation into a confirmed fact. Label what the characters observed, what an NPC claimed, and what the players suspect. That distinction matters in mysteries and open-ended stories, where a character’s inference can be wrong even when the recap is accurate.

Try phrasing details precisely: “The guard said the captain left at sunset” reports dialogue; “The captain left at sunset” presents it as fact. “The party suspects the blue chalk marks a route” preserves an inference. If the notes do not establish what happened, say so briefly or check with the GM before sharing it.

Also separate player knowledge from character knowledge when it affects the scene. If the returning player heard an out-of-character plan but their character was elsewhere, do not present that plan as something the character knows. You can provide the player with enough context to participate while making the boundary explicit: “You, as a player, know the group plans to question the ferryman; your character was not present when they made that plan.”

Keep the absent character’s knowledge and choices clear

Explain what the character experienced, what they were told afterward, and what remains unknown. Do not imply that the absent player’s character made a consequential choice unless the table agreed in advance how that character would be handled. If another player or the GM temporarily portrayed the character, mention only the actions that matter to the current situation and invite the returning player to clarify their character’s intentions going forward.

For example: “While you were away, the party crossed the old bridge. Your character stayed with the pack animals, so they did not see the meeting in the tower. The others told you that the mayor offered a reward, but they have not explained why they distrust him.” This lets the returning player decide how their character responds without granting them unexplained knowledge.

There is no single procedure that suits every campaign. D&D’s guidance says that if a missed player’s character left the party for a while, the GM should make sure there is a way for that character to return. That is a useful reminder to make the character’s current position intelligible, though individual tables may handle absences differently. D&D Beyond, “The Basics”

Include the details that will matter next

A recap does not need every joke, failed roll, or repeated attempt. Keep a detail when it changes what the characters can do, explains why they are somewhere, introduces a person likely to matter, or records an unresolved promise or danger. Include a memorable character moment when it helps the returning player understand the relationships or mood in the current scene.

A useful editing question is: “Would leaving this out make it harder for the player to choose what their character does next?” If not, it may belong in a longer campaign journal rather than this catch-up note. A journal can preserve more history; the recap should help someone re-enter the present scene. The Alexandrian’s discussion of campaign recall describes both player-led scene-by-scene recaps and campaign journals as different tools, noting that journals take time but can help in large, complicated campaigns. The Alexandrian, “GM Don’t List #10: Idea Rolls”

Use a player recap as a check, not a test

At the next session, invite a player who attended to summarize the previous events if that suits the group. Then fill in the few facts that matter and give the returning player a moment to ask for clarification. D&D’s rules describe a GM-led recap as useful when specific information needs to be delivered concisely, and a player-led recap as a way to learn what the group considers important; the GM can add missing details. D&D Beyond, “The Basics”

Treat this as a way to orient the table, not a memory quiz. A player’s version may emphasize a character beat or an unexpected detail that the GM’s notes missed. The Alexandrian recommends prompting scene by scene and remembering that recaps can include cool moments and character beats as well as mission-critical information. The Alexandrian, “GM Don’t List #10: Idea Rolls”

A quick written recap also helps when players cannot all meet before the next session. Chaosium describes two Call of Cthulhu campaign groups planning short between-session discussions about what happened and what they intend to do next. That example supports a simple practice: preserve the current situation and intentions, while making clear that plans can change once play resumes. Chaosium, “Significant Streams #11: Armchair Keepers of Arcane Secrets”

A practical recap template

Use this structure as a starting point, then remove headings that do not fit the session:

For instance: “You rejoin the group outside the flooded mill, just before nightfall. While you were away, the others followed the lantern signals to the mill and found a locked cellar hatch. They persuaded the miller to lend them a key, but he insisted they return it before dawn. Your character was guarding the road and saw no one approach. The group is deciding whether to open the hatch now or question the miller again.” The names, events, and stakes here are fictional; adapt the structure to the actual session.

Common recap mistakes to avoid

A good recap does not reproduce the missed scene. It gives the player enough accurate context to understand the present, preserves the difference between fact and speculation, and leaves room for them to decide what their character does next.

Sources

Keep exploring this topic