Plan coverage
Coverage is the plan for how a scene becomes editable: which angles exist, how they connect, and where the edit escapes when a take fails.
What this is about
Editors inherit coverage decisions made weeks earlier by people under time pressure. A scene shot as one beautiful oner is locked to that take's weakest second; a scene with a master, two sizes and honest cutaways can be rebuilt around any problem — a fluffed line, a boom shadow, a client note. Planning coverage means deciding per scene how much editability to buy and what it costs in setups. The classic rules earn their keep here: staying on one side of the axis keeps eyelines consistent, and matching sizes across characters keeps a dialogue cuttable.
The order matters more than the tools. Skip a step and you usually notice two steps later — by which point the fix costs several times as much.
What runs differently here
In planning terms, that means:
- Coverage is a per-scene budget decision: every additional angle costs a setup, and setups are the currency of the day.
- The 180-degree rule is about eyelines, not dogma — cross the axis deliberately with a bridging shot, never by accident.
- Interviews count too: two camera sizes on one interviewee buy the freedom to cut inside an answer.
- Cutaways are planned coverage, not leftovers shot at wrap when everyone wants to go home.
Step by step
This order gets you there fastest:
- Decide per scene what carries it: performance, information or atmosphere. That answer determines whether you need a patient master or a fast chain of specific angles.
- Choose the covering pattern: master plus coverage for dialogue and decisions, a planned oner where rhythm matters more than repair options.
- Draw the axis for every scene with more than one person and fix which side the camera lives on. Eyeline errors are invisible on set and loud in the edit.
- Match sizes across characters in dialogue — a medium answering a medium — so reverse angles cut together without a bump.
- List cutaways and inserts per scene as their own shots: hands, screens, reactions, room details. They are the edit's escape hatches and deserve schedule time.
- For interviews, plan two sizes per person, framed for the cut, so an answer can be shortened invisibly without a jump.
- Write the coverage decisions into the shot list with the scene's purpose noted, so on set a dropped angle is a known cost instead of a silent one.
- Walk the plan with the editor if you can. Nobody prices missing coverage more accurately than the person who has to cut around it.
Common pitfalls
What most often goes wrong in practice:
- Trusting a single oner because it looked great in the third rehearsal — the edit inherits its weakest moment.
- Crossing the axis between reverse angles without a bridging shot, so eyelines flip mid-conversation.
- Shooting cutaways 'if there is time' — there never is, and the edit pays for it.
With TillyGen
TillyGen builds coverage into the shotlist it drafts: masters, reverses and cutaways appear per scene, so the editability of a day is visible before it is shot.
Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.
Frequently asked
What is the minimum coverage for a dialogue scene?
A master that holds the whole scene, matched singles or mediums on each speaker, and at least one cutaway. Less than that gambles the scene on perfect takes.
When is a oner the right call?
When rhythm and space are the point and the team can afford rehearsal time. Protect it with a safety angle or accept that the scene lives or dies with one take.
How does coverage planning change for interviews?
Two sizes per person, cut-friendly framing, and b-roll planned against the expected answers — so the edit can compress twenty minutes into ninety seconds without visible seams.
How long does it take to get started with TillyGen?
A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.
Can the results be exported?
Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.