Pitch a TV Format That Puts Professionals and Amateurs in Different Roles

Most pitches built on unequal experience spend their words on the labels. A professional chef and a home cook. A concert pianist and someone who took lessons for two years. That is a casting notice. It tells the person reading your pitch who is standing on set, and nothing about what will happen between them for forty minutes.

The format lives in a smaller question underneath: what does each of them know, what does each of them control, and how do those two facts change the task the viewer follows? Answer that and the labels become legible. Skip it and you have a competent person and a novice in the same room, with the audience already told which one to expect less from.

Everything below works through one invented task. No participants have been recruited, no recordings exist, nothing has been cut or judged. That is deliberate. The design work comes first, and it is cheap; the production is neither.

Name the task before you name the roles

Write down what must be made, discovered or decided. Then break it into the abilities it actually calls on, because "professional" is a status that covers a domain and not much else.

A professional sound editor is a competent recordist, a fast judge of which take reads, and a reliable hand with levels, layering and noise treatment. That same person may be a poor interviewer, an indifferent musician, and no expert at all on what a particular neighbourhood means to the people who live in it. Professional status is not a general-purpose competence badge, and a pitch that treats it as one is really promising that the professional will be effortlessly right about everything.

"Amateur" is worse, because in most pitches it means exactly one thing: no formal training. That is a fact about a résumé, not a role. It gives a performer nothing to do and a viewer nothing to watch.

So give the person a second domain, and give it to them concretely. Not "passionate about the area." Not "brings a fresh perspective," which is a phrase that has never survived contact with a shooting day. Something you can write in one sentence and that a viewer can watch them use.

The invented example: a trained sound editor and a resident who has lived beside a working harbour for thirty years are asked to make a sixty-second sound portrait of that harbour, using recordings made there over one day. The editor knows the medium. The resident knows the place — which sounds are the harbour and which sounds merely happen there, what it sounds like at five in the morning, which noise a visitor never notices and a local could not mistake.

Each of them is a beginner in the other's domain. That symmetry is not decoration. It is the thing the format is made of.

Pick the relationship, not the adjective

Four relationships are available, and each one generates a different question for the episode. Choose on the basis of the task, not because "pro versus amateur" sounds like a format on its own.

Teaching. One role transfers an operation to the other. The episode question: can this person learn this in the time we have? That requires the operation to be genuinely learnable inside the format's window, and it requires teaching, which is a separate skill from doing. Some people can mix a record and cannot explain a fader.

Collaboration. Two kinds of knowledge combine. The episode question: can they make something neither could make alone? This works when the two knowledges are complementary rather than ranked — craft and place, technique and memory.

Exchanged constraints. One person sets limits and the other solves inside them. The episode question: can someone work well inside choices that aren't theirs? The drama is in the collision between a constraint and a solution, not in a winner.

Competition. Both attempt the same task. The episode question: can a person win under these conditions? This is the one that requires the most honesty about resources, and the next two sections explain why.

For the harbour portrait, collaboration is the relationship the task asks for: the two contributions are different in kind, not just in level. Competition is available, but only if you are willing to put the equipment on the table instead of pretending it doesn't matter.

Write the ledger: information, decisions, resources, intervention

Before you write a single line of scene description, produce the ledger. Who can see what. Who can intervene, and when. What help is allowed. Who makes the final choice. Then walk through the specific moments where one role changes what the other can do.

For the collaborative version of the portrait:

Materials. A recordist spent a day at the harbour and made the recording pool. Both participants work from it. That recordist is production help, and the pitch should say so. A format that credits a resident with "capturing the place" when someone else stood there holding the microphone is claiming an achievement that belongs to a third person — and once that becomes visible, everything else in the show looks shakier. Offscreen technical support should be visible and boring: named, credited, explained in one line.

Visibility. The resident hears the pool alone and returns the selections and the claim; the editor is not in that room and receives a list, not a session. The editor assembles without the resident present. The resident hears the mix once, before the final render, with the editor there to explain it. Fix that timing in the pitch, because it decides whether the collisions below are scenes or verdicts.

Selection. The resident chooses which sounds define the harbour and what the portrait is meant to say about it. They rule on inclusion and meaning.

