When One Film Pitch Needs Different Versions for Different Readers

Keep one deck when the readers need the same argument. Add an appendix when one needs more depth behind that argument. Make separate versions when the decisions are different enough that the opening, the evidence sequence, or the request must change.

The distinction is not between an important reader and an unimportant one. Nor is it a reason to make the project seem more experimental to one person and more settled to another. Tailoring changes the route through the film's current reality. It must not create several incompatible realities.

Sundance Collab's feature-film guidelines acknowledge different audience versions and optional supporting material.[^1] They do not give a universal test for choosing between them. The comparison here is an editorial decision method, developed through a fictional example—not a report that a particular package configuration won a project support.

Compare the requests, not the job titles

A cinematographer may need to understand the whole project's present shape before deciding whether to speak. A producer may already know the story and want to discuss a particular formal problem. Their titles do not tell you which information should come first.

Write down what each person has actually requested, what they already know, and what they can reasonably decide next. “Be impressed” is not a decision. “Read the script,” “discuss a development role,” and “consider a visual workshop” are different actions with different information needs.

For a fictional feature called The Glasshouse, imagine these requests:

Devin, a cinematographer who has read the screenplay: “Send the visual logic and the questions you would want to explore in a workshop.”

Ari, a potential producing collaborator who knows only the premise: “Help me understand what is developed, who is involved, and what another producer would be needed for.”

Devin does not need a long introduction to the screenplay before encountering its visual problem. Ari does need enough story and approach to understand the project, but also needs an accurate account of its present development. Neither has been asked to commit to making the film on the strength of a PDF.

A single opening could serve both badly: several pages recapping a script Devin knows, followed by diagrams Ari cannot yet connect to the project. The problem is not insufficient detail. It is that each person enters at a different point and is being asked a different question.

Establish what cannot change between versions

Before adapting the route, identify the shared facts. For this example, all names, dates, requests, roles, and project details are invented. They are stipulated facts within the exercise, not information about a real film.

At the first fictional cutoff, The Glasshouse has these particulars:

• Rowan Bell is its writer-director. The current screenplay is the second draft, dated September 1, 2026.
• The story follows Ruth, a conservator cataloging a neglected glasshouse. She discovers that its owner is quietly replacing rare plants with common ones and must decide whether to expose the substitutions or help make the collection ordinary.
• Rowan's current approach proposes stationary compositions that change position when Ruth crosses between the exhibition area and the work area.
• Celia Moss has agreed to work with Rowan on development. That role does not imply a production commitment, financing, or authority to promise a schedule.
• No filming location or cast is confirmed. The next work includes examining the screenplay's spatial logic and organizing the development process.

These facts can be omitted where irrelevant, but they cannot become stronger in a different version. “Location not confirmed” cannot turn into “our glasshouse” under a photograph. “Working on development” cannot become “production team in place” because the package reader might find it reassuring.

Keep the qualification with any claim that needs it. An appendix cannot rescue an overstated team page if the reader never reaches the qualification. Shorter copy remains responsible for the impression its surviving words create.

A shared factual reference need not become a new database. In this case, a dated note identifying the current script, approach, roles, and unresolved matters is enough. Name who confirmed each item in a real project. The note supports the documents; it does not replace the people responsible for their accuracy.

Give one deck and an appendix a fair trial

Separate files should not be the first answer to every difference. Suppose two recipients both need an introduction to The Glasshouse, its story, Rowan's approach, its current team, and the development invitation. One also asks for a closer look at the proposed spatial construction.

A shared deck with a focused appendix could work. The main route might move from Ruth's task and discovery to the formal approach, then to current development and the request. The approach page can direct the interested reader to two supplementary scene diagrams. The second recipient does not have to read the diagrams to understand what the film proposes.

The appendix earns its place by answering a defined question: “How does the camera's position change when Ruth moves between the two areas?” It is not a storage area for everything that was difficult to edit.

The main page could say:

The boundary changes the view. The camera holds its position within each area. When Ruth crosses from the exhibition space into the work area, the next composition gives her a different relation to the plants and the person tending them. The supplementary scene study compares the two positions; these are proposals, not confirmed location plans.

The appendix would then develop that particular relation. It should not introduce a new protagonist or reveal, for the first time, that the location is hypothetical. Those are not optional details behind an already intelligible argument.

This route has a useful maintenance advantage: the principal story, status, and request remain in one place. It also has a cost. The supplement can grow until the supposedly shared file contains two competing documents. A recipient may not know which material is essential, especially when the same information is repeated in slightly different language.

