Build a Film-Slate Pitch That Gives Each Project a Reason to Be There

A slate pitch should help someone make a choice across several projects. Start with that choice, not with a folder containing every film your company hopes to make.

Are you asking a development collaborator to consider a working relationship? Introducing a production partner to projects with different immediate needs? Presenting a specific producer-led package? Those conversations may draw from the same inventory, but they do not require the same selection, order or depth.

The slate’s job is to explain why these films belong in this conversation together. Each film still needs a recognizable identity, an honest account of its stage and a distinct next step. Putting three shortened decks in a row may introduce three stories without making the relationship between them any clearer.

Film Independent’s published Imaginar Producers Residency application guidance separates a slate overview—how the projects were selected and who the collaborators are—from individual project information such as status, history, goals and available creative material.[^1] That distinction is useful beyond the particular program. The overview explains a selection; the project records substantiate it. Neither can replace the other.

Decide what the recipient is being asked to consider

Write a private sentence identifying the decision this meeting could reasonably produce. Be concrete enough that you could recognize a useful response.

“Introduce our exciting slate” describes your activity. “Find out whether this collaborator would consider a focused development pass with the writer of our lead feature” describes a decision. It also tells you what the recipient needs to see: the film, the existing material, the development question, and enough of the producer’s wider work to understand the proposed relationship.

A broad first conversation does not have to end in a commitment. Agreeing which script to read can be a legitimate result. But “start a relationship” is too vague to determine what belongs in the deck unless you say what kind of work that relationship might involve.

For the example here, a fictional producer is meeting a potential fiction-development collaborator. The producer wants to introduce a feature with a defined writing task and show a little of the work around it. The meeting is not a request to finance three films, assemble a shared crew or approve a company strategy.

Keeping that purpose stable prevents the deck from changing its ask halfway through. If the final page suddenly requests production commitments across the whole slate, the earlier project descriptions have not prepared the reader for that decision.

Give each film a record before giving it a page

The producer’s fictional inventory contains three projects. The stages and materials below are part of the imagined scenario, not claims about real projects or attachments.

The Last Screening is a fiction feature about a projectionist who needs a print from the former collaborator whose restoration work she claimed as her own. A full draft exists, but the relationship through the middle needs a focused development pass.

Night Window is a short about a hotel receptionist who, during a night shift, must decide whether to keep helping a guest rehearse the call in which he will admit that he has lost his job. Its treatment is stable. The producer needs a partner to assess the production approach, including the lobby setting and night work.

The Sound Below is a documentary research proposal about technicians who listen for faults in underground water infrastructure. It has research questions and possible access routes, but no filming access is represented as secured.

Before designing matching cards, compare five things:

Each field changes a decision. Identity tells the recipient what kind of film they are considering. Stage prevents “we have a project” from implying “we have a script.” Available material tells them what they could actually examine next. The open need distinguishes a creative question from a production task. The final field forces the producer to justify the space a film occupies here.

If you cannot fill that last field without saying “we also love this one,” keep the project in the inventory while you decide whether it belongs in the meeting.

Use a shared interest without flattening the differences

These projects have a plausible connection: people doing work that places them inside difficult relationships or makes them attend to something others overlook. That may help explain the producer’s interests. It does not make the projects interchangeable.

For the development meeting, an opening could read:

We are developing fiction about the responsibilities people acquire through their work. We would like to begin with The Last Screening, whose current draft has a specific relationship question to address. Night Window, a short at treatment stage, gives a second view of that interest and the work we are building around it.

The introduction gives the slate a center without pretending the two films have the same need. It also avoids a manifesto so broad that any story could fit beneath it.

You could mention the documentary when discussing the company’s wider interests, but it does not need a full project section in this pitch. The potential collaborator has not been asked to solve documentary access, and the research has not yet established a film they can assess in the same way as the feature draft.

Omission is not a judgment that the documentary is less valuable. It is a judgment about what this reader can use in this conversation. Save it for a discussion in which its actual research question and access limits can receive proper attention.

