Pitch Sports Coverage by Separating the Event, the Supplied Feed, and Your Program

Your coverage page probably looks convincing. A row of camera positions, a graphics panel, a note about grabbing the winner at the finish, and a line about bringing viewers closer to the action. Every item is drawn the same way, in the same confident font, as though all of it were the same kind of thing.

It isn't. Some of it is happening on a track whether you are there or not. Some of it is pictures that somebody else is making and handing to you. Some of it is the only part you actually author. A pitch that holds those three layers apart is easier to approve, and it is the only kind that survives contact with a real meet.

The short version: name what happens at the event, name which pictures you can obtain and who controls them, and name what your program adds on top. Where an editorial promise depends on material nobody has confirmed, say so beside that promise rather than saving it for a general caveat at the end.

Identify the program, not just the event

A close race is exciting on its own, and that is exactly the trouble with using the excitement as the reason your coverage should exist. The excitement belongs to the event. It will be present whether your program is good, bad, or absent. Plenty of thrilling races have made dull television.

So the pitch needs a claim the event doesn't make for you. A few tend to hold up. Your program helps a viewer understand a contest they don't otherwise follow: which runners matter, what a slow pace means, when this race usually changes. Or it follows one tactical question all the way through. Or it introduces the participants as people with a reason to be here. Those are different programs, and each makes different demands on your pictures later. Choose before you reach the camera list, not after.

It helps to keep two audiences separate. The recipient of your pitch is a commissioning editor or a programming contact, reading for feasibility and fit: can this be made, does it belong in that slot, what exactly is being asked of them. The viewer meets your program cold, halfway through a race, with no deck and no context. Write for the first. Describe for the second. When a pitch slides from "the viewer will understand the race" into "we will have everything we need," it has quietly swapped one audience for the other.

Get specific about the promise and the vague adjectives fall away on their own. "We'll bring viewers closer to the action" invites the obvious question: closer than what? The viewer is on a sofa; the stadium is full. Compare a version a viewer could actually notice: our commentary tracks the four runners who can win this, so anyone arriving at lap two knows who to watch.

That sentence has consequences, and they are the useful part. It needs names, a start list, and a commentator who knows the field. It does not need a close-up. Some editorial promises survive a single fixed wide camera and some collapse without a finish-line lens, and the way to find out which kind you have written is to state the promise first and the facilities second.

Give every proposed passage a source of pictures

The most useful thing a coverage page can do is put its status marks where a reader can see them.

Confirmed means the person who controls the thing has agreed to it. Not "the host sounded positive." Not "we normally get that." Proposed means you are asking. Unknown means nobody has told you yet, and the plan should visibly change because of it. Marking something unknown is not a confession of weakness. It tells the person approving your pitch exactly what they are being asked to confirm, which is usually the thing they wanted to know anyway.

Two inputs get confused more often than any others, so it is worth separating them by name. A supplied edited view and an individually selectable camera both arrive as a video signal, and they are not the same thing. If you can choose which camera you are on, or which part of a frame to use, you can cut. If somebody else is cutting, you inherit their decisions, including the moment they leave the race to show a crowd. One of those is a program you direct. The other is a program you narrate. A pitch that promises operators cutting between four angles when you have been offered one is not an ambitious version of your pitch. It is a different pitch.

Every addition also has a material requirement, and each requirement has an owner:

• Commentary needs a feed to talk over, a position to sit in, and a path for the audio. This is usually the part you control outright.
• Graphics need data. A lap counter is easy. A live split time is not, unless the timing service is feeding splits in a form your operator can actually use.
• Replay needs a recording of a signal with enough detail where the question is. Replaying a wide shot gives you the same wide shot, in slow motion.
• Interviews need a place to stand and somebody with the standing to bring the athlete there.