Use an explicit reference from the main page, give the supplement a descriptive heading, and keep the main route complete without it. Then ask whether the additional material really adds depth or whether it changes what the reader has been asked to decide.

Know when an appendix becomes a detour

Return to Devin's actual request. Devin has read the script and wants to examine a workshop possibility. Asking Devin to work through a complete introduction before finding the visual question in an appendix imposes the wrong route.

You could send a note directing Devin to that section. Sometimes that is sufficient, particularly for a familiar collaborator requesting one detail from an existing file. But if most of the main document is irrelevant and the meaningful request is buried at the end, a short separate version is cleaner.

Try two opening paragraphs for the two actual recipients.

For the cinematographer:

The current approach gives the exhibition area and the work area fixed but different viewpoints. Ruth's crossings change what we can see of the owner's substitutions. The question for a workshop is whether those changes make her shifting involvement legible without explanatory coverage. The location remains unconfirmed; the discussion begins with the September 1 screenplay and proposed spatial relations.

For the potential producing collaborator:

The Glasshouse is a fiction feature by writer-director Rowan Bell, currently on its second screenplay draft. Ruth's cataloging assignment becomes a choice about exposing or helping conceal the owner's substitutions. Celia Moss is working with Rowan on development. The project needs a clearer development sequence and examination of its spatial demands; this conversation would explore what an additional producing collaborator could take responsibility for.

The paragraphs are compatible but do different work. The first begins with a filmmaking problem a script reader can recognize. The second establishes a defined project, a limited current role, and an unanswered responsibility question. Neither invents a budget, a secured cast member, or momentum that the other must hide.

Their routes should follow those openings. Devin's version can move from the formal proposition to two proposed scene situations, then to the workshop question. Ari's can establish the story, its cinematic intention, the current materials and people, and the development need. The spatial studies may remain supplementary for Ari because they deepen rather than replace that argument.

A different cover alone would not accomplish this. Nor would changing every adjective. The justification for two versions is the different sequence of understanding needed for the requested conversation.

Compare the cost as well as the fit

The choice is not “generic” versus “personalized.” Each arrangement can be appropriate and each can fail.

Also consider how the file will travel. A supplementary page that works when attached to the whole deck may lose its explanation when forwarded alone. Put enough context on a likely standalone extract to identify the project, the material's status, and the question it answers. That does not require duplicating the entire introduction.

Conversely, avoid building a bespoke document for an imagined future reader whose request is not known. Keep useful source material available, but do not turn every possible reading condition into an active version that someone must maintain.

For the requests in this example, two versions are justified: a creative-workshop route for Devin and a project-development route for Ari. The latter may contain a small appendix. That is not an admission that the choice was inconclusive; the appendix solves a depth difference within Ari's route, while the separate file solves a different decision for Devin.

Treat an application as a request, not another cover

An application can require a different presentation even when the underlying film is unchanged. Follow its actual fields and current instructions rather than treating the general deck as an answer that must fit everywhere.

For a dated real example, Sundance Institute's 2027 Development Track “Next Steps” distinguished an updated synopsis, optional project updates, a current full screenplay, and optional visual material. That cycle is closed as of this article's September 19, 2026 inspection; the example is not an invitation to apply.[^2] Its relevance here is the separation of requested materials, not a universal application format.

In the fictional Glasshouse exercise, imagine an application asking for a story synopsis, the current team, a development question, and an optional visual sample. These are invented requirements for the example, not Sundance's rules.

Ari's opening paragraph cannot simply be pasted into all four fields. The synopsis needs to explain the story rather than sell a producing conversation. The team answer needs the limited current roles. The development question needs the unresolved work the program would help examine. The visual sample should illuminate that work without pretending to answer the written questions for the applicant.

A fictional development-question answer could read:

The next draft needs to clarify the point at which Ruth stops documenting the substitutions and begins assisting them. We want to examine whether the spatial progression makes that change visible or whether the current script depends on explanation after the fact.

That is different from the workshop request and the producing request. It identifies a development problem in the script. The film has not changed; the requested account of it has.

Trace a changed fact through the argument

Now change one shared fact. At a second fictional cutoff, September 15, Rowan confirms that Celia is no longer involved. No replacement producing collaborator has been agreed. The current screenplay and approach are unchanged.

A weak update removes Celia's biography and leaves everything else alone. A complete update follows the consequences into what each file asks the reader to do.

In the producing version, the current-team paragraph changes from:

Celia Moss is working with Rowan Bell on development. This conversation would explore how an additional producing collaborator could share responsibility for the next phase.

To:

Rowan Bell is currently developing the project without a producing collaborator. This conversation would explore a producing role in defining and coordinating the next development phase.

