A working approach to ttrpg campaigns, from first signal to repeatable practice
A healthy campaign workflow captures the world in terms of active fronts, people with desires, and scenes the players can actually touch. Session notes become far more valuable when they record consequences and open questions instead of trying to transcript the whole night.
A sequence I would actually hand to a teammate:
1. Start with the campaign promise, player hooks, and the kind of session rhythm you want to run.
2. Build prep documents that highlight scenes, NPCs, stakes, and flexible responses instead of scripting outcomes.
3. After each session, update the notes with what changed so future prep stays grounded in actual play.
Useful operating references:
- Ironsworn downloads: ironswornrpg.com/downloads
Free tools and PDFs that are genuinely generous for solo or guided campaign work.
- Iron Vault source: github.com/iron-vault-plugin/iron-vault
A thoughtful open plugin for running Ironsworn and related games in Obsidian.
If your team has a better workflow, post it with the context around team size, constraints, and exactly where the process tends to break.