Keep acquisition authority and creative intention in separate columns of the same table. Wanting a line camera is a creative intention. Having one is a facility. Being allowed to use the feed you've been offered, in the way you intend, on the platforms you intend, is a third question again — and access to one feed answers none of the other two. This is not a matter of reading the paperwork yourself; it is a matter of naming, on the page, who says yes to each line. For any item in your pitch, you should be able to answer one question without hesitating: who is the person who can confirm this?

Walk through ordinary coverage before the decisive moment

Pitches love the highlight. But almost all of a program is the ordinary passage, and the ordinary passage is where a thin picture source is most exposed — and, handled well, where the program earns its place.

Here is an invented example. No meet, feed, or agreement is being described; the details exist only to make the distinctions visible.

Assume a fictional regional invitational at a community track. The only confirmed picture source is one fixed wide camera, high on the far side, framing the whole oval. It is continuous and it does not move. The framing is not yours. There is no second angle, no selectable camera, and no confirmation that the supplied signal carries clean ambient sound.

Sit with the ordinary passage for a moment. The race is three and three-quarter laps of a 400-metre track, and on lap two nothing has happened yet. The wide view establishes real information: eight runners, on the track, in a particular order, at a particular point in the race. What it does not do is point. Every runner is the same size in the frame. There are no faces, no sense of effort, and the camera does not move to follow whoever is making a move. A viewer who doesn't already recognise these athletes by their vests is not being told who is who.

Now watch where the understanding comes from. Commentary names the leader, identifies the favourite sitting fourth, explains that the pace is slow enough to keep the field together, and flags the point where this race usually breaks. A graphic counts laps and puts names against numbers. If the supplied feed carries clean ambient sound, the crowd and the footsteps carry tension the picture cannot. If it doesn't, that part of your promise has no source — and that is worth knowing before you write it down.

Notice the direction of the argument, because it is the opposite of what most coverage pages assume. With a wide-only feed, your program is doing more identifying work, not less. The instinct that a limited feed leaves you less to add only holds if the program is a pure pass-through of the picture. Anything that helps a viewer follow a race they don't know is work the camera isn't doing. That is your editorial proposition, and the ordinary passage demonstrates it. A highlight reel never will.

Now the finish — conditionally, because you do not know what will happen. Suppose the race comes to the line with two runners together.

The supplied picture establishes that two runners reach the finish. It cannot settle which one crossed first, by how much, or whether either dipped or stumbled. From a camera on the far side covering the whole oval, two figures at the line are small, and the margin between them can be centimetres. The picture shows you the race and does not adjudicate it.

What settles it is the meet's timing arrangements. An organised meet establishes placings with equipment at the line, and that result is published. Your program can report it. What your program cannot do from this feed is show the viewer why the result is what it is.

Commentary can clarify a great deal around that gap: the shape of the last lap, who committed first, what the result means in the context of the season. What commentary cannot do is replace the picture. Saying "she had it by a whisker" over a wide shot where nobody can see the whisker does not add coverage; it asserts a detail the program hasn't shown. And note that none of this assigns a result. Neither should your pitch. A pitch that predicts the finish is a pitch about a race that hasn't been run.

Remove the preferred view and see what survives

Now take the close finish camera out of the plan. It was never in it — that is the point. A coverage page that leans on it while its status reads unknown has been describing a program that does not yet exist, and the writer may not have noticed.

Three moves are honest. Pick one per promise, and pick it deliberately.

A bounded account. Carry the finish from the wide view, report the official placing when it arrives, and tell the viewer plainly that the margin is not something your camera can show. The explanation of the race still happens; it just doesn't pretend to be forensic.

A clearly identified uncertainty. Say, on air and in the pitch, that the picture does not resolve the order. This is not a failure of nerve. It is the difference between a program that knows what it is showing and one that doesn't.

Original coverage, separately confirmed. A camera at the line would genuinely solve the problem. It is also a new request with a new owner, a new position at the track, and a new cost. Treat it as a dependency to be confirmed, not as a fallback you can reach for in the edit.

