How to prep a D&D session: the one-page, nine-step checklist
Nine steps, run the night before or in the twenty minutes before people arrive. The whole thing is on this page — read it here, copy it into your notes app, or have the printable emailed to you.
Recap last time
One or two sentences on where the party left off and any cliffhanger.
Know your "why"
The one thing you want to happen this session. Everything else is improv.
Three beats, not a script
An opening hook, a midpoint complication, a possible ending. Leave room for the table.
Stat the likely fights
Have 1–2 encounters ready to run; note initiative, HP, and one tactic each.
Names on tap
A short list of NPC names so an unplanned shopkeeper or guard never stalls the game.
One map or visual
Even a rough sketch. Players orient faster when they can see the space.
Loot & rewards
Decide what a win is worth before they ask — gold, an item, a lead, or info.
Loose threads
Jot the dangling hooks players might chase so you are not caught flat-footed.
Press record
Start the recording before the first dice roll — DM-Scribe writes the recap and wiki for you.
How to run the nine, in order
The order is not decoration: you cannot pick this session’s “why” until you know where the party is standing, you cannot stat a fight until you know which beat it belongs to, and the loose threads fall out of the recap you just wrote. It also splits cleanly across two sittings.
The night before, the decisions: steps 1 to 4, and 7. Write the recap first, while last session’s notes or recording are to hand. Pick the why, sketch the three beats around it, stat the fights those beats imply, and decide what winning is worth. This is the part that needs a quiet half hour and your full attention.
Twenty minutes before, the setup: steps 5, 6, 8 and 9. Jot the name list, put the map or sketch where the table can see it, jot the loose threads the recap turned up so they are front of mind, and — if your table has agreed to be recorded (the consent guide covers asking) — start the recording before anyone rolls. None of these needs much thought, which is why they survive being done while people arrive.
When twenty minutes is all you have, keep steps 1, 2 and 4, in that order, and 9 if you record. The recap and the why are what the table notices when they are missing, one statted fight saves the book-flipping, and the recording means next week’s step 1 is already half done. Cut the rest in this order: the map first (describe the room instead), then the beats down to just the opening hook, then the loot (a lead or a piece of information is a reward you can hand out on the spot), and the names last (borrow any list of names you already have). Loose threads come free if your recap’s last line is the cliffhanger.
Copy it into your own notes
Plain text, so it pastes cleanly into Notion, Obsidian, Google Docs or the top of your session notes. It is deliberately one page: a prep checklist you have to scroll is a prep checklist you stop using by session four.
1. Recap last time — One or two sentences on where the party left off and any cliffhanger. 2. Know your "why" — The one thing you want to happen this session. Everything else is improv. 3. Three beats, not a script — An opening hook, a midpoint complication, a possible ending. Leave room for the table. 4. Stat the likely fights — Have 1–2 encounters ready to run; note initiative, HP, and one tactic each. 5. Names on tap — A short list of NPC names so an unplanned shopkeeper or guard never stalls the game. 6. One map or visual — Even a rough sketch. Players orient faster when they can see the space. 7. Loot & rewards — Decide what a win is worth before they ask — gold, an item, a lead, or info. 8. Loose threads — Jot the dangling hooks players might chase so you are not caught flat-footed. 9. Press record — Start the recording before the first dice roll — DM-Scribe writes the recap and wiki for you.
A fill-in session prep template
The same nine steps as blanks: a DM prep sheet you duplicate for each session, so preparing means filling in lines rather than facing an empty page. Keep a master copy, duplicate it, and name the copy by session number.
This is the before-the-table half. Once play starts, switch to the session notes template, which is built for what happens during and after the session.
Session prep sheet (copy this)
SESSION PREP SHEET Session #: ____ Date: ________ 1. RECAP LAST TIME (1-2 sentences, ending where they stopped) ____________________________ 2. KNOW YOUR "WHY" (the one thing I want to happen) ____________________________ 3. THREE BEATS, NOT A SCRIPT Opening hook: ________________ Midpoint complication: ________________ Possible ending: ________________ 4. STAT THE LIKELY FIGHTS Fight 1: ____________ init __ HP ____ tactic: ____________ Fight 2: ____________ init __ HP ____ tactic: ____________ 5. NAMES ON TAP ______ ______ ______ ______ ______ ______ (cross off as used) 6. ONE MAP OR VISUAL ____________________________ 7. LOOT & REWARDS Gold or item: ____________ Lead or info: ____________ 8. LOOSE THREADS - ____________________ - ____________________ - ____________________ 9. PRESS RECORD Started at __:__, before the first roll
A session prep example, filled in
One sheet for an invented game, at the level of detail that is enough. Every line is short on purpose: a sheet you can read in thirty seconds is a sheet you will actually glance at mid-session.
SESSION PREP SHEET Session #: 15 Date: Friday 1. RECAP LAST TIME They cut the ferry loose at Grey Ford with the smugglers' ledger aboard. Ended on the ferry drifting toward the weir. 2. KNOW YOUR "WHY" The party finds out who in town is buying from the smugglers. 3. THREE BEATS, NOT A SCRIPT Opening hook: the ferry hits the weir - jump or go over Midpoint complication: the ledger names the reeve's own clerk Possible ending: the clerk asks to meet them alone at the mill 4. STAT THE LIKELY FIGHTS Fight 1: 4 smugglers on the bank init 12 HP 11 each tactic: two hold the rope, two shoot Fight 2: the clerk's bodyguard init 15 HP 30 tactic: runs for the reeve at half HP 5. NAMES ON TAP Oda Brannick Sela Thorn Old Ruel Kip Marten Vey 6. ONE MAP OR VISUAL Rough sketch of the weir, both banks and the mill path 7. LOOT & REWARDS Gold or item: 40 gp in the ledger box Lead or info: the clerk's name 8. LOOSE THREADS - the smuggler who escaped across the ford - Sela's unpaid tab at the inn - who sank the second ferry? 9. PRESS RECORD Started at 19:02, before the first roll
Notice what is not on it: no read-aloud text, no backstory for the clerk, no plan for what happens if the party skips the mill. The beats are possibilities, not a script. If the table ignores the ledger and chases the smuggler who escaped instead, the name list and the first fight still work, and the sheet has done its job.
Want the printable in your inbox?
We will email you this checklist as a one-page printable — one email, that is the whole transaction. It is the same nine steps you just read.
Why these nine, and not thirty
Every line exists because skipping it costs table time. A missing recap spends the first fifteen minutes reconstructing last session from six disagreeing memories. An unstatted fight means flipping through a book while the table checks their phones. No name list means every incidental shopkeeper is called “the shopkeeper” forever. The checklist is not a prep philosophy — it is the shortlist of things that cannot be improvised without the table noticing.
Just as deliberately, there is no worldbuilding on it. Prep that produces lore the players never touch is the main way prep time balloons — how long prep should actually take covers what surveyed DMs spend and what the hour should buy. And if your problem is capturing what happens once the session starts, that is a different artifact: taking notes during the session covers it.
The last item is the one that pays compound interest: a session you recorded writes next week’s “recap last time” line for you, and the one after that. That is the whole trick this site is built on.