How do I prep a session efficiently?

Prep for retrieval, not for volume. The goal isn't more written material — it's being able to find any fact about your world instantly while the table waits. Pull together the NPCs, locations, and threads the coming session is likely to touch, keep them where you can reach them in seconds, and rely on your world's rules to handle whatever the players do that you didn't anticipate. Efficient prep is a few likely scenes plus a world consistent enough to improvise the rest.

How do I stop players from seeing my secret plot notes?

Keep the hidden layer physically separate from anything you might show the table. The villain's true identity, the twist behind the cult, the reveal you're seeding for months — those need to live somewhere you can reference but never accidentally expose, and they must be excluded from any handout, map, or export you hand the players. Building your prep so secrets sit in a locked, GM-only layer is what lets you run a mystery for a year without spoiling it by a slip of the screen.

Should I prep a linear plot or a situation?

Prep a situation, not a script. Players won't follow a plotted sequence of scenes, so prepping one mostly guarantees wasted work and a railroaded table. Instead prep the situation — what the factions want, where the pressure is, which NPCs are in play and what they'll do — and let the session emerge from the players' choices meeting that situation. A well-built situation survives contact with the table; a plotted script rarely survives the first decision.

Session Prep: Keeping a Campaign's Canon at Your Fingertips

CanonBoardWorld logic engine

The tool behind these field notes. Build a story world that actually holds together — free to start.

See how it works

There's a myth that good session prep means writing more — more read-aloud text, more plotted scenes, more pages. In practice the game masters who run the smoothest tables often prep the least text and the most structure. Because the real test of prep isn't how much you wrote; it's whether you can find the baron's daughter's name in the two seconds before the momentum dies, and whether the world holds together when the players do the thing you didn't prepare for.

So session prep is really a retrieval problem, not a writing problem. This guide is about prepping the world you've already built — the setting from how to build a homebrew campaign setting and the cast from managing NPCs and factions — so it's usable at speed: how to prep situations instead of scripts, how to keep the canon at your fingertips mid-scene, and how to keep the secrets the players shouldn't see out of everything you put in front of them.

Prep situations, not scripts

The most wasteful prep is the plotted sequence of scenes, because the players will not walk it. They'll skip your set piece, befriend your villain, and solve your mystery from an angle you didn't consider — and every hour spent scripting the path they don't take is an hour gone. The alternative is to prep the situation: what each faction wants and is about to do, where the tension sits, which NPCs are in play. Drop the players into that and the session generates itself from their choices.

A situation survives contact with the table because it doesn't assume a route. Whichever direction the players push, the situation has an answer, because it's built from live forces rather than a fixed order of events. This is also far less work than scripting — you prep the pieces and their motives once, and they recombine into whatever the session becomes. Your prep stops being a screenplay you hope the players follow and becomes a board you can run from any direction.

Keep the canon at your fingertips

The difference between a session that flows and one that stalls is often just retrieval speed. When a player asks who runs this town, or whether they've met this NPC before, or what the northern road connects to, you need the answer now — not after a minute of scrolling through a linear document while five people wait. A world you have to search is a world that keeps interrupting your own game.

The fix is the same one that makes any world bible usable: structure it as discrete, connected, findable pieces rather than prose, and ideally lay it out spatially so you retrieve by location and memory instead of by search. When your NPCs, places, and threads live as connected cards you can scan at a glance, mid-scene lookups take seconds and the table never notices. That's the full argument in why a world bible belongs on a canvas. Prepping a session then becomes mostly a matter of pulling the handful of cards the coming session is likely to touch and keeping them in front of you.

Keep the secrets the players can't see — hidden

A campaign runs on things the players must not know yet: the traitor in the party's patron, the truth behind the cult, the reveal you've been seeding since session one. These are the most important facts in your prep and the most dangerous, because a single slip — a wrong screen shared, a handout with a note left in — can undo a year of setup in an instant. Secrets need a home you can reference constantly but never expose.

That means keeping the hidden layer physically separate from anything shareable. Reveals, twists, and true identities belong in a GM-only vault, deliberately excluded from any map, handout, or export you generate for the table — so that when you hand the players a document, it can't contain the thing that would ruin the surprise. Building prep with that clean line between what's shown and what's locked is what lets you run a long mystery without living in fear of your own notes. It's the same instinct a screen provides at the table, applied to your world document.

Frequently asked questions

How do I prep a session efficiently?: Prep for retrieval, not for volume. The goal isn't more written material — it's being able to find any fact about your world instantly while the table waits. Pull together the NPCs, locations, and threads the coming session is likely to touch, keep them where you can reach them in seconds, and rely on your world's rules to handle whatever the players do that you didn't anticipate. Efficient prep is a few likely scenes plus a world consistent enough to improvise the rest.
How do I stop players from seeing my secret plot notes?: Keep the hidden layer physically separate from anything you might show the table. The villain's true identity, the twist behind the cult, the reveal you're seeding for months — those need to live somewhere you can reference but never accidentally expose, and they must be excluded from any handout, map, or export you hand the players. Building your prep so secrets sit in a locked, GM-only layer is what lets you run a mystery for a year without spoiling it by a slip of the screen.
Should I prep a linear plot or a situation?: Prep a situation, not a script. Players won't follow a plotted sequence of scenes, so prepping one mostly guarantees wasted work and a railroaded table. Instead prep the situation — what the factions want, where the pressure is, which NPCs are in play and what they'll do — and let the session emerge from the players' choices meeting that situation. A well-built situation survives contact with the table; a plotted script rarely survives the first decision.

Stop discovering continuity breaks in the table read.

CanonBoard scans your whole world and tells you where it disagrees with itself.

Start free