Adapt the Licensed Format or Develop a Different Show? Make the Creative Comparison Explicit

At some point in a local adaptation, the team loses the ability to explain itself. The deck still carries the licensed name. The conversations with the owner are still technically live. But when somebody asks what the format is doing for this show — which decision it settles, which problem it removes, why the pitch is stronger with it than without it — the answers turn atmospheric. The title is recognizable. The shape is familiar. It would be easier to place with a known brand attached.

The last of those may well be true. It is also not a creative comparison. And it is arrived at so gradually that nobody notices the moment it replaced one.

Two arguments usually appear at this stage, and both are made badly. The first says: we have changed so much that we are paying for nothing, so let us develop our own show. The second says: we have changed so much that it is practically ours, so let us keep the name and stop worrying. The second is a rights question disguised as a creative one, and it will be dealt with separately below. The first is a creative claim that has not yet been tested, because "we have changed a lot" is not the same statement as "the package contributes little," and the two can point in opposite directions.

The comparison worth doing is narrower and more laborious than either argument. It asks what the licensed package contributes to the show you actually intend to make, what a genuinely separate show would have to invent for itself, and who has to approve the next round of decisions on each side. What follows is a method for producing two bounded proposals that owners and commissioners can evaluate — not a verdict about your rights, and not a claim about what any particular license contains.

That last limit is real. No owner-authorized package, production bible, license or cost plan was inspected for this piece, and no deal terms were reviewed. The worked comparison further down is invented on purpose, and flagged where it appears. The method is the deliverable; the legal questions stay with qualified review, where they belong.

Resemblance and dependence are different axes

The confusion that produces both bad arguments is a single conflation. Teams treat how much the local show resembles the format as a proxy for how much it depends on it. These are unrelated measurements, and they can move in opposite directions.

A show can look almost nothing like its source and depend on it heavily. Suppose every on-screen element has been localized — the set, the host, the casting, the runtime, the regional archive — while the episode architecture, the way an episode is cut so that the audience learns a rule at the same moment a participant does, and a consultancy arrangement that gets the first block shot in nine days all came from the package. The visual resemblance is low. The dependence is high, and it sits in places a pitch deck never shows.

A show can also resemble its source closely and depend on it barely at all. If the team watched the episodes, reverse-engineered the rules, rebuilt the protocols, and now believes the remaining overlap is mostly surface, then the package may be contributing a name and an audience expectation and not much else. That is a genuine possibility. It is also, note, a completely separate question from whether the resulting show is free to make. Resemblance is not the test for anything, in either direction.

So the deck's resemblance count tells you nothing. What tells you something is an inventory of what the team would have to answer alone if the package's documents disappeared and nobody from the owner's side answered email for a month. Each question your team could already answer is not a point of dependence. Each one that would stall production is.

That exercise is editorial, not legal. It produces a list of the decisions the package is actually settling, which is what a comparison needs. Do not let it become a substitute for reading the license; the license tells you what you may do, while this exercise tells you what you are relying on. They are different documents with different jobs.

The package contributes a list, not an atmosphere

Before either route can be argued, name what the show is trying to preserve. Not the genre. The specific thing: what the audience should feel by the end of an episode, what relationship participants have with each other, what recurring activity organizes the hour. Write those down as aims, then mark each one's origin. Some came from the format. Some came from your own viewing of it, which is not the same as the format. Some came from your commissioning conversation, your audience research, your regional archive, your scheduling reality.

Two shows can share an interest in how people combine local knowledge and share nothing else at all. Agreement at that level of abstraction is nearly free — everyone competes, everyone negotiates, everyone has a time limit — and it tells you nothing about whether two shows share a mechanism. Push each aim down to the level where a specific decision changes: who chooses, whether the choice is visible, what happens when two participants want different things, what the audience is waiting for. That is the level at which formats either overlap or don't.

Then inventory the package itself, in categories, because these arrive together in a deal but constrain you differently:

The engine. The mechanism that produces the episode's tension and its resolution. This is the part people mean when they say "the format," and it is usually the smallest category.

Episode architecture and rules. What happens in what order, how scoring or elimination works, how an episode ends, how a season accumulates.

Production knowledge. How the thing is actually shot: how long a segment can run before an audience loses the thread, how to protect a piece of information on set, what the edit must show and when. FRAPA, the Format Recognition and Protection Association, describes detailed production information as part of transferring a format to another producer (services page, checked 8 September 2025). That page is a pointer, not an inventory: it confirms that production knowledge is a thing formats transfer, and it suggests what to ask for under authorized access. It is not a bible, a license or a boundary, and it does not tell you what any arrangement contains.

Brand and audience expectation. A real contribution, and a different kind from a solved production problem. It is also the one most easily mistaken for the whole package.

