Book-to-screen development

Show and Universe Bibles: Building a World That Can Sustain a Series

By Jeff Jones · Storyforge Imaginarium · October 28, 2026

A show bible explains why a series can keep generating stories. A universe bible records how its world works. They may live in one document, but they solve different problems: one supports dramatic development, while the other helps prevent contradictions.

Start with the series engine

Define what creates a new episode. A team investigating impossible disappearances has a repeatable task; discovering one hidden doorway may be only a premise. Identify the recurring pressure, the characters who respond to it, and the larger question that develops across the season.

For an illustrative series about a rescue crew working in cities that vanish at dawn, each rescue can provide an episode objective. The crew’s search for the cause supplies the season arc. The rules governing dawn, evacuation, and who remembers the missing cities belong in the universe bible.

Record the rules and their consequences

Document geography, institutions, technology or magic, social structures, and limitations. Give each important rule an example and a consequence. If a device can reverse time once, explain the cost and why the characters cannot use it to solve every problem.

Mark the difference between established fact, a character’s belief, and an unresolved development idea. An unreliable narrator’s claim should not silently become authoritative canon.

Connect character arcs to season structure

For each principal character, record the starting belief, the choices that challenge it, and the intended end state. Outline episode purposes without pretending every future season is already fixed. Later-season possibilities should grow from durable conflicts rather than a list of increasingly large threats.

Use a simple canon ledger

• Fact: the rule or event being established.
• Source: manuscript chapter, approved script scene, or development decision.
• Status: proposed, approved, revised, or retired.
• Dependencies: characters, locations, and episodes affected.
• Owner: who can approve a change.

If the writers change how the vanishing cities work, the ledger identifies which scripts and visual sequences need review. This is more useful than a beautiful document that nobody updates.

Keep the pitch version and production version distinct

A pitch bible should make the premise, tone, characters, audience experience, and series potential easy to understand. A working production bible can contain detailed timelines, spoilers, asset references, and continuity notes. Give each reader the level of information needed for their decision.

Build a development package in stages

Begin with a paid series-development brief: premise, series engine, principal characters, world rules, season-one arc, and a pilot outline. A pilot screenplay, expanded universe bible, and cinematic pitch assets can follow after those foundations are approved.

The goal is a coherent package a collaborator can evaluate. A bible supports development and communication; it does not promise a sale, financing, or a production commitment.