Pitch a Finished Screenplay Before a Director Is Attached
Pitch a Finished Screenplay Before a Director Is Attached
A finished screenplay with no director attached is not a hole in the project. It is a project with one job still open.
The usual mistake in that situation is not vagueness. It is the opposite. Wanting the film to feel real, the writer starts describing how it will be shot — and because nobody has been hired to shoot it, those sentences quietly invent a director, a shot plan, and an agreement that does not exist. A producer reads three paragraphs of camera behavior and starts wondering who signed off on it.
The fix is not to strip the visual thinking out. A pitch with no cinematic thought in it gives a reader nothing to want. The fix is to sort your sentences into three piles: what the script requires, what you suggest, and what you want help deciding. Almost every problem in this kind of pitch is a sentence standing in the wrong pile.
Here is how to do that sorting, roughly a page at a time.
Say what is open without making the script sound unwritten
Two facts need to sit side by side, and they must not bleed into each other. The screenplay is complete. The directing role is not filled.
Those facts do not imply one another. A finished draft does not mean the film is cast, crewed, or financed. An open directing role does not mean the story is still being figured out. When a pitch blurs them, a reader can't tell which risk they're being asked to take — the risk of a script that still needs work, or the ordinary risk of a film that hasn't found its director yet. Those are very different conversations.
So make the status explicit, early, in plain sentences: the draft is finished, here is its state if that state is anything other than final, and the directing job is open. Then say who is speaking. A writer pitching their own script on their own authority is a clear position. A pitch that never identifies its speaker drifts into a corporate "we" that sounds like a studio, a producer, and a director all agreeing in unison.
That "we" is where fabricated attachments are born. Use "I." It is more precise, and in this situation it is also more interesting.
Find the requirement in the scene, not in the feeling
A screenplay establishes certain things that any finished film must preserve. Call these requirements. They are not stylistic. They are the conditions that make the drama work at all.
Some requirements are informational: the audience must learn a thing the character does not. Some are about duration: a stretch of the film has to feel like it will not end. Some are about offscreen action: something must be heard and not seen, or the reverse. Some are about who is in the same room as whom.
The test is simple. If you change the requirement, the scene stops meaning what it meant. If you change the solution, it doesn't.
Solution is the second pile's word: the particular choice you are suggesting, the one that satisfies the requirement. That pile holds two separable things. One is the solution itself — the staging, the cut, the sound. The other is your reading of what that solution will do to an audience. They are not the same claim: one is a proposal about what to do, the other an impression about what it will produce.
When you write about effect, you are partly reading your own script — guessing what the page will do to a person watching it. That guess is legitimate and useful. It is also not the same thing as the requirement, and it should not be dressed as one.
Take an invented scene. Nura is pouring tea with her back to the table. Her mother lifts a letter off the table and hides it. The audience sees the concealment. Nura does not.
The requirement is the gap. The film has to put the audience in possession of a fact it withholds from Nura. Nothing about staging, lenses, or cutting is fixed by that, but the gap itself is not negotiable — remove it and there is no scene.
Now the inference — the other half of the second pile. If you write that this moment "makes the audience complicit with the mother," you have left the requirement behind and entered interpretation. Maybe it does. Maybe it produces dread, or a small flare of dislike, or nothing much until forty minutes later, when the same letter returns. That's your reading of your own work, and it can be a good one. Label it as a reading: my sense is, I think this lands as. It costs you nothing and it tells the reader exactly how much weight to give it.
One warning while you're at it. The pitch is a terrible place to improve the script. If your paragraph would work better with Nura pausing mid-pour, checking the script. If the page doesn't have the pause, don't put it in the pitch. You have just handed a reader a version of the film that doesn't exist, and the first person who notices will be the director you eventually want.
Two solutions are an exercise, not a menu
Once you know the requirement, you can show something a bare description can't: that the requirement survives more than one filmmaking decision. That demonstration is the most persuasive thing a directorless pitch can contain, because it proves you're inviting collaboration rather than collecting a pair of hands.
Back to the tea. Hold the room in one frame, both women in shot. The concealment happens inside Nura's blind spot, in the same ordinary space as the pouring, and the audience is simply present for it. Or: cut to the mother's hand for the removal itself and come back to Nura. The act gets its own weight, and the audience gets pulled a half-step closer to the person doing it.
Both versions preserve the gap. Both keep the letter hidden from Nura. They differ in emphasis. The wide frame keeps the concealment domestic and almost casual — it is a thing happening in a kitchen while someone makes tea. The cut turns concealment into an event. That's a cost as well as a gain: a close cut announces that something matters, and if the script wants the letter's significance to arrive late, the announcement spends some of that.
A model paragraph, written as the writer, might read:
The tea scene has one job: the audience learns the letter is hidden, and Nura doesn't. The script does that with her back turned to the table, so the concealment happens slightly outside her attention while she's occupied. Two ways to hold that. Keep the room in one frame with both of them in it, so it plays as an ordinary kitchen moment the audience happens to see. Or cut in on her mother's hand and come back, which gives the act its own beat and makes the audience a closer witness. I lean toward the second, because I think the not-knowing reads harder when we've been pulled away from her for a moment — but that's my guess about effect, not a requirement. I wrote the scene to work either way.
Three things are separated there. The requirement is stated flatly. The execution is offered as a suggestion, and the reason for preferring it is marked as an inference. And the last sentence says the latitude is real.
Here is the same material gone wrong:
In the tea scene we shoot wide to hold both women in frame, then our director cuts to the hand and back. We've decided the film stays in long static takes through the domestic scenes, which is what makes the withholding work.
Nobody in that paragraph exists. There is no director, so there is no director's cut. "We've decided" claims an agreed visual program, which claims a conversation that hasn't happened. And the last clause turns one possible approach into the reason the film functions at all, which forecloses the only interesting thing you had to offer.
The opposite failure is quieter and just as common: "a tense domestic drama with rich characters and a strong visual sensibility." That tells a reader nothing they couldn't have guessed, and it leaves the actual question — what does this film need a camera to do? — sitting in the room, unanswered. Specificity is not the problem. Unattributed specificity is.
One honest note on sourcing. The scene above is invented, and both versions of the paragraph were written for this page. Nothing here has been shot, shown to an audience, or sent to anyone. If you want a stronger version of this exercise, the useful material is real pitch documents from writer-led projects and writer-director projects, along with the creators' own account of which visual commitments were actually made at each stage. That comparison isn't available here, so the illustration stays fictional and makes no claim about how any real film was pitched.
References point at a question, not a look
References are the most abused sentence in film pitching, because the lazy version is short and sounds confident: this film is one thing meets another thing. That formulation imports a whole visual identity and presents it as settled. It also usually describes a film the reader has seen, which means you've now invited them to compare your unmade movie to a finished one, on the strength of a mood.
The useful version does something narrower. A reference can name a relation you want the audience to have, and then hand it over as a question.
Suppose you admire a film for holding a frame well past the point where the audience expects a cut. What you're borrowing isn't the film's look. It's a question: how long can this kitchen sit before the audience starts anticipating the letter? That question is worth putting in front of a director. The color palette, the aspect ratio, the lens — those aren't questions yet, and offering them as answers skips the part where anyone agreed to anything.
So attribute. What I keep coming back to is a patient framing that lets a room get uncomfortable — that's my suggestion, not a plan. Two sentences, and the reader knows precisely what is being offered: an avenue to discuss, not an execution that has been agreed, not a collaborator's endorsement, not a shot list.
This is also where you can get out of your own way. A reference you can't fully justify is still useful if you say what you're reaching for. A reference deployed as a finished visual identity is a small piece of impersonation, and it's the kind that gets found out in the first meeting.
Write the invitation to the director who hasn't arrived
Everything so far has been preparation for one short movement: saying what you want help with.
Name the creative problem, not the role. "We're looking for a director" is a job posting. "The problem I want a director for is holding an information gap across a scene without the audience feeling managed" is a conversation, and it tells a director whether they have anything to say about your film. Which, incidentally, is the thing you're trying to find out.
Keep the script's requirements intact while you do it. You can be open about execution and immovable about drama in the same breath, and the combination is reassuring rather than contradictory. A writer who will discuss anything is a writer with nothing to defend.
What you should not do is fill the empty chair with guesses — what a particular director would think of the material, whether they'd be interested, what their schedule probably looks like. That's not a pitch, it's a fantasy with a name in it, and it makes you look like you're shopping rather than collaborating. Say what the film needs. Let the reader decide who fits.
A practical way to keep the sorting straight is to check where each sentence would land if a director read it tomorrow:
- Script fact. "The script keeps the audience in the room for the concealment and keeps Nura out of it."
- Writer's suggestion. "I'd cut in on her mother's hand and come back to her, though I'm not attached to it."
- Writer's reading, flagged as a guess. "My sense is the not-knowing reads harder when we've been pulled away from her for a moment."
- Open question. "What I want help with is how long the audience should be made to sit with that before the scene moves on."
Nothing in that list is weaker for being honest about the open role. A pitch that admits uncertainty about execution while being exact about effect reads as a writer who knows the difference. That's a much better first impression than a phantom director's shot list.
End on the invitation, in your own voice:
The film I've written keeps the audience close to what Nura doesn't know. What I need from a director is a way to hold that — to pull us a half-step closer to her mother for the moment it happens without the scene turning into a wink at the audience. I have an idea about how, and I'll happily be talked out of it. I'd like to hear what you see in it.
Frequently asked questions
How should a writer describe a finished script when no director is attached?
State early and plainly that the draft is finished and the directing role is open, then identify who is speaking. Those facts do not imply each other, and a pitch that blurs them leaves the reader unable to tell which risk is being asked of them.
What separates a script requirement from a suggested solution?
A requirement is a condition any finished film must preserve for the drama to work — an informational gap, a duration, an offscreen sound, or who is in a room. If changing the requirement makes the scene stop meaning what it meant, it is a requirement; if changing it does not, it is a solution.
Should a writer include visual ideas in a directorless pitch?
Yes, but label them as suggestions rather than settled plans. Separate the proposed execution from the writer's reading of its effect; mark effects as my sense is or I think this lands as, since that is an inference about the script, not a requirement.
Why demonstrate two possible solutions?
It shows the requirement survives more than one filmmaking decision and signals that the writer is inviting collaboration rather than collecting a pair of hands. Two solutions are an exercise, not a menu, and they should not be written as decisions already made.
How should references and the closing invitation be framed?
Use a reference to name a relation or question you want the audience to have, attributed as a suggestion, not as a finished visual identity. In the invitation, name the creative problem rather than the role, keep the script's requirements intact, and do not guess what a particular director would think.