Session Zero Isn't a Rules Read-Through: The 90-Minute Framework We Actually Use
A concrete, 90-minute Session Zero framework for GMs: pitch, lines and veils, safety tools, and building characters together in GameMasterCraft before session one.
Every table has run this version of Session Zero: the GM reads the core rules for twenty minutes, everyone nods, someone asks if they can play a half-orc barbarian, and the "expectations conversation" lasts about ninety seconds. Then three sessions later you find out one player thought this was a lighthearted heist campaign and another was quietly building a redemption arc around a dead sibling nobody mentioned. That gap is what Session Zero is actually for, and it's worth doing on purpose.
Here's the framework we lean on, and it fits in about ninety minutes if you keep it moving.
Start with the pitch, not the rules (15 minutes). Tell the table what the campaign actually is: tone, stakes, how much combat versus intrigue versus exploration, and whether it's a tight three-act arc or an open sandbox. This is also where you say the quiet part out loud - "I'm planning for character death to matter" or "nobody's dying unless you want them to." Vague pitches produce mismatched characters, and mismatched characters produce the player who's building a pacifist bard for your dungeon-crawl.
Do lines and veils before character creation, not after (15 minutes). This is the one groups skip and regret. Lines are hard no's - topics that don't come up at all. Veils are things that can happen but happen off-screen, a fade-to-black instead of a scene. Go around the table and let everyone list a couple of each, GM included. It takes ten minutes and it's the cheapest insurance your campaign will ever get. Pair it with an X-card or a verbal equivalent - any player can pause or redirect a scene in progress, no explanation owed - and an open-door policy that nobody has to justify stepping away from the table.
Build characters together, in the room (40 minutes). Not solo homework turned in at session one - actually together, so you can catch the two players who both want to be the party's only healer, or the backstory that assumes a sibling nobody else knows about. This is where GameMasterCraft actually earns its keep for us: we run the party build in it together so everyone can see the bonds, the open plot hooks, and each other's concepts as they're written, instead of piecing it together from four separate Discord messages a week later.
Close with logistics (10-15 minutes). Schedule, session length, how late you're texting "running 20 late," what happens if someone has to miss three sessions in a row. Unglamorous, and it's the thing that actually kills more campaigns than any monster does.
None of this needs to feel like a seminar. Keep it conversational, let it run long if the table's into it, and treat it as session one of the story rather than paperwork before the story starts. The campaigns that fall apart around session four almost always skipped this, not because the GM forgot the rules but because nobody agreed on what game they were playing.
If your table's never run one, this weekend's as good a time as any. Ninety minutes now versus a mid-campaign implosion later isn't a close call.
What does your table's Session Zero actually cover -- and what's the one thing you wish you'd nailed down before session one?
Comments (0)
Sign in to join the conversation
Sign InNo comments yet. Be the first to share your thoughts!