TV Pitch Deck vs. Series Bible: What Does a Scripted Show Need?

Someone asks for a “bible,” and suddenly a writer is considering thirty pages of backstory for a project that has not yet persuaded anyone to read the pilot. Someone asks for a deck, and the opposite happens: a complicated season is reduced to a logline and a few moody photographs, as though the hard parts will become clear through atmosphere.

Neither document is inherently more serious. They do different work. A pitch deck selects enough of a scripted series for the decision currently in front of the reader. A development bible gives more room to explain how the story design holds together. A working production reference records continuity that has actually been settled. The right depth comes from the reader’s use of the document, not from the weight of the word bible.

Screen Australia’s 2018 Story Documents: Drama guide explicitly distinguishes a “development bible” from a “production bible,” and cautions that terms such as treatment, bible, scriptment, outline, and synopsis vary. It is Australian guidance, not a universal definition or a current US submission rule. Its useful warning is that labels are unreliable unless you know what the document is meant to help someone do. Screen Australia, Story Documents: Drama

Ask what the reader is being asked to do

Before you choose a document, ask the recipient three plain questions:

• Is this a first read to decide whether the show is worth pursuing?
• Is this a development conversation about the story’s unresolved machinery?
• Is this a reference for people already making the show and needing to agree on what is true?

Then ask what they expect under the label they used. Some people say “bible” when they mean a deck with more story. Some mean a character-and-season document. Some mean a continuity reference with agreed rules, prior events, and production-facing details. If they have a brief, follow it. If they do not, offer a short contents proposal before you build an encyclopedia no one requested.

For a first decision, a deck may be enough. It gives the premise, the particular viewing experience, the people whose conflict makes episodes possible, and a clear sense of where the series goes. Its discipline is selection. It should not hold the reader at the door until page 26; it simply does not need to settle every exception to a world rule or every turn in a future relationship.

For a development conversation, deeper material earns its space when it explains a difficulty the deck has revealed. How exactly does this relationship change when the characters are both right? What rule of the world creates choices rather than decorative lore? What happens when the pilot’s solution becomes a later problem? The development document is not “the deck, but longer.” It is a place where causal links can be examined.

For a working production, the question changes. What has now become continuity? Which prior events, names, locations, timelines, rules, and decisions must the team share? That is not a fantasy version of the series. It has to distinguish established facts from things still being debated. Do not make a development document impersonate production certainty merely because it has a detailed table of contents.

What a deck needs to establish

Return to the fictional comedy-drama The Loan Desk. June manages a neighborhood tool library. Sal repairs the tools. June believes a rule is only useful if it protects the person standing in front of her; Sal knows that somebody eventually pays for every waived fee.

Here is a deck-sized entry:

At a neighborhood tool library where broken things arrive with their owners’ bad luck attached, June and Sal argue over who should absorb the cost of keeping the place open. The library owns one generator and lends it to borrowers. When one running a block cooling center returns it damaged during a blackout, June calls in a favor from a contractor to repair it at no charge, then waives the borrower’s replacement fee. Sal says the repair fund will not survive many mercies. Each loan puts their competing forms of care under pressure; across the season, a funding deadline forces the library to decide whether it can survive without becoming less available to the people it was made for.

That passage earns its page. It establishes the central relationship, a first incident, a repeatable source of conflict, and a direction of travel. A reader can imagine the show without being asked to memorise the library’s policies.

The deck might add one later-episode example: the contractor who repaired the generator at no charge now wants it for a private job, just as June has promised it to a family preparing for a heat wave. The favor June asked for in the pilot returns as a debt. This is enough to demonstrate that the series remembers what it has done.

What does not belong here just because it exists in the writer’s notes? A full history of June’s childhood, a complete calendar of lending rules, every possible recurring customer, and an invented answer to every question a future writer might ask. A deck is not thin because it leaves those things out. It is thin when it leaves out the reason the next episode must happen.

What development depth adds

Now imagine a producer responds well to The Loan Desk but asks, reasonably, whether June and Sal can sustain more than a pleasant disagreement. This is where a development bible can earn its additional pages.

June’s rule: No one loses access because they have had a bad week. She built this rule after seeing a neighbor sell a needed repair tool to cover a hospital bill. She does not say this history aloud; it appears in the way she makes exceptions before anyone asks. Her blind spot is that she treats a decision to delay payment as a decision that costs no one.

Sal’s counter-rule: A promise is cruel if it depends on someone else taking the loss. He will bend for a borrower who admits they cannot pay, but not for a person who treats the library as a free replacement store. His blind spot is that he mistakes the ability to survive a rule for proof that it is fair.

The generator, later: The contractor’s request forces June to confront that the earlier waiver was not private kindness; it rearranged power inside the library. Sal argues the contractor should pay in full. June fears that refusing will expose the favor she asked for. Neither solution restores the old balance: lending the generator risks the heat-wave family; refusing it risks the contractor’s work and June’s credibility.

