Theatre Management System (TMS)

Each screen has its own server and media block, and each one can be driven on its own from a touch panel in the booth. That works for one screen. It does not work for eight, and it certainly does not work when a title moves between auditoriums mid-week.

A TMS sits above all of them. Ingest once and it distributes the package to the screens that need it. Build a show playlist once — lights, curtains, adverts, trailers, certificate card, feature, credits, house lights — and schedule it across screens and days. It tracks which content is on which server, flags what is missing for tomorrow's schedule, and reports what actually played rather than what was supposed to.

That last part is the one people undervalue. A TMS knows a show started eleven minutes late; without one, nobody does.

A TMS runs the screens. It does not sell tickets, it does not know your prices, and it has no opinion about your website. The point of confusion in most tenders is the boundary between the TMS and the ticketing system, because both of them hold something that looks like a schedule.

The distinction that matters: the ticketing system owns the sellable session — a time, a screen, a seat map, a price. The TMS owns the show playlist — what physically plays and when the lights go down. They describe the same performance from two sides, which is why the integration between them is worth getting right and why a mismatch shows up as a session on sale for a screen that has no content ingested.