Session preparation
Prepare the next session without rereading every note
Scattered session notes are hard to scan when the next game is close. Pull out only the unresolved threads, confirmed changes and jobs that could matter this time.
Mark the lines that carry forward
After a session, label the few facts you expect to need again. Keep the label beside the original wording. You don't need to reorganise the whole document or rewrite it as a campaign wiki.
Open thread: Find who paid the ferryman.
Source: session 12, line 18
Next-session job: Decide what the ferryman knows.
Source: session 12, line 24
Remove threads when they close
Mark a thread resolved where the answer appears. That gives you a reason to remove it from the next briefing while preserving the old note. Deleting the original makes later contradictions harder to check.
Don't promote guesses into campaign facts
Notes can contain abandoned ideas beside events that actually happened. Put a phrase such as the ferryman might work for Mara into a review list. Decide whether it's true before carrying it forward.
Build a short briefing, not another archive
Start with open threads and explicit preparation jobs. Add only confirmed NPC or location changes that could affect the next session. Keep a session, page or line reference beside every item so you can check the source quickly.
CampaignKeep is testing this exact job
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