What Is a TV Format Bible—and How Is It Different From a Pitch Deck?
What Is a TV Format Bible—and How Is It Different From a Pitch Deck?
A pitch deck exists so that someone can decide whether to pursue a show. A format bible exists so that a team — often a different team, in a different territory, on a different budget — can make the show work again without the original producers in the room.
Both documents describe the same show, which is why they get mixed up. What separates them is the recipient's job. A document is only as good as the task it lets someone finish: take a meeting, commission a pilot, budget a series, or run a recurring segment with three guests, a host, and a playback operator who has never seen the show before.
Page count won't tell you which one you have. A great many documents called bibles are simply longer pitches.
Start with what the recipient has to do
Think about two different readers.
The first is evaluating. A commissioner, an acquisitions executive, a co-production partner looking at a format that has already run somewhere else. Their questions are about the proposition: What is this show? Why would an audience choose it? What does it cost roughly? Where does it sit in a schedule? Does the engine survive a second series, or does it spend everything in the first? They may need to know how the thing looks and feels, and they may need enough of the mechanism to believe it repeats. They do not need to know how many candidate sound recordings the production office gathers.
The second reader is preparing to make a version. A producer in another country, or another division of the same company, has been authorized to adapt the format and needs to understand how the show operates: what starts a segment, who is on screen, what has to be supplied, what order things happen in, what ends it, and which parts they are free to change. That reader has a schedule and a budget and a crew meeting on Monday.
Design for one of those readers and you have designed for the other badly. A ninety-page operational manual does not help an executive decide; a persuasive pitch does not help a producer build a rundown.
There is also a constraint on the first document that people forget. You can only put in what the team is authorized to share at that stage. Not every production detail belongs in an enquiry pack, and some of it belongs in a conversation that follows a signed agreement rather than an email that precedes one. That isn't paranoia — it's just knowing which document you're writing.
The same segment, described twice
Here is an invented example. Nothing below has been produced or tested; it's a construction for showing the difference between two jobs. Call the fictional unscripted format Three Sounds.
First, the pitch version — the paragraph that would sit on a slide:
Three Sounds. Three ordinary noises, recorded from a real kitchen, a stairwell, and a front door. Our guests hear each one and say out loud what they think made it. They commit to an answer before they find out. Then we show them. Almost nobody gets all three — and the moment a sound you've heard your whole life turns out to be something you've never once looked at, that's the show.
That does its job. It names a pleasure, gives a reason to watch, and hints at repeatability. It also leaves almost everything operational open, which is fine for a pitch and fatal for a handoff.
Now the same segment as a production document would describe it:
Three Sounds — segment rundown. Target: roughly five minutes of program time.
Inputs. Three finished sound recordings, three to five seconds each, selected from a pool of at least nine candidates. Each is recorded on location by the production office, and each has a paired reveal: a two-to-four-second clip or still of the source being made, shot in the location where the sound was recorded.
Roles. Host runs the segment and holds the answer sheet. Three guests, seated in a fixed order. A floor producer logs the source of every sound and confirms with each location that recording is permitted. A playback operator cues the sounds and the reveals.
Sequence. (1) Host plays Sound A once, then leaves a beat of silence. Guests discuss what might have made it, thirty to forty-five seconds. (2) Host asks each guest, in seating order, for one committed guess for Sound A; the floor producer writes each guess on a card. (3) Repeat steps 1 and 2 for Sounds B and C. (4) Reveals, in play order: A, then B, then C. Each reveal shows the source clip before cutting back to the studio for reaction. (5) Host reads the cards against the answers and closes the segment.
Endpoint. The segment ends after the reaction to Sound C's reveal.
Notice what the second passage had to name that the first never did. Who records the sounds and how many candidates get made before three are chosen. Permission at the location. The reveal as a made asset rather than a fact the host happens to know. The guess as a physical object written by a named person. A duration for the discussion. An endpoint, so the segment has a shape that can be repeated.
Notice also that it is a worse read. That's expected. It isn't trying to be persuasive; it's trying to be usable, and those two ambitions pull in different directions.
Two sentences in the pitch conceal real decisions. "Three ordinary noises" hides a selection process: someone has to define ordinary, gather more candidates than the segment needs, and reject the ones that are too easy or too obscure. "They commit to an answer before they find out" hides cards, a producer, and a moment in the rundown — and, as we'll get to, a rule that hasn't been written.
What has to stay the same, and what is furniture
A version made in another territory will change things. The question is which changes preserve the segment and which quietly replace it. To answer that, you have to say what the mechanism actually is.
For Three Sounds, the mechanism looks like this: a sound the audience has heard many times in ordinary life, which could plausibly have more than one source; discussion before any answer is given; a guess that is committed before the reveal; a reveal that shows the source. Strip out any one of those and the segment stops being the segment.
Now test two proposed adaptations.
Adaptation one: record the sounds locally instead of using the originals. Does it preserve the mechanism? It can — but only if the substitution is tested against the mechanism rather than against the tape. The invariant is a property of the sound, not the specific recording: familiar to this audience, ambiguous enough that more than one source is plausible, visible on reveal. Replace a dripping kitchen tap with something equally common in the new territory, screen a fresh pool of nine down to three, and check that the difficulty balance still holds. The last part matters, because the pitch's claim — almost nobody gets all three — rests on that balance. If the local pool is all easy, the reveal has nothing to do, and the segment's pleasure evaporates.
The variation fails when the substitute keeps its ambiguity but loses its familiarity. Swap the tap for the call of a bird that lives in one valley and the guests aren't recognizing anything; they're guessing blind. The reveal flips from I've heard that my whole life and never once looked to I could never have known that. Different pleasure, different segment, even though the rundown looks identical on paper.
Adaptation two: reveal the answers before the guests discuss them. Does it preserve the mechanism? No. The commitment is load-bearing. Show the source first and the discussion becomes description of a known object, the cards have nothing to record, and the reaction after the reveal has nothing to push against. This is not a scheduling tweak; it's a different segment wearing the same name.
So: local sourcing preserves the mechanism when the substitute passes the same screening the original did. Revealing first changes it, and changes what the audience gets. The useful test isn't "does this feel like our show" — it's "does this still produce the same thing happening on screen."
Furniture is the rest. The studio color, the card stock, the host's catchphrase, the title sequence. Protect them if the brand depends on them. Just don't confuse them with the thing that makes the segment run, and don't treat a long list of visual details as though it were an operational explanation.
"Bible" is a label, not a specification
The two documents aren't rungs on a ladder. They're different jobs, and a normal development process produces several things along the way: a pitch, sometimes a demonstration tape, development materials that show how the show would be made and how it would look, and eventually an operational document for whoever builds the authorized version. The last one is what people usually mean by a format bible.
In scripted television, "bible" commonly means something else: a document about characters, world, tone, and story direction, written for the room that will produce episodes. That is a development task, not a reproduction manual. A scripted series bible and a format bible share a word and not much else, and neither one is a season-arc document for the other.
Some companies call the pitch deck a bible. Some call the operational document a format paper, a production bible, or a know-how document. The words move between territories. So agree on the recipient's task and the level of detail it requires, rather than trusting a title — or a table of contents. Knowing a document's chapter headings are "Games," "Rounds," and "Art Department" tells you nothing about whether the beat structure of a recurring segment has actually been written down.
One practitioner account is worth reading alongside this, with limits. Justin Scroggie's 8 October 2021 piece on The Format People's site describes a revised and expanded bible template produced for FRAPA, and frames the template's purpose around transferring know-how and separating what is essential from what is negotiable. That distinction is the same one this article is drawing. The template itself is members-only and was not inspected here, so what it contains in detail is not established by the account, and nothing about its contents should be treated as a standard. It's a practitioner's description, not a specification.
Two things follow, in plain terms. More pages do not turn a pitch into usable production knowledge — a two-hundred-page bible without an operational sequence for its recurring segment is a longer pitch. And the document itself doesn't grant anything. Whether a team may produce a local version, and on what terms, is settled by the agreement between the parties, not by the table of contents. Receiving a bible is not the same thing as being authorized to reproduce a format.
The question the pitch never has to answer
Go back to that rundown. Step five says the host reads the cards against the answers and closes the segment. It doesn't say what makes a card correct.
Suppose a guest says "a door" and the answer is "a front door." Is that right? Count it as correct and the studio gets a small, cheap win, and the format's claim that almost nobody gets all three starts to wobble. Count it as wrong and the guest who named the actual mechanism feels robbed, the audience may take the guest's side, and the reveal's pleasure turns into a technicality. Either way the host is standing in a studio with three cards about to say a word, and the document hasn't told them which word.
That's the unresolved production question, and no page count answers it. In the pitch, "almost nobody gets all three" sounds fine either way; the sales paragraph never has to decide, because it isn't describing a moment where a person has to choose. The operational version is describing exactly that moment, and until it decides, it has handed the segment to whoever happens to be hosting.
This is the shape of the difference between the two documents. Not pages, not formality, not the word on the cover — decisions. The pitch decides what to promise. The bible decides what happens when the promise meets a Tuesday shoot, and how much of that another authorized team can genuinely reproduce on their own.
The right level of detail is the amount that lets your recipient finish their job. For the reader evaluating the format, that means enough of the engine to believe it runs and enough of the promise to want it. For the reader preparing the authorized version, that means the inputs, the roles, the order, the decision rules, and the endpoint — plus an honest note about the question the sales paragraph was never required to settle.
Frequently asked questions
What is the central difference between a pitch deck and a format bible?
The recipient's job. A pitch deck exists so someone can decide whether to pursue a show. A format bible exists so a team, often in a different territory or on a different budget, can make the show work again without the original producers in the room. Page count does not tell you which document you have; many documents called bibles are simply longer pitches.
What does an evaluating reader need compared with a producer preparing an authorized version?
The evaluator needs the proposition, audience appeal, rough cost, schedule fit, whether the engine survives a second series, and enough mechanism to believe it repeats. The producer preparing the authorized version needs inputs, roles, order, decision rules, endpoint, and what is free to change. A persuasive pitch does not help build a rundown, and a ninety-page operational manual does not help an executive decide.
In the Three Sounds example, what is mechanism and what is furniture?
The mechanism is a sound the audience has heard many times in ordinary life and that could plausibly have more than one source, discussion before any answer, a guess committed before the reveal, and a reveal that shows the source. Strip out any one and the segment stops being the segment. Furniture includes studio color, card stock, the host's catchphrase, and the title sequence; protect it if the brand depends on it, but do not confuse it with the mechanism.
When does local sourcing preserve a format mechanism, and when does it fail?
It can preserve the mechanism if the substitute passes the same screening: familiar to the new audience, ambiguous enough that multiple sources are plausible, visible on reveal, and still balanced in difficulty. It fails when the substitute keeps ambiguity but loses familiarity, such as a bird call from one valley; then guests are guessing blind and the reveal changes from recognition to impossibility.
What unresolved production question shows why a format bible has to decide more than a pitch?
The Three Sounds rundown says the host reads cards against answers but does not say what makes a card correct when a guest says 'a door' and the answer is 'a front door.' Counting it right lets the format's claim that almost nobody gets all three wobble; counting it wrong can make the guest feel robbed. The pitch can leave that undecided, but the operational version describes the moment a host must choose. Also, the document itself does not grant rights; permission to produce a local version is settled by the agreement, not the table of contents.