Prepare for a Film-Development Interview Without Repeating the Application

An invitation to talk about a project you submitted puts you in a strange position. You have already made your case in writing, at length, to roughly these same people. Now you have twenty-five minutes and your voice, and the temptation is to compress the application and deliver it well.

That's the wrong preparation. The written application answers what is this? A development conversation is usually trying to answer something else: how does this filmmaker think about the work, and what does it need next? Those questions need different material. What travels well in a room is not a summary; it's a handful of scenes you can account for, an honest description of what isn't settled yet, and a few questions only the program can answer.

Prepare for the invitation you actually received

Read the invitation twice, the second time with something to write with. Pull out four things:

• Purpose. Is this a development conversation, a general meeting, an interview that feeds a selection decision, or a check-in before a decision is announced?
• Format. One-to-one, a panel, a small group of applicants, a group discussion with staff observing. These behave differently, and the ones with more people give you less room to develop a single answer.
• Requested preparation. Anything you were asked to send or bring, and by when.
• Named participants. If names are given, the roles attached to them may tell you whether you're speaking to programmers, story staff, a producing team, or former participants.

If a practical instruction is missing — length, platform, whether pages should be sent ahead, whether anyone else will be in the room — ask the contact. That is an administrative question, it gets answered quickly, and asking it costs you nothing. What you should not do is fill the gap by importing the routine from a different program you have heard about or read about. Programs differ in how they run these conversations, and a confident routine borrowed from somewhere else can be worse than no routine, because you'll spend the hour performing a format nobody in the room is using.

Keep two lists, separate. One is access and logistics: call time, link, travel, materials, who else will be present. The other is artistic preparation. Mixing them means you spend your last evening before the conversation worrying about a video link.

One more thing about research. Public descriptions of a program's mission are useful for exactly one job: working out whether your project belongs there. "We support formally ambitious first features" tells you what the program says it is for. It does not tell you what a particular panelist will ask, and reading it as a set of clues about the questions is a guess dressed up as diligence. Prepare from your work and from the invitation in front of you. If you want to know how a program runs its conversations, the honest sources are its own published guidance for invited applicants or a first-person account from someone who has been through it — and even then, that's one account, not a script.

Return to the version they read

You have kept working since you submitted. The pages they have may be two drafts behind where your head is now. So open the application and the work sample exactly as they were sent, and read them the way a stranger would.

Then mark a small number of consequential decisions — not themes, decisions — that you can point at inside a scene. A character chooses something. A viewer learns something, or is deliberately kept from it. A scene ends where it ends. Aim for three to five marks, no more. Each one gets a sentence: scene or page, what the choice is, and what the viewer knows at the end of the scene that they didn't know at the start.

If you have a scene where a character makes a choice and you cannot say what the viewer is meant to take from it, that's worth noticing now rather than in the room. It might be a scene that needs work. It might be a scene you've never had to justify to yourself.

Then, separately, write down what has changed since submission. One line each, with dates. This matters for an ordinary reason: an answer that describes a version your listeners don't have is confusing, and it sounds like you're improvising even when you aren't. "Since I sent it, I've moved the confrontation out of the kitchen and into the car, and here's what that fixed" is a good answer. Describing the car scene as though it were in the pages they hold is not.

The object you're producing is a short scene-to-decision sheet. One page. It is not a second application and not a fresh synopsis. If you find yourself writing another logline, stop.

Explain an unresolved choice precisely

Two failure modes bracket this section. At one end: "the middle doesn't work." Nobody can respond to that, including you. At the other: "I've solved everything." That may feel safer, but it removes the conversation you were invited to have, and it's rarely true.

The usable middle is a choice, two live options, and what each one changes. That sounds abstract, so here is a fictional project, constructed for this article. It isn't real, and no program's response to it is being described.

Two siblings, Dana and Wes, are emptying their mother's storage unit over a weekend. In the submitted scene on page 14, Dana finds a key in a shoebox, puts it in her coat, and tells Wes the box is empty. The filmmaker's intention is that the audience understands the action — a deliberate concealment — before it learns the motive.

Here's the answer that recites the plot:

"It's a two-hander about a brother and sister clearing out their mother's storage unit over a weekend. There's a key, and it becomes important later. Really it's about inheritance and silence, the things families don't say. Family drama with a bit of a thriller engine."

Everything in that may be true. None of it gives a listener anything to hold. The only question it invites is what happens next, which is the plot's job, not yours.

Here's the answer that locates the decision:

"On page 14, Dana finds a key in a shoebox, pockets it, and tells Wes the box is empty. The scene is built so the audience is ahead of Wes and behind Dana. You see the action, you know it's deliberate, and you don't know why. That's the engine of the film: for the next hour you're watching a woman decide, scene by scene, whether to keep a lie going."

Now a listener can ask real questions. Why that object? Does Wes suspect? What does she think she's protecting?

Notice that the second answer doesn't resolve anything. It does something more useful: it names what's fixed and what's open. In this example, what's fixed is that the audience gets the reason at some point, that Dana never says it out loud, that there's no confrontation scene, and that the unit empties in a single weekend. What's open is where the reason lands and what Wes gets to do afterward.

Two things to avoid here. Don't manufacture decisiveness — if you announce a solution you haven't actually chosen, you'll spend twenty minutes defending it, in front of the people you'd most want to think alongside. And don't go the other way and let the film dissolve: "it's about ambiguity, so the back half could be a lot of things" is not an unresolved choice. It's no film yet. The test is whether you can say, in two separate breaths, what the film is currently doing and what you don't yet know it should do.

