The post-session routine that keeps a campaign alive
The ten minutes right after the game are the highest-leverage prep you will ever do. Everything is still fresh, and future-you will remember none of it. Here is the wind-down.
The short answer
Before you close the laptop, do three things: capture what happened while it is fresh, thread the new facts into your world, and tee up next session. Ten minutes now saves an hour of "wait, what were we doing?" later — and it is the difference between a run of one-shots and a campaign that remembers itself.
The wind-down
- Capture the beats. Note the three to five things that actually mattered tonight, in a sentence each, while you still remember the room. This is the raw material for the recap and the answer to next month’s "when did we meet the collector?"
- Log the consequences. What is now true about the world because of what the players did? An NPC is dead, a faction is hostile, a promise was made. Consequences are what make a campaign feel like it is keeping score.
- Update the NPCs and places touched. Add the "since last time" line to anyone who recurred, and note anything the players learned. Retrofitting this after five sessions is a job nobody ever does — that is why it goes in the wind-down.
- Draft the recap. Write the short, player-facing version now, while it is warm. You will send it the day before next game as the "previously on…". The morning-after recap is always the best one you will write.
- Tee up one thread for next time. Note the single open question the next session will lean on, so you never start prep from a blank page.
A worked example
After the harbor session: Beats — fence found dead, reliquary gone, party traced a ship leaving at dawn, buyer identified in town. Consequences — harbormaster now considers the party a nuisance; the rogue owes a witness fifty crowns. NPCs — Verrin the clerk fled the city (add "since last time"); the buyer now knows the party is on his trail. Recap drafted, four sentences, ends on "the buyer knows you are coming — he has not decided what to do about it." Thread for next time: the reliquary aboard the ship is a fake.
If you only ever do one item on this list, make it the recap. It is the one that changes what happens at the next table, not just what you remember.
Questions GMs actually ask
What should I do right after running a session?
Spend ten minutes while it is fresh: capture the three to five beats that mattered, log the consequences of what the players did, update any NPCs and places they touched, draft a short recap, and note one thread for next time. Doing it immediately is what makes it accurate.
Why write the recap the same night?
The morning-after recap is the best one you will write because the session is still warm in your memory. Waiting a week means reconstructing it from sparse notes, and the emotional beats — the ones players actually care about — are the first to fade.
How does a post-session routine keep a campaign coherent?
It turns each session into durable, linked memory: consequences recorded, NPCs updated, threads tracked. Over months that accumulation is the difference between a campaign that remembers itself and a run of disconnected nights.
Where Storywright fits
Storywright was built around exactly this loop. Your session notes are already linked to the NPCs and places they mention, so capturing consequences updates the world instead of a separate document. When you close the session, it drafts the recap from those notes; you sharpen it and publish, and players get it as a briefing before the next game. The wind-down stops being discipline you have to remember and becomes the shape of the tool. Free to start, free for your players.