How do you track faction turns between RPG sessions?

A faction turn only needs to answer one question

As more factions become active, it's easy to lose track of who acted, what changed, and which consequences the players have actually seen. A GM trying to be thorough can end up tracking resources, rosters, and rival moves for organisations nobody at the table is thinking about, and a tool meant to save prep time turns into more prep.

A faction turn should answer one question: what changed in the world while the players were busy elsewhere? An off-screen organisation needs only enough structure to say what it tried to do, who it targeted, what evidence it left behind, and what changed on the campaign map — everything else is detail in service of that answer.

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 NPC, location, or rival involved.
• Resolve the outcome Decide whether the move succeeds, stalls, or triggers a setback. In narrative systems, compare the faction's standing and resources against its target. In dice-driven games, make a single opposed roll or advance a progress clock.
• Surface a visible consequence Translate the result into tangible evidence the players encounter 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 what changed Record the result as a dated entry on your campaign timeline and update the faction's relationship to its target. Logging it immediately avoids contradictions 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 factions that currently matter to the party. 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, that's still information worth acting on. If nobody is meaningfully opposing it, consider letting the move succeed without a roll — unopposed momentum makes the campaign world feel alive. If another faction or some other obstacle still stands in the way, resolve it normally, perhaps from a stronger position. When the party chooses to pursue a dungeon rumour rather than guard the granary, the grain cartel might complete its monopoly on schedule and the town faces food rationing, unless a rival guild or a bad harvest gets there first.

Between-session faction turn checklist

Complete this sequence before concluding your session prep:

• Pick no more than three or four factions active around the party.
• Assign each faction one specific action targeting a named NPC, location, or rival.
• Resolve the action with a single opposed check, a clock tick, or a plain comparison of who has the advantage.
• Note at least one visible consequence the players will notice or hear about next session.
• Update the relationship links on your campaign map and log the outcome on the timeline.