A Simple TTRPG Session Prep Checklist for Busy Game Masters

Introduction

Good TTRPG session prep does not make the session for you. It makes you ready to run whatever session the players decide to have.

That distinction is the whole game. If you prep a script, the table has one good way to disappoint you: not following it. If you prep a situation, the table can push in any direction and you still have something true to say back.

This is a checklist for busy Game Masters, the ones prepping on a lunch break, on the bus, or in the thirty minutes before people arrive. It borrows the spirit of Sly Flourish's Return of the Lazy Dungeon Master and its eight steps of lazy prep: prepare only what helps you improvise, and skip everything else. The goal is not less caring. It is less waste.

Table of Contents

• Prep for decisions, not scripts
• A fast session prep checklist
• A twenty-minute prep schedule
• Step 1: Review the characters
• Step 2: Build a strong start
• Step 3: Outline flexible scenes
• Step 4: Separate secrets from clues
• Step 5: Stock locations, NPCs, and rewards
• Prep consequences and offscreen moves
• A worked example
• How much time should prep take
• Use a post-session reset
• Common session prep mistakes
• TTRPG session prep FAQs
• Final thoughts on TTRPG session prep

Prep for Decisions, Not Scripts

Here is the reframe that saves the most time: you are not writing the session. You are stocking the shelves.

A scripted session assumes you know the order of events. The party will meet the informant, follow the lead to the warehouse, fight the smugglers, and find the map. But the party does not know they are in your outline. They will skip the informant, break into the warehouse from the roof, talk the smugglers into switching sides, and never find the map because they already guessed the answer.

None of that is a failure. It is what makes tabletop different from a novel. Your prep should expect it.

So prepare the ingredients a session needs: a reason to act, a few things that could happen, people with agendas, truths that can surface in more than one place, and consequences that respond to choices. Then let the players cook.

A Fast Session Prep Checklist

If you have twenty minutes, answer these questions in order and stop when you run out of time:

• What has changed since last session, and who noticed?
• What is the first thing the players see when the game starts?
• What are three or four scenes that could happen tonight?
• What is the truth the players might uncover, and how many ways can they reach it?
• Which two or three NPCs are likely to appear, and what do they want right now?
• What would make success feel earned, and what does it cost?

That is a runnable session. Everything below is how to answer those questions well.

A Twenty-Minute Prep Schedule

When time is genuinely short, a checklist still needs a clock. Use this order:

Minutes 0 to 3: recover the current state

Read the last session's final paragraph, not the entire campaign archive. Write down the location, immediate problem, unresolved player decision, and any promise you made at the table.

Minutes 3 to 6: review the characters

Choose one personal hook and one character ability, relationship, or goal that deserves room tonight. You are not planning a private scene for every hero. You are making sure the situation can notice who they are.

Minutes 6 to 9: write the strong start

Prepare the first image, active problem, and immediate question. Begin as close as possible to a decision. If the previous session ended mid-crisis, your strong start may simply sharpen that crisis.

Minutes 9 to 13: list flexible scenes

Write three scene prompts in no fixed order. Give each a person, pressure, or discovery. Mark one as optional so you already know what to cut if play runs slowly.

Minutes 13 to 16: write secrets and clues

List three truths that could matter. Give crucial truths multiple possible clues, but do not assign every clue to one exact room.

Minutes 16 to 19: stock the likely content

Note two NPC wants, two location details, and any rules material you do not want to search for during play. For a tactical encounter, record the relevant creature or hazard references and the purpose of the scene.

Minute 19 to 20: prepare the first consequence

Ask what happens if the party waits, fails, or walks away. One clear offscreen move gives the situation momentum and gives you somewhere to turn if the table stalls.

Stop when the timer ends. If a later scene needs more detail, take a short break during play or make a quick ruling. Do not spend your last five minutes polishing material that may never appear.

Step 1: Review the Characters

Prep starts with the people at your table, not the plot in your head.

Before anything else, look at the player characters and ask what each one currently wants, fears, or is chasing. You are looking for hooks you already planted and forgot, and for spotlight you owe someone.

• Whose personal thread has gone quiet for a session or two?
• Which character has a relationship, debt, or rival you can put on screen tonight?
• What did a player lean into last time that you can reward this time?

You do not need to service every arc every week. You need one or two moments that tell each player the campaign is paying attention. When the rogue's old crew shows up, or the cleric's temple asks an uncomfortable favor, prep has already done its most important job.

Step 2: Build a Strong Start

The opening is the one part of the session you can prepare with real confidence, because it happens before the players have made any choices. So make it count.

A strong start drops the party into motion. It shows a problem, implies a consequence, and asks "what do you do?" without a paragraph of throat-clearing.

Weak start:

You arrive in the town of Millbrook. It's a quiet farming village. What would you like to do?

Strong start:

You reach Millbrook at dusk, in time to see three farmers nailing the well shut while a fourth argues that whatever's down there is still someone's daughter.

The second version gives the table a situation, a disagreement, and a clock in one sentence. Nobody has to ask what the adventure is about. Prep the first ninety seconds this well and the session almost starts itself.

Step 3: Outline Flexible Scenes

Do not write scene one, scene two, scene three. Write a short list of scenes that might happen, in no fixed order.

Think of each scene as a tool you can reach for when it becomes relevant: a tense negotiation, an ambush, a discovery, a ritual interrupted, a confrontation with someone who knows too much. If the party takes a hard left, you drop the scene that no longer fits and pull one that does.

Sly Flourish calls scenes the catch-all step, and that is the right instinct. A scene can be as short as a name and a hook:

• The grieving father: begs the party not to open the well and knows more than he admits.
• The night the well answers: if the party waits, something climbs out and takes a second child.
• The old survey: a map in the town hall shows the well predates the town.

Three or four of those is plenty. You are not guaranteeing they happen. You are making sure that when the table creates an opening, you have something ready to fill it.

Step 4: Separate Secrets from Clues

This is the single upgrade that makes mysteries stop breaking.

A secret is a truth about the world: who did it, what the artifact really is, or why the well was sealed. A clue is a way the players might learn that truth. The mistake most GMs make is welding the two together by putting the one crucial revelation behind the one locked door and the one failed roll.

Instead, write your secrets as a plain list, unattached to any location. Then make sure each important one can be discovered more than one way.

Justin Alexander's three-clue rule puts it precisely: for any conclusion you want the players to reach, include at least three clues. Three, because players miss the obvious, fail the roll, or interpret the evidence sideways. Three clues is a plan with two backups.

Secret: the mine foreman sealed the shaft to hide that his crew woke something.

Clue 1: the sealing order is dated a week before the "accident." Clue 2: a miner's widow says her husband stopped sleeping, not stopped breathing. Clue 3: the thing below imitates a voice the foreman flinches at.

If the party skips the office, the widow still talks. If they never meet the widow, the creature gives it away. The truth survives contact with the players.

Step 5: Stock Locations, NPCs, and Rewards

The last of the fast steps is stocking the shelves the session will actually pull from.

Fantastic locations. Prep a few evocative places with one strong detail each, not floor plans. "A chapel where the candles burn but give no light" does more work than a room-by-room map. Aim for locations that already have trouble in them.

A handful of NPCs. Two or three is usually enough. For each, note what they want, what they know, and one behavior a player can recognize at the table. Skip the biographies.

Rewards that open doors. Treasure is fine, but the best rewards create the next problem. A favor from a faction, a map to a sealed place, safe lodging that comes with an obligation, forbidden knowledge that someone will kill to keep quiet. A reward should answer "what did we gain?" and quietly ask "what does that gain cost?"

If you are starting cold, a structured generator like SessionRoll can hand you a villain, factions, NPCs, locations, and a starting situation in one pass. The value is not treating the output as gospel. It is having enough raw material that your prep becomes editing instead of invention.

Prep Consequences and Offscreen Moves

Flexible prep still needs direction. The direction comes from people and threats that act when the party does not stop them.

For each active pressure, write one next move:

• The rival faction buys the witness's debt.
• The flood reaches the lower archive.
• The duke announces the trial will happen at dawn.
• The creature imitates a second missing villager.

These are not events you force into the session. They are what happens when enough time passes or when the party creates the opportunity. If the players prevent the move, cross it out and let that success stand.

Good consequences change the situation instead of closing it. A failed negotiation may raise the price, cost an ally, reveal the party's interest, or force a less safe route. A failed search may take long enough for the opposition to act. The game keeps moving, but the world records the failure.

Prep consequences at the same scale as the choice. A rude conversation should not cause the kingdom to fall. A public accusation against a powerful faction may cost access, reputation, or safety. Proportion makes the world feel responsive rather than vindictive.

It also helps to know what opposition knows. Write how an enemy receives information: spies, witnesses, official reports, magic, or rumor. If the players block that channel, the enemy should not react with impossible accuracy.

Finally, prepare one sign for every offscreen move. Players cannot respond to a clock they never see. New guards, empty shelves, smoke on the horizon, a changed sermon, or a frightened message can show that pressure advanced.

A Worked Example

Here is the whole checklist in about fifteen minutes of prep.

Characters: The paladin swore an oath to protect a village that just went dark. Tonight is her spotlight.

Strong start: The party crests the hill and sees the village, untouched, lamps lit, dinner on the tables, and completely empty of people.

Scenes that could happen:

• The one resident left, hiding, who thinks the party did it.
• The root cellar where the sound comes from at night.
• The traveling priest who arrived the day everyone vanished.

Secret and clues: The priest is real, but the thing wearing him is not.