If the program's guidance or invitation describes particular development support — a script editor, a table read, a workshop with other projects — connect your open question to that. An open question is more useful in the room when the room can actually help with it.

Rehearse an answer that can survive a follow-up

The shape you're practicing is short: the question, one scene, the reason for the choice, and its current limitation. Four beats. Say it out loud, because silent reading hides the places where you lose the thread.

The point of the shape is to survive interruption. A follow-up is not an accusation; it's the conversation working. In the fictional example, the follow-up to the storage-unit answer is: why does the motive arrive later?

A rehearsed answer:

"Two options are still live. In one, the audience gets the reason just past the midpoint, and Wes finds the key himself not long after, so the second half is the two of them carrying something one of them still won't say. In the other, the reason stays back until the last ten minutes and lands only with the audience. Wes leaves the film not knowing. The cost of that second version is that he has nothing new to act on in the back half — he'd be running on suspicion rather than knowledge. What's fixed either way is that Dana never says it out loud, and there's no confrontation scene. What I'd want to work on is whether Wes's second half can carry the film on suspicion alone, because that's what decides it."

That answer names two options, what each changes, what stays fixed, and where the actual developmental question sits. It also doesn't pretend to a preference. If you rehearsed with a partner who asks "so which one is it?" the right move is to repeat the deciding question, not to invent an answer for the sake of sounding finished.

Rehearse with someone willing to interrupt and to ask for a second example. If you catch yourself three sentences into synopsis, that's the signal to stop and go back to the scene. If you can't find a scene that supports the explanation, that's information — either the preparation note needs revising or the decision isn't really visible in the script yet. Fix the note or admit the gap. Polishing the recital only hides the problem from both of you.

Bring questions about the work, not supposed winning answers

Prepare two or three questions tied to something the invitation or the program's own guidance actually says. Good ones are about the work and its conditions: how a mentor pairing is made, what a table read requires of a project at your stage, how much revision happens between sessions, whether the program expects a full draft at the end or a treatment, what happens to projects that arrive with one section still undecided. These are answerable, and the answers change what you'd do with a place if you got one.

The question to avoid is the one that asks the interviewer to solve your film on the spot. "What do you think I should do with the second half?" puts them in an awkward position: any answer becomes a rewrite you didn't commission, offered in a conversation too short to support it. There's a version that works — asking how a particular piece of support has been used by other projects at your stage — but it has to be grounded in what the program says it provides, not in a hope that someone will hand you the answer.

While you're there, notice what actually becomes clearer. Not whether people smiled, not who leaned back, not whether the tough question was a bad sign. You cannot read a selection outcome out of a room, and trying to is a good way to leave with a false conclusion and a worse memory of the conversation. Write down instead what you now understand better about the film. If a question changed your mind about the midpoint, that's the real return on the hour.

The one-page preparation sheet

Keep everything on a single page. It should be readable in the ten minutes before you walk in.

The invitation. One line: purpose, format, length, participants, anything to bring.

Scene-to-decision sheet. Three to five rows.

Open questions. Two or three, each with two live options, what each changes, and what stays fixed.

Changes since submission. Dated, one line each, kept visibly separate from the pages they hold. For the fictional project: 11 March — cut the submitted draft's final scene, where Wes drives home alone. The film now ends as the two of them load the last boxes into Dana's car. That keeps the audience inside the weekend and inside Dana's decision; the earlier ending handed the last word to Wes, who doesn't know what the film knows.

Questions about the program's work. Two or three, each tied to something the invitation actually says.

One sentence. What I want to understand better about the film when I leave.

That last line is the one that keeps the sheet honest. You are not there to prove the project is finished; you are there to show how you work on it. If the middle is still undecided when the conversation ends, that isn't the interview failing. It's the work continuing, with better questions than you had when you walked in.

Frequently asked questions

What should I prepare for a development conversation after I have already submitted a written application?

Do not compress the application and deliver it. The written application answers what the work is; a development conversation usually asks how the filmmaker thinks about the work and what it needs next. Prepare a small number of scene-level decisions, an honest description of what is not settled yet, and a few questions only the program can answer. Keep logistics separate from artistic preparation.

How should I handle missing practical details such as length, platform, or whether pages should be sent ahead?

Ask the contact. These are administrative questions and usually get answered quickly. Do not fill the gap by importing a routine from another program you have heard about. Programs differ in how they run conversations, and performing a borrowed format can be worse than having no routine.

How can I describe an unresolved story choice without sounding vague or pretending it is solved?

Name a choice, two live options, and what each option changes. Also state what stays fixed. Avoid both 'the middle does not work' and 'I have solved everything.' If the program describes particular development support, connect your open question to what that support can actually help with.

What belongs on the one-page preparation sheet?

Include one line on the invitation, a scene-to-decision sheet with three to five rows, two or three open questions with live options, dated changes since submission kept separate from the pages they hold, two or three questions about the program's work, and one sentence about what you want to understand better about the film when you leave. It is not a second application or a fresh synopsis.

How should I rehearse answers so they survive a follow-up question?

Practice four beats: the question, one scene, the reason for the choice, and its current limitation. Say it out loud with someone willing to interrupt and ask for a second example. If you catch yourself three sentences into synopsis, stop and return to the scene. If no scene supports the explanation, revise the preparation note or admit the gap.

Further reading

• Reapply With a Revised Film, Not Just a Revised Application — Read this if you need to describe what changed since you submitted, so the revision is located in the material rather than in refreshed wording.
• Write a Nonlinear Film Synopsis Without Straightening Out the Film — Read this to map viewer knowledge scene by scene, keeping when events happen separate from when the film lets the audience understand them.