Explain the Whole Competition Season, Not Just One Round

You can already describe a round. The task, the rule, the person who leaves. What the pitch usually can't yet answer is what that round did to the season. Six interesting tasks in a row are not a season until something carries between them, and nothing carries until you've decided what the last stage is for.

Two questions organize everything else. What carries from one round to the next — a score, an advantage, the right to keep playing, or nothing at all. And what ends the season — a final comparison, an accumulated total, or something else entirely. Settle those two and the middle of the season tends to fall into place on its own.

What follows uses a fictional format, sketched here as a proposed architecture and nothing more. It is not an approved rulebook, and it contains no cast, no results, and no rules commitments.

Choose what the final result is meant to decide

Start at the end and work backwards. Does this season produce one winner from a last head-to-head? A ranking from play across many rounds? A winner who survives one final test after a long tally that only earned them the right to take it?

Here is the proposed map. Six participants enter. One leaves after each of the first three rounds. A return stage then brings back one of the three who left, producing four semifinalists. Two advance from the semifinal to the final, and the final determines the winner. Round scores do not carry forward. Eligibility does.

Read that end condition carefully, because it tells you what every earlier stage is for. If a single final decides the winner, then rounds one through three are a selection mechanism: they reduce six to three. The return stage lifts that back to four. The semifinal cuts to two. The final decides. Nobody wins anything meaningful in round two, because the design doesn't let round two pay out — it only removes.

This is the point where field sizes stop being arbitrary. If you want a four-person semifinal but only three people survived the earlier rounds, something has to add a fourth, and that something is your return stage. If you want a two-person final, the stage before it has to cut exactly two. Working backwards from the finish is how you find that out before you've built three rounds that don't fit together.

A sequence of interesting tasks, arranged in ascending order of difficulty, explains none of this. It doesn't say who remains eligible at each stage, and it doesn't explain why this finale belongs to this season rather than to any other six people doing anything.

Compare accumulation with elimination

Take one round and ask what it changes.

Under elimination, a round changes who is present. Five people remain where six stood. The person who left is unavailable for everything downstream: later tasks, later partnerships, later payoffs. That is a real structural cost, and it's the reason a comeback stage is even a coherent idea here. The absence you created is the thing the return stage repairs.

Under accumulation, a round changes standing. The field stays at six. Nobody goes anywhere. The season's shape becomes a curve rather than a shrinking cast list, and a bad round is a setback rather than an ending.

The trade-off is specific, not atmospheric. Elimination gives every round a departure as its consequence, and it narrows the people available for whatever the later stages want to do with relationships — rivalries, alliances, rematches. Accumulation keeps everyone available the whole way, and pulls its tension out of position instead: who is close, who needs a big round, who is mathematically out of reach. Neither route is inherently more dramatic. Elimination manufactures stakes each time; accumulation manufactures a race.

One consequence is easy to miss. Accumulation usually defers elimination rather than avoiding it. If you keep six people on points through three rounds and still want a two-person final, some stage has to reduce six to two. Points typically decide when that cut happens rather than whether it does. The only way to skip the cut entirely is to end the season on a ranking with no finale at all — highest total after the last round wins, and the last round is simply the last round.

Where points go matters as much as whether they exist. They can persist across every stage, reset at a stage boundary, or change function — accumulating through the qualifying rounds, then clearing so the final is a fresh contest. That third version is worth stating out loud in a pitch, because it means everything before the final bought admission and nothing else. A reader who assumes the leader carries an advantage into the finale will misread the whole season.

The fictional map above sits at the far end of that spectrum: there are no points at all. Rounds carry eligibility and nothing more. Notice what that does to the return stage. Because nobody accumulated anything, a returning participant arrives level with everyone. Try to bolt a comeback onto a pure points season and you'd find there's nothing to come back from — the device only means something when leaving was the consequence.

Trace one ordinary participant path

Follow one person all the way through. Call her A. She is not a character; she's a placeholder for anyone who simply never gets cut.

Look at the carried column. It never changes. A survives three rounds and has nothing to cash in for it. Under these rules, surviving round one and surviving round three leave her in exactly the same position, which is: still here.

That isn't a flaw, but it is a design consequence the pitch has to state, because a reader will assume momentum unless told otherwise. "She's carried her score this far" is a sentence your format does not support, and if the audience invents it, they will misjudge every stage that follows.

There's a useful test buried in that table. If you can't describe what a participant carries in a single line, the season probably isn't clear yet. Complicated carrying is fine; unnameable carrying is not.

Notice also that field size and carried state move independently. Between entry and the semifinal, A's situation never changes while the field around her drops from six to four. That's the whole trick of elimination architecture — the story is happening to the field, not to any one person's tally. Fix the arithmetic in a table like this before you draw a polished season graphic, because a diagram will hide a miscount that a table makes obvious.

Add the exceptional path that changes the map

Now follow D, who leaves after round two. D competed in rounds one and two, sat out round three entirely, and returns at the return stage as one of four semifinalists.