Owner services. Consultancy, training, review of cuts, casting support — dependencies with a schedule and an opinion attached, which is worth counting as more than a line item.

Permission and obligation. Territory, term, approvals, spin-off rights, whatever the agreement actually says. This category is where the creative comparison stops and rights review begins.

Sort your inventory by which of these the package genuinely supplies, and by which questions it has already answered rather than answered once. A format solved a problem in its own market, with its own audience expectations and its own budget. Some of that travels. Some of it has to be re-derived locally, and a protocol that looks like knowledge may turn out to be a protocol for a show you are not making.

One further possibility deserves a straight answer: the package's contribution can be negative. If your local changes have removed the element that made the supplied engine work, the package may now be contributing architecture and a name while its engine sits unused. That is not automatically a reason to walk away — architecture and a name have value — but it has to be said out loud rather than averaged into a general sense of usefulness.

An alternative that exists as a sentence cannot be compared

This is where most comparisons quietly cheat. The adapted version is a developed proposal with a set, a host, a casting plan and a shoot schedule. The "original show" is a paragraph. The paragraph wins on charm and loses on credibility, and whichever way the team's mood is leaning, the mismatch does the arguing.

Give the alternative the same resolution. A premise. A participant choice with real alternatives and a real cost — what does a participant decide, and what do they give up by deciding it? A progression: how is episode six different from episode one, and what changes for the people in it? A decision rule for when participants disagree, since a show built on negotiation that has no way to conclude is not yet a show. A resolution that satisfies: what exists at the end, and why does the audience accept it as an ending?

Then record, in writing, next to the alternative, the development and testing questions it has not answered. Those questions are the alternative's cost, and they are the reason the comparison has to happen before the pitch rather than after.

Two things this process is not. It is not a method for taking the licensed show, renaming its stages and calling the result original — decoration changes do not change a beat sequence, and a beat sequence is what a rights review would look at. And it is not a test for legal distinctness. Renaming everything and asking whether the structure still matches is a useful way to understand your own show. It is not a clearance procedure, and no amount of change you can describe on a slide establishes independence.

The same work, at the same resolution, on both sides

Now put the two proposals beside the same editorial aim and write down, for each: material you can actually use, work your team must do that nobody else will, decisions that belong to somebody else, specialist input you have to buy or borrow, and what needs testing before anyone commits.

Two asymmetries will try to corrupt the comparison while you write it. The first: a licensed route's costs are visible — fees, approvals, constraints — while its savings are invisible, because you never see the eleven mistakes it stops you from making. The alternative is the reverse. Its benefit is visible and its costs are not, because development is a list of discoveries you have not made yet. Correct for this deliberately, or the comparison will simply reproduce whichever version is more developed.

The second: work already done is not a contribution from the package. Hours your team spent localizing are your hours. If they are entered on the adaptation side of the ledger, they will make the licensed route look more valuable than it is, and they will also make abandonment feel like loss in a way that has nothing to do with the show.

And resist both stock assumptions. Adaptation is not automatically easier: a package can add approval latency, editorial constraints you then spend effort working around, and a training obligation with its own schedule. Development is not automatically cheaper: you become the people who have to find out what does not work, and you find out on your own budget. Neither route is the cautious one.

A worked comparison: two invented shows

Everything in this section is stipulated fiction, written to show the shape of the comparison. No real format, license, owner or production is described, and nothing here establishes that any show would be legally distinct or available.

Both invented routes share one broad interest: how people combine local knowledge.

Route A, the adaptation. The proposed show uses a licensed package whose engine runs on hidden information. Each episode, one participant privately selects three items from a curated archive. The selection stays hidden. At a staged reveal, the other participants see only the items and have to reconstruct why those three were chosen; a host adjudicates, accurate reconstruction earns points, and the strongest accumulator across the season continues. The package is stipulated to include the archive-curation protocol (how a set of holdings is assembled so three items can support more than one plausible story), an adjudication sheet, edit guidance for cutting the reveal so the audience learns the item set at the same moment the second participant does, and consultancy days during the first shooting block. The local team has already changed the archive to a regional oral-history collection, cast a local host, shortened the episode — and replaced the staged reveal with a discussion in which everybody already knows the selection.

Route B, the alternative. Four participants each episode must add one item to a public collection. They bring candidates, negotiate, and have to agree on one; the item is documented, prepared and installed, and the season ends with the assembled exhibition and the group's recorded reasons for why these items belong together. The stipulated decision rule: consensus for the first three episodes, and after a stated point in any episode a rotating chair decides, with the chair's reasoning recorded on camera. The tension is not secrecy but permanence — the thing they choose goes on public display, and they will be asked to defend it. The satisfaction at the end is an artifact that exists in the world rather than a correct answer.

Now the comparison, item by item.

