Show a Film’s Release Sequence, Not a Wishlist of Platforms

<!-- ARTICLE BODY START -->

“Festival. Theaters. Community tour. Streaming.” The words suggest movement, but they do not yet describe a release plan. They leave out why the order matters, what must happen before each step, and who has agreed to anything.

A useful release page connects intended audience encounters to a conditional sequence of work. It distinguishes confirmed arrangements from intentions and alternatives. A recipient should be able to see the next decision, not merely the destinations the team would enjoy reaching.

Start with the encounter rather than the outlet. Perhaps the first priority is a screening in the place where the film was made, with participants able to attend. Perhaps it is timely at-home access for people who cannot reach a venue. Those aims can lead to different orders. A row of logos does not resolve the difference.

Give each stage a reason to exist

Consider Last Crossing, an original fictional observational documentary about the final months of a ferry service. The film follows the routines of passengers and crew, including the long gaps between departures. The team's own pitch page lists a festival premiere first. The sequence proposed below instead begins with a locally hosted encounter and moves to wider at-home access.

Within this exercise, the team wants people connected to the ferry to have an early opportunity to see the film together. The later at-home route would serve people who cannot travel to that gathering. These are proposed relationships to the work, not research findings about attendance or demand.

The team's initial pitch page reads:

Major festival premiere → regional theatrical tour → community events → global streaming.

In the imaginary deck, each stage is illustrated by an unconfirmed partner logo. No outlet or partner has actually agreed to take part.

Remove the logos and ask what the sequence promises. Why must a major festival come first? What does a theatrical tour add to the intended local encounter? Is global streaming a chosen access goal, an acquisition hope, or a description of rights the team has not established? The page has collapsed several different questions into one confident arrow.

A better starting statement is:

We intend an early locally hosted screening that can bring ferry passengers, crew, and other interested viewers into the same room. We then intend a wider at-home route for people unable to attend. Neither route is booked or contracted. The immediate work is to establish the host, materials, and conditions that could make the first encounter possible.

The ambition is more specific, not necessarily smaller. The statement explains what the team values without claiming access to everyone it hopes to invite. It also stops a desired venue or platform from becoming a substitute for the encounter itself.

Put prerequisites beside the step they affect

Before putting dates on the page, identify what would allow each intended stage to proceed. Some prerequisites concern the film and materials. Others depend on someone outside the team saying yes. Treat them differently.

For the fictional local screening, the team needs an appropriate viewing version, accurate information about available access materials, a host willing and able to proceed, agreed responsibilities, and confirmation from the responsible parties that the proposed event can take place on the intended terms. A hopeful conversation with a venue does not settle all of those questions.

For later at-home access, the team needs a route it is authorized to use, the required delivery materials, and agreement about the relevant timing and conditions. “We will upload it” is not an adequate description when the team has not established who can authorize that action or what earlier commitments affect it.

Keep the detail proportionate to the pitch. A recipient does not need the entire operational file, but a condition that could change the order belongs next to the affected stage. Burying it in a general disclaimer lets the main arrow keep making the unsupported promise.

A working note might distinguish the following:

The table does not mean that preparation is complete. It distinguishes kinds of work so the producer can see which task can be assigned and which outcome cannot be scheduled into existence.

Why the order is a real decision

In Sundance Institute's account of Columbus's 2017 release, the team considered simultaneous theatrical and digital release before choosing theatrical first. The reported Landmark arrangement carried a 90-day theatrical window, constraining how quickly the film could move to digital. That historical condition belongs to that arrangement, not to all films or current exhibitors.[^columbus]

The case shows why a release order needs its conditions attached. An earlier choice may affect what can happen later; a later opportunity may change the value of the earlier choice. The pitch should let a recipient understand that relationship without turning a historical example into a rulebook.

