Explain What Your TV Format Does Differently—not Just What It Looks Like
Explain What Your TV Format Does Differently—not Just What It Looks Like
You know the sentence. It arrives in the second meeting, usually from someone well-disposed: So it's [familiar show] meets [familiar show], but in a lighthouse. Everyone nods. Nothing has been said about your show.
The sentence isn't wrong, exactly. It's just doing a different job than the one you need. It places your format in a family. It doesn't tell anyone what a contestant can know, choose, risk, or cause that they couldn't in the version they already have in mind. And that second thing is the entire argument.
The way to make it is to compare the two formats at the level of play rather than at the level of premise, and then to show one decision diverging. Not a vibe. A rule, and what follows from it.
One boundary before anything else, because it will otherwise get blurred by the third person who reads this: comparing mechanisms is a creative argument. It is not an originality opinion, an ownership claim, or a view on infringement. Those are different questions, answered by different people with different training. What follows is about making your distinction legible enough that a competent person can evaluate it.
Define the comparison at the level of play
Start by naming the nearest existing format, and then name where its rules actually live. This second step is where most pitches quietly cheat. The reference format's rules are not what you remember from a finale you watched in 2019. An undocumented recollection of one famous episode is not a rule description — it's a story about a night. Rule changes between seasons, rule changes between territories, and rules that exist only in a format bible all make "everyone knows how that show works" a bad foundation for a comparison you intend to defend.
Go to the documents. Official rule pages maintained by the rights holder, broadcaster press packs, published format descriptions, and — where you can get one — the format bible itself. FRAPA's services page describes a Format Bible Generator among its resources, which is a reasonable place to learn the vocabulary of documented format elements. I should be plain about what that is: a description of a service, not the underlying template, and not something I used. The same organisation's format analysis route is a comparison path worth knowing about; I haven't obtained such a report or paid for any service, and nothing here rests on one. Treat all of it as a research route, not as evidence about your show.
Then split the rule set into five columns, and keep them separate:
- Entry conditions. Who gets in, how, and what state they arrive in.
- Choices. What a participant actually decides, and when.
- Information. What each person knows at the moment of deciding, and who else knows it.
- Consequences. What happens after a choice, immediately and later.
- Episode progression. How one outcome produces the next opportunity, and how an episode ends.
Two formats can share a premise and diverge in only one of those columns. That's fine. One real divergence is worth more than five decorative ones.
To inspect the mechanism without waving anyone's actual show around, the rest of this article uses two invented rule sets. They are hypothetical, they belong to nobody, and no comparison to a real programme is intended or implied. Call them Retry-Only and Retry-or-Peek.
Both run the same invented premise, and in the beginning they are the same document.
Twelve sealed envelopes sit on a board, each labelled with a task category and a coin value of 2 or 3. Four contestants — Ada, Marcus, Priya and Tomas — take turns in that order for three rounds. On your turn you take any remaining envelope, read its label, and choose: attempt the task inside, or pass. The task stays hidden until you attempt it. Pass and you bank 1 coin. Attempt and succeed, you bank the envelope's value. Attempt and fail, you bank nothing. Either way the envelope leaves the board. Highest bank after turn twelve wins the episode. Every contestant begins with one Retry token, and unused tokens carry forward.
Here is the only difference. In Retry-Only, that token may be spent one way: after a failed attempt, to attempt the same task again, inside the same turn, without costing you a later turn. In Retry-or-Peek, the same single token may be spent that way or before you decide, to see the specific task in the envelope. The peek is private: you and the audience see it, the other three contestants do not. Spend it on a peek and the recovery use is gone. Not saved — gone.
That's the whole divergence. No set, no host, no prize, no chapel conversion.
Give both systems the same starting problem
Now hold everything still except the rule.
It's turn seven. Banked so far: Ada 5, Marcus 4, Priya 3, Tomas 2. Six envelopes remain and six turns remain, so the board is exactly as long as the game. Priya is on, she trails Ada by two, and she has two turns left including this one. Same contestants, same standings, same board, same remaining turns, same token in her hand, in both systems.
She takes the Rope envelope worth 3. Rope tasks are her middling category, and she knows the range: in this format a rope envelope can hold something tidy or something genuinely fiddly. Everything she can see — category, value, her own bank, the standings — is identical across the two systems. The rule is the only variable.
Here is where the paths split, and it's worth pausing on what kind of split it is. In Retry-Only, Priya's token has exactly one purpose: to turn a failure into a second chance. In Retry-or-Peek, she has a choice about what the token is for. Both systems let her attempt blind and keep the token in reserve. Only one of them lets her buy certainty — and pay for it out of the same pocket she'd need for recovery.
So the two available lines are: decide with limited information and keep the safety net, or decide with better information and lose it. Not a better line and a worse line. A trade.
Follow the different choice into the episode
To see which way that trade points, you need one more fact, and it lives in the task design rather than the rule. It's the question of how Rope-3 fails. Two plausible task pools give opposite answers. Same envelope, same value, same everything else — only the difficulty spread is different, and I'm flagging that change because it's the lesson rather than a slip.
Pool one: failures are near-misses. The Rope-3 envelope is equally likely to hold either of two tasks. One is a bowline Priya lands about nine times in ten. The other is a splice she lands about one time in four. She can't tell which is in there without peeking.
Under Retry-Only, she attempts, and the token sits behind her. If the bowline is in the envelope she banks 3 nine times in ten, and touches the token only in the tenth. If the splice is in there, she fails more often than not — and the token is worth something real, because a second go at a one-in-four task is still worth a shot. Run the two branches and average them and the attempt is worth roughly 2.14 coins.
Under Retry-or-Peek, she can peek. Bowline: she attempts, banks 3 about nine times in ten. Splice: attempting is worth three-quarters of a coin, and passing is worth a guaranteed one, so she passes. Average the branches and the peek is worth about 1.85.
The peek loses. By around three-tenths of a coin, in this state, because the recovery option she gave up was worth more than the information she bought. A splice is a task she might have managed on a second attempt, and she sold that chance for the privilege of finding out.
Pool two: failures are decisive. Same envelope, same value, same pass rule. But now the two tasks are a bowline she never misses and a splice she never lands.
Under Retry-Only she attempts blind. Bowline: 3, token untouched. Splice: fail, retry, fail — and here's the part that matters — she already knows, after failing, that the splice is the thing in the envelope. The retry has nothing to rescue. Her attempt is worth 1.5.
Under Retry-or-Peek she peeks. Bowline: 3. Splice: pass, 1. Average 2.0. The peek wins, by half a coin.
The difference between the two pools is not the value and not the standings. It's whether failure carries information that the recovery option can act on. When your failures are near-misses, a retry is one of the most valuable things you can hold, and a peek is expensive. When your failures are hopeless, a retry is nearly worthless — a second attempt at something you cannot do is still nothing — and a peek is cheap.
Put these two side by side and you get a design rule that survives contact with an argument: the token's two uses trade off across the difficulty spectrum, and one eats the other. Recovery peaks when tasks are coin-flips. Information peaks when tasks are decisive. They draw on the same coin, so a contestant who needs the first can't afford the second, and vice versa.
Read that back onto the format's identity and something uncomfortable surfaces. Retry-or-Peek is only different from Retry-Only when the task pool makes the peek a live choice. Load the show with coin-flip tasks and contestants will rationally never peek, the distinctive rule never fires, and you're left pitching a format whose headline mechanic is ornament. The rule change and the task design are one decision, not two. If the peek is the thing you want to sell, the difficulty spread is part of the mechanism, not the set dressing.
This trace holds the turn fixed to isolate the rule. It doesn't solve the episode. Tokens carry forward, other contestants take envelopes off the board, and Priya's third turn changes what either version is worth. What the trace shows is what each rule set makes available and what it makes cheap — not what a contestant will do. That's the honest scope of the claim, and it's also the useful part.
Name what the difference costs
Every mechanism-level distinction is paid for somewhere. Retry-or-Peek buys a second axis of strategy and charges for it in at least four places.
Explanation. Retry-Only is one sentence. Retry-or-Peek is one sentence plus a carve-out about exclusivity, plus a clause about privacy, plus a reason the audience should care that one contestant knows something three others don't. Pitches get less legible before they get more interesting, and the carve-out is exactly the part a listener will miss.
Pacing. The peek has to be shown, or its value is invisible — and a peek that resolves into a pass is a segment that ends in nothing happening. That's a real beat in the cut, bought at the price of a possible anticlimax.
Production. The peek creates an asymmetry between the audience and the three contestants who aren't in it. That has to be staged and enforced. If the peek ever leaks to the room, you're running a different game than the one you pitched.
Simplicity. The audience has to hold one object with two functions in mind across an episode. Formats that ask that of a viewer usually earn it back through repetition; a rule that fires twice a series doesn't.
Now the specimen you should never write, which is the failure mode this whole method exists to catch. Suppose the pitch says: same board, same decisions, same token — but the studio is a converted chapel and the host is a former national champion. Room and host changed. Choices, information, consequences and episode progression untouched. That's not a new engine. It's the same engine in a different building, and anyone who has seen the reference format will feel it immediately, no matter how good the chapel looks.
The defensible version is shorter and duller on the page. It names a rule and a consequence:
Contestants hold one token that can buy either a peek or a replay. Certainty and recovery come out of the same pocket, so a player who peeks and then fails has already spent the only thing that would have saved them.
That statement is checkable. Someone can disagree with it by pointing at a rule. It doesn't say the format is original, valuable, or sellable. It says what the mechanism does, and it lets the listener evaluate whether that's interesting.
What you can defend, and what you can't
Put the two systems back-to-back and the difference reduces to a sentence you can hold: in one format the retry is a safety net, and in the other the retry is a budget.
Everything above that is consequence. The peek is cheap when failures are decisive and expensive when they are near-misses. A pool of coin-flip tasks quietly disables the format's own headline rule. The rule costs you a legible pitch, a segment that can resolve into nothing, and a privacy obligation in the studio.
That's the shape of a mechanism comparison worth making. For each part of it, you should be able to point at a rule and then at what follows from it — not at a feeling about the show, and not at the room it's shot in.
And keep the last step separate. Whether your mechanism differs from another format is a creative question. Whether that difference matters legally, commercially, or to an audience is three other questions, none of which this comparison answers. It gives you something to hand to the people who do answer them: a clear claim about what your participants can know, choose, risk and cause, in terms that a rule document can support or contradict.
Which is more than the lighthouse ever did.
Frequently asked questions
Why is a comparison like '[familiar show] meets [familiar show], but in a lighthouse' insufficient?
It places a format in a family, but it does not explain what a contestant can know, choose, risk or cause that they could not in the version already in the listener's mind. A useful comparison works at the level of play and shows one decision diverging, with a rule and what follows from it.
What five rule columns should a format comparison keep separate?
Entry conditions, choices, information, consequences, and episode progression. Two formats can share a premise and diverge in only one column; one real divergence is worth more than several decorative ones.
In the invented Retry-Only and Retry-or-Peek systems, what is the only rule difference?
In Retry-Only, the single Retry token may be spent only after a failed attempt to try the same task again in the same turn. In Retry-or-Peek, the same token may be spent that way or before deciding, to see the specific hidden task privately; spending it on a peek removes the recovery use.
How does task difficulty change whether the peek is a live choice?
When failures are near-misses, a retry is valuable and a peek is expensive: in the example, the blind attempt is worth about 2.14 coins and the peek about 1.85. When failures are decisive, a retry is nearly worthless and the peek is cheap: about 1.5 versus 2.0. If a format is loaded with coin-flip tasks, contestants will rationally never peek and the headline mechanic becomes ornamental.
What costs does the peek mechanic impose beyond the rule sentence?
It costs explanation (an exclusivity carve-out, a privacy clause, and a reason the audience should care), pacing (the peek must be shown and may resolve into a pass that ends in nothing happening), production (the asymmetry between the audience and three contestants must be staged and enforced), and simplicity (the audience must track one object with two functions). A rule that fires only twice a series may not earn that back.