I run a solo D&D 5e campaign that has quietly crossed 40 sessions, and the only reason it survived past session five is a tracking system I built after watching three earlier campaigns die from the same cause. Losing the thread between sessions kills more solo campaigns than bad dice, bad rules, or bad luck. Nothing saps motivation faster than sitting down to play, opening your notebook, and spending 20 minutes trying to remember what your character was even doing.
This guide shows you how to track a solo campaign’s progress across many sessions using a simple, repeatable system. I will walk you through the five-step framework, the five data categories worth tracking, the before-session and after-session rituals, the notation syntax that makes your notes searchable, and a copy-paste session template. Whether you play D&D 5e, Ironsworn, Shadowdark, B/X, or hop between systems, the same bones work.
Table of Contents
Why Tracking Solo Campaigns Is the Difference Between a Campaign That Ends and One That Lasts?
Most solo TTRPG campaigns die from neglect, not from catastrophe. The story fades, the momentum leaves, and the next session quietly never happens. The single biggest reason is that the player has no memory hook to grab onto when they sit back down.
The 20-Minute Re-Entry Trap
Without a tracking system, the first 20 minutes of every solo session are spent re-reading old notes. The session officially starts, but you are not playing yet. You are catching up. That warm-up window is where most solo campaigns quietly die, because the player procrastinates starting the next session at all. The briefest, cheapest fix is a 3-to-5 bullet session recap at the end of every previous session. Reading three bullets is fast. Reading pages of prose is not.
The Motivation Death Spiral
When re-entry is hard, motivation drops. When motivation drops, sessions get skipped. When sessions get skipped, the notes get more confusing. When the notes get more confusing, re-entry gets even harder. The loop closes on itself, and the campaign ends. A simple, consistent tracking system breaks that loop. The session always starts on a specific bullet, the recap is always three lines, and the next session is always a 5-minute reset away.
Tracking is not about recording everything. It is about preserving the spark that made you want to keep playing. Treat your solo campaign journal like a hook, not a ledger.
How to Track a Solo Campaign’s Progress Across Many Sessions in 5 Steps?
Track a solo campaign’s progress across many sessions with this 5-step system: (1) run a 5-minute before-session ritual to re-read your last recap and quest threads, (2) capture only what changes during play, (3) tag every NPC, location, and story thread in a consistent notation, (4) run a 5-minute after-session ritual to write a 3-bullet recap and update your dashboard, and (5) keep one campaign dashboard page that holds the current state of every active thread.
Run a 5-minute before-session ritual. Re-read the last session’s 3-5 bullet recap, scan the active quest threads, and pick one micro-goal for tonight.
Capture only what changes during play. Skip filler. Write down the new NPC, the new location, the changed quest status, the depleted resource.
Tag NPCs, locations, and threads in a consistent notation. First mention gets a special tag, references get a short one. Your notes become searchable later.
Run a 5-minute after-session ritual. Write the recap, update the dashboard, mark closed threads, and leave 1-3 open questions for next time.
Maintain a campaign dashboard. One page that always shows the current state of every thread, NPC, and location. This is your game’s save file.
The rest of this guide expands each step into the specific tactics, templates, and tool choices that make the system work for long campaigns. Skim the framework above, then dig into the sections that match your style.
What to Track in a Solo Campaign: The 5 Essential Data Categories?
Tracking solo RPG progress comes down to five categories: PC status, NPCs, locations, quest threads, and world state. Most failed tracking systems fail because they try to capture everything. Successful systems capture only what changes between sessions, and they keep it bucketed into these five buckets so the dashboard stays current.
PC Status and Resources
Track your character’s hit points, spell slots, exhaustion level, conditions, gold, encumbrance, and any per-session resources. The goal is to open your dashboard and know exactly what your character is holding and missing. Update this at the end of every session, not during play. During play, just scribble a one-word note like “lost 12 HP” or “spent 50gp” and clean it up later.
NPCs and Relationships
Not every NPC deserves a full entry. Only track NPCs that matter. A useful threshold: if you might mention this NPC’s name in three or more sessions, they get a card. For each, note name, role, last-known location, faction, and one or two relationship hooks with the PC. A merchant you will never see again does not need a card. A rival who appears in three different towns absolutely does.
Locations and Maps
Locations matter because they are physical anchor points in your story. Track only the ones the PC has visited, plans to visit, or hears about. For each, capture the name, a one-line description, the NPCs present, and the active threats. Whether you use a hex map, a region map, or a simple bulleted list of place names, the rule is the same: the dashboard always shows what the PC knows about the world.
Quest and Story Threads
This is the most important category. A story thread is any plot line with an open status. It can be a side quest, a romance, a personal character goal, a faction slow-burn, or a prophecy. Each thread gets one line on your dashboard, plus a status: open, closed, or abandoned. Most failed campaigns let dead threads pile up until the dashboard is unreadable. Prune aggressively. If a thread has not moved in three sessions, mark it dormant or cut it.
World State and Factions
Factions are the slow movers of your campaign. A guild gains power, a kingdom shifts politics, a cult grows. Track each faction with a one-line current state and a flag if something changed this session. This is the category solo players most often forget, and it is the one that makes the world feel alive when you return to it. A line that says “The Crown is now hostile to the Iron Wardens” is enough to trigger a whole scene three sessions later.
The Before-Session Ritual: Re-Entering Your Campaign in 5 Minutes
The before-session ritual is the single highest-leverage thing you do for solo campaign longevity. It is the difference between a 5-minute re-entry and a 20-minute re-entry. Here is the exact sequence I run every time I sit down.
Read the last session’s 3-5 bullet recap. This is the recap you wrote at the end of last session, not the full session notes. Bullets only.
Skim the quest thread list. Glance at the active threads on your dashboard. Pick the one that pulls you most.
Review active NPCs and their last-known status. You only need a quick scan. The dashboard already has the details.
Set one micro-goal for this session. Not a session plan. One specific thing you want to happen tonight, like “find the cartographer’s apprentice” or “confront the innkeeper.”
Note 1-3 open questions for the oracle. These are the questions you would ask the GM if you had one. Save them for play, not for prep.
That is the entire ritual. Five steps, five minutes, and you are sitting at the table ready to play. The point is not to plan. The point is to enter the world with a single thread in your hand.
During the Session: What to Capture and How to Notate It
During a solo RPG session, capture only what changes: new NPCs, new locations, resolved quests, depleted resources, and faction shifts. The notation you use should make these things searchable later, not aesthetic. Three simple tricks cover 90% of the work.
First Mention vs Reference Syntax
When you first encounter an NPC, location, or thread, give it a unique tag. For example, the first time you meet a halfling smuggler named Pip, write [N:Pip|halfling smuggler|Jorvik docks]. Every later reference writes just [N:Pip]. This is the basis of most solo TTRPG notation systems, including the Lonelog spec and the Solo TTRPG Notation Obsidian plugin. The first mention defines the entity, the reference keeps your notes short and searchable.
Story Thread Tagging
Open a story thread the first time it appears with [T:thread-name|status]. The status is open, closed, or abandoned. When the thread moves, you update the status. When the thread plateaus for more than three sessions, change it to dormant. This is what separates a campaign dashboard from a pile of session notes. The dashboard always shows how many threads are open, which is the most useful metric for whether the campaign still has momentum.
Progress Clocks, Tracks, and Timers
A progress clock is a visual tracker that fills as danger increases. Use it for threats that grow toward a tipping point. A progress track fills as you make progress toward a goal. Use it for quests with measurable milestones. A countdown timer counts down to a deadline. Use it for time-sensitive events like “the festival is in three days.” Notation-wise, a clock or track is usually a 4-segment or 6-segment visual filled with a single character. Keep them on your dashboard. They are the fastest way to spot momentum at a glance.
Oracle Dice Logging
Every oracle roll is a piece of campaign state. Record the question, your roll, and the interpretation in one line. “Oracle: will the bandits surrender? Result: yes-but. They surrender but demand half the loot.” Two sessions later, that line will remind you exactly how that scene played out. Skip the explanation, keep the result.
The After-Session Ritual: Close the Loop in 5 Minutes
The after-session ritual is the bookend of the before-session ritual. It is also the only reason the next session can start in five minutes. The temptation is to write more. Resist it. Five minutes is the goal.
Write a 3-5 bullet recap. These are the only bullets you need next session. Skip flavor. Keep plot turns, decisions, and state changes.
Update the campaign dashboard. Cross out closed threads, add new ones, mark NPC status changes, and adjust any progress clocks or tracks.
Mark any threads closed or abandoned. If a thread resolved, drop it off the active list. If it is dead, mark it abandoned. A clean dashboard matters more than a complete one.
Set the next session’s micro-goal. One sentence. Stash it next to the recap so future-you finds it instantly.
Write 1-3 open questions for next time. These become the starting fuel for the next oracle rolls. They are not questions to answer now. They are questions to carry forward.
That is the entire ritual. If you skip a session, the rituals still apply. They are the muscle that keeps the campaign alive.
Tools for Solo Campaign Tracking: Physical Journal vs Notion vs Obsidian vs Dedicated Apps
The best tool for solo campaign tracking is the one you will actually use. A beautiful Obsidian vault you never open is worse than a cheap notebook you always do. Most solo players settle on one of four approaches, and each has real strengths.
| Tool | Strengths | Weaknesses | Best For |
|---|---|---|---|
| Physical journal | Tactile, immersive, no setup, no friction | Hard to search, hard to link, easy to lose | Players who want immersion and minimal setup |
| Notion | Free, fast templates, easy to share, blocks, databases | Tends to over-engineer, slow with large campaigns, offline is weak | Players who want a polished dashboard fast |
| Obsidian | Local markdown, powerful plugins, fully searchable, linkable | Learning curve, requires setup, plugins can break | Players who want long-term, portable campaigns |
| Dedicated solo app (Saga20, Lonelog, etc.) | Built-in notation, automatic indexing, dashboards out of the box | Niche, may be abandoned, sometimes paid | Players who want zero setup and a guided system |
Pick the row that matches your style. Hybrid setups work too. Many solo players keep a physical journal for the narrative session log and a digital dashboard for NPC and thread tracking. The split is fine as long as the dashboard is the single source of truth for current state.
A Reusable Solo Campaign Session Template You Can Copy
Here is a session template you can paste into any tool that supports markdown. It works in Obsidian, Notion, Saga20, or a plain text file. The structure is the same as the rituals above.
# Session [number] - [date]
## Before-session
- Last session recap: [paste 3-5 bullets]
- Active quest threads: [paste thread list]
- Tonight's micro-goal: [one line]
## During-session
- Scene 1: [name or one-line]
- New NPCs: [tags]
- New locations: [tags]
- New threads: [tags]
- Oracle rolls: [Q, roll, result]
- Scene 2: ...
- Scene 3: ...
## After-session
- Recap (3-5 bullets):
- [bullet]
- [bullet]
- [bullet]
- Dashboard updates:
- Closed threads: [list]
- New threads: [list]
- PC status change: [line]
- Faction change: [line]
- Next session micro-goal: [one line]
- Open questions: [1-3 lines]
Save this as your session template. Duplicate it every time you start a new session. After 10 sessions, the pattern becomes automatic, and that is when the system pays off.
How Much to Write: Avoiding the Novel-Length Notes Trap?
The most common solo tracking mistake is writing too much. Many players, especially those who love narrative, write detailed prose for every session. The first session is fun. The tenth session is a slog. By the twentieth, the notes are unreadable. The fix is to choose a depth on purpose, not by default.
Here is a useful rule of thumb: write only what you would forget in two weeks. If you would absolutely remember the halfling bartender’s name in a fortnight, do not write it down. If you can predict that you would forget the tavern’s location in two sessions, write it down. The level of detail should match the level of narrative weight the item carries.
For a typical solo campaign, the right depth is usually bullet points, not paragraphs. One line per scene. One line per NPC introduction. One line per oracle roll. The role of session notes is to jog memory, not to be the memory itself. Your memory is the story. The notes are the index.
If you want a write-up for sharing as a blog play report or a novel draft, do that as a separate, optional layer. The campaign notes themselves stay short. The play report is a polished output, not a working log.
Managing Long Campaigns: Tracking Across Dozens of Sessions and System Changes
Around session 30, the campaign starts to feel like a different game. You have dozens of NPCs, a dozen threads, multiple factions, and a PC with a complicated history. The dashboard that worked at session 10 will not work at session 30. Two habits keep long campaigns healthy.
Prune Ruthlessly
Every session, look at the dashboard. If a thread has not moved in three sessions, mark it dormant or cut it. If an NPC has not appeared in five sessions, drop them to background. If a faction has had no news, compress it to a one-line summary. The dashboard should always reflect the current campaign, not the entire campaign history. Historical detail goes in archived session notes, not the active dashboard.
Keep Continuity When You Switch Systems
System hopping is common in solo play. You might run a campaign in D&D 5e for 20 sessions, then swap to Shadowdark to try the new rules. The killing move is to start over. The better move is to keep the setting, the characters, and the threads, and only swap the rules. Your dashboard already holds the story. The system is just the engine. Use a holding page in your notes that lists the current campaign’s setting, characters, and threads, and you can swap systems without losing anything.
Long campaigns are also where the campaign dashboard pays off most. The dashboard is the save file. The session notes are the highlights reel. The two together let you re-enter a 50-session campaign in five minutes flat, and that is the entire game.
Frequently Asked Questions
What is the best way to track a solo Du0026amp;D campaign?
The best way to track a solo Du0026amp;D campaign is to use a consistent system with a 5-minute before-session ritual, a 3-5 bullet after-session recap, and one campaign dashboard page that always shows the current state of every active quest thread, NPC, and location. The depth of notes should stay at bullet points, not novel-length prose, so re-entry is fast and motivation stays high.
How do you keep track of NPCs in a solo RPG?
In a solo RPG, track only NPCs that matter and give each a one-line card on the dashboard with name, role, last-known location, faction, and a relationship hook. Use a first-mention tag like [N:Pip|halfling smuggler] the first time you write about them, and a short reference tag like [N:Pip] every time after. This keeps your notes searchable and your dashboard current.
What should I write down during a solo RPG session?
During a solo RPG session, write down only what changes: new NPCs, new locations, resolved quest threads, depleted PC resources, faction shifts, and oracle dice results. Skip filler, narration, and descriptions you would remember in two weeks. The goal of session notes is to jog your memory for the next session, not to be the memory itself.
How do I remember what happened in my last solo session?
To remember what happened in your last solo session, write a 3-5 bullet recap at the end of every session and keep it at the top of your campaign dashboard. Reading three bullets is fast, which is the entire point. When you start the next session, read the recap, scan the active threads, and pick one micro-goal to enter the world with.
What tools do you use for solo RPG tracking?
Common tools for solo RPG tracking include a physical journal for narrative session logs, Notion for fast dashboards and templates, Obsidian for searchable markdown notes with plugins, and dedicated solo apps like Saga20 or Lonelog for built-in notation and dashboards. The right tool is the one you will actually open, so pick for momentum, not feature count.
How do I journal solo Du0026amp;D without writing a novel?
To journal solo Du0026amp;D without writing a novel, set a one-line-per-scene rule and stop there. Write only what you would forget in two weeks, prune dormant threads every session, and treat session notes as an index to your memory, not a full transcript. If you want to write a novel or a blog play report, do that as a separate, optional layer on top of the campaign notes.
Start Tracking Your Solo Campaign Today
That is the whole system for how to track a solo campaign’s progress across many sessions. The 5-step framework, the before-session and after-session rituals, the 5 data categories, the copy-paste template, and the comparison table all serve the same goal: make the next session easy to start. Solo campaigns do not die from bad stories. They die from bad re-entry. Build the rituals, keep the dashboard, and the campaign will outlast your enthusiasm.
Pick one tool today, paste the session template, and run the after-session ritual on whatever you just played. That first recap is the hook that will pull you back into the chair next week. The rest of the system grows from there.