Coresee

BlogGuidesPost-production

How to Shortlist and Compare Persistent Video Platforms for Post-Production

8 min readNovember 9, 2026

Summarize

TL;DR

Build a shortlist by elimination. Write your screens first: the security obligations your productions actually carry, the support hours you need, how fast an outside vendor must be able to join, and your minimum exit terms. Build the long list from peers and your own vendors, send one short information request, then run identical demos on your own material, including a deliberate failure segment and an evening session. Get written terms from every finalist, run one real session, and set a decision date.

Why build a shortlist by elimination?

Screening and comparing are different jobs. Screening asks whether a candidate is eligible at all and gives a yes or no. Comparing asks which eligible candidate is better and gives a judgment. Run them together and a strong demo can override an unmet requirement, which is the most common way facilities shortlist a vendor they can’t actually use.

Screening first also protects the scarcest resource in the process: time from post supervisors, assistant editors and technical staff during periods when they’re already busy. This guide covers the buying process. For what to look for in the platforms themselves, including fidelity, re-encoding, color and content security, see our guide to persistent video collaboration priorities for post-production.

From long list to decision

  1. 1

    Write the screens

    Security obligations, support hours, onboarding time and exit terms, before contacting anyone.

  2. 2

    Build the long list

    From peers, your own outside vendors and industry associations.

  3. 3

    Send one short request

    Evidence, not descriptions. It removes most of the long list on its own.

  4. 4

    Run identical demos

    Your material, your connection, a failure segment and an evening session.

  5. 5

    Check and decide

    Independent references, one real session, written terms from every finalist, a date.

Each stage removes candidates before the next, more expensive one. Writing the screens down first is what stops a good demo from overriding a requirement.

Which screens come first?

Security obligations your productions actually carry. On studio work, contracts often reference the MPA Content Security Best Practices, which the Trusted Partner Network maintains along with its assessment program.1 Read what your contracts require. Some require vendors to hold a specific assessment, which is a hard screen. Many set rules for how material is handled, which several kinds of platform can meet, so ask each vendor how. Applying the strictest standard you’ve heard of, instead of the one you’re bound by, removes suitable candidates for no reason.

Support hours. Post work runs in the evenings and at weekends. Ask for coverage hours in writing, and who is reachable when a session fails at 9 p.m. with an executive watching.

Onboarding time. Decide the longest your productions can tolerate between requesting access for an outside vendor and that vendor joining a session, and remove candidates who can’t meet it.

Exit terms. How long material is kept after a show wraps or the contract ends, and what deletion is committed to, because productions often require material to be destroyed on a set date. Vague answers here become expensive exactly when a production wraps. Ask what can be exported too. It matters most for anything that will exist only in the platform; if your masters, notes and decisions live elsewhere, a platform without export can still pass this screen.

Three finalists is right for most facilities. Two gives no real comparison; four or more usually means screening was incomplete. If honest screens leave only two, go with two instead of relaxing a screen to reach three.

Where do the candidates come from?

Start by knowing what kind of supplier you need. Vendors from different origins use the same words, and “persistent room” means something different to a company that began in file-based review than to one that began in live video transport.

Four kinds of supplier, and where each is strongest

  • Persistent workspace vendors

    The always-on room is the product: media, layouts and participants kept between sessions, several sources at once, browser access for guests.

    NeedsClear answers on support hours and exit terms.

  • Review and approval platforms

    Version control, frame-accurate comments and approval trails, with live sessions usually added later.

    NeedsProof the live layer handles directed sessions, if you need them.

  • Broadcast and contribution vendors

    Professional video transport: signal handling, encoding, redundancy and facility integration. Strong for live camera feeds.

    NeedsEngineering staff to run it, or an integrator who will.

  • Remote workstation access

    Gives one artist control of a machine. A complement for hands-on work, not a shared review room.

    NeedsA separate tool for group review.

Each kind of supplier tends to be strongest where its product started. Many facilities end up with one per workflow; ask every vendor what its product was originally built to do.

Then build the long list from people, not search:

  • Peer facilities running comparable work. Ask whom they use, whom they stopped using, and what went wrong after signing.
  • Your own outside vendors. Editorial houses, visual effects vendors and colorists join other facilities’ sessions constantly and know which platforms are pleasant to join.
  • Industry associations. The Hollywood Professional Association is a non-profit member association connecting businesses that provide creative and technical expertise, tools and infrastructure for professional content creation, distribution and archive.2 Its members and events map who serves this market.

What should the information request ask?

Ask for evidence, not descriptions. “Do you support persistent rooms?” gets a yes from everyone. A written session specification, security documentation, a support coverage statement and exit terms give you something to compare.

Ask what “persistent” means in their product: does the room keep its media, layout, participant list and permissions between sessions, or only its address? And ask for any latency figure on a stated basis. The IETF defines streaming latency as the glass-to-glass time from an event to its playback on the viewer’s device, including encoding, decoding and buffering, not just network transit.3 A figure with no basis isn’t a specification.

Keep it short. A long questionnaire sent to eight vendors creates work for everyone and rarely changes the outcome. A focused one gets answered properly by serious vendors instead of being handed to a proposal team.

How do you make demos comparable?

Assume a vendor’s own demo is optimized: their content, their infrastructure, small audiences. So standardize everything before the first session: same material, same participants, same connection, same length, same things recorded. And drive it yourself, with your footage on your connection and your people joining from their usual locations.

