Pitch a Found-Footage Series Through Who Records, Keeps, and Shares the Images

Every found-footage pitch ends up in front of the same question, and it is not about the grain. It is: who is holding the phone, and why are they still holding it?

The look is the easy part. Shaky frame, burned-in timecode, a lens flare smeared across a stairwell — a production designer can give you all of that by lunchtime. What a scripted series cannot fake is the reason the images exist at all, episode after episode, and why anyone is watching them in the order you have chosen.

The workable version treats the images as a supply with four stations: recording, retention, access, assembly. Someone points a device at something. Something keeps the file. Someone can open it. Someone decides what part of it an audience sees. Match the stations to your story and you can build a whole season inside them. Mismatch them, and every episode quietly relies on a camera appearing wherever the plot needs one.

What follows is built on an invented series, because the method needs a worked case and no real production's material has been checked against it here.

Choose the recording situation before the camera style

Start with a single image your proposed episode cannot do without. Not the opening shot — the one that carries the episode's turn.

For the example, that image is a woman walking into a rehearsal room and telling a man he has spent three weeks on a phrase that was replaced that afternoon.

Before you decide how that looks, decide four things. Who records it. Why they are recording. What their device can plausibly encounter. And what the story's convention allows.

In the example, the man is Tobin, a member of a five-person physical-theatre company, Bright Hour, devising a stage piece over eleven weeks. The company keeps a shared video log: at the end of a session, anyone who wants to leaves a short phone video of the phrase they worked on, so collaborators who missed the session can see the movement without another rehearsal. Tobin's device is his own phone, propped on a shelf above the mirror, because he is filming a longer solo session — the log entries are usually two to five minutes, but a person can leave the camera running to capture a whole run.

Look at what that single decision buys and costs. Tobin's phone sees the room from the shelf: Tobin, the mirror, the door, whoever walks through it. It does not see the corridor. It does not see the far side of the room, and if Tobin turns his back, it does not see his face. It cannot move closer.

A fixed camera in that corridor would know the corridor for months and nothing else. A recorded call knows two voices and no faces, which is a severe limit if your scene turns on who looks away. A dashcam knows forward and nothing else. A body camera knows what a chest points at, and it starts and stops on someone else's rules. Each of those is a knowledge limit, and the limit is the writing tool.

Boundary worth saying plainly: these are fictional devices with fictional limits. What a real system would capture, keep, or hand over is a different question, and not one a scripted pitch answers.

The failure mode here is unrestricted coverage by accident. If your scene needs two people at opposite ends of a room and a look that passes between them, one phone on one shelf cannot deliver it. So either the scene changes, or a second source exists — and a second source has to be established before you need it, not discovered on the page where it becomes useful.

This is also where you separate yourself from a mockumentary. A mockumentary puts a documentary crew in the room and lets the characters know it; the tension is performance under observation. A distributed recording system has no crew at all, and nobody is performing for the same audience the show eventually reaches. Different source of pressure, different engine.

Follow the image beyond the moment of recording

A camera running is not yet a story. The second station is retention, and it asks uncomfortable questions: who keeps the file, who knows it exists, and why would the person assembling your episode be allowed anywhere near it.

Bright Hour's rules, set at the start:

• Members record entries on their own phones. Each person decides what to leave; some sessions produce four entries, some none.
• Entries go to one shared cloud folder, the log, on the company account. Videos sync automatically when a phone charges on Wi-Fi. Voice notes are added by hand.
• Nadia, the director, adds members when they join.
• Nothing has ever been deleted. The folder is treated as a running archive, on the reasoning that you never know which version of a phrase you will want later.

That last rule is doing a lot of work, and it should be in place long before it becomes convenient. Because of it, Tobin can stop a recording and still have the file land in the log that night while he sleeps. He never decides to keep it. He never decides to delete it either. The retention is a byproduct of a practice that already existed for other reasons — which is the only kind of retention that feels honest on screen.

Then there is the question the pitch most often dodges: an image's presence on a device does not explain its presence in your episode. Those are two facts, not one. You need the file to exist, and you need a route by which someone with a reason gets it. Bright Hour's route is a newcomer.