Do not manufacture a shared production advantage to strengthen the connection. Two films involving work at night do not thereby share locations, permissions, crew arrangements or a schedule. A creative relationship between projects can be real while their practical requirements remain separate.

Make the lead project earn its extra attention

The Last Screening leads because it gives the proposed collaboration something tangible to do. Its section should establish the story, the existing draft and the specific question for development. It need not become a complete single-film deck nested inside the slate.

A short introduction could say:

On a cinema’s final night, a projectionist needs a replacement print from the former collaborator whose work she claimed as her own. A current feature draft and synopsis are available. We are seeking a focused development conversation with the writer about how their changing relationship carries the middle of the film; we are not presenting that pass as finished.

That paragraph permits a useful next question: which turns currently exist, and where does the relationship need work? “A powerful, fully realized drama ready for its next chapter” would make the unfinished task harder to discuss.

The lead may deserve more story detail and a more precise development note than the short. That is not unequal affection expressed through page count. The recipient needs more information to judge the work being proposed.

Night Window can be introduced briefly with its premise, treatment status and production need. It shows a related interest without becoming a second development assignment by implication. If the recipient wants to see more, the producer can agree to share the separate treatment. The slate does not need to answer every question about every film before the meeting can begin.

There is no useful universal rule here that the lead gets three pages and the others get one. Choose depth by the decision. If the slate comparison is clear but one project needs a longer discussion, that may be the point to move into its separate material rather than keep expanding the overview.

Let the status language survive the design

A coherent visual system can help someone compare projects. It can also conceal differences when every card says “in development” beneath equally finished artwork.

Prefer stage descriptions that name the relevant condition: “full draft; relationship pass needed,” “stable treatment; production approach open,” or “research stage; access not secured.” You need not create a complete production-management system in the deck. Explain the condition that changes what the reader can sensibly do next.

A public production-company slate offers a bounded example of this distinction. UNLEYEK’s own slate page identifies projects by format, writer and stage: its displayed entries distinguish, for example, KINIG as a feature in advanced development and THE SHARED as a short in pre-production.[^2] Those are the company’s published descriptions, not independently verified production statuses. The useful observation is how separately labeled projects remain distinct within one presentation.

In your own pitch, keep evidence and intention apart. “Writer approached” is not “writer attached.” “Potential filming access identified” is not “access secured.” “Treatment available” is not “screenplay available.” Do not let a polished image, a name in a large typeface or an optimistic heading erase the distinction made in the small print.

The same applies to the producer’s role. State what you actually represent for each project rather than using a collective “our” to suggest identical authority across different relationships. When the scope is unresolved, describe the current conversation instead of turning it into a claim of control.

Date the working slate and check the status descriptions before sharing it. If one project has changed, update that record. You do not need to make the other projects appear to have moved forward just to keep the presentation symmetrical.

Change the meeting, not the facts

Now put the same producer in a different conversation: a potential production partner is open to discussing how a short could move from treatment toward production.

Night Window becomes the lead. The treatment and the lobby and night-work assumptions are now directly relevant. The feature can become brief context for a possible longer relationship, provided it is still described as needing development. The documentary remains outside the present task.

The new opening might read:

We would like to discuss the production approach for Night Window, a short with a stable treatment. The immediate task is to assess feasibility and agree what needs resolving before a production plan can be set. Our feature, The Last Screening, remains in development and is included only as context for the work ahead.

Nothing about the files has changed. The short has not acquired a completed screenplay, confirmed location or locked schedule because it now comes first. The feature has not become less developed because it now comes second. Selection and emphasis changed because the recipient’s possible contribution changed.

This is a useful check against opportunistic rewriting. Put the two versions beside each other and compare their factual claims. Differences in emphasis are expected. Differences in stage, availability or attachments need an actual explanation, not just a more persuasive meeting strategy.

