What Is a Series Bible, and What Goes in One?

A series bible is the document that explains what a television series is, how it works, and where it can go.

That sounds simple until you try to write one.

A good series bible has to communicate a lot of information without becoming a storage unit for every thought the creator has ever had. It needs to be detailed enough to prove the series has been developed, but focused enough that someone can understand the project without reading fifty pages of mythology first.

I think of it as the operating manual for the story. It shouldn’t replace the pilot, and it shouldn’t explain every mystery. Its job is to show that the world, characters, and episode structure can support an ongoing series.

The core concept

The first thing a bible needs is a clear explanation of the series. What is the show? Who is it about? What keeps happening? Why can this story continue for multiple episodes or seasons?

This is usually communicated through a logline, a short overview, and a description of the series engine.

The series engine is especially important. It explains what generates future episodes.

A workplace comedy might generate stories through new customers, employee conflicts, and management disasters. A mystery series might generate stories through new cases while a larger season-long investigation continues underneath them. An anthology might use a shared theme, setting, or rule rather than recurring characters.

A reader should be able to finish the overview and understand why there’s an episode two.

Tone and genre

Saying a project is a drama, comedy, thriller, or science-fiction series usually isn’t enough. Two projects can share a genre and still create completely different experiences.

The bible should describe how the story feels. Is the humor dry, aggressive, absurd, uncomfortable, or character-driven? Is the horror graphic or psychological? Is the science fiction grounded in familiar systems or built around a distant future?

It can help to name comparable projects, but comparisons should be used carefully. They’re shorthand, not a substitute for identity. Saying a series has elements of two existing shows can help someone find the neighborhood. The bible still needs to explain why this particular house is different.

The world

The world section establishes the environment in which the series operates.

For some projects, that means explaining a fictional town, institution, workplace, historical period, or technological reality. For others, the setting may look familiar, but the social rules or central premise make it function differently.

The goal isn’t to document every street or invent a century of history that never affects the story. The goal is to explain the parts of the world that create pressure.

What can characters do here? What can’t they do? Who holds power? What does daily life look like? What changes because this series exists in this particular world?

World-building becomes useful when it affects decisions. Otherwise, it’s trivia wearing a costume.

The characters

A series bible should introduce the central characters as people, not just job titles attached to plot functions.

A character description usually needs to communicate:

• Who the character appears to be
• What they want
• What they’re afraid of
• What contradiction makes them interesting
• How they create conflict
• How they may change during the season

The best character sections also explain relationships.

Television characters rarely operate alone. Their chemistry, resentment, loyalty, attraction, history, and inability to communicate often generate more story than the external premise.

A character can be intelligent, funny, successful, reckless, or guarded, but those qualities become dramatically useful only when they collide with someone else.

The rules

Some series need a dedicated section explaining their rules. This is common in science fiction, fantasy, horror, animation, mysteries, and any project built around a repeating structural device.

What activates the central premise? What are the limits? What consequences carry from one episode to another? What can never happen?

Rules keep the story from solving problems whenever it becomes convenient. They also help future collaborators understand what belongs inside the series and what would break it. Rules can evolve, but they shouldn’t feel optional.

While developing By Design, the rule that the technology does not malfunction became a filter for the entire series. It shaped the conflicts, the endings, and the kinds of stories that belonged in the season.

Without that rule, the project could easily become a collection of generic warnings about broken machines. With it, the focus remains on human choices and systems doing exactly what they were designed to do.

The season

A bible should provide a sense of movement.

Where do the characters begin? What changes during the season? What relationships strengthen, fracture, or become dangerous? What larger question keeps building?

A season overview doesn’t always need to reveal every ending, especially in an outward-facing pitch document. It does need to show that the creator has thought past the pilot.

This is where the document starts proving that the project is more than a premise.

Episode examples

Episode summaries demonstrate range.

They show how the series engine produces different stories while maintaining the same tone and identity. They can also reveal how character arcs and season-long threads progress.

These summaries don’t have to contain every scene. They should communicate the episode’s central conflict, major escalation, emotional movement, and place within the larger season.

For By Design, I developed eight technological premises for the first season. The details differ, but every episode returns to the same larger concern: what happens when people place too much faith in systems built to satisfy them?

That connection is what makes the ideas part of one series instead of a folder of unrelated concepts.

Visual identity

Not every series bible needs extensive artwork, but visual direction can help communicate the project quickly. This may include:

• A title treatment
• Character artwork
• Location references
• A restrained mood board
• Poster concepts
• Typography and graphic direction
• A few carefully selected visual references

The artwork should support the writing rather than bury it. A bible isn’t improved by filling every empty space. Sometimes one strong image establishes more atmosphere than six pages of generic stock photography.

Current status

I also think a bible should be honest about the project’s current stage.

Is the pilot complete? Are additional episodes outlined? Is there a finished manuscript or existing intellectual property? Are producers, actors, directors, or other collaborators attached? Is the creator seeking representation, financing, development partners, or production support?

Clear status prevents the document from implying commitments or progress that don’t exist.

What a bible shouldn’t be

A series bible shouldn’t be an encyclopedia.

It shouldn’t explain every secret, include every abandoned character, or preserve every version of the project. It isn’t a scrapbook of development history.

It also shouldn’t be so vague that every section sounds like marketing copy.

The strongest bibles create confidence because the creator has made decisions. The reader may not know every future plot point, but they understand the world, the people, the rules, and why the series can continue.

That’s the real job of the document.

A pilot shows that you can write one story. A series bible shows that you know what story you’re building.

← Back to all notes