What D carries is the same as everyone else: eligibility. D does not return with points, because no points exist in this version. What D knows is different — firsthand experience of two rounds and a spectator's view of the third. What survives the departure is eligibility, plus whatever the format says about relationships formed before the exit, and that last part is genuinely unspecified here. A partnership made in round one, with one member gone for a round and then back: does it still hold? The map doesn't say. That's a question to answer, not a gap to paper over in a diagram.

Then the field changes. Before the return stage, three people are active and three are outside. After it, four are active and two are outside. If your season graphic keeps three in the out column and adds a fourth active participant, you have silently grown the cast to seven, and your semifinal no longer adds up.

D's path has another feature worth naming. D departs at the end of round two, and if D is eliminated again later, that is a second departure charged to the same person. A cast chart with one exit date per person will misrepresent that second exit, and anyone reading the chart will come away with the wrong participant count.

As written, the stated map permits D to reach the final and win it. Nothing in the stated rules distinguishes D's semifinal status from anyone else's. Whether that is intended is something the pitch should answer deliberately rather than discover in the edit. If a returning participant cannot win, that exclusion belongs in the return rule itself; if they can, say so plainly, because the audience will ask within about ninety seconds.

The same goes for the exceptions this map hasn't designed yet. A tie in an elimination round: does one person leave or two? Two shifts every field size downstream. A withdrawal in round two: does the withdrawal count as that round's departure, or does the round still remove someone? If it counts, the return slot may not exist yet. A newcomer arriving mid-season: does the field go back up, and does a newcomer compete for the return slot? A tie at the return stage: how is one of three chosen?

These should appear in the pitch as open questions, not as improvised legal-sounding clauses. Drafting "in the event of a tie, the participant with the lower cumulative index is eliminated" invents an authority the proposal doesn't have, and it hides a decision that a qualified format and production team should actually make.

Compress the logic into a usable pitch account

Here is the map in its smallest honest form.

entry          6 active | 0 outside
after round 1  5 active | 1 outside
after round 2  4 active | 2 outside
after round 3  3 active | 3 outside
return stage   4 active | 2 outside
semifinal      2 active | 4 outside
final          1 winner | 5 outside

Read the outside column as who is out right now, not as a running tally of eliminations. The season contains six departure events either way. They involve five distinct people when the returning participant is eliminated a second time, and six when the returner goes on to win, since that branch charges the returner only one departure, at round two. Getting that column wrong in either direction is the most common way a season graphic lies.

The paragraph that goes with it:

Six competitors enter. Each of the first three rounds removes one. A return stage brings back one of the three who left, giving four semifinalists. The semifinal cuts to two, and the final determines the winner. Round scores do not carry forward; eligibility does. The architecture is proposed. Adjudication, eligibility, welfare, casting, and production review sit with the format team.

That's the whole season in five sentences, and it holds both the ordinary route and the exceptional one without making the reader walk every branch. What it still owes a reader: whether the returning participant can win, and what happens on a tie.

One question deliberately stays outside this piece. Because scores don't carry, a returning participant reaches the semifinal on equal footing with someone who survived three rounds. Whether that's fair, or whether it makes the first three rounds feel like bookkeeping, is a question about what the rules reward — and that comparison deserves its own treatment, after the state changes are clear enough to argue about.

So the season map ends where it started: with what carries and what concludes. Six enter, three leave, one comes back, four become two, and the final decides. Keep the ordinary path visible in that account — the person who is simply present from start to finish is the reader's baseline — and let the exceptions sit beside it as the questions they currently are. A tangle of hypothetical ties and withdrawals shouldn't be allowed to bury a season whose basic shape is, at last, easy to follow.

Frequently asked questions

What two questions should a season pitch answer before describing individual rounds?

What carries from one round to the next — a score, an advantage, the right to keep playing, or nothing at all — and what ends the season, whether a final comparison, an accumulated total, or something else. Settling those two tends to make the middle of the season fall into place.

In the proposed six-person map, what actually carries from round to round?

Eligibility only. Round scores do not carry forward. A contestant can survive rounds one through three and have nothing to cash in for it beyond still being present, which the pitch must state because readers otherwise assume momentum.

Why does the return stage fit this elimination-based map?

The first three rounds remove one person each, reducing six to three. The return stage brings one of those three back to produce four semifinalists. In a pure points season, there would be nothing to come back from, because leaving was not the consequence.

What does the outside column in a season graphic commonly misstate?

It should show who is out right now, not a running tally of eliminations. The season contains six departure events; they involve five distinct people if the returning participant is eliminated a second time, or six if the returner wins, since that branch charges the returner only one departure at round two. Keeping three out and adding a fourth active participant silently grows the cast to seven.

What remains unresolved in the proposed season map?

Whether a returning participant can win, and what happens on a tie in an elimination round, a withdrawal, a newcomer arriving mid-season, or a tie at the return stage. These should appear as open questions rather than improvised legal-sounding clauses.

Further reading

• Run a Small Tabletop Trial of a TV Format Before Filming a Pilot — If your season map leaves ties, withdrawals or returner eligibility as open questions, this describes how to settle one uncertainty with a cheap tabletop run before committing production.