Assembly. The editor builds the sixty seconds: levels, layering, transitions, noise treatment, the final order of events within the piece. They rule on the mix.

Intervention. Neither overrides the other's domain. If the resident wants a sound the editor suspects will not register in a minute, the resident wins on inclusion and the editor decides how to place it so that it reads. If the editor proposes dropping a sound, the resident can hold it. A hold is narrow, and the pitch should say how narrow: the sound stays in the selection and must appear in the finished piece, but the mix that carries it — level, treatment, where it sits — belongs to the editor. Inclusion is protected; audibility is not. The rule is small, and it is the whole format.

Now the collisions, which are the scenes you are actually pitching.

The resident wants a low, unglamorous hum included. The editor, working from the list alone, thinks sixty seconds is short and the hum will read as a technical fault. Under the rule the hum stays, and the editor's job becomes placing it so it reads rather than cutting it. That is a scene with a shape: a technical judgment and a meaning judgment meeting over the same twelve seconds of audio, and a rule that says which one gets to act.

The second collision is sharper, and it is where a hold's narrowness shows. The editor's noise treatment would take that same hum — still in the piece, still on the list the resident fixed — and process it until the quality that makes it the harbour is gone. The resident cannot rule on the mix, so the editor wins on treatment. But the objection is not technical. The resident is saying that a mix decision is now a claim about the place, and that the claim is false. Both rules are being obeyed: nothing was excluded, and the sound is present and inaudible at once. Your pitch does not have to resolve this, but it does have to notice that domain ownership lets assembly overrule meaning without ever breaking the rule the viewer was told to trust. What the format does instead of resolving it: the resident hears the mix once, the editor explains the treatment on screen, and the resident says whether the result still sounds like home. That is the format doing its job — two kinds of knowledge, visibly in contact, and a disagreement the criteria do not settle.

Say what finished means, and don't call the rule fair

Completion conditions should be dull and checkable. Sixty seconds exactly. Only recordings made in that harbour on that day. Continuous playback, no narration, no music added in post. Every clause is a decision, and every decision is arguable, but a viewer can tell whether it was met.

Judgment is where pitches start cheating. Suppose the criterion is that a listener who has never been to the harbour should recognise it. Fine — but recognise it as what? To whom? If the test audience is a panel of strangers, the criteria quietly reward whatever reads fastest to an outsider, which may be the opposite of what the resident thinks matters. That is a real tension and it belongs inside the format rather than under it. Name the tension; don't paper over it with the word "authentic."

Two distinctions are worth writing into the pitch document itself. An understandable rule is not a tested rule, and a tested rule is not an equitable one. And a producer saying "we'll keep it even" is an intention, not a result.

There is an unresolved advantage in the harbour task and you should let the reader see it: the editor has a vocabulary for the medium. The resident has to argue about levels and treatment in a language they don't have, which means the resident may lose an argument they were right about. Whether that is a structural disadvantage or simply the cost of the collaboration is not something a pilot episode settles. Say so, then move on.

Run the task a second time and see what survives

A single worked encounter proves very little. Run the same role relationship again with a different constraint or a different person, and check whether the structure still does anything.

Version B: same pair, same harbour, but the resident may not name the place anywhere in the piece, and the sixty seconds must include one sound a first-time visitor would notice and one only a regular would. The role structure is unchanged — selection and meaning on one side, assembly on the other — but the constraint forces the resident to use their knowledge instead of describing it.

Version C: a different resident. A ferry engineer instead of a lifelong neighbour. What holds is the shape; what changes is which sounds count as defining. If the role only works with one particular charismatic person, it is not a format yet.

Then the test that matters more than the others. Ask what disappears if the professional performs alone. For the harbour portrait, the answer has to be selection: a specific, defensible set of sounds and a claim about what they mean, which the editor could not assemble from the same pool without being told. If you cannot write that sentence, the resident's role is decoration and your format is a solo show with a guest in the room.

Two temptations to refuse here. The first is guaranteeing failure. A format that needs the amateur to struggle has to keep producing struggles, and it also tells you the professional's contribution isn't really load-bearing. The second is guaranteeing transformation. Competence is a payoff. So is a disagreement that ends without anyone learning a lesson.

