Session Prep Guide for Busy DMs: Run Great Games in Under 2 Hours

You have a job. Maybe a family. The campaign session is in three days and you haven't touched your notes. You open your prep folder, see the sprawling map you promised yourself you'd finish, the six NPCs you meant to flesh out, the encounter balance spreadsheet — and you close the folder. You'll "do it tomorrow."

Tomorrow comes. Session is in four hours. You prep in a panic, over-explain everything at the table to compensate, and spend half the session staring at your notes instead of your players.

This guide is for you. Not the DM with fifteen hours a week for world-building — the DM with a full life who still wants to run great games. There's a repeatable system that gets you session-ready in under two hours without sacrificing quality. Here's exactly how it works.

Why Over-Prepping Is Hurting Your Games

There's a belief among new DMs that more prep equals better sessions. It's false. Over-prepping produces two failure modes: the railroad (you prepared so much that you can't deviate from it) and the freeze (your players go off-script and you have nothing, because everything you prepped was for a story they're not playing).

The best sessions don't come from exhaustive prep. They come from a DM who knows three things deeply: where the players left off, what they care about, and what could happen next. Everything else is improvised with confidence, not improvised in panic.

The goal of this system isn't to do less work. It's to do the right work — prep that actually matters at the table versus prep that lives in a document you never look at.

"Prepare situations, not plots. Plots are what happens when you fight the players for control of the story."

Step 1: Start Where You Left Off (15 minutes)

The single most valuable prep habit: write a session debrief within 24 hours of each game. It doesn't need to be long. Five bullet points covers it:

• Where did the session end? Exact location, time of day, party status
• What did the players decide? Not what happened — what did they choose
• What threads are dangling? The NPC they haven't followed up on, the mystery they noticed but haven't solved
• What are they excited about? Where did the table light up? What are they talking about in the group chat?
• What consequences are pending? Every significant player choice creates a world response — what hasn't landed yet?

If you wrote this debrief after last session, your prep just got 40% shorter. You're not reconstructing — you're continuing. If you didn't write it, do it now. Spend 15 minutes reconstructing these five points before you do anything else.

That's your prep foundation. Everything else builds on this.

Step 2: Build the Session Spine, Not a Script (20 minutes)

A session script is a sequence of scenes you expect to happen. A session spine is a set of pressures that will generate scenes organically, whatever the players do.

The spine has three elements:

• The Push: Something that demands a response this session. Not a vague threat — a specific, time-pressured situation. Tavira will be executed by dawn. The bridge captain has already sent a rider. The sister has been spotted in the market district.
• The Pull: Something enticing that's within reach. A lead on the symbol. A contact who knows where the sister is. A reward for dealing with the rider before he reaches the capital.
• The Wild Card: One thing that will change regardless of player choices, purely as a function of the living world. The faction with the ring makes a move. The inn burns down. A bounty hunter arrives looking for someone — not necessarily the party.

Push, pull, wild card. That's your session. Not a script of scenes — a set of forces that guarantee something interesting happens no matter what your players decide to do.

Write these three things down. You're done with the macro level. Move on.

Step 3: Prepare Three Scenes, Not Thirty (25 minutes)

You don't need to prep everything that might happen. You need to prep three scenes that are likely to happen and be flexible about the rest.

For each scene, write down exactly four things:

1. The opening image: What does the party see/hear/smell when the scene begins? One vivid sensory detail.
2. The tension: What decision or conflict is present? Not what you want to happen — what problem requires the players to engage.
3. Two possible directions: How does this scene go if players push? How does it go if they pull back? You don't need more than two — improv handles the rest.
4. The hook forward: What does this scene reveal or establish that connects to the next thing? One clue, one consequence, one door that opens.

Three scenes. Twelve total pieces of information. That's forty-five minutes of solid table time — more if your players dig in, which they will if the scenes are built around their choices instead of your expectations.

Keeping all of this organized during play is where many DMs stumble. The ForgeLight Session Planner Kit gives you a structured one-page layout for exactly this — session spine, three scenes, NPC notes, and space for live tracking, designed to be used at the table without shuffling through loose documents.

Step 4: Give Your NPCs One Thing Each (15 minutes)

The most common over-prep mistake: writing full character backstories for NPCs the players might not talk to for more than two minutes.

Every NPC needs exactly one thing: what do they want right now, in this scene? Not their life history. Not their personality in depth. One want, one mannerism, one name.

