Write yours · saved in this browser
Free read-aloud D&D session recap
Catch everyone up in ninety seconds. Then return to the story.
Use five sentences to restore where the party was, what became true, what they chose, what it cost, and what demands attention now.
0/5
Previously, at the table…
Ready to read aloud- 1
Where we were
You followed Mara beneath the Drowned Chapel.
- 2
What we learned
Chancellor Vey's crest marks the warning seal.
- 3
What we chose
You trusted Mara and took the lower route.
- 4
What it cost
Orin now knows you carry the bell-map.
- 5
What happens now
A bell rings from a tower that has been empty for forty years.
Opening question: Who answers it?
The worked example reads in roughly a minute. What you type stays in this browser and is never sent to Multiloop.
Use the recap you need
The same events can serve different readers.
A table opener creates momentum. An absent-player update restores inherited decisions. An archive preserves names and consequences worth finding later.
Read at the table
End on the opening image.
Aim for 60–90 seconds, then ask a question that belongs to the players.
Catch up a player
Name the decisions they inherit.
Include the choice, the consequence, and what they need to decide next—without replaying every scene.
Save for later
Preserve the handles you will search for.
Use consistent names and keep the decisive consequence attached to the session it came from.
Edit for re-entry
Keep the decision. Cut what the outcome already says.
Chronology records what happened. A useful recap restores the information and pressure needed to make the next choice.
The raw account
The party met at the Lower Quay, haggled with the ferryman, bought rope, argued about the stairs, rested, inspected three doors, and then Mara showed them the lower route.
KEEP THE DECISION
You trusted Mara and took the lower route—leaving Factor Madric’s offer unanswered.
Where the recap lives in Multiloop
One session record, three separate jobs.
Write what happened, decide who can read the recap, and keep player perspectives separate from private DM preparation. Those are related choices, not one master visibility switch.
The Ashen Accord · Session 12
The Bell Below
Quick Recap
Mara led the party beneath the Drowned Chapel, where Vey’s crest marks the warning seal. They took the lower route. A bell now rings from an empty tower.
Detailed Notes
- Accepted Mara’s route despite Orin’s warning.
- Promised Orin 200 gold for a dry passage.
- Ilyra kept a fragment of black wax.
Inside the session record
Give the recap a session record of its own.
Multiloop keeps Quick Recap and Detailed Notes beside attendance, player-note perspectives, sharing controls, and private preparation.
A free Multiloop account and campaign are required. The recap drafted in this browser is not transferred automatically.
Where the five-beat template is enough
A notes app is enough. Use the session when the recap needs context.
Paste the five-beat recap into Discord and stop there if that solves the problem. Create a session record when attendance, player perspectives, sharing choices, and private next-session preparation need to sit around the recap.
Questions worth settling before play
Session recap questions, answered plainly
How long should a D&D recap be?
For a spoken table opener, 60 to 90 seconds is a useful target. Go longer only when players genuinely need more context to act.
Who should write the recap?
The DM can write it, players can rotate, or the group can keep a shared version. Choose the habit that will actually survive a busy week.
Should a recap include secret DM information?
No. Write the recap for its audience. Keep future plans, hidden motives, and private reminders in a clearly separate DM-only space.
Open the next session with momentum
Keep the recap with the session.
Copy the five-beat template for free. When the recap needs attendance, player perspectives, sharing controls, and private preparation around it, Multiloop keeps those boundaries attached to the same game.