It is also where a slate can become unnecessary. If the production conversation genuinely concerns only Night Window, lead with that project’s material and leave the wider slate for a brief introduction or later discussion. More films do not automatically make a stronger proposal.

End with the decision you prepared

For the fiction-development meeting, the final ask could be:

Would you consider reading The Last Screening and discussing a focused development pass with its writer? We can share the current draft, synopsis and the specific questions we would like that conversation to address.

For the production-partner meeting, it could instead be:

Would you review the Night Window treatment with us and help identify the production assumptions that need resolving before we plan the shoot?

These are different requests supported by different parts of the same inventory. Neither asks the recipient to accept responsibility for every project in the company.

A financing proposition would require another conversation and the responsible producer’s actual terms and evidence. Shared themes, multiple titles and attractive comparison pages do not establish pooled resources or reduced financial risk. Do not append those claims as a closing flourish to a creative-development pitch.

The finished slate should leave you with a selected set of projects, a justified lead and a reason for every inclusion. Keep the omitted work in your records. Its absence from this deck leaves room for the conversation in which it can be presented honestly.

Sources

[^1]: Film Independent, Imaginar Producers Residency, “How to Apply” → “Slate and Project Information,” especially the separate slate overview, project sourcing and project-information fields. Published program guidance. Inspected 19 September 2026. Used as an example of document purposes, not current application advice. The page contains historical and inconsistent cycle dates; no deadline, eligibility, financial term or live opportunity is relied on here.

[^2]: UNLEYEK, Our Slate / In Development, displayed KINIG and THE SHARED entries. Production company’s public slate. Inspected 19 September 2026. This is the company’s public presentation, not a private pitch deck or independent confirmation of each project’s current status.

Frequently asked questions

What should determine which projects appear in a slate pitch?

Start with the decision the recipient is being asked to consider. In the example, a fiction-development meeting leads with The Last Screening, includes Night Window briefly, and omits The Sound Below because it has no immediate role in that conversation. Omission is not a judgment that a project is less valuable; it is a judgment about what this reader can use in this meeting. Each inclusion should have a reason beyond we also love this one.

How can projects share a theme without being flattened into the same pitch?

A shared interest can help explain the selection, but it does not make projects interchangeable or create shared production advantages. Two films involving night work do not thereby share locations, permissions, crew arrangements or a schedule. In the example, the feature needs a relationship development pass, the short needs assessment of its production approach, and the documentary needs research and access conversations.

What status language should a slate use?

Prefer stage descriptions that name the relevant condition, such as full draft; relationship pass needed, stable treatment; production approach open, or research stage; access not secured. Keep evidence and intention apart: writer approached is not writer attached, potential filming access identified is not access secured, and treatment available is not screenplay available. Do not let polished design or a name in large type erase those distinctions.

How does the slate change when the recipient changes?

Selection and emphasis change because the recipient's possible contribution changes. For a production partner, Night Window becomes the lead, The Last Screening becomes brief context, and the documentary remains outside the present task. Nothing about the files has changed: the short has not acquired a completed screenplay, confirmed location or locked schedule, and the feature has not become less developed. Compare factual claims between versions; differences in emphasis are expected, but differences in stage or availability need an actual explanation.

How should a slate end?

End with the decision you prepared. For the fiction-development meeting, ask whether the recipient would read The Last Screening and discuss a focused development pass with its writer. For the production-partner meeting, ask whether they would review the Night Window treatment and help identify production assumptions that need resolving. Do not append financing claims, pooled resources or reduced financial risk as a closing flourish to a creative-development pitch.

Further reading

• Sequence a Film Pitch Deck So Each Page Makes the Next One Possible — Read when the order of the slate feels arbitrary, for a page-by-page method of giving each item a job and placing the knowledge it depends on beforehand.
• Pitch an Anthology Feature Without Treating It as a Film Slate — Read when several shorts might be a feature rather than a slate, to tell editorial adjacency and a collective proposition apart from separate component pitches.