What is the hardest part of subtitle planning for mixed festival audiences?

It is usually balancing language coverage, audience entry, and operational simplicity at the same time. A plan that looks good on paper can still become difficult to run if the venue changes or front-of-house support is too thin.

Should festivals try to cover every possible language at launch?

Start with the audience-language mix that is most likely in the room, then expand only when the workflow has proved stable.

Festival Subtitles for Mixed Audiences: Keep the Promise at Every Venue | SurtitleLive Planning

Short answer

Plan festival subtitles around the audience service the travelling team can genuinely sustain. A longer language list is not inclusion when venue change, limited staffing, unclear entry, unpaid rescue work, or a missing fallback leaves people without the promised text.

At a Festival, Every Venue Tests the Audience Promise Again

Festivals rarely repeat one stable audience journey. Language needs can vary by performance, reading conditions change with every room, and the people available at the venue may not be the people who planned the service. Treat each venue as a new test of what the public information promises—not as a reason to ask audiences to work around an unsupported setup.

Define a Promise the Festival Can Actually Keep

Which audiences, languages, performances, reading routes, and limits are being promised at this venue—not in an idealised festival plan?
Who owns approved text, translation and access review, public information, live operation, and recovery after a change or failure?
Can representative seats read a projection, and can a new user enter a mobile route from the public instructions without backstage help?
Is there a discreet, supported alternative for people who cannot or do not want to use a phone?
Are preparation, handoff, audience support, and recovery funded work with named primary and backup people?

Where a Festival Plan Becomes an Unkept Promise

Languages are advertised before their approved text, reading route, audience information, and recovery have been rehearsed.
Each venue receives the same instructions even though seats, screens, connectivity, privacy, or front-of-house support differ.
Visitors must disclose a need, own a particular device, or find a staff member to obtain ordinary support.
Late changes create unowned copies or require translators, operators, or volunteers to repair the service unpaid.
A fallback exists only in a document, or only one person can recover it during a performance.

Listen, Pay, and Rehearse Before Expanding

Invite intended audiences, translators, caption writers, access specialists, venue colleagues, and operators to identify real barriers. Explain how feedback will be used, obtain informed consent, keep participation voluntary, collect only necessary information, and fairly compensate requested time and expertise. No one should need to disclose a diagnosis, disability, language need, or device ownership—or provide unpaid labour—to receive ordinary support. For the multilingual workflow side, continue with Multilingual Surtitles and Separate Slide Decks. For audience delivery choices, continue with Mobile Subtitles vs Projection Surtitles. SurtitleLive can support prepared text, human review, projection, browser delivery, language selection, and human-controlled advancement. It does not provide translators, access specialists, venue connectivity, audience devices, live operators, or certification of accessibility or legal compliance.