• The militia captain wants to avoid a diplomatic incident. His ring marks him as a member of a guild he's supposed to have left. He tugs the ring whenever he's nervous.
• Tavira wants out, but she's protecting someone by staying quiet. She's angrier than she's scared.
• The innkeeper wants the party gone before the next patrol. She's been paid to keep quiet about who's stayed here.

Three sentences per NPC. That's enough to improvise a conversation that feels real. The players will fill in the rest with their own assumptions — and if those assumptions are interesting, follow them. Your NPC's "backstory" can be written backward from what the players believe.

If you find yourself needing to reference NPC names and details mid-session without breaking immersion, the DM Quick-Ref Cards give you a compact format to write these one-line NPC profiles and keep them within eyeshot during play.

Step 5: Prep Encounters That Can Flex (20 minutes)

Encounter prep is where most DMs spend the most time and get the least return. The antidote: prep modular encounters, not fixed ones.

A modular encounter has a core conflict that stays constant but elements that can scale up, down, or sideways based on how the players approach it.

The 3-Tier Model

For any combat or challenge encounter, prep three versions:

• Easy tier: If the party comes in rested, with good information, with a clever plan. What do the enemies/obstacles look like at 70% strength?
• Standard tier: The baseline. What you'd run if the party walks in at full strength and no special knowledge.
• Hard tier: If the party comes in compromised, low on resources, or without information that would have helped. Add one reinforcement, one environmental hazard, one time pressure.

You decide which tier to run at the table, based on actual party state. This takes five minutes to write and eliminates the most common encounter prep failure: a fight that's trivially easy or immediately lethal because you prepped for a party that doesn't exist.

The Flexible Encounter Formula

For skill challenges and social encounters, prep them as a set of questions rather than outcomes:

• What does success look like? (Partial success? Full success with complications?)
• What does failure look like? (Failure with a cost? Failure that opens another door?)
• What information becomes available regardless of outcome?

Players feel agency when their choices matter — not when they're locked into a win/fail binary. Prepping outcomes as a spectrum takes the same time and produces twice the table satisfaction.

For balanced encounter math, ForgeLight's Encounter Randomizer handles the XP budget calculations automatically so you can spend your prep time on the interesting parts instead of cross-referencing tables.

Tools That Cut Your Prep Time in Half

The system above works without any specific tools. But the right toolkit eliminates the friction that turns 90 minutes of prep into 4 hours.

What You Actually Need

• A session log: Somewhere to write the five-bullet debrief immediately after play. A note on your phone works. The habit is what matters.
• A one-page session template: Not a blank document — a structured format that prompts you for spine, scenes, NPCs, encounters. Blank documents invite scope creep. Structured templates constrain you toward the right prep.
• Quick-reference cards at the table: NPC names, faction relationships, key world facts. Not a binder. Not a laptop. A card you can glance at while maintaining eye contact with your players.
• Encounter tools that do the math: Don't spend prep time calculating XP budgets. Use a tool that calculates balanced encounters by party size and level so you can focus on what the fight means, not whether the numbers are right.

The Session Planner Kit ($4.99) at ForgeLight is built around this exact workflow — one-page session template with spine, scenes, NPC notes, and encounter flex-tiers, printable or fillable. It's the physical artifact of the system described in this guide.

Paired with the DM Quick-Ref Cards ($3.00) — a pocket reference for rules lookups, NPC tracking, and condition reminders — your entire table toolkit fits in a folder and takes ten minutes to update between sessions.

Your Busy DM Quick Reference

Here's the full system compressed. Pin this somewhere visible:

Total: 100 minutes. Which is under two hours, including the gut check.

The gut check is not optional. If you can't explain a scene in 30 seconds, you haven't prepped it — you've written a novel. Great DMs know the difference between understanding a situation and having notes about a situation. Your prep should land in your head, not live on the page.

What to Do When Players Go Off-Script

They will. Every session. Here's the three-second response framework:

• Is this in service of what they care about? (The dangling threads, the things they're excited about.) If yes, follow it — you already know what matters to them.
• Does the living world respond? (Your wild card.) Off-script player choices don't pause the world. The faction that sent the rider doesn't wait for the party to catch up. Let the world keep moving.
• What's the simplest interesting complication? Not a punishment. Not a railroad back to your prep. Just: what's the most interesting thing that could complicate this direction, given what you know about the world?

You're not improvising blind. You're improvising from a foundation — session spine, dangling threads, NPC wants, living world pressures. The system gives you everything you need to say "yes, and" to player choices instead of freezing.

That's what separates a good DM from a great one. Not more prep. Better prep, applied with confidence.