Sundance's account of Unrest describes physical and virtual encounters as part of its release design, including remote participation in selected theatrical events for homebound viewers.[^unrest] That is another historically specific approach, not an instruction to use the same service today. It makes the intended encounter visible as a planning choice.

For Last Crossing, “local first” therefore needs a reason stronger than habit. The reason in our scenario is the proposed shared encounter with people connected to the ferry. If the local event becomes impractical, the team must decide whether preserving that order is still more important than making the film available through another confirmed route.

There is no general answer hiding inside the arrow. The priority has to belong to this film and this release proposal.

Draw one alternative that changes something

An alternative should respond to a specific obstacle. Adding another desirable festival or streaming service below the main row only makes a longer wishlist.

For our fictional film, the obstacle is simple: the proposed local host may be unable to proceed. The meaningful alternative is not another logo. It is a different order—wider at-home access before a later local gathering—if the producer decides that earlier access should take priority and the alternative route is actually confirmed.

The working sequence can be written without graphics:

Prepare and verify the required film materials.
                    |
Can the local host and necessary arrangements be confirmed
at the producer's planned decision review?
           /                                  \
         YES                                  NO
          |                                    |
Locally hosted screening.          Decide whether to change the order.
          |                                    |
Wider at-home access, once         At-home access first, but only after
its route and conditions          its own route and conditions are
are confirmed.                    confirmed; local event stays optional.

The “no” branch contains a decision, not an automatic publication instruction. If the alternative's prerequisites are also unresolved, the film does not become released merely because the map reaches its last box. The producer records the unresolved dependency and revises the plan.

The proposed decision review is an internal checkpoint, not a public screening date. Its purpose is to prevent an unconfirmed host from holding the whole plan in an indefinite state by accident. The real team would choose a review point based on its actual production position and obligations, not copy an arbitrary waiting period from this example.

The alternative also changes the description of the eventual local gathering. Once at-home access has happened, the team should not continue presenting that gathering as the film's first public encounter. Update the claim when the sequence changes. Do not preserve attractive language after its factual basis has gone.

Label the state of the plan, not its level of enthusiasm

Use status words consistently. Confirmed should identify the particular arrangement or fact that has been established. Intended describes the route the team is currently pursuing. Alternative describes a route that would be considered under a named condition.

These labels work best at the level of the individual statement. “Release confirmed” is too broad if only a viewing copy is ready. “Host confirmed” is too broad if someone has agreed to read a proposal but has not agreed to present the film. Say exactly what the confirmation covers, who supplied it, and when it was checked in the working record.

For our fictional case, the producer's note might say:

Planning status, September 19, 2026: Local-first release is the intended route. No host or at-home outlet is confirmed. The team is preparing the material inventory and host brief. The alternative is at-home access first if the local event cannot be arranged, subject to a separate producer decision and confirmation of that route.

That date belongs to the invented planning scenario, not to an actual release. It demonstrates why the page should identify the state it represents. An undated page may remain in circulation after a host declines or a new arrangement changes the sequence.

Name the next owner and next evidence in the internal note. Here, the producer owns confirming the host's decision and the relevant arrangements. A response that merely expresses interest leaves the event unresolved. The person handling delivery reports which version and access materials are ready, rather than certifying that the whole release can proceed.

This division keeps a useful distinction intact: the team can do work that improves readiness, while an outside party still controls its own decision.

Reduce the working map to one readable pitch page

The public-facing or partner-facing page does not need every dependency from the working file. It needs the chosen priority, proposed order, material uncertainty, and relevant next step. Preserve those while removing the rest of the administrative detail.

For Last Crossing, the replacement page could read:

Intended first encounter — locally hosted viewing
Bring ferry-connected viewers and other interested local audiences together around the film. Host and event arrangements remain unconfirmed.

Intended next encounter — wider at-home access
Provide a route for people unable to attend. Delivery route, timing, and conditions remain to be confirmed.

