After the session
Write the recap before it becomes a second job
A useful game-master recap doesn't need to retell four hours of play. Save the decisions and changed facts that your next session could depend on.
Start with consequences
Write down what changed because of the players' choices. A new alliance, a missed deadline or an improvised promise will matter longer than a turn-by-turn account of the fight.
Changed fact: Mara now controls the river gate.
Source: session 12, rough note 7
Open thread: The party promised to return the ferryman's map.
Source: session 12, rough note 11
Separate memory from invention
It's easy to fill a gap with what you meant to happen. Mark anything you're unsure about for review. Don't polish it into a confident sentence until you've checked the original note or asked the table next time.
Keep the rough note close
Add a page, line or timestamp beside each carried-forward item. You can return to the source when a detail is disputed without rereading the entire session log.
Stop when the next game is covered
A private preparation recap can be short. Keep confirmed changes, unresolved commitments and one or two jobs for next time. A polished story for players is a different task, and you don't need one to preserve continuity.
CampaignKeep is testing this handoff
CampaignKeep is an unbuilt software idea that would turn lightly labelled notes into a source-linked next-session briefing. Unclear prose would stay in a review list. The planned price is A$8 per month, and no payment or email is collected.
See the planned offer and give a price answer