Invite an Editor Into the Film You Have Actually Shot
Invite an Editor Into the Film You Have Actually Shot
A development deck describes a film that does not exist yet. That is its job. Its scenes, its tone, its comparison titles and its director's statement are all proposals, and they are written to persuade people who will never watch an assembly. Once the shoot is over, though, an editor cannot assess a proposal. They can look at what the camera recorded, hold it against what you meant, and tell you what the difference allows. So the material you send has to lead with that difference instead of restating the pitch that got the film financed.
The short version: name the film you meant to make in two or three sentences, describe the state of the material honestly, and send one sequence that contains the assembly question you cannot answer alone, with enough run-up and aftermath and alternative takes for the choice to be intelligible. Ask for a conversation about it. Say plainly which events were never shot. Then stop.
That is easier to write than it sounds, mostly because the habit you have to break is the habit of selling.
Replace the development promise with a material account
A deck is written for people deciding whether the film should exist. A material account is written for a person deciding how to build it. Different reader, different information.
The material account needs four things, and it should fit on a page.
The intended film, in a few sentences. Not a synopsis for strangers — a statement of what the thing is supposed to do. Whose film it is. What the ending is meant to leave behind. Tone worth one sentence, no more, because you will show the tone rather than describe it.
The state of the assembly. Rough pass of most scenes, four not yet cut, no score, temp everything. Be specific about how rough, because "rough assembly" covers both a watchable two hours and a folder of unassembled takes.
The significant difference between the two. Name the biggest gap between the film you intended and the footage you have. This is the sentence the editor will keep in mind while watching everything else, and it is usually the sentence people bury.
The inventory: sequences that exist, alternative takes and viewpoints, missing coverage, and temporary elements — temp score, unmixed sound, no ADR, placeholder titles, effects not started.
Keep recorded material in its own list, apart from anything you still plan to shoot. This is not pedantry. If a scene appears in your notes as "the confrontation" and the reader has no way to know the middle of it was never filmed, they will assume there are takes to work with, and every judgment they make about your film will be built on material that does not exist. A hoped-for pickup is not footage. Give it its own heading: Not shot. One list of what exists, one list of what doesn't.
Turn "it isn't working" into an editorial question
"It doesn't land." "It's not coming together." "I need a fresh eye." These are honest descriptions of a feeling, and they are useless to someone deciding whether to take the job. An editor can assess a choice. They cannot assess your unease.
So convert the feeling into a choice. Most assembly problems reduce to one of a few questions. Whose viewpoint organizes the scene — and does the cut stay with that person? Which performance carries the conflict, when two takes pull in different directions? Is there a transition where the film needs one, or does the scene end without a shot that gets you out? Which structure does the recorded material actually permit, as opposed to the one the script assumed?
Then point at the material that makes the question hard. An editor wants to know where the difficulty lives in the footage — which two takes are in conflict, which beat has no coverage, which cut you have already tried and rejected. Pointing is what turns a complaint into a brief.
And if your question depends on an event you never recorded, say so. "Can you find the scene in the edit" is a request for editing. "Can you find the confrontation in the edit" is a request for an event that was never captured. That second kind of request is legitimate — productions end up needing pickups all the time — but it belongs in the invitation as a production problem, clearly marked, not smuggled in as an editorial one. An editor who discovers mid-conversation that the rescue is really a reshoot has learned something about how you describe your own material, and not the thing you wanted them to learn.
Choose a sample that reveals the work
Two kinds of sample do two different jobs.
A highlight reel answers: is this film promising? That is a real question, and funders, cast and festival programmers ask it. It has music, it has the best photography, it runs under three minutes, and it cannot answer anything an editor needs to know.
A working sample answers: what does assembling this film involve? It is one sequence, plus whatever minimal context makes that sequence legible — the tail of the scene before it, the opening of the scene after. It includes the competing possibilities as separate, labelled clips rather than pre-blending them into a version that hides the choice. It labels omissions and temporary elements. It does not need to be flattering. It does need to be intelligible, which is a different requirement and the one that gets ignored.
The failure mode here is the media dump: a link to four hundred clips, a folder named with a date, no note. That does not communicate scope; it transfers the work of finding the problem to the person you are asking to solve it. If the editor has to reverse-engineer your worry from a bin of files, you have outsourced the framing, and you will get back a reply about logistics.
Practical shape: streamed links, not a hard drive. Clip names that say what the clip is. Time codes. One page of notes. A stated duration, so the editor knows whether they are being asked for ten minutes or ninety. And an explicit line about what you have withheld and why — because sending only part of a film is a decision the other person should be able to see and argue with.
Ask for a conversation, not speculative editing
The first conversation has one job: to establish whether this is the kind of assembly problem this editor wants, and how they would come at it. That is a decision about fit and approach. It is not a decision about the finished cut, and the invitation should make the difference obvious.
So scope the ask. A sequence, a question, a conversation of a stated length. Then be explicit about what a real engagement would unlock — the full assembly, the selects, the notes, the project files — and when. Keep the eventual technical handoff separate from this conversation. Project files, media management, drives, conform, deliverables: those are the logistics of a working relationship, not the opening move, and folding them into the first email makes a small request look enormous.
The line to watch is the one between "tell me how you'd approach this" and "cut me a version so I can see." The second is a job. It has a schedule, and a version of the film built on spec is not a conversation opener — it is unpaid work with a deliverable. If you genuinely want to see how someone edits before committing, that is a reasonable thing to want, and it belongs in a separate arrangement that both people agree to on purpose. One sentence acknowledging that is enough, and it reads as respect rather than caution.
Two things can come back that are not rejections. The editor may ask to see the whole film before answering your question, which is fair — a scene's job depends on the film around it. Or they may say the question you asked is not the one they would start with. Both are useful. Neither is the answer you scripted.
An invented example: the departure nobody shot
The example below is fictional, and the method here is a proposal for framing an invitation rather than a description of how intake usually runs.
A fiction feature, working title Low Season, has finished shooting. There is no editor attached. A rough assembly exists for most of the film.
Scene 31 is the confrontation. As written: Renata comes in, makes her accusation, Theo answers, Theo leaves, Renata is alone.
What was shot:
- Renata's arrival and the accusation, covered adequately.
- Theo's answer, in two takes. Take 4 plays him cold and already gone. Take 11 plays him tired and still trying.
- The aftermath: Renata alone in the room, his keys missing from the hook by the door.
- Temporary score over the aftermath. On-set sound only in the hall. No ADR.
What was not shot: Theo leaving. No shot of him standing, crossing the room, opening the door, or the door itself. Nothing.
Two decisions are tangled here, and that is what makes the sequence worth sending. First: which take does the aftermath answer? If take 4, the aftermath confirms what the audience already believes. If take 11, the aftermath has to carry a reversal nobody watched happen. Second: can the scene end on the aftermath at all, or does the departure need to be filmed? Those two questions are not independent. With take 4, the ellipsis might work — the aftermath tells the audience he left, and the question is whether being told is enough. With take 11, the ellipsis is doing much heavier lifting, and the answer may be that the scene needs the shot it doesn't have.
Note what the aftermath does and does not do. The keys missing from the hook are a trace of the departure, inscribed in material that exists. A trace is not coverage. It gives the cut something to lean on without giving the audience the event, and whether that lean holds is exactly the kind of judgment an editor can make from the footage and you cannot make alone, because you have watched take 11 forty times.
Two packets, two conversations
Packet A is two minutes and forty seconds of the best-looking material, scored wall to wall with temp music. The confrontation appears as arrival, take 4, aftermath, with a music swell across the join. The missing departure is invisible — the cut reads as a deliberate ellipsis, and the sequence looks like a film.
Here's a two-minute look at where the film is. I think it's coming together. Would love your thoughts on whether you'd be interested in editing it.
That is a real email people send. Its costs are specific. The editor cannot see the problem, so the conversation has nothing concrete to work on. The music is doing work the scene has not decided, which means every performance and pacing judgment is being made against a temp score rather than the material. And if the engagement goes ahead, the missing departure surfaces later, after scope has been discussed, which makes a known gap look like a discovered one. Packet A also answers the question you already know the answer to — whether the film looks promising — while leaving the actual question untouched.
Packet B is about seven minutes.
- 0:40 — tail of scene 30, the meal
- 1:50 — scene 31 as shot, through the accusation
- 0:50 — take 4, labelled
- 0:55 — take 11, labelled
- 1:10 — the aftermath
- 1:20 — opening of scene 32, the following morning, to show what the aftermath competes with
- one page of notes: written scene versus shot scene, the missing departure, every temp element
I've finished shooting Low Season and I'm assembling. Two-hander, one house, the film turns on whether the two of them can stay in the same room.
The sequence below is scene 31. As written, Theo leaves at the end of the confrontation. We never shot the departure — no exit, no door. What exists is Renata's arrival and accusation, two takes of Theo's answer (take 4 plays him already gone, take 11 plays him still trying), and Renata alone afterwards with his keys off the hook.
The question I can't settle: does the aftermath carry the departure, and does the answer depend on which take I use — or does the scene need the departure filmed? If it's the second, I'd rather know now than after I've locked the shape of the middle.
Everything is temp: the score on the aftermath, the hall sound, no ADR. The rest of the assembly is rough and I haven't sent it, but I will if it's useful. Would you have half an hour to look at the sequence and talk about how you'd come at it?
Packet B is not more polished than Packet A. It is more legible. It hands over a decision rather than a verdict, names the material that does not exist, and shows the editor the shape of the job without pretending the job is finished. The question it asks is answerable from the footage. The boundary between editing and new production is drawn in the email rather than assumed.
The brief
The whole invitation reduces to four lines and a link.
- The film, in two sentences.
- The material, honestly: what exists, what is temp, what was never shot.
- One sequence, with the competing possibilities labelled.
- One question, and the conversation it would take to answer it.
Then say what you are not asking for. Not a recut. Not a schedule. Not a verdict on the whole film from seven minutes of it.
What stays open is the thing that should. Nobody can tell you from a description whether take 4 or take 11 belongs in the film, or whether the aftermath can absorb a departure the camera never saw, because the answer depends on how the two takes read at length, how the temp score has been shaping the aftermath in your head, and how scene 32 opens when the cut finally has to leave the room. That is what the editor is for. Your job is to make sure that when they sit down to look, they are looking at the film you actually shot.
Frequently asked questions
What should replace a development deck when inviting an editor?
Send a one-page material account: the intended film in a few sentences, an honest state of the assembly, the significant difference between the film you intended and the footage you have, and an inventory of sequences, alternative takes and viewpoints, missing coverage, and temporary elements. Keep recorded material separate from anything you still plan to shoot, and give pickups their own heading such as 'Not shot.'
How do you turn 'it isn't working' into a useful editorial question?
Convert the feeling into a choice: whose viewpoint organizes the scene, which performance carries the conflict when two takes pull in different directions, whether a transition is needed, or which structure the recorded material permits. Point at the material that makes the question hard, such as which two takes conflict or which beat lacks coverage. If the question depends on an event that was never recorded, mark it as a production problem, not an editorial one.
What makes a working sample different from a highlight reel?
A highlight reel answers whether the film is promising. A working sample answers what assembling the film involves: one sequence plus minimal context, competing possibilities as separate labelled clips, labels for omissions and temporary elements, and enough clarity to be intelligible even if not flattering. Avoid the media dump of hundreds of clips with no note, which transfers the work of finding the problem to the editor.
What is the line between asking for an approach and asking for speculative editing?
'Tell me how you'd approach this' opens a conversation. 'Cut me a version so I can see' is a job with a schedule; a version built on spec is unpaid work with a deliverable. If you genuinely want to see how someone edits before committing, that belongs in a separate arrangement both people agree to on purpose.
In the invented Low Season example, why is the sequence worth sending?
It contains two tangled decisions: which take of Theo's answer the aftermath answers, and whether the scene can end on the aftermath or the departure needs to be filmed. Take 4 plays him cold and already gone; take 11 plays him tired and still trying. The missing departure is not coverage. The keys missing from the hook are a trace of the departure, not the event itself. The question is answerable from the footage, but the director cannot settle it alone.