Game Master Prep Techniques: Planning Sessions Efficiently

Game Masters who run consistently engaging sessions rarely improvise everything — but they also rarely script everything. Efficient prep sits between those two poles, and finding that balance is one of the most practically useful skills a GM can develop. This page covers the core methods for planning sessions with less wasted effort, how to match prep style to campaign type, and where the boundaries between over-preparation and under-preparation actually fall.

Definition and scope

Game Master prep refers to the work done between sessions to prepare the fictional world, encounters, NPCs, and narrative threads that players will interact with at the table. It is distinct from long-term worldbuilding for tabletop RPG — which can stretch across months — and from in-session improvisation skills for game masters, which handles the unexpected in real time. Prep is the structured middle layer: the 1 to 4 hours most GMs spend in the days before a session organizing what they already know about the world into something usable.

The scope of prep varies significantly by system. A Dungeons & Dragons 5th Edition dungeon crawl built around published adventure modules might require 30 minutes of reading ahead plus minor customization. A homebrew campaign running on a narrative-heavy system like a Powered by the Apocalypse game — see Powered by the Apocalypse games for system context — might need no encounter math at all, but substantial work sketching NPC motivations and location atmospheres.

How it works

Efficient prep operates on a simple principle borrowed from screenwriting: prepare the situation, not the story. GMs who script what will happen spend enormous energy on content players frequently bypass. GMs who prep vivid situations — charged locations, NPCs with clear wants, factions with active agendas — generate usable material regardless of which direction players move.

A structured prep workflow typically runs in this order:

1. Review last session notes — identify unresolved threads, player-stated goals, and any NPCs whose actions would logically continue offscreen.
2. Advance the world clock — determine what the active antagonist or key faction did during the week since the last session. This keeps the world from feeling static.
3. Prep 3 locations — not maps necessarily, but a name, a dominant sensory detail, and one complication per location. Three covers most sessions; rarely does a group reach a fourth.
4. Prep 3 to 5 NPCs — each with one want, one fear, and one piece of information. The creating NPC characters page covers deeper characterization, but this skeleton is sufficient for most sessions.
5. Prep 1 to 2 encounters — stat blocks if the system requires them, or tension triggers if it does not.
6. Write a one-sentence session hook — something that places an interesting problem in front of the players within the first 10 minutes.

This skeleton approach, popularized in part by Sly Flourish's Return of the Lazy Dungeon Master (Michael Shea, 2018), is grounded in the observation that GMs consistently over-prep scenes and under-prep connections between scenes.

Common scenarios

New GM running a published module: Prep time can drop to under an hour. Read 2 encounters ahead, highlight any NPC names that appear repeatedly, and flag decision points where player choices branch. The structure is already provided.

Veteran GM running a long-term sandbox: The sandbox vs. linear campaign structure page addresses the fundamental design difference. In sandbox play, prep shifts toward maintaining a living world document — a running list of faction moves, NPC status updates, and rumor tables — rather than scripting specific scenes. Time investment averages 2 to 3 hours per session, most of it updating existing materials rather than creating new ones.

One-shot or convention game: Prep compresses to character hooks, a 3-act structure with clear escalation, and pre-generated characters. The tabletop RPG conventions in the US context means GMs are often running for strangers, so the session hook needs to be immediately legible to players with no shared history.

Rules-heavy vs. narrative systems: Combat prep in Pathfinder 2nd Edition (Paizo) involves action economy, encounter XP budgets, and terrain effects — a rules-heavy system where under-prepped encounters can collapse into chaos. A narrative-first system running on Apocalypse Engine mechanics may require zero combat math but demands sharper NPC voice work.

Decision boundaries

The central tension in prep is investment versus flexibility. Over-prepared GMs often experience what might be called "prep grief" — the mild but real frustration of watching players walk past a room that took 45 minutes to detail. Under-prepared GMs hit improvisation walls, usually around the 90-minute mark of a 3-hour session when the prepared material runs out.

Three useful boundary tests:

• The discard test: If prep material would be discarded without regret when players ignore it, the investment was appropriate. If abandoning it would feel wasteful enough to nudge players back toward it, it was over-investment.
• The portability test: Good prep material can be moved. A detailed tavern prepared for Session 4 can become a different city's tavern in Session 9 if players changed course. Single-use material is the most expensive kind.
• The player-agenda test: At least one prepared element per session should directly address a stated player-character goal. The broader tabletop RPG campaign types context shapes how many of these goals exist at any one time.

For GMs building toward longer campaign management, the full resource hub at tabletoprpgauthority.com covers the adjacent skills — encounter design, safety tools, and digital platforms — that feed into session-level execution.