What houses ask us before they start

From the system in which you already maintain it. signage42 polls your programme source on a schedule and on demand. If your house system speaks its own format, we write an adapter for it rather than having someone retype the season. An export, a database or a spreadsheet is also a fine starting point.

Not for the programme. Starter templates such as the entrance panel or the week view show performances, times, casts, images and sponsors straight from the imported programme. For everything else, such as sponsors, exhibitions, house rules or campaigns, there is a media library and a layout editor with preview.

Yes. Beside the programme there is a media library for images, video, PDFs and live web pages, filled by drag and drop and organised in folders. From it you build playlists that run in order or weighted random, with cut or crossfade. A video brings its own real duration. In the layout editor, programme and campaign sit side by side on one screen, or the playlist gets screens and times of its own. Marketing works in its own workspace for this without touching the house programme.

Each screen is bound to the stage it serves. A layout is designed once and published house-wide; each screen then shows the performance of its own stage. A screen bound to nothing stays empty on purpose, so a setup mistake is noticed immediately.

The change is made in the house system, as before. At the next sync every screen shows the new state. A cancelled performance is marked as cancelled, and the screen time that was automatically scheduled for it disappears with it.

In two clicks in the interface, or automatically from your cue or building system. The notice takes over the affected screens in seconds, applies to one stage, one building or the whole house, and always carries an expiry so it ends by itself. Emergency outranks delay, delay outranks interval.

The screens keep playing. Every player keeps its schedule and media locally, several gigabytes of it. Emergency content is additionally held in a protected store and plays with the network down. The outage is invisible in the foyer; operators see it in the overview.

The player is a browser application. It runs on a small computer such as a Raspberry Pi behind the panel, on a smart display, or on anything with a modern browser. Portrait and landscape, 16:9, 9:16, 1:1, 21:9 or a custom ratio.

In under a minute. The panel shows a short code, an operator enters it in the interface, and the screen is live. No files, no keyboard at the device. A device can be revoked at any time; it then shows nothing immediately.

Yes, throughout. Every programme field carries its translations, every layout can show German and English side by side, and every screen labels itself in its own language. The interface for your team is fully available in German and English as well.

Yes. Six fixed roles, workspaces with their own approval rule and folder-scoped groups let marketing move fast, keep the house programme under four-eyes review, and show an agency only the folders you grant. Every publish, approval and signal is logged.

Either: on your own hardware, in your own data centre, or hosted. Your data stays in the deployment you choose.

Yes, the interface is built to WCAG 2.1 AA. There is a light and a dark mode, optionally following the operating system, so the front-of-house desk in a sunlit foyer can work comfortably too.

An AI assistant built on Claude by Anthropic, together with a tool for technical staff. You describe in one sentence what should go on the screens; the assistant uploads, builds the playlist, checks for conflicts and asks before every publish. It acts only with your own permissions and can neither change members or settings nor delete anything.

Half an hour, live in signage42. We show you a sample house from the hall door to the interval notice, resolved per stage, in both languages, and answer the questions of your house directly in signage42.