Scheduling
The right content, at the right hour, without anyone touching it
A canteen menu at eleven, a safety briefing at six, the company loop the rest of the time.
Schedules are recurring by day and time, or a one-off window. They target a screen, a group or the estate.
Two schedules that overlap have a defined winner: priority first, then weight, then whichever was changed most recently. Not whichever the database happened to return first, which is the kind of detail nobody asks about until the wrong thing is on a wall during a board tour.
What you get
- Recurring by weekday and time, or a single dated window
- Deterministic overlap resolution: priority, then weight, then recency
- A schedule whose playlist was deleted falls through rather than blanking the screen
- Everything resolves in the organisation’s timezone, not the server’s
See it yourself
A live system with your own login, and someone to walk you through this specific part of it.
Request a demoAlso in the product
The rest of it
See it running on your own screens
We will set up a live system with your own login, and walk you through anything you want to see.
No open demo, no sign-up wall, a person reads every request.
