A solo campaign notebook is a return tool. It should answer the question future you will ask: where was I, what changed, what is still open, and how do I begin again? It does not need to become a scrapbook, archive, or public proof of play.
Start With Five Sections
Use sections for character, rules reminders, open threads, map and places, and session log. Keep each section short at first. If you overbuild the notebook before play, it can become the project instead of supporting the project.
For rules reminders, summarize in your own words. Do not copy long rulebook passages into public files or shared templates unless the creator permits it.
Put Current State Up Front
The first page should hold current state: character status, resources, active location, immediate goal, open danger, and next session hook. Older logs can live behind it. This prevents the common problem of rereading ten pages before moving one token.
If the game has official save sheets, use them. Your notebook fills the human memory gaps around them.
Make It Easy to Resume
Use tabs, sticky flags, index cards, or colored edges. If handwriting is difficult, use short typed notes, voice notes, or photos for private reference. If photos are not welcome, write object lists instead: “three cards in hand, lantern spent, bridge locked.”
Accessibility supports are part of the notebook design.
Close Every Session
Use the same closing lines: happened, changed, open, next. That is enough. A long journal entry is welcome when you want it, but continuity should not depend on beautiful prose.
End with one physical restart cue: open to map page, place blue token on bridge, read clue card, roll weather. Future you needs a handle.