The competitive version, with the equipment on the table

If you want the two roles to compete, define the resources honestly instead of declaring them equal.

Same tools. Both get the workstation, both build sixty seconds from the same pool. The competition is then knowledge against craft. The cost is that the resident has to learn the editing tools first, which eats the episode, and your format now contains a training segment it never planned for.

Different tools, stated on screen. The editor works in the full workstation — layering, processing, noise treatment, level automation. The resident gets a basic two-track app and can only trim and order. Same recording pool, same sixty seconds, openly unequal equipment. The resource difference becomes content: the audience watches what the missing tools cost. But the judging then has to account for it. Otherwise the resident is being measured on the editor's axis while standing without the editor's equipment, and the word "competition" is doing work the design hasn't earned.

Choosing the second version does not solve the fairness question. It relocates it into the criteria, where it is at least visible.

Neither version has been made. That is the point of writing the ledger before writing the shooting script, and of keeping permission, access and safety arrangements for the harbour recordings in a separate column from the format design. Being allowed to record on a working quay at five in the morning is a production problem. Whether the resident's role makes sense is a format problem. Don't let one answer the other.

The role map, and one task that needs both of them

The complete task, end to end: one day of recordings is made at the harbour by a recordist, who is credited. The resident listens through the pool alone and selects the sounds that define the place, plus a sentence about what the portrait should claim. The editor builds sixty seconds from those selections — ordering, layering, treating, mixing — without the resident in the room. The resident then hears the mix once, before the final render, and can require a held sound to stay in the piece, while how it is placed and processed remains the editor's. Nothing enters the piece that the resident did not choose. Nothing is broadcast in a form the editor did not assemble. The piece is done when it runs sixty seconds, uses only that day's recordings, and plays without narration.

Strip the resident out and the pool is still there, the tools are still there, and sixty seconds is still easy to fill. What is missing is the reason any particular sixty seconds is about this harbour rather than any other. That is the contribution the format has to be able to name — and if a pitch can't name it, the labels were carrying the whole idea.

Frequently asked questions

What is missing from a pitch that only names a professional and an amateur?

It is a casting notice, not a format. The pitch must say what each person knows, what each controls, and how those facts change the task the viewer follows. Professional is a status in a domain, not general competence, and amateur usually only says no formal training.

How should a pitch choose between teaching, collaboration, exchanged constraints and competition?

Choose by the task and what the episode needs to ask. Teaching asks whether an operation can be learned in the window; collaboration asks whether two knowledges can make something neither could alone; exchanged constraints asks whether someone can work inside choices not their own; competition asks whether someone can win under those conditions. For the harbour portrait, collaboration fits because craft and place are different in kind.

What should the ledger establish before scene description?

Who can see what, who can intervene and when, what help is allowed, who makes the final choice, and how one role changes what the other can do. In the harbour example, selection and meaning belong to the resident, assembly and mix to the editor, with a credited recordist making the recordings and a narrow hold rule protecting inclusion but not audibility.

Why should a pitch avoid calling its rules fair or promising transformation?

Completion conditions should be dull and checkable, such as exact duration, only that day's recordings and no narration. Judgment is where pitches cheat: an understandable rule is not a tested rule, and a tested rule is not necessarily equitable. Guaranteeing failure keeps producing struggles, while guaranteeing transformation treats competence or an unresolved disagreement as a lesson.

How can a pitch test whether the amateur role is load-bearing?

Run the task again with a different constraint or a different person, and ask what disappears if the professional performs alone. In the harbour example, the missing piece is a specific, defensible selection of sounds and a claim about what they mean. If that contribution cannot be named, the role is decoration and the format is a solo show with a guest.

Further reading

• When Your Competition Rules Reward the Wrong Kind of Play — For a competitive version, audit what the rules pay a participant to do, including whether sitting out saves resources, then weigh the four repairs it compares.
• Explain Who Your Unscripted Format Needs to Cast—and Why — After the role map, turn each column into a casting function with the task it performs, separating what someone can do from what they will do on camera.