• Clue 1: he casts no reflection in the still water of the trough.
• Clue 2: the missing villagers all attended his sermon.
• Clue 3: the hidden resident saw him counting the townsfolk like inventory.

NPCs: Hidden resident (terrified, useful), the priest-thing (patient, hungry), a returning merchant (will blunder in at the worst time).

Reward: Save the village and the paladin's oath holds, but the thing escapes wearing a face the party trusts, which is next session's problem.

Notice what is not prepped: the exact fight, the priest's full history, a map of every house. Those can wait until the table asks.

To make the example more resilient, add two consequences. If the party spends the night searching houses, the priest-thing takes the returning merchant. If they openly accuse the priest without evidence, it uses the paladin's trusted face and asks the hidden resident to choose whom to believe.

Add one flexible rule reference only if the system needs it: the creature's likely escape method and the difficulty of resisting its voice. Everything else can use existing rules or a table ruling. This keeps mechanical prep attached to the decisions most likely to matter.

How Much Time Should Prep Take

Less than you think, if you prep in the right order.

The steps above are sorted by value. Review the characters and build a strong start even if that is all you have time for. Those two alone will carry a session. If you have more time, add scenes, then secrets and clues, then locations and rewards. Stop whenever you run out of time because you prepped the important things first.

A useful discipline: set a timer. Give yourself thirty minutes, not three hours. Constraint kills the instinct to over-document, and over-documentation is where most GM burnout hides. You are not trying to write everything. You are trying to arrive ready to improvise.

Prep time can grow before important finales, mysteries, or unfamiliar systems. That is not a failure. The useful measure is whether each extra minute reduces a real burden at the table. Reviewing a complex hazard may help. Writing four pages of history nobody can discover tonight probably will not.

Use a Post-Session Reset

The best time to begin the next prep is while the current session is still clear.

Take five minutes and record:

• Where the party ended.
• What decision changed the situation.
• Which NPCs or factions learned something.
• What promise, clue, or question remains open.
• What the players seemed excited to pursue.

Then update one sentence for every major actor: what will they do next? You do not need to build the next session yet. You are preserving the state that future prep would otherwise spend ten minutes reconstructing.

Separate events that happened from plans that were unused. If the party never met the smuggler, do not let your notes quietly turn that encounter into canon. Move reusable material forward, archive the rest, and mark improvised names or rulings before you forget them.

A voice memo works if writing feels impossible after a long session. Transfer only the important decisions when you next open your notes. The method matters less than preserving continuity.

Common Session Prep Mistakes

Scripting player decisions. If your notes say "the party will," rewrite them to say "the party can." You do not control the verbs.

Writing boxed text you will never read aloud. A paragraph of prose describing a tavern will be skimmed and abandoned. One vivid detail and a reason to care beats three sentences of scenery.

One path to the clue. If a single failed roll can stall the session, you have a design problem, not a bad table. Add a second and third route.

Prepping the whole campaign every week. Session prep is not campaign prep. Prepare the next session and the pressure that points past it. Let the rest stay fog until the players walk toward it.

Ignoring last session. Five minutes updating who is angry, what clock advanced, and what the players cared about is worth more than an hour of new invention.

Preparing rules with no situation attached. A page of creature abilities is not a scene. Know why the encounter might happen and what changes when it ends.

No sign that pressure advanced. Offscreen moves only create agency when players can perceive their consequences.

TTRPG Session Prep FAQs

How many scenes should I prepare for one session?

Three or four flexible scenes are usually enough for a typical session. Mark at least one optional. The table may create scenes you never listed, which is exactly why each prompt should remain movable.

Should I prepare every possible player choice?

No. Prepare the actors, pressures, locations, and truths that remain valid across choices. Decide consequences when you know what the players actually do.

How much should I write for an NPC?

For a likely NPC, write a current want, useful knowledge, next action, and one recognizable behavior. Expand the record only if the NPC becomes important through play.

What should I prep for combat?

Know the opposition, environment, objective, and likely ending conditions. Keep needed rules references nearby. Avoid adding enemies merely to fill an assumed quota.

What if the players go somewhere completely unexpected?

Reuse portable truths, NPC motives, and pressures where they make sense. Take a short break if you need it. You can also end on a strong decision and prepare the new direction for next time.

Is improvising a sign that I failed to prepare?

No. Preparation supplies stable facts and useful ingredients. Improvisation connects them to choices nobody could predict. The two skills support each other.

Final Thoughts on TTRPG Session Prep

The best TTRPG session prep is not the prep that predicts the session. It is the prep that survives the session.

Review your characters. Build one strong start. Outline a few scenes you might use. Separate your secrets from your clues and give each truth several doors. Stock a handful of locations, NPCs, and rewards. Then close the notebook and trust yourself to improvise the connective tissue, because that is the part players remember anyway.

Prep the pressure. Prep the openings. Prep the truths. Let the table prep the plot because they were always going to.