How to Run a D&D Campaign

A campaign is different from a one-shot in one specific way: it has to survive its own history. Player decisions from session two need to still matter in session twenty. That's the whole difficulty of running a campaign, and it's what most campaign advice skips past.

Start with less than you think you need

You don't need a finished world before session one. You need:

• A starting location your players can act in immediately
• Two or three factions with reasons to care what the party does
• One central conflict big enough to fill several sessions, but not the whole campaign
• A handful of NPCs who can plausibly show up again

Everything else - the empire's history, the pantheon, the trade routes - can be built as it becomes relevant. Worldbuilding that never gets used at the table isn't campaign prep, it's a separate hobby.

Structure the campaign in layers

Think of a campaign as three layers stacked on top of each other:

1. The campaign arc - the multi-month conflict that gives the whole thing a shape and an eventual ending.
2. The current adventure - the chapter you're in right now, usually a few sessions long, with its own smaller goal.
3. The next session - the specific scenes, encounters, and NPCs you're prepping this week.

Most GM burnout comes from trying to fully plan layer one before ever touching layer three. Do the opposite: sketch the arc loosely, then spend most of your prep time on the next session, using the arc as a compass rather than a script.

Let player choices actually change things

A campaign feels alive when consequences persist. If the party lets a village burn, that village should still be gone three sessions later - referenced in dialogue, visible on the map, affecting what NPCs will and won't do for the party. You don't need a spreadsheet to track this. You need a habit: after every session, write down two or three things that changed because of what the players did, and check that list before you prep the next session.

Keep a campaign log, not just session notes

Session notes describe what happened. A campaign log tracks what's still open:

• Which threads are unresolved
• Which NPCs are owed something (information, a favor, revenge)
• Which factions are currently allied, neutral, or hostile to the party
• What the party knows that the reader (future you) might forget

This is the single highest-leverage habit for running a long campaign, because it's the thing that lets you improvise consequences on the fly during a session instead of forgetting them.

Expect the campaign to change shape

The campaign you planned in session zero will not be the campaign you're running by session fifteen. Players will get attached to an NPC you meant as a one-scene extra. They'll ignore a plot hook you spent hours writing. That's normal - it means the campaign is actually responding to the table instead of running on rails.

A connected workspace makes this easier to sustain: when your NPCs, factions, and session history live in the same place as your prep for next week, "what changed because of what they did" is a lookup instead of a memory test. See how ArcForge's Dungeon Master tools organize a campaign around plan, prep, run, track, and continue.