The graphic trap sits right here, and it is easy to walk into. If the pictures cannot resolve the margin, a graphic must not draw one as though the picture contained it. Putting the official placing on screen is fine, because the placing has a source — the timing service. Animating two runners separating at the line, with a stated gap, implies the separation came from a camera that never saw it. If the margin came from the timing system, say where it came from. If it came from nowhere, don't draw it.

All of which produces a smaller promise. We'll show you the race, we'll tell you the result, and where our picture can't settle it, we'll say so.

That promise is keepable, and it is not automatically the lesser program. For a distance race, the explanation of why it went the way it did — the pace, the move, the moment the favourite had to go wide — lives in the commentary layer, which is the layer you own entirely. Where a promised explanation genuinely cannot be carried by commentary over a wide shot, ask for the thing that would carry it and mark that ask as a dependency. Asking is fine. Assuming is what turns a workable pitch into a broken one.

What the finished version sounds like

A real pitch would still have to check the actual feed specification and the actual permissions with the people who hold them. What you can settle now is whether your own plan holds together. Here is the same fictional finish as the program would carry it, with the sources visible:

"...and they're level with two hundred to run. [wide feed — confirmed, and the only picture source] Two to go, and it's close, and I'll be straight with you — from where the single wide camera sits, we cannot see that margin. [wide feed] The result is in: the placing comes from the meet's timing system, not from our picture. [timing service — published] We'll have the placings up in a moment. [graphics — proposed, pending the data feed] If the meet confirms a camera at the line, we'll bring you the margin; that request is still open. [unconfirmed]"

Every promise in that passage has a source beside it, and the one thing the picture cannot do is named where the viewer can hear it rather than buried under a closing disclaimer.

The viewer does not care which camera is on the roof. They care whether the race makes sense to them by the time it's over. That is what your pitch is selling. Every camera position in the deck is a promise to the viewer made with somebody else's equipment — so name the ones you actually control, and the pitch stops describing a broadcast you can't make.

Frequently asked questions

What three layers should a sports coverage pitch keep separate, and why?

The event activity happens whether you are there; the supplied feed is pictures someone else makes and hands to you; your program is what you author. Separating them makes the pitch easier to approve and more likely to survive a real meet.

What is the practical difference between a supplied edited view and an individually selectable camera?

Both arrive as a video signal, but a selectable camera lets you choose the angle or part of the frame and therefore cut; a supplied edited view means someone else is cutting, so you inherit their decisions, including when they leave the action. One is a program you direct, the other a program you narrate.

How should uncertain pictures or permissions be marked?

Use confirmed for what the controller has agreed, proposed for what you are asking, and unknown where nobody has told you. Marking unknown tells the approver what they are being asked to confirm. If a promise depends on unconfirmed material, put the caveat beside that promise rather than only in a closing disclaimer.

Why should a pitch walk through ordinary coverage instead of the decisive moment?

Most of a program is ordinary passage, and that is where a thin source is most exposed. With one fixed wide camera, commentary and graphics must do more identifying work; the ordinary passage demonstrates that editorial proposition, while a highlight reel will not.

What can a program honestly do if no finish-line camera is confirmed?

It can carry the finish from the wide view, report the official placing once the timing service publishes it, and tell viewers plainly that the margin is not something the camera can show. A line camera is a separate request with its own owner and cost, not a fallback. A graphic must not draw a margin the picture never resolved.

Further reading

• The Commercial Needs a Second Take of an Event That Will Happen Only Once — Use this when a promised beat depends on a moment that happens once and cannot be reshot, to decide which story the coverage can still tell.
• Make the TV Format’s Scoreboard Explain the Game — Use this when building a graphic from a feed you don't control, to keep earned, pending and projected numbers in separate columns.
• Live, As-Live, or Edited: What Does the TV Pitch Actually Promise? — Once your picture sources are named, this sorts out what calling the coverage live, as-live or edited actually commits you to.