Jonas joins in week three as the sixth member, and is added to the log the day he arrives, the way everyone has been. He works through the archive from the beginning, in order, because the piece's opening movement is built from the earliest devising and he has to learn it before anything else. He stays behind the recordings at first, then closes the gap as the piece nears opening.

Now separate three kinds of knowledge that are easy to blur:

• The recorder's. Tobin knows exactly what happened after he stopped that camera.
• The assembler's. Jonas knows what is in the archive and nothing else, and he has not yet reached everything.
• The audience's. Whatever survives that filter.

Nadia knows a fourth thing — what people told her later. Keep them apart deliberately. Most plot holes in this form come from letting one of these know something the others cannot.

Put the camera under pressure

Choose the difficult beat at which recording would be inconvenient, unwanted, or impossible, and answer it with the fiction you already built rather than with new equipment.

The beat: week five. Tobin is alone in the room, thirty-five minutes into a solo session on that phrase, his phone still running on the shelf. Elin comes in to tell him the phrase was changed by her and Priya that afternoon and what he is working on is out of date. He did not know. He has been on it for three weeks.

They argue. He reaches past the camera and stops the recording. The file ends there.

Notice what the episode gets. It gets the first four minutes of the argument. It gets the act of stopping — an arm crossing the frame, the image cutting out mid-exchange, because the device was on a shelf and his hand had to come into the shot to reach it. The stop is content. The gap has a visible cause, which is far more useful than a gap that merely exists.

Why did the recording continue that long? Because it was already running for an unrelated purpose. Why did it stop? Because a person decided it should, in the middle of a difficult conversation. Both answers come from the system, not from the plot.

Now the temptation. The episode wants Elin's face at the moment she says the thing that lands. There is no device in that room facing her. You can add one — her own phone on the table — but it has to have been established, and it has to have had a reason to be there, and once it exists the whole episode can see more than you might want. Add it for this beat alone and the audience learns something corrosive: cameras appear when the story needs them. Every gap you leave after that stops meaning anything.

The permitted alternative is a later account. Tobin records a voice note walking home and posts it that night. Bright Hour allows audio-only entries — people use them when they are commuting and cannot film — so this is inside the system, not a special dispensation.

What the voice note establishes: what Tobin says happened, in his own words, within hours, with nobody else in the room. That is worth a great deal. What it cannot establish: what Elin said after the camera stopped, whether anything was resolved, or whether Tobin's account is fair to her. An account is testimony. Testimony is not coverage.

Assemble an episode from the permitted sources

Now map the episode using only what the system can supply. Every proposed image needs a row, and every row needs an honest limit.

Beat 5 is the one to protect. Do not let the episode solve it a scene later with a second angle; the missing material is the point, and the season's credibility rests on it staying missing.

The assembler's role matters most at beat 8. The order Jonas watches in becomes the order the audience receives things, and that is a selection with consequences. If you show him, you gain a knowledge limit you can use — he genuinely has not seen next week's files — but you take on a debt: you now owe the audience his access and his motive, and if every gap gets waved off with he hasn't got there yet, the excuse wears thin within a few episodes. If you do not show him, the archive stands alone and its ordering has no in-fiction justification, which you then have to accept rather than pretend away.

One last separation, and it matters for this premise more than most. In-story provenance is Tobin's phone on a shelf. The material used to demonstrate the pitch is staged: actors, lighting, a phone operated as a prop, probably a second camera shooting the scene that the prop phone is supposedly capturing. Both are legitimate; they are different claims. A phone-shaped frame with grain and a timestamp is an aesthetic, not evidence that an image records a real event. Label the demonstration material as demonstration, and let the in-story provenance stay where the fiction puts it.

Show how the next installment finds different material

A found-footage series dies at episode two if the second script needs a camera it did not have in the first. So demonstrate that the same system produces different material, and show that the change comes from motive, access, or custody rather than from new equipment.