The stipulated reading is uncomfortable for both sides. Route A's engine is inference under hidden information; the payoff depends on the selection being hidden and the reveal functioning as a test. The local version removed the test. What remains from the package is the curation protocol, part of the consultancy, some architecture and the name — real, but noticeably less than the deck implies. Meanwhile Route B has a genuinely different engine, an unfamiliar cost profile, and an additional third-party dependency beyond the owner approvals Route A already carries: an institution that has to agree to display what the participants choose. Neither side is simply the easier one, and the ledger above is the point of the exercise rather than a tiebreaker.

Two things this example does not do. It does not tell you whether the modified engine is permitted under any license; that is a scope question for the owner's authorized materials and qualified advice. And it does not tell you whether Route B is distinct from the package it was invented alongside. Structural judgments of that kind belong to rights review, not to a creative comparison, however carefully the comparison is done.

The creative decision, and the questions it does not answer

What comes out of all this is not a verdict about the format. It is a paragraph: which route your team can bring to a pitchable state with the time and resources it has, which unanswered question would most change that judgment, and what that question would take to answer. Something like — the adaptation continues only if the reconstruction reveal is restored, because the package's remaining contribution is otherwise architecture we could design ourselves, and we can test the reveal in a two-day pilot; the alternative proceeds in parallel to an episode-level treatment, with the institution's preliminary position confirmed first.

Then name what could change the decision, because a decision that cannot say what would move it is a preference. An owner's authorized description of what the package actually supplies. An episode-level draft of the alternative rather than a paragraph. A commissioning signal on either engine. An answer from the owner on whether your modified engine sits inside the licensed scope. None of these is available from the inside of a team meeting, and each of them is cheap compared to a wrong development slate.

If neither route is defined well enough to choose between them, that is a legitimate outcome, and it should be written down as one: the next step is to develop the alternative to the resolution of the adaptation before deciding. Naming that work is more useful than forcing a verdict the material cannot support.

Three questions stay open regardless of which way the creative argument lands. Does the license permit the engine as you now intend to run it? Is the alternative distinct from the package you have been working alongside? And what obligations does the adaptation route carry if you proceed? Those are rights questions, with their own documents, their own reviewers, and their own answers. A creative rationale that is internally persuasive does not answer any of them, and should not be asked to.

Adaptation is not the safe route and development is not the brave one. The question underneath both is who has already answered the next hundred small production decisions, who has to approve them, and whether your team can live with the answers. Resemblance never tells you that. An inventory does.

Frequently asked questions

Why is resemblance a bad measure of how much the licensed package contributes?

Resemblance and dependence are different axes. A show can look localized and still depend heavily on episode architecture, edit guidance or consultancy, and a show can look similar while the team has rebuilt the rules and relies on the package mainly for a name and audience expectation. The useful exercise is inventorying what would stall production if the package's documents and owner answers disappeared.

What categories should an inventory of the package cover?

The engine; episode architecture and rules; production knowledge; brand and audience expectation; owner services; and permission and obligation. These arrive together but constrain the team differently. Sort by what the package genuinely supplies and by which questions it has already answered, not by how much the deck resembles the source.

How can an alternative original show be compared fairly against the adaptation?

Give it the same resolution: a premise, a participant choice with real alternatives and a real cost, a progression, a decision rule for disagreement, and a satisfying resolution. Record the development and testing questions it has not answered. Also correct for visible versus invisible costs and do not count hours the team already spent localizing as a contribution from the package.

In the invented comparison, what does the adaptation lose and what does the alternative add?

Route A's engine runs on hidden information and inference at a reveal; the local version replaced the staged reveal with a discussion where everyone already knows the selection, so the package's remaining contribution is curation protocol, part of consultancy, architecture and the name. Route B has a different engine, permanence as tension, and a third-party institution that must agree to display the chosen items. Neither route is simply easier.

Which questions does the creative comparison not answer?

Whether the license permits the engine as now intended, whether the alternative is distinct from the package, and what obligations the adaptation route carries if the team proceeds. Those are rights questions with their own documents and reviewers. The creative output is instead a paragraph about which route can be brought to a pitchable state, what unanswered question would most change that judgment, and what answering it would take.

Further reading

• Adapt a TV Format Locally Without Just Changing the Place Names — Read when resemblance keeps masquerading as dependence; it turns each aim into the specific on-screen action the format must still allow after local adaptation.
• What Did Your Unscripted Format Test Actually Prove? — Read before treating a pilot or test round as proof; it separates comprehension, unaided operation, repeatability and appeal so your comparison does not overclaim what was shown.
• A Local Format Adaptation Improves a Rule. Change the Core Bible—or Keep a Local Version? — Read when a local rule change might justify keeping the licence; it separates observation from claims of success and traces what else must travel with the change.