Alternative — reverse the order when necessary
If the local event cannot be arranged, the producer will consider at-home access first once that route is authorized and ready. A later local gathering would not be described as the first public encounter.

Next dependency
Confirm the host's decision and practical requirements against the team's actual material inventory. No festival, venue, or platform booking is represented here.

The page is still a pitch: it explains the intended experience and the logic of the sequence. It simply refuses to use graphic certainty where the project has only a proposal.

A named logo can return when its relationship to the project is both established and appropriate to show. Until then, a functional description is more informative. “Locally hosted screening, host unconfirmed” tells the recipient something they can assess. An unexplained venue mark asks them to guess whether it means a booking, a conversation, an aspiration, or an aesthetic reference.

Update the consequence when new information arrives

Suppose the fictional host replies that it cannot run the event in the proposed period. Change the status in the working record and the pitch page. Then revisit the decision the map was built to expose: wait for a locally shared first encounter, or pursue the separately confirmed at-home route first.

Do not claim that the host's refusal demonstrates weak audience interest. It establishes the host's answer to this proposal. The team may need to investigate the reason, but the map should not invent it.

If the producer changes the sequence, update the invitation, version of the plan, and next dependency together. If the producer preserves local-first, identify the new unresolved requirement rather than leaving a declined host in the confirmed column. The useful result is a release proposal that can change without concealing what changed: a chosen encounter, a conditional order, and the actual decision needed next.

<!-- ARTICLE BODY END -->

Sources

[^columbus]: Sundance Institute, Distribution Case Study: Columbus, “Balancing Theatrical and Digital Windows.” Inspected September 19, 2026. Historical account of the 2017 release; the reported window is not a current universal rule or a forecast.

[^unrest]: Sundance Institute, Distribution Case Study: Unrest, “Creating an Initial Release Pattern” and the discussion of OVEE screenings for disabled and homebound audiences. Inspected September 19, 2026. Used only for the historical arrangement of viewing encounters, not current service availability, medical claims, or predicted results.

Frequently asked questions

What should a release page show instead of a list of destinations?

It should connect intended audience encounters to a conditional sequence of work, distinguish confirmed arrangements from intentions and alternatives, and show the next decision. A row of logos does not resolve differing aims.

Why does the order of release stages matter?

Earlier choices affect what can happen later, and later opportunities can change the value of earlier choices. In a Sundance account of Columbus's 2017 release, the team considered simultaneous theatrical and digital before choosing theatrical first; the reported Landmark 90-day window constrained how quickly the film could move to digital. That condition belongs to that historical arrangement, not to all films.

How should prerequisites be placed beside a proposed step?

Put a condition that could change the order next to the affected stage. Separate work the team controls from decisions or facts still external. For example, preparing a screening package is team work, while host acceptance and permissions are external; a hopeful venue conversation does not settle them. Burying conditions in a general disclaimer leaves the main arrow making an unsupported promise.

What makes an alternative meaningful rather than a longer wishlist?

It responds to a specific obstacle and changes something. For the invented film, if the local host may be unable to proceed, the meaningful alternative is a different order—at-home access first before a later local gathering—if the producer decides earlier access should take priority and the route is confirmed. The no branch is a decision, not automatic publication.

How should confirmed, intended, and alternative labels be used?

At the level of individual statements. Confirmed identifies the particular arrangement or fact established; intended describes the current route; alternative describes a route considered under a named condition. 'Release confirmed' is too broad if only a viewing copy is ready, and 'host confirmed' is too broad if someone only agreed to read a proposal. Say what confirmation covers, who supplied it, and when it was checked.

Further reading

• Pitch a Community Screening as an Event, Not Just a Film Link — If the first encounter is a locally hosted screening, this shows how to describe the evening, division of labor, and one decision a host can answer.
• Build Audience Access Into the Film Proposal, Not Just the Final Export — When the at-home route depends on captions, description, or transcripts, plan that access work alongside the proposal instead of promising a finished export later.