The change is not cosmetic. Ari is no longer considering how to complement an existing producing relationship. The open role now includes responsibility that was previously associated with Celia. That difference belongs in the invitation, not only in a biographical correction.

The closing request must change for the same reason. “Discuss the next steps with Rowan and Celia” becomes “Discuss the development role and next steps with Rowan.” If a supplementary working note says Celia is coordinating the spatial study, that note must now identify coordination as unassigned rather than leave an obsolete commitment alive.

The fictional application also changes. Its current-team answer can state that Rowan is the writer-director and no producing collaborator is currently involved. It need not invent a reason for Celia's departure. If its development plan relied on her coordination, revise that dependency too. Do not leave the plan describing resources the current-team answer has just removed.

Devin's creative version is different. In this example, it never named Celia, did not imply a producing team, and directed workshop discussion to Rowan alone. Its formal proposition and request can remain unchanged. Check it against the new factual reference and record that no copy change was necessary. “Review every active version” does not mean “rewrite every active version.”

Keep the record small enough to use

A compact record for the example now reads:

Identify the factual cutoff on the record and keep old files distinguishable from current ones. An earlier deck may remain useful as history, but it should not sit beside the replacement under another equally plausible “final” name. When correcting an already shared file, make the changed information explicit to the people relying on it; a new local export does not update their copy.

There is one limit versioning cannot solve. If Rowan has not decided which screenplay ending governs, sending one ending to Devin and another to Ari is not reader adaptation. It leaves the underlying creative question unresolved while concealing it in different documents. Get the maker's decision, or describe the uncertainty consistently where it matters.

For The Glasshouse, the result is two distinct reading routes and a separately answered fictional application, all tied to one current account of the film. The advantage is relevance. The obligation is upkeep: when a fact changes, follow it beyond the sentence where it first appeared and into the decision you are asking someone to make.

Sources

[^1]: Sundance Collab, Pitch Deck for Fiction and Nonfiction Feature Films, p. 1, questions about audiences and consistency; p. 4, addendum and additional optional elements. Inspected September 19, 2026. Supports the existence of audience-specific versions and supplementary material, not an explicit practitioner comparison of appendix versus separate deck. The decision test and worked reconciliation in this article are original editorial reasoning. No financing or credit-offering recommendations from the source are adopted.

[^2]: Sundance Institute, 2027 Development Track, “Next Steps” and closed-cycle notice. Inspected September 19, 2026. Used as a dated example of separately requested materials. The fictional application in the article has its own expressly invented requirements; no current eligibility, deadline, selection likelihood, or application advice is supplied.

Frequently asked questions

When is one pitch deck enough, and when are separate versions justified?

One shared deck works when recipients need the same main explanation and next decision. An appendix works when the main argument works for everyone but one reader needs specific supporting depth. Separate versions are justified when the requested decisions require substantially different entries, evidence sequences, or requests, such as a creative-workshop route versus a project-development route.

How should you decide what each reader needs rather than tailoring by job title?

Compare the actual requests, what each person already knows, and what they can reasonably decide next. For example, a cinematographer who has read the screenplay may need the visual logic and workshop questions; a potential producing collaborator who knows only the premise may need the story, current development state, who is involved, and what another producer would be needed for. Titles do not dictate which information comes first.

What facts must stay consistent across versions, and what may not be changed for reassurance?

Shared facts can be omitted where irrelevant but cannot become stronger in a different version. In the example, location not confirmed cannot become our glasshouse under a photograph, and working on development cannot become production team in place. Qualifications must stay with claims that need them; a shorter version remains responsible for the impression its surviving words create.

If one fact changes, what should be updated?

Follow the change beyond the sentence where it first appeared and into the decision being asked of each reader. When Celia Moss is no longer involved, the producing version’s current-team paragraph, closing request, and coordination note change; the application’s current-team answer and coordination dependency change. The creative-workshop version, which did not name Celia and directed workshop discussion to Rowan alone, can remain unchanged after review.

How should an application be handled relative to the general deck?

Treat an application as a request, not another cover. Follow its actual fields and current instructions rather than forcing the general deck to fit everywhere. In the example, a story synopsis, current team, development question, and optional visual sample each need different accounts; a producing-conversation opening cannot simply be pasted into all four fields.

Further reading

• What Is a Film Pitch Deck—and What Is It For? — Read this first if the deck's basic job is unclear; it defines the named reader, the decision, and why a deck supports the conversation rather than replaces it.
• One Film, Two Exhibition Forms: Separate Versions or a Flexible Work? — Read as a comparison for pitches that claim one work can serve different viewing conditions; it asks which version the reader is actually being asked to support.