Content scheduling decides what plays where and when: by time of day, by date range, by location group, or by a condition being true. It is the feature that makes one network behave like many.
Dayparting is the obvious use (breakfast menus before eleven, happy hour after five), but the higher-value cases are conditional. Play the umbrella creative when the weather API says rain. Pull the promotion automatically when stock falls below a threshold. Show the safety briefing only on screens inside the warehouse.
The caveat is conflict resolution, and it is the question nobody asks during a demo. When a national campaign, a regional promotion and a store-level notice all target the same screen at the same moment, something must decide. Systems handle this by priority, by layering, or by silently letting the last edit win, and the third is how a store manager's stock notice quietly disappears.
Ask to see two overlapping schedules resolved on screen. Ask who can override whom. On a network with more than one publisher, that hierarchy is the product.