What a Campaign Workspace Should Track for a Game Master
A campaign workspace should reduce friction, not become homework. The best setup gives you quick access to the things that change during play: sessions, quests, notes, NPCs, factions, locations, items, encounters, and lore.
Separate prep from records
Session prep is temporary. Records are persistent. Your opening scene, possible encounters, and scratchpad belong to the next session. NPCs, factions, locations, and lore should live as reusable campaign records.
This separation keeps your workspace clean after several sessions.
Track quests as state, not prose
A quest record should tell you whether the quest is planned, active, completed, or failed. Long prose is less important than current status, reward, secrecy, and the next obstacle.
When quests are stateful, recaps and session prep become much easier.
Keep GM-only and player-visible notes apart
A useful workspace should distinguish secrets from table-facing information. The GM needs hidden motives and future reveals; players need clear summaries and discovered truths.
This becomes especially important once campaigns move toward player portals or shared pages.
Import generated content, then edit it
Generated content is most valuable when it becomes editable campaign structure. If a generated NPC or faction stays only on the campaign card, it is easy to forget. If it becomes a workspace record, it can evolve with the campaign.
The workflow should be: generate, import, edit, run, update.