Skip to content

A D&D session zero checklist, and the questions to ask your players

Session zero is the meeting before the first real session, where the table agrees what game it is playing. The checklist below covers the five things it has to settle: the game, the characters, the content lines, the schedule and table rules, and the record you will keep. Copy it, work down it in about an hour, and send the answers round afterwards.

· 7 min read

What a session zero is for

A session zero is a meeting, before the campaign starts, where the game master and the players agree what kind of game they are about to play. Some tables make characters at it, some only talk; it can be a full evening or forty minutes on a call. What makes it a session zero is that nothing is decided by dice and everything that would be painful to argue about in session six is decided now.

Most problems that end campaigns are mismatched expectations rather than bad play: one player wanted a dungeon crawl and another a court drama, one thought the game was weekly and another monthly, one was fine with horror and another was not. A session zero costs an hour and removes most of them before anyone is invested.

Session zero is one step of several; how to start a D&D campaign puts it in order with choosing the game, finding players and fixing the schedule.

The session zero checklist

Work down it in order. The first three blocks shape the characters, so do them before anyone commits to a build. Write the answers down as you go; the last block is about what happens to them.

Session zero checklist (paste into a doc or the group chat)

SESSION ZERO CHECKLIST

THE GAME
[ ] System and edition, and any house rules
[ ] Setting and starting place, in two sentences
[ ] Tone: heroic / gritty / comic / horror / mixed
[ ] The mix: fights, talking, exploring, puzzles
[ ] How long: one arc (~10 sessions) or open-ended

THE CHARACTERS
[ ] Starting level, stats method, allowed sources
[ ] Why this party is together, and why it stays
[ ] One tie between each character and another
[ ] Character names, spelled, and how to say them

CONTENT
[ ] Lines (never in the game)
[ ] Veils (happens off-screen)
[ ] A signal to stop or skip a scene mid-game
[ ] Player-vs-player: allowed, or not

SCHEDULE AND TABLE RULES
[ ] Day, start time, length, how often
[ ] Quorum: how many can miss before we cancel
[ ] What happens to an absent player's character
[ ] Phones, food, breaks, rules arguments

THE RECORD
[ ] Who keeps notes, and who writes the recap
[ ] Recording: ask out loud, everyone present
[ ] Where the recap and NPC list will live
[ ] When we check in on how it is going

Session zero questions to ask your players

A checklist tells you what to settle; these questions get each player talking about what they want. Ask them one player at a time, and listen for the answers that do not match. Those are the conversations session zero is for.

  • What is the best session of any game you have played, and what made it good?
  • Which do you want more of: fights, talking to people, exploring, or solving things?
  • What is your character for? What do they want that they do not have yet?
  • Is there anything you never want to see in this game, or want kept off-screen?
  • How much do you want the story to be about your character, and how much about the party?
  • Are you happy with characters disagreeing? With characters fighting each other?
  • Which nights can you actually make, most months, without cancelling something else?
  • What made a past game stop being fun for you?

Safety tools: lines, veils and the X-card

Lines and veils come from Ron Edwards, who set them out in his 2003 book Sex & Sorcery, and they are the easiest tool to run at a first session. A line is something that will not appear in the game at all. A veil is something that can happen in the story but off-screen, with the scene cutting away. Go round the table, collect both, and write them down where everyone can see them. The list can change later; anyone can add to it privately by messaging the game master.

The X-card, created by John Stavropoulos and free to use under a Creative Commons licence, covers what nobody predicted. A card with an X on it sits on the table, or a hotkey or emoji is agreed for an online game, and anyone can tap it to skip the content in play, with no explanation asked. Agree at session zero that it exists and that tapping it is never questioned.

Both, and a dozen more, are explained in the TTRPG Safety Toolkit, a free collection curated by Kienna Shaw and Lauren Bryant-Monk. You do not need every tool there is, and a table of old friends may need only lines, veils and a stop signal. What matters is that the tools are agreed before they are needed, because asking in the middle of a scene is exactly when people say nothing.

Schedule and table rules: the part that ends campaigns

More campaigns end from scheduling than from anything in the story. Settle the day, the start time and the length (see how long a session should be), and agree a quorum: the number of players who can be missing before the session is cancelled rather than run short. Three of five is a common answer. Decide too what happens to an absent player’s character: it fades into the background, someone else runs it in fights, or it stays behind at camp.

