Small Teams & Rollout

How to Scope a Subtitle Rollout Budget Before Procurement

Budget the full audience promise across content, accessibility review, paid staff time, rehearsal, support, fallback, and correction—then narrow scope before procurement if the operating commitment is not funded.

Short answer

Budget the audience promise, not only the software. A responsible subtitle budget covers content and language work, accessibility review, paid staff time, realistic rehearsal, audience support, fallback, and correction across both introduction and ongoing use. If those costs are unfunded, narrow the service before procurement—not after audiences have been asked to rely on it.

How to Scope a Subtitle Rollout Budget Before Procurement

A licence quote is a price, not a service budget. Subtitles reach an audience only after people prepare and review the text, rehearse the service, explain how to use it, operate the performance, recover from failures, and maintain the work over time. Comparing tools without pricing those responsibilities makes the least complete proposal look artificially inexpensive.

Underfunding does not remove the work. It shifts it onto employees' unpaid overtime, one access advocate, artists asked to absorb extra duties, or audience members left to improvise around an unsupported service. A credible budget makes those transfers visible and changes scope when the organization cannot resource the commitment responsibly.

Separate one-time introduction costs, per-production costs, recurring programme costs, and contingency. State the production volume, languages, venues, delivery modes, staffing, rights, retention and exit assumptions, and access commitments behind every figure. A total without assumptions cannot support a fair procurement decision.

Build the Budget Around the Whole Service

  • Content and rights: source preparation, cue segmentation, translation, same-language caption writing, permissions, approvals, and version control
  • Access and language review: readability under realistic conditions, specialist review, audience evidence, and correction after findings
  • People: protected paid time, training, handoffs, live operation, relief, project ownership, front-of-house support, and technical help
  • Rehearsal: late changes, real seating and sightlines, public instructions, likely failures, handoffs, and demonstrated recovery
  • Audience journey: accurate listings, signage, QR or link entry, language choice, supported alternatives, and complaint handling
  • Venue needs: projection, displays, network, audience devices where supplied, power, mounting, transport, and changeovers
  • Governance and data: procurement, contracts, privacy review, minimal collection, retention, exports, deletion, exit, and incident records
  • Contingency and correction: replacement staff or equipment, alternative routes, urgent content repair, communication, and another rehearsal

Do Not Treat Accessibility as an Optional Add-On

If the public promise includes accessibility, the base budget must include the work required to make that promise credible. Review, audience information, supported alternatives, and recovery cannot be postponed as optional enhancements while the service is advertised as accessible.

When disabled people, Deaf or hard-of-hearing people, multilingual audience members, or other intended users contribute time or lived expertise, explain how their input will be used, obtain informed consent, keep participation voluntary, collect only the information needed, and budget fair compensation. Do not require a diagnosis or proof of disability to participate or receive ordinary audience support. Participation is not a free substitute for qualified review or the production team's own rehearsal responsibilities.

A budget can legitimately limit languages, performances, devices, or venues. It cannot responsibly promise a broader service and quietly rely on unpaid labour, undisclosed audience workarounds, or a fallback that has never been funded and rehearsed.

Separate Introduction, Recurring, Expansion, and Failure Costs

  • Introduction: service design, initial content, setup, training, public guidance, and rehearsal under the intended conditions
  • Steady operation: each production's editing, review, rehearsal, staffing, support, maintenance, rights, and reporting
  • Expansion: additional languages, performances, venues, delivery modes, devices, support demand, and backup coverage
  • Failure and recovery: replacement staff or equipment, service communication, incident review, correction, and renewed evidence

A pilot is not automatically cheap. It may carry most introduction costs while serving fewer performances. Record which costs are genuinely avoided, merely deferred, or repeated before wider use; otherwise the pilot can understate the steady-state budget.

Compare Total Operating Assumptions Before Procurement

  • What the quoted price includes, excludes, limits, meters, or requires from another supplier
  • How many paid hours and specialist roles preparation, review, rehearsal, operation, support, and recovery require
  • Which venue equipment, audience devices, connectivity, storage, export, deletion, and exit arrangements remain local responsibilities
  • How costs change with languages, simultaneous viewers, performances, venues, operators, storage, or service hours
  • What support response is included and what the organization must recover without a supplier during a live performance
  • Which assumptions have been demonstrated under intended conditions rather than inferred from a sales demonstration

Set Funding Gates Before Signing

Name the rollout owner, budget owner, specialist approvers, and person who can narrow or stop procurement. Minimum funded conditions should include approved content, trained primary and backup roles, realistic rehearsal, truthful public instructions, a usable fallback, a funded route to correct material findings, and a workable exit if the service cannot be sustained.

If the organization cannot fund one of those conditions, revise the audience promise or phase the introduction. Procurement should not lock the team into a public commitment whose operating cost was deliberately left outside the business case.

Where SurtitleLive Fits

SurtitleLive can support prepared content, language versions, review, projection, browser-based audience viewing, language selection, and live subtitle progression. It does not estimate local labour, equipment, language, access, rights, device, power, network, or support costs; approve content; supply staff or venue infrastructure; certify accessibility, labour, privacy, or procurement compliance; guarantee savings or return on investment; or decide what an organization should buy or promise. Local evidence and an accountable budget owner remain essential.

Related Procurement and Rollout Guides

Sequence the work with Subtitle Pilot or Full Rollout?. Assign budget authority with Who Should Own Subtitle Rollout?. Fund competence and handoffs with How Much Training Does a Subtitle Rollout Require?. Cost the recovery plan with How to Plan Subtitle Backup and Fallback.

If You Are Moving Into Implementation

These product guides cover setup, live deployment, and audience access in SurtitleLive.

Common Questions

What do teams often miss when planning a subtitle rollout budget?+
A licence quote excludes much of the service: content and language work, rights, accessibility review, paid staff time, realistic rehearsal, audience support, fallback, correction, data handling, exit costs, and the recurring work required to keep the service dependable.
Why should a subtitle budget separate introduction and ongoing use?+
Introduction carries service design, setup, training, initial guidance, and early rehearsal. Ongoing use adds per-production editing, review, staffing, support, maintenance, rights, storage, and recovery. A pilot may defer some costs rather than remove them.
Should accessibility be a separate optional budget item?+
Not when accessibility is part of the public promise. The base scope must fund review, audience information, supported alternatives, recovery, privacy safeguards, and fair compensation for people contributing time or lived expertise that makes the claim credible.
When should a team narrow a subtitle rollout before procurement?+
Narrow the scope when the budget cannot support approved content, paid and trained primary and backup roles, realistic rehearsal, truthful public guidance, a usable fallback, correction of material findings, or a workable exit. Do that before audiences are asked to rely on the service.

More in Small Teams & Rollout

← Back to Planning Library