Bright Hour's second route was set up in week one. Ruth is an outside dramaturg who visits about once a month. Nadia added her to the log and asked her to leave her notes there so the company could read them. Ruth's practice is different in kind from the members': after a session she sits in her car and records a voice note about what she saw — an assessment, not a record of phrases — and posts it to the log. Nobody watches everything, so nobody necessarily notices when one appears.

The second episode covers the week the company cut a six-minute passage — the chair section.

Beat 3 deserves attention. An absence is a fact about the practice, not testimony about the decision. No member logged that day because the session ran long and everyone went home — not because anything was hidden. Members' videos reach the log by auto-sync rather than by anyone choosing to file them, so the gap means no phone had anything to send. Ruth's note, added by hand from her car that evening, is the only record of that session. Say the gap that narrowly, or the audience will read concealment into a coincidence and you will have taught them something your fiction did not mean.

What changes in episode two: the motive is assessment rather than recall; the access is an outsider who was in the room; the custody is a private copy plus a posted one; the knowledge is one person's view from outside the ensemble. What stays the same is everything that makes the show a show — phone, log, folder, shared access, a member working through it in order.

And the interpretation problem is now built into the material. Ruth's note says Elin proposed the cut. Nothing else in the archive corroborates that. But the audience already watched the week-five argument between Elin and Tobin, so they will connect the two, and the connection will feel true. It is an inference the archive does not supply. Let the audience make it — do not have anyone in the fiction confirm it, because the moment someone does, the archive stops being evidence and becomes exposition.

Two episodes, two different engines, one system. The phrase argument runs through material the members made for their own use. The chair section runs through material an outsider made for hers. Neither needs a camera that was not already there.

That is the test to hold the whole pitch against. Write the source and custody map first. Put every proposed image in it and mark what it cannot show. Then find the beat where recording would be most inconvenient, and let the missing picture stay missing — because the absence is the story, and grain, handheld motion, and screen artifacts are only the way it is dressed.

Frequently asked questions

What are the four stations a found-footage pitch should map before worrying about the look?

The article names them as recording, retention, access, and assembly. Someone points a device at something, something keeps the file, someone can open it, and someone decides what part an audience sees. Matching the stations to the story can build a season inside them; mismatching them makes every episode quietly rely on a camera appearing wherever the plot needs one.

Why does the article argue that retention should feel like a byproduct of an existing practice?

In the Bright Hour example, Tobin never decides to keep or delete the file. His phone records a solo session, and the video syncs automatically to the shared log when the phone charges on Wi-Fi. Because the folder is already treated as a running archive, retention happens without a character choosing it, which the article says is the only kind of retention that feels honest on screen.

In the worked scene, what does the recording stopping mid-exchange give the episode?

It gives the first four minutes of the argument and the act of stopping: an arm crosses the frame and the image cuts out because the phone was on a shelf and had to be reached. The stop is content, and the gap has a visible cause. What it cannot establish is everything after the stop, including the outcome, an apology, or a resolution.

How can a second episode find different material without introducing new equipment?

The change should come from motive, access, custody, or knowledge rather than from a new camera. In the article’s second route, Ruth is an outside dramaturg who records a voice note in her car after a session and posts it to the same log. Her motive is assessment rather than recall, her access is as an outsider in the room, and her custody is a private copy plus a posted one, while the phone, log, folder, and shared access stay the same.

Are the Bright Hour examples based on a real production?

No. The article says the method is built on an invented series because it needs a worked case, and no real production’s material has been checked against it. It also states that the devices have fictional limits; what a real system would capture, keep, or hand over is a different question that a scripted pitch does not answer.

Further reading

• Pitch a Factual Series Built From Self-Recorded Video Diaries — For material people film themselves, this covers who asked, what happens when the camera stops, and how to treat ordinary gaps without reading intent into them.
• Animate Documentary Testimony Without Turning Metaphor Into Evidence — For demonstration material, it compares what a speaker reports with what an image adds and when to declare metaphor's author instead of letting it read as evidence.
• Pitch a Series Told From a Different Character’s Viewpoint Each Episode — Read this when one source's access differs from another's: it explains making a new viewpoint necessary through different knowledge or authority, not a new biography.