Agree the small things while nobody is annoyed yet: phones during play, who brings food, when breaks happen, and how rules arguments end (the game master rules now, and anyone can look it up after the session). If the group is large or its calendars do not overlap, a fixed table may be the wrong shape; a West Marches campaign is built for exactly that. At a paid table, cancellations and refunds belong in the listing before anyone books; becoming a paid DM covers what to write.

Names, spellings and who keeps the record

This is the block most checklists leave out, and it is the one that decides whether anyone can remember the campaign in six months. Get every character’s name written down, spelled the way its player spells it, with how to say it. "Wendelbrie, WEN-del-bree" settles in ten seconds what otherwise becomes three spellings across three people’s notes.

Then decide who keeps the record. The game master taking all the notes is the default and the most common way the notes stop; a rotating player recap, or one player who enjoys it, spreads the job. How to write a session recap has a format for whoever takes it on.

If you want to record sessions, ask now, out loud, with everyone present: what you are recording, what it is for, who can see it and how long you keep it. One person saying no means no recording. Recording consent and the law covers the conversation and the legal side.

Session zero for Daggerheart, Pathfinder and other games

The checklist is not D&D-specific. Every block applies to any tabletop RPG; only the first two lines of "the game" change. Daggerheart’s own site names session zero as the place to set expectations, and credits Lines and Veils and the X-card among its session zero tools. For Daggerheart, settle which campaign frame you are using and read its pitch aloud, because a frame sets tone and themes the way a setting does in D&D. For Pathfinder, agree which sources are allowed and whether you use the free archetype or other variant rules.

Games with a strong genre of their own make the content block more important, not less. A horror game like Call of Cthulhu or Vampire: The Masquerade earns its lines and veils conversation more than a lighthearted dungeon crawl does.

Running session zero online

On a call, share the checklist on screen and fill it in live so everyone sees the answers land. Do the content questions privately as well as aloud: a form or a direct message to the game master lets a player name a line they would not say in front of the group.

If the game will live on a Discord server, set it up before session zero and pin the answers in a channel, so a player who joins later reads them instead of asking. Running D&D on Discord has a layout to copy.

After session zero

Send the filled-in checklist to everyone the next day. A decision nobody can find again was not really made. Then plan the first session around what you heard: the hooks players asked for, the ties between characters, the tone everyone agreed. How to start a D&D session covers the first few minutes.

Come back to it. After three or four sessions, ask whether the game is the one everyone signed up for; Stars and Wishes is a five-minute way to do that every week.

Where session zero and its safety tools come from, with sources

Every third-party figure quoted above, with where it came from and when it was checked. Prices move — if a date here is old, verify before relying on it.

WhatValueSource
What a session zero is, in D&D Beyond’s words"'Session Zero' is a pre-game meeting typically initiated by the group's Dungeon Master"; players "should also come prepared with things you don't want included in your game" (James Haeck, 21 February 2020)sourceas of 2026-11-13
Lines and veils, defined by their originator’s site"Lines refer to content which a person, or group, does not want to include in the current fiction of play." "Veils refer to content which is acceptable but which a person, or group, does not want to describe explicitly."sourceas of 2026-11-13
The X-cardBy John Stavropoulos: it "allows anyone in your game (including you) to edit out any content anyone is uncomfortable with as you play"; published under CC BY-SA 3.0sourceas of 2026-11-13
The TTRPG Safety Toolkit"a free resource making TTRPG safety/support tools easy to approach and use", "Co-Curated by Kienna Shaw and Lauren Bryant-Monk"sourceas of 2026-11-13
Session zero in DaggerheartThe Daggerheart site: "From setting expectations in a session zero, guiding players through mechanics"; its credits list "SESSION ZERO TOOLS", including Lines and Veils (Ron Edwards) and the X-Card (John Stavropoulos)sourceas of 2026-11-13

How we sourced this: Each row quotes the page shown, read on that date. The 2003 date for Sex & Sorcery is Ron Edwards’s own, from a 2018 post on the same site. The checklist, the questions and the advice on running session zero are ours.

Related guides

All guides