--- title: "9 signs your RPG campaign notes need more structure" description: "Recognize repeated lookup problems, conflicting records, and missing follow-up. Find a small fix before changing your whole note system." last_updated: 2026-10-01 --- # 9 signs your RPG campaign notes need more structure Plain-text Markdown mirror of [https://storywright.io/guides/campaign-notes-need-structure](https://storywright.io/guides/campaign-notes-need-structure). A shared document can carry an RPG campaign for years. Long notes aren't a problem if you can still find what you need during play. But if the game pauses while you search three documents for an old ally, something needs to change. The same goes for a town description you can't share without revealing the villain's name. Here are nine signs to look for, with a small change you can try before moving your whole campaign. ## 1. You can picture the NPC, but you can't find their name You remember the ferryman who helped with the prison escape, but not his name or which session he appeared in. Name his entry “Orin, ferryman at the east docks.” Add a sentence about the escape and a link to that session. Next time, you can search for “ferryman” even if you've forgotten his name. ## 2. Two pages disagree about the same person The captain owes the party a favor in one note and wants them arrested in another. Both were true, but it's hard to tell which came first. Update her NPC entry with what she now thinks of the party: “Hostile since the party exposed her smuggling in session 12.” Keep the older favor in the session where she offered it. That way, you can answer both “How will she react tonight?” and “How did we get here?” ## 3. Sharing a page requires a spoiler check You'd like to send players the town description. Unfortunately, the paragraph about the wells also names the person poisoning them. Put the shareable town description in its public entry and the poisoning culprit in private GM notes. A “GM only” heading doesn't help if everyone can open the document. [See examples in the spoiler-safe lore guide.](/guides/spoiler-safe-lore) ## 4. “Where's the recap?” has become a weekly question One recap is in Discord, another went by email, and last week's is still in your draft document. The players aren't necessarily ignoring them. They may simply have lost track. Pick one home for finished recaps and use chat to share the link. A visible date or session title helps people find the right one. [Using Discord? Read the recap delivery guide.](/guides/discord-recaps) ## 5. An old promise vanishes from the notes The party agreed to find a missing apprentice. Three sessions later, the apprentice hasn't come up again, and nobody remembers whether the search is still on. A short quest note is enough: “Still missing. Last seen at the north gate. Party promised the tutor they'd investigate.” Link the session where they made that promise. Update the note when they act on it, decline it, or learn something new. ## 6. You open the same six tabs before every game The previous recap, tonight's location, two NPCs, the quest list, and the map. You know what you need; getting to it is the chore. Try a short page of links for tonight. If you rebuild that page every week, keep those references beside the session notes instead. [See Storywright's session workflow.](/sessions) ## 7. A player's theory starts looking like a fact “I think the captain betrayed us” gets shortened to “the captain betrayed us.” A month later, everyone treats it as settled history. Label theories as theories and keep the writer's name attached. A personal journal is a good home for suspicions, especially when characters disagree. The shared recap can say what happened: “The captain didn't arrive at the docks. We don't know why.” ## 8. A small correction turns into a copying job You change the faction leader's name, then remember it's pasted into four quest documents. Give the faction one main entry and link to it from each quest. Keep the quest's details on its own page. A brief reminder such as “the dockworkers' guild” is enough; you don't need to copy the whole history. ## 9. Your template is too much work to keep up with Your template takes so much work that you keep putting off the post-session updates. Drop the fields you never read. If “weather,” “treasure ledger,” or “NPC mood” hasn't helped you run a session, it doesn't have to be mandatory. Keep only the fields you actually update and use during play. ## Common questions **What if players still don't read the notes?** Ask what they'd find useful between games. They might want a five-sentence recap and the name of the person they're meeting next. Agree on what to share, then make it easy to find. ## When a campaign manager is worth trying A campaign manager is worth trying when you keep copying the same facts between notes, checking pages for spoilers, or rebuilding the same prep list. In Storywright, each person or place can have one entry linked to the sessions and Story Arcs where it matters. Give Orin an NPC entry and link him from the prison-escape session. Put the town's revealed lore in its public description and hidden details in GM notes. Players can keep their own journals without folding every suspicion into the recap. After each game, update the entries that changed. For example, note why the captain became hostile or whether the party found the apprentice. If several of these signs sound familiar, try adding just the people and places you expect to use next session. Keep your original notes. [Read the Storywright manual.](/manual) [Compare Storywright with Google Docs.](/compare/google-docs) ## Related - [Organize campaign notes](/guides/organize-campaign-notes.md) - [Move existing notes](/guides/move-campaign-notes.md) - [vs Notion](/compare/notion.md) - [vs Obsidian](/compare/obsidian.md) - [Full site index](/sitemap.md)