Everything so far has been about time: hours, days, dates. But scheduling does not have to stop at the clock. A screen can also respond to what is happening around it.
The same machinery that decides “play this on weekday mornings” can decide “play this while the production line is behind target,” or “show this only when a system is down.” The trigger is no longer the time. It is a live condition, drawn from your own data.
This is where signage stops being a calendar and starts being a window onto the present. An alert can appear the instant something goes wrong and clear itself the moment it recovers. A status board can surface only when a number crosses a line worth watching. Nobody has to spot the problem and put the content up; the screen does it on its own.
You do not need any of this to run great signage, and most screens never use it. But it is worth knowing the ceiling is high. If your systems can answer a question, a screen can react to the answer.
Connecting content to live data is a developer’s job. It runs on predicates, covered in Predicates under Build with Screenly. Here, the takeaway is the idea: a schedule can be about far more than the time of day.