This is not merely more character description. Each paragraph adds a relationship between desire, rule, and consequence. The later episode becomes difficult for a specific reason. The writers can test whether the complication belongs to June’s season arc, Sal’s, or both.

The last sentence in that development discussion might be: “Unresolved: does June admit the original favor before or after Sal has made his own unapproved exception?” That note is valuable because it identifies a real design choice. It is not a defect to be polished away. A development bible should let provisional thinking remain provisional where the story has not earned a final answer.

Here is the version that looks substantial but adds almost nothing:

June learned to solder at age ten with her father in a garage behind their duplex. Sal’s uncle drove a blue truck and kept a coffee tin full of screws. June once won a regional science fair. Sal has a tattoo he will eventually explain.

Any of those facts might become useful in a scene. In this document they do not show how the series generates episodes, why the two leads bend, or what a later story can do with their conflict. Length has occurred; depth has not.

Keep production continuity separate from development hope

Once a show is working with a room, directors, designers, or other teams, a reference document can take on a different obligation: it helps people avoid contradicting what has been established. That may include character facts, previous events, geography, terminology, timelines, and the rules that the production has agreed to honor.

It should not quietly upgrade every exploratory note to canon. In the Loan Desk development material, the neighbor’s hospital bill is a possible source for her rule, and the timing of her confession to Sal remains unresolved. Those are story-development questions. If an episode establishes that June never knew the neighbor personally, or the room chooses another source for her rule, the production reference needs the settled version—not the attractive discarded one.

An operational format bible is another thing again. Its task may be to let another team reproduce an entertainment format faithfully: its recurring steps, permitted variations, contributor roles, and safeguards. That is a different problem from explaining how a scripted relationship produces a scene. Do not call for a format manual when what you need is a clearer season arc; do not bring an interior character document to a handoff that needs operational instructions.

Agree on contents before arguing about length

For the same recipient question—“Can this show sustain a first season?”—the documents might look like this:

This is a comparison, not a mandatory contents list. A limited thriller may need a fuller progression; an ensemble may need more relationship architecture; an early pitch may need less. The recipient’s actual question determines the necessary proof.

The useful clarification to send is simple: “Are you looking for a first-decision presentation, a deeper account of character and season design, or a working continuity reference? If it is a development document, which unresolved questions would you like it to address?” That exchange can save you from writing a production bible for a reader who wanted three good pages—or a glossy deck for a reader who needs to see why episode five exists.

If you need help choosing the right depth and building a TV pitch document around the decision it has to support, pitch.dog offers Film/TV pitch-deck work. Share the project, current materials, intended recipient, and deadline at [email protected].

Frequently asked questions

What is the core difference between a TV pitch deck and a development bible?

They do different work. A pitch deck selects enough of a scripted series for the decision currently in front of the reader. A development bible gives more room to explain how the story design holds together. A working production reference records continuity that has actually been settled. The right depth comes from the reader's use of the document, not from the weight of the word bible. Screen Australia's 2018 guide distinguishes a development bible from a production bible and cautions that such terms vary, but that is Australian guidance, not a universal definition or current US submission rule.

How can I decide which document depth a recipient needs?

Ask three plain questions: Is this a first read to decide whether the show is worth pursuing? Is this a development conversation about the story's unresolved machinery? Is this a reference for people already making the show and needing to agree on what is true? Then ask what they expect under the label they used. If they have a brief, follow it. If not, offer a short contents proposal before building an encyclopedia no one requested.

What should a pitch deck establish for a first decision?

A deck may be enough for a first decision. It gives the premise, the particular viewing experience, the people whose conflict makes episodes possible, and a clear sense of where the series goes. Its discipline is selection. It can add one later-episode example to show the series remembers what it has done. It does not need to settle every exception to a world rule or every turn in a future relationship, and it should not hold the reader at the door until page 26.

What makes development depth useful rather than just longer?

It earns space by explaining a difficulty the deck has revealed. It adds relationships between desire, rule, blind spot, and consequence, so a later episode becomes difficult for a specific reason. In the Loan Desk example, June's rule, Sal's counter-rule, and the generator's later return let writers test whether a complication belongs to a season arc. It can also leave real design choices unresolved. Facts that merely sound substantial, like childhood history or a tattoo, may become useful in a scene but do not show how the series generates episodes.

What belongs in a production continuity reference?

Once a show is working with a room, directors, designers, or other teams, a reference document helps people avoid contradicting what has been established: character facts, previous events, geography, terminology, timelines, and rules the production has agreed to honor. It should not quietly upgrade every exploratory note to canon. It needs the settled version, not an attractive discarded one, and it should distinguish established facts from things still being debated. An operational format bible is another thing again.

Further reading

• Show How Your TV Ensemble Generates Stories — Read this when the development pages need more than character adjectives and you want each central relationship described as machinery that keeps producing episodes.
• The Deck, Pilot, and Bible Describe Different Shows. Reconcile the Package — Use this when a deck, pilot and bible each look fine alone but disagree about who carries the series; it separates gaps from real conflicts.