Session Zero: The 90 Minutes That Saves Your Campaign

Here’s how a campaign actually dies. Session four is scheduled for Thursday. On Tuesday, someone posts in the group chat: “hey, work thing came up, can we push to next week?” Everyone says sure, no problem. Next Thursday, someone else has a birthday dinner. The week after that is fine, you play, it’s great. Then two more reschedules land back to back, a month has passed since anyone rolled a die, and the DM quietly stops prepping because prepping for a game that keeps evaporating feels bad. Nobody ever says the campaign is over. The group chat just changes subject.

Notice what’s missing from that story: a bad plot. A rules argument. A player conflict. The campaign was good. Everyone liked it. It died anyway, of the most boring cause there is, and if you’ve played for a few years you have attended several funerals exactly like it.

Session zero is the meeting where you prevent that death, plus a few others, before the campaign starts. Most guides treat it as a character-creation workshop with a safety talk bolted on. Those things belong in it. But I want to convince you that the single most important thing you decide at session zero is the schedule, that it deserves more time than tone and setting combined, and that ninety minutes is enough for all of it if you know what you’re doing. By the end of this post you’ll have the full agenda.

What session zero actually is

Session zero is a get-together before the campaign begins where the table decides, out loud, what game you’re playing and how you’re going to sustain it. No dungeon, no initiative. You’re answering two questions: what are we playing (tone, setting, content, characters) and how are we playing it (schedule, attendance, table norms). Everything worth covering falls under one of those two, and the second one is the one that kills campaigns, so we start there.

The scheduling contract comes first

Campaigns die of scheduling. Say it out loud at session zero, because your players have all watched it happen and naming it gets everyone on the same side. Then negotiate the following, for real, with calendars open:

A recurring slot, not a rolling negotiation. “Every other Thursday, 7 to 10” is a campaign. “We’ll find a time each week in the chat” is a countdown timer. If I could know only one thing about a table and had to bet on whether it’s still playing in a year, I’d want to know whether the slot is fixed, sitting in everyone’s calendar like a standing meeting. Pick it together at session zero while everyone’s motivated, because you will never again have this much collective goodwill to spend on calendar Tetris.

The quorum rule. Decide now, while it’s hypothetical and nobody’s feelings are involved: how many players can be missing and we still play? I push hard for “we play unless two people are out.” One absence cancelling the game hands every single player a veto over everyone else’s Thursday, and the reschedule spiral from the opening of this post is what that veto costs. Playing with someone missing is mildly awkward. It is enormously better than the alternative. Agree on how absent characters are handled (they fade into the background, someone else runs them, the party leaves them guarding camp) and move on.

What “can’t make it” means. A campaign slot is a commitment to five other people, and it’s fair to say so. The norm that works: you show up unless something real comes up, you give notice as early as you can, and “I’m kind of tired” gets you sympathy and an expectation that you show up anyway. This sounds strict written down. In the room it takes thirty seconds and everyone nods, because everyone has been the person who dragged themselves to game night tired and was glad they came by the second scene.

Who owns the calendar. One person sends the “we’re on for Thursday” message. Usually the DM, but honestly the best pick is your most organized player, who has been waiting their whole life for this assignment.

That’s the contract. Ten minutes of conversation, and it does more for your campaign’s life expectancy than anything else in this post.

What game are we actually playing

Now the fun half. The goal here is to surface mismatched expectations while they’re still cheap to fix. A player who wanted grim political intrigue and a player who wanted to befriend every monster can absolutely share a table, but only if they find out about each other at session zero instead of session three.

Pitch the campaign like a TV show. Two or three sentences: genre, tone, what the party does. “Low-magic mercenary company, war-torn borderlands, morally gray, think Black Company” sets completely different expectations than “high-magic heist romps in a wizard city.” Your players cannot read your mind, and the campaign lives in your head in far more detail than in theirs. Say the elevator pitch out loud and watch their faces.

Set the rating and the lines. Decide together what’s on screen, what happens off screen, and what stays out of the story entirely. You don’t need formal terminology for this. “Anything anyone doesn’t want in the game?” asked sincerely, with the DM offering one of their own first to make it safe (“I don’t do harm to kids in my games”), gets you ninety percent of the value. Write the answers down. And agree on a mid-session mechanism, any mechanism, for “I’m actually not okay with where this scene is going,” because it’s much easier to invoke a rule you set up at session zero than to interrupt a scene cold.

Build a party, together, that has a reason to stay together. Characters made in isolation produce the classic session-one problem: five strangers in a tavern, each waiting for a reason to care about the other four. Make characters in the same room, and require two things of every sheet: a reason this character stays with the group when things get hard, and one connection to another player’s character. Siblings, old war buddies, debtor and creditor, anything. Two sentences per player, established in ten minutes, and your party enters session one already tangled together in a way that would otherwise take a month of play to grow. This is also your best insurance against the lone wolf who works alone (great in a novel, poison at a table, and completely fixable at session zero by just asking for a different concept).

The boring house rules. Phones at the table, how rules disputes get settled mid-session (DM rules now, look it up after, I’m right sometimes), who’s hosting, how food works. Two minutes each. Deciding them now means never having a tense version of the conversation later.

Play something before you leave

A session zero that’s pure meeting sends everyone home having done paperwork about a game instead of playing one. So end with dice. Run one short scene, twenty or thirty minutes: the party’s first job interview with their patron, a bar brawl, the last fight of the war that ended yesterday. New players get their first taste of how the game flows before the campaign has any stakes, and everyone drives home having actually played, which is the feeling that carries a table to session one.

If you have brand-new players at the table, this scene matters even more. I’ve written about what a first session actually feels like from the player’s side, and about getting a group together in the first place if you’re reading this without one yet.

The 90-minute agenda

Steal this outright:

That last row is real, by the way. Momentum is worth protecting, and the strongest opening move a campaign can make is the date of session one going into the chat while everyone’s still in the room.

The part everyone forgets by session twelve

One more thing, from someone who builds campaign-memory software for a living. Everything you decided at session zero (the tone, the lines, the quorum rule, why the ranger owes the warlock money) lives in exactly one place: your table’s collective memory. That memory is five busy adults, and it leaks. By session twelve, nobody’s sure what was agreed about character death, two players remember the patron’s deal differently, and the ranger’s debt has been silently forgotten by everyone except the warlock’s player, who is waiting.

Write session zero down. One page, pinned in the group chat, is plenty. The campaigns that go multi-year keep their agreements and their history somewhere outside their heads. That’s the actual job of my product, for what happens after the dice start rolling: Loracle sits in your Discord voice channel, records the session, and keeps the recaps and the growing campaign wiki so the story’s memory stops depending on anyone’s Tuesday brain. Session zero is the one session it can’t keep for you, because session zero happens before there’s anything to record. So bring a notebook to this one.

Then pick a Thursday, hold the meeting, play the scene, and post the date. Campaigns that get a real session zero start better, and a year from now they’re the ones still meeting, because the thing that kills the others got handled in ninety minutes, back before it ever had a chance.