How do you track faction turns between RPG sessions?

Off-screen simulation dies of administrative bloat

Game Masters often begin faction play by drafting sprawling spreadsheets with dozens of numerical stats, balance sheets, and complex rolling procedures for every organisation on the continent. By the fourth session, running this simulated wargame between sessions consumes several hours of prep, burns out the GM, and generates pages of unobserved background lore that players never touch.

Faction turns exist to produce player-facing tension, not to run an unobserved wargame. An off-screen organisation needs only enough structure to answer four practical questions: what did it try to do this week, who was targeted, what physical evidence did it leave behind, and what changes permanently on the campaign map.

The five-step faction turn loop

Resolve each active organisation during between-session prep using five focused steps:

• Define the intent Identify what the faction needs right now to advance its agenda. Keep this specific to a single objective, such as seizing an abandoned watchtower, blackmailing a town magistrate, or cornering the salt trade, rather than a vague multi-year ambition.
• Select a targeted action Choose how the faction pursues that intent this cycle. Standard moves include expanding territory, seizing an asset, infiltrating a rival, forging a pact, or sabotaging an enemy holding. Always name the specific target entity, location, or NPC involved.
• Resolve the outcome Decide whether the move succeeds, stalls, or triggers a setback. In narrative systems, compare the faction's relative standing and resources against its target. In dice-driven games, make a single opposed roll or advance a multi-segment progress clock.
• Surface a visible consequence Translate the mechanical result into tangible evidence the players encounter in the next session. A failed infiltration leaves an arrested spy in the stocks; a successful raid leaves smoke on the horizon, displaced villagers on the road, and doubled sentry watches at the gate.
• Log the permanent history Record the result as a dated entry on your campaign timeline and update the faction's relationship to the target entity. Logging the turn immediately prevents contradictions four sessions later when players ask when the docks burned down.

Limit active turns to organisations in the party's orbit

A common mistake is attempting to run between-session turns for every nation, cult, and syndicate on the world map. Restrict active turns to three or four organisations directly interacting with the region where the adventurers are currently operating. Distant factions can advance on broad seasonal milestones when the party travels to new regions.

When the players deliberately ignore an active faction's move, let that organisation succeed automatically on its next turn. Unopposed momentum makes the campaign world feel alive: when the party chooses to pursue a dungeon rumour rather than guard the granary, the grain cartel completes its monopoly on schedule and the town faces food rationing.

Between-session faction turn checklist

Complete this sequence before concluding your session prep:

• Pick no more than three or four factions active within the party's operational area.
• Assign each organisation one specific action targeting a named NPC, location, or rival.
• Resolve the action with a single opposed check, clock tick, or position comparison.
• Note at least one visible consequence that players will observe or hear rumoured next session.
• Update the relationship links on your campaign map and append the outcome to the timeline.