Festival Screener Version Management When You Have Six Submissions Running Parallel

If you are submitting a documentary or indie feature to film festivals seriously, six simultaneous submissions running parallel is not unusual. Some projects have twenty or more in flight during peak season. Each festival may have different technical requirements, different cut versions, different subtitles, different run times. Each screener needs to be tracked: who has access, whether it has been watched, and whether it is still live.

Festival screener version management across multiple simultaneous submissions is one of those workflow problems that looks manageable until you are in it. Then you are updating spreadsheets at midnight trying to remember whether the Berlin screener had English or German subtitles, or whether the Sundance link was the theatrical cut or the broadcast cut.

The Specific Problems That Sink Festival Season

From working with documentary producers who run serious festival campaigns, I have seen a few failure modes repeat themselves:

Wrong version at the wrong festival. The broadcaster-approved cut has different music than the theatrical cut. The festival you submitted to has very specific rules about music rights. You submitted the wrong version and did not notice until a programmer flagged it.

Screener links stay live after rejection. A festival passes on the film. The screener link is still open. Someone at that festival shares it internally with colleagues who might refer it to another platform. You have lost control of the material without any deal in place.

No record of who watched. A festival programmer says they never received the screener. You cannot tell whether the link was opened. You are stuck reconstructing an email chain to prove submission.

Version confusion at the festival itself. You uploaded a rough cut to a screener platform months ago and forgot to update it when picture was locked. The programmer watched the wrong version.

Building a Version Registry

Before submission season starts, build a simple registry of every version of your film that exists or may exist:

Every festival submission links to a specific row in this registry. When you create a screener link, you record which version it serves. When you update a version, every submission that used the old version gets flagged for review.

One Review Project Per Version, Not Per Festival

The structural mistake most teams make is organizing screeners by festival: a Sundance folder, a Berlin folder, a SXSW folder. This makes it feel organized but it creates version chaos. If you update the theatrical cut, you have to update every festival-specific folder.

Organize by version instead. Create one project in PlayPause for each version of the film. When you create a screener link for a festival, it points to the appropriate version project. If the theatrical cut is updated, you update one project and all links pointing to it serve the new version.

Each festival gets its own link with its own settings: password, expiry date, download disabled. But the underlying film version is managed centrally.

Review_Cut_v4.mp4In Review

212160p · ProRes

00:34 / 02:18

SR

Sarah 0:34

Frame-accurate note, everyone sees the exact same thing.

Managing Access and Expiry Across the Season

Festival screeners should have expiry dates. Not for trust reasons but for practical ones: a screener that was submitted in January and is still open in September has outlived any legitimate use. Programs have been selected. The festival's decision has been made. The link should be closed.

For each submission, set the expiry to a reasonable window: submission deadline plus sixty days is a common approach. That gives the programming team time to watch during their selection process without the link living indefinitely.

For your own records, note the expiry date alongside each submission in your tracking system. Two weeks before expiry, check whether the festival has made a selection. If they have passed or the decision is still pending and you want to extend access for a follow-up conversation, renew the expiry intentionally rather than leaving it open by default.

For secure screener distribution principles that apply equally to sales agents and festival circuits, see our guide on the right way to share a locked cut with a sales agent before a market.

Tracking Viewing Across Multiple Programmers

Major festivals often have teams of programmers. Your screener link may be shared internally. Knowing that at least one programmer watched the full film is more valuable than knowing the link was opened without context.

PlayPause gives you view data: when the link was opened, how far the viewer got, and whether they came back. This is useful for follow-up: if your screener was opened but only watched for ten minutes, a follow-up email a week before programming decisions are announced is a reasonable step. If it was watched twice to completion, you have a different conversation.

Handling Technical Requirement Variations

Different festivals have different technical requirements. Some want a DCP, some want ProRes, some want H.264. Some require specific metadata embedded in the file. Some have strict requirements about leader and tail.

For screener purposes (as opposed to theatrical delivery), most festivals accept a good-quality web-ready file. But the version you screen them still needs to be the correct cut, with the correct music, with correct subtitles if required.

For productions managing multiple cut versions simultaneously for different exhibition contexts, see our guide on managing multiple cut versions for a broadcaster, festival, and streaming delivery for a broader view of how to keep these tracks clean.

Keeping the Registry Current Through Season

Festival seasons run for months. Versions get updated. New festivals open submission windows you did not plan for. Festivals you submitted to months ago suddenly have second-round review and ask for an updated screener.

The registry only works if you maintain it. Build a habit of updating it every time:

• A new version of the film is created
• A new submission is made
• A screener link is shared
• A festival responds (positively or negatively)
• A screener link is expired or updated

At the end of festival season, the registry becomes a complete record of the film's submission history: which versions were shown where, who watched, what the outcome was. That record is valuable for future distribution conversations.

For keeping documentary footage approvals organized across a long production, our piece on keeping archive documentary footage approvals organized across a year-long edit covers the documentation discipline that carries through to festival season.

For productions where access control is a priority, our guides on sending secure festival screeners without leaks and how to watermark and track a rough cut screener sent to potential co-producers go deeper on protecting pre-release material.

If your current festival season management involves a Google Sheet, a folder of exported files, and a lot of memory, it is worth tightening the system before submissions get complex. PlayPause is free to start, and the Creator plan at $9/month gives you enough to manage a full festival campaign for one film. The tracking alone is worth it.