Why Storywright helps with long-running RPG campaigns
Keep recurring people, unfinished business, and session history connected. Players can look up shared notes while the GM keeps secrets private.
Six months ago, the party promised an innkeeper they'd recover her son's silver compass. Tonight, they walk back into her tavern.
One player remembers the promise. Another remembers a locked room upstairs. You remember that the innkeeper had a secret, but it's buried somewhere in last winter's notes.
Keep one current entry for each recurring person, then link it to the sessions where their situation changed. Players see shared details; GM notes stay private.
Keep Tamsin's latest details in one place
For tonight, Tamsin's entry only needs what she wants, what the party owes her, and how she will greet them:
Tamsin offered the party a room in exchange for recovering her son's compass. They haven't returned it yet. She'll ask about it before offering any more favors.
Link Tamsin from the session where she made the offer. Her entry gives you her current attitude; the old session preserves the details of the bargain.
If they return the compass tonight, update her entry afterward: “Compass returned. Grateful; will hide the party from the town watch.” Leave the original bargain in its session notes. Next time, you can see how Tamsin feels about the party without rereading every visit.
See more examples in the NPC notes guide.
Keep the promise when the party goes elsewhere
Keep the compass on an open Story Arc while the party follows other leads.
Create a Story Arc in Storywright for recovering Tamsin's compass. Note the last lead and link the people involved. Before the party returns to town, ask whether they still intend to look for it.
If the party abandons the search, record that too. You can then decide how Tamsin reacts when they return.
Let players look up what they already know
The party should be able to find the Salt House and Tamsin's name without asking you to repeat the introduction. They shouldn't discover what's in the locked room by opening her page.
Share Tamsin's entry with the party: who she is, where to find her, and the bargain they've made. Keep her hidden motives and the room's contents in private GM notes.
Player journals add another perspective. If a character suspects Tamsin is lying, the player can record that suspicion in their character's journal. Keep the shared recap to confirmed events.
Choose an audience with the player journal guide.
Decide what to reveal with the spoiler-safe lore guide.
Write down what changed after the game
After tonight's game, record only the changes that will matter when the party returns: the compass came back, Tamsin offered shelter, and the party still hasn't opened the room.
Update Tamsin's entry, save the session notes, and publish a short recap. The next time you open that session, the prep and recap are together.
Stop after the details you expect to use again.
Start with the post-session checklist.
On plans with AI recap or briefing drafts, use the draft as a starting point and check it for errors and spoilers before publishing. You can use the same workflow entirely by hand.
Is it worth moving an ongoing campaign?
Try Storywright when you regularly bring back the same NPCs, locations, and unfinished promises. Keep maps and character statistics in the tools you already use, whatever tabletop system you play.
Begin with next week's session and a few recurring people or places. Keep your old documents nearby, and bring over older details when they become relevant.
A one-shot with a page of prep may already have all the organization it needs. For an ongoing game, try a simple test: can you find an old promise, see what's changed, and share the relevant part with a player?