Run each session in three parts: a short vendor orientation, a run led by the facility, and a deliberate failure segment in which a path drops, someone joins on a weak connection and attendance exceeds the plan. The third part is where candidates separate. Run at least one session in the evening at realistic scale, when your upload is already busy with renders and transfers, and see whether vendor support picks up.

Record the same measurements every time:

  • Time to set up the room
  • Time for a guest to join from outside
  • Observed delay on a directed action, such as “stop there”
  • Visible artifacts on your hardest material
  • What happens when a weak-connection participant joins mid-session

Agree the weighting of each dimension in writing before any demo. Weights set afterwards tend to justify a preference that has already formed. And include the assistant editors and post coordinators who will run sessions every night; their view of the fiftieth session matters more than anyone’s impression of the first.

How should cost be compared?

Vendors price different things: named users, viewers, concurrent rooms or streams, storage, quality tiers. Headline rates aren’t comparable. Take a real show at a real stage, count the rooms, sessions, participants, hours and media kept, and ask each vendor to price that month. Then price your busiest foreseeable month, and ask what happens when you exceed a tier. Rankings often change between the average month and the peak.

Add the costs outside the subscription, such as your own upload capacity, encoding hardware or software, and the time to standardize room setup. They vary with each platform’s architecture.

How should references be checked?

Vendor-supplied references will be satisfied customers, so ask them specific questions: what went wrong in the first ninety days, and how did the vendor respond? A reference who can’t recall any friction either had an unusually smooth start or isn’t being candid.

Find at least one reference the vendor didn’t supply, through peers or your own outside vendors. And find one long-running user, because a facility two months in can’t tell you how a platform behaves at eighteen.

What happens between shortlist and decision?

Run one real session on a live production with the leading candidate. A real dailies or editorial review with real stakes shows more than another demo, and most vendors will support it if asked.

Run the security review in parallel, not at the end. Waiting for a favorite to emerge before starting adds weeks and sometimes reveals the favorite was never viable.

Get commercial and exit terms in writing from every finalist, not just the leader. Comparable written terms are your leverage, and asking only the front-runner gives it away. Protect yourself the same way whatever the vendor’s size: retention and deletion terms, export rights where material lives only in the platform, notice of material change, and a shorter first term if doubt remains.

Then set a decision date and keep it. Shortlists go stale within weeks as staffing, productions and pricing change.

FactorScreen first, then demoDemo widely, then narrow
Senior timeSpent on candidates that could be chosenSpread across candidates that may be ineligible
Risk of a demo overriding a requirementLow: eligibility is settled firstHigh
Elapsed timeShorterLonger, and prone to drifting across a quarter
Quality of comparisonIdentical sessions on identical materialEach vendor shapes its own session
Common failureScreens set too tight, leaving fewer than twoThe decision drifts and the process is abandoned
Screening first compared with demoing widely and narrowing later

How to run it

  1. Write the four screens from your actual contracts and working hours.
  2. Decide which kind of supplier you need, and ask each vendor what its product was built to do.
  3. Build the long list from people: peers, your outside vendors, industry associations.
  4. Send one short information request asking for evidence, a definition of “persistent” and a stated latency basis.
  5. Weight the dimensions in writing, then run identical demos with a failure segment and an evening session.
  6. Price a real month and a real peak with every finalist.
  7. Check one independent and one long-running reference, run one real session, get written terms from all, and decide on the date you set.

Coresee makes a persistent, browser-based video collaboration workspace, one of the kinds of supplier this guide describes.

References

  1. Trusted Partner Network. “Our Mission.” Trusted Partner Network. Accessed November 9, 2026. trustedpartnernetwork.org/our-mission
  2. Hollywood Professional Association. “Who We Are.” HPA. Accessed November 9, 2026. hpaonline.com/about/who-we-are
  3. Holland, J., A. Begen and S. Dawkins. “RFC 9317: Operational Considerations for Streaming Media,” Section 4. Internet Engineering Task Force. October 2022. rfc-editor.org/rfc/rfc9317.html#section-4
Found this useful? Share it:XLinkedInEmail

Published November 9, 2026

Frequently asked questions

Our screens left us with one candidate. What now?

Check whether a screen was written as an ideal instead of a threshold. Support hours and onboarding times often are, and relaxing an ideal is legitimate where relaxing a contractual obligation isn’t. If every screen is a real requirement, proceed with one candidate but test harder: run a real session on a live production, complete the security review, and negotiate a shorter first term.

A vendor won’t let us run our own material in the demo. Is that disqualifying?

Treat it as strong evidence, not an automatic no. There can be a real reason, such as a format their trial environment can’t accept, and a vendor who explains it and offers an alternative is behaving reasonably. A vendor who simply prefers to control the session is managing an impression. Ask what would need to change to make it possible before deciding.

Our supervisors and assistants reached opposite conclusions. Who’s right?

Both, about different things. Supervisors judge the review experience; assistants judge the work of setting it up and keeping it running. Weight the dimensions explicitly: a facility running several sessions a night should weight setup labor heavily, while one running occasional high-stakes reviews can weight the session experience higher. Making the trade visible lasts longer than settling it by seniority.

More from the Coresee blog

View all articles

GuidesNovember 9, 2026

Browser-First Collaboration for Agencies: What Belongs in the Browser and What Doesn't

GuidesNovember 9, 2026

How to Set Up a Persistent Video Workspace for a Post Facility

GuidesNovember 9, 2026

Choosing an Enterprise Live Event Platform: Latency, Scale and Production Control