The Campaign Bible: What to Write Before Session One

Walk into any community of dungeon masters and you'll find two camps. One has nothing — half-remembered NPC names scribbled on an initiative tracker, a vague idea of "the kingdom," a starting town invented on the fly. The other has a forty-page world bible with cosmology, language families, a chronological history reaching back six thousand years, and somehow no clear sense of what's happening in the first session.

Both camps run into the same problem. The first runs out of consistency. The second runs out of momentum. The fix is the same document, scaled correctly: a campaign bible just detailed enough to keep the world consistent, lean enough to stay useful as the campaign evolves. Not a novel. Not a wiki dump. A reference document. The kind of thing you can read in fifteen minutes, find anything in thirty seconds, and update in two after each session.

This is a guide to what belongs in that document, what doesn't, and how to write it so it serves you instead of becoming another thing you have to maintain. Spend an evening on it before session one and you'll have a living tool you're still using thirty sessions later.

What a Campaign Bible Is (And Isn't)

A campaign bible is a reference tool. It exists so that during a session, you can look up an answer fast. Who is the watch captain? What does the merchants' guild want? Where is the river temple? Who's the duke's heir? You should find any of those in under a minute, mid-conversation, without breaking the flow of play. That's the bar.

A campaign bible isn't creative writing. It isn't a place to flex your prose, or a worldbuilding project for its own sake. The moment it becomes those things, it stops being useful — entries get long, structure gets buried, and you stop opening it because reading takes too much effort. The best campaign bibles read like a wiki crossed with a contact list. Short entries. Strong structure. Easy to scan.

This framing helps with the hardest discipline in building one: cutting. Most DMs over-write. They have a vivid picture in their heads of the world they want, and the bible becomes the place they try to capture all of it. That's the wrong instinct. The bible is the working notes, not the novel. The novel is what happens at the table, week after week. If you only remember one rule for this document: every entry should fit on a phone screen. If it doesn't, it's been over-written.

Section 1 — The Premise

Open the document with a single paragraph that captures what the campaign is. Tone, genre, inciting situation. The paragraph should fit on an index card, and if you read it aloud to a friend they should be able to repeat the gist back to you in one sentence.

A good premise has three components. The setting in present tense — where are we, what kind of place is it, what's the broad situation. The hook — the political crisis, the dying god, the unstable border, the missing heir. And the party's role — why these specific adventurers are involved.

For example: "A frontier barony on the edge of a kingdom that's been quietly rotting for a generation. The old baron is dying without a clear heir, three factions are positioning to control the succession, and a series of mysterious raids on the northern villages has begun shifting the balance. The party are mercenaries hired to escort a tax collector to a remote village — and they arrive to find the village empty." Three sentences. That's a campaign.

The premise is the spine. It should be the first thing in the bible and the last thing you change. Other sections will update constantly. If the premise is still true after twenty sessions, you've kept the campaign focused.

Section 2 — The World at a Glance

This is where the active factions live. Not a history of the world — what's currently in motion. Each major faction gets a short entry: name, current goal, who leads it, who their major rival is, and one line about their methods or vibe.

Limit yourself to five factions at most for the starting region. More than that, and you'll lose track. If you can't get the list down to five, you're including factions that don't actually have wants in motion — cut those, they're background, they can come back if a player asks.

Each entry should look something like this:

House Vellan. Old noble family, currently the strongest claimant to the barony. Lord Vellan is pragmatic and patient; Lady Vellan is the strategist. Want: secure the succession through marriage alliance with the merchants. Rival: House Cordray. Methods: legalistic, well-connected, slow.

That's everything you need to run House Vellan for the first ten sessions. You don't need their banner, their motto, or their family tree. If those things come up, invent them on the fly and write them down after. Keep entries in present tense, with active goals — if you find yourself writing "the guild was founded in," stop. That's history, not state. The world-at-a-glance section is about now.

Section 3 — The Starting Region

The starting region is the place the party will spend their first five sessions. Define it densely. Maybe a city and its surrounding farmland. Maybe a frontier town and the wilderness pressing on it. Maybe a noble's estate with its village. Whatever the scale, the rule is the same: the area the players can reach within a day of travel should be the area you've actually built.

Write a short entry for each major location — the market, the watchtower, the temple, the inn. Two or three sentences per location: what it is, who runs it, what makes it distinct, and what's currently happening there. That last part matters. Every location should have a current happening attached. The market is in the middle of a price dispute. The watchtower is short-staffed because half the guard was sent north. The temple is preparing for a holy day. These aren't side details; they're the texture that makes the region feel inhabited.

Geography matters less than density. You don't need a beautiful map. You need to know what's where, what's close to what, and how the players move between them. A sketch with five labeled locations and arrows is more useful than a kingdom map. Spend more pages on this section than on any other — the starting region is where the campaign actually lives for the first month or two of play.

Section 4 — Key NPCs

Five to ten named NPCs. No more. These are the people the party will encounter in the first few sessions, plus the major players in the factions you've defined. Each one gets an entry that includes the four things every memorable NPC needs: what they want, what their flaw is, what they're hiding, and how they relate to the party.

Sample entry:

Veska Half-Orc. Captain of the watch in Halmar's Ford. Wants: a promotion to the duke's personal guard. Flaw: she'll bend the law for anyone with leverage over her career, and she knows it about herself. Secret: she's been quietly taking bribes from House Vellan to look the other way on certain shipments. Relationship to party: official authority in town, will treat them coolly at first, can be turned into an ally if they help her solve the missing-villagers case publicly.

Four data points. Fits on a phone screen. Tells you everything you need to play Veska consistently, including the angle for any scene she's in. Avoid the trap of writing full biographies — where she grew up, what her parents did, what her favorite food is. None of that helps you run her at the table. If a player asks, you'll improvise and add it to the entry afterward. The bible isn't a novel about Veska. It's the four pieces you need to perform her reliably.

Section 5 — Secrets and Threads

This is the part of the bible that's only for you. What's actually going on, behind the curtain? What's the villain's real plan? What's the truth about the raids? Who is the duke's secret heir? What was in the missing barge?

Write these out plainly, in a section the players will never see. The big-picture threads — what the campaign is actually about, who the eventual antagonist is, what the stakes will become — should be sketched in. Mid-range threads, the immediate mysteries the party is investigating, should be specific. Session-level threads, what's happening in next week's scene, should be detailed enough that you can run them.

The reason this section stays separate from the rest of the bible is that secrets need to be tracked just as carefully as public facts. A campaign whose secrets the DM has half-forgotten by session ten is a campaign that contradicts itself. Players notice. Track the truth as carefully as you track the lies, and note the current version of any plan that might shift as the players surprise you.

What to Leave Out

Most of what people write into campaign bibles doesn't belong there. Ancient history is the worst offender — anything more than a generation back, unless it's directly causing a current conflict, can wait until a player asks. If they never ask, it never needed to be written. Cosmology is similar. The names of the planes, the structure of the afterlife, the gods' family tree — leave them. 5e has defaults you can fall back on, and your version only matters when it intersects with what the players are doing.

Languages don't belong in the bible unless the campaign turns on them. Geography beyond the starting region is satisfying to draw but useless to your sessions — the party isn't going to that continent for the first ten sessions. And the shopkeeper they'll talk to in session two doesn't need a full life. He needs a name, a want, a flaw, and a secret. Save backstory writing for the NPCs who become recurring.

The discipline of cutting is what keeps the bible usable. Every entry that doesn't earn its place makes the document harder to scan. Be ruthless. If you can't bring yourself to delete a beautiful piece of writing, paste it into a separate file labeled "lore I might use later." It can stay there. It doesn't belong in the working document.

Keeping It Updated

The bible is alive. After every session, spend five minutes updating it. New NPCs the party met get short entries. Existing entries get updates — Veska's bribery is now half-exposed, Lord Vellan's marriage plan was disrupted, the merchants' guild has a new spokesperson. Anything established in play gets logged. Anything contradicted gets corrected.

The bible tracks what's true in the world the players have experienced, not what you originally planned. If the players blew up your planned temple schism in session four, the bible should note it — schism averted, tensions remain under the surface. Players remember the broad strokes. They don't remember names, dates, places, or relationships. That's your job. A campaign that holds together across thirty sessions is one where the DM has a working memory better than the players', because they've been writing it down. If updating ever starts to feel like a chore, you've over-written some entries — trim them.

Ready to put these ideas into practice? Nocera is an AI world-building tool built for dungeon masters — describe your NPCs, locations, factions, and events in natural language, and Nocera builds a linked wiki automatically. Start for free →