Schedule programming:
practical dayparting

Why dayparting changes the game

Most digital signage screens in small businesses show exactly the same content at 8am and 11pm. That means a breakfast customer sees the dinner cocktails promo, and a dinner customer sees the morning coffee offer. Content is decoupled from when it's seen, and that wrecks its effectiveness.

Dayparting solves this: you define rules like "from 7-11 show content A" and "from 12-4 show content B", and the system switches by itself. Customers always see what's relevant to their moment. And you don't have to remember — the screen runs itself.

Beyond context, there are three more advantages that get underestimated:

• Consistency: you never forget. If you rely on switching manually when dinner service starts, some days you (or your team) will forget. Scheduled, it always happens.
• Forward planning: in September you can schedule the Black Friday campaign to start Nov 24 and end Dec 1. Then forget about it. The date arrives, the campaign runs itself.
• Multi-location sync: if you run 5 locations, scheduling one central campaign guarantees all 5 activate at the same hour. No email to each manager, no manual coordination.

The 4 types of scheduling your platform should support

The first 3 types are in any decent signage software. The 4th (conditional/external events) is for advanced platforms and requires API integration (weather, sports calendar, etc.). At Digisini the first 3 are standard in any plan; the 4th is in Pro and above.

Sample calendar: hospitality (bar/restaurant)

This is the industry where dayparting makes the biggest difference. A typical weekly calendar:

That's 6 blocks × 2 variants = ~12 pieces to have ready. Once produced and uploaded with correct scheduling, it rotates on its own. Add seasonal campaigns (Christmas, Valentine's, Halloween, Easter) and that's 4-6 more high-priority rules that briefly override the base calendar.

Sample calendar: retail

Retail benefits more from date than hour scheduling: seasons run long. Typical annual campaigns:

All of that scheduled in September = 1 day of work, then rotates all year. If you have 10 locations, the difference vs manual coordination is huge.

Sample calendar: gym

Typical annual campaigns:

• Jan 1-31: "New Year, new you" — 50% off membership, 90-day plans.
• Apr 15-Jun 15: "Pre-summer" — short summer pass, pre-beach challenges.
• Sep 1-Oct 15: "Back to routine" — post-vacation recovery.
• Nov 15-Dec 23: "Black Fitness" — annual discount with fixed monthly fee.

More industries

Step-by-step setup (in Digisini)

Here's how to configure a typical rule from the panel:

1. Create the base playlists. Before scheduling anything, prepare the 4-8 calendar playlists (breakfast, lunch, dinner, etc.). Each with its content pieces. No playlists = nothing to schedule.
2. Set the screen's timezone. If multi-location, each screen with its own zone. Default takes account-level zone, but you can override per screen.
3. Create the first rule in the Scheduling panel. "New rule" button: descriptive name ("Breakfast Mon-Fri"), playlist to use, days of the week (toggle 7 days), time slot (07:00-11:00), priority (30 for base rules).
4. Create the 4-6 base rules (lunch, afternoon, dinner, weekend). Keep priorities consistent (all "base" at 30).
5. Add campaign rules with higher priority (70-90). Specify date range and, where applicable, time-of-day override (Black Friday can be 24/7 throughout range).
6. Define the "default" rule with low priority (10). It's what shows if no other rule applies (e.g. late night when venue is closed but screen still on — generic branding).
7. Test overlaps. Manually change the system time to simulate different moments and verify the right rule activates.
8. Activate global scheduling. Up to here, scheduling is draft. The final toggle ("Scheduling active") pushes it live.

In order, full first setup takes 2-3 hours (most of it preparing playlists, not rules). Each new annual campaign: 10-20 minutes.

Overlapping rules: how priorities work

The universal system in signage is numeric priorities: each rule gets a number (1-100), and when two would apply at the same time, the higher number wins.

With this system, a screen during lunch hours with active Christmas campaign will show Christmas (priority 70 > 30), not the lunch menu. If you want the lunch menu to appear anyway, embed a lunch sub-piece inside the Christmas playlist — but the choice is yours.

Advanced rules: weather, conditional, integrations

On advanced platforms (Digisini Pro and up), you can define conditional rules depending on external variables:

• Weather: "if local temperature >30°C, activate ice-cream campaign". "If rain >60%, show hot coffee promo". Rule queries weather API every N minutes.
• Sports events: "If local team plays today, activate match-day viewing pack". Integration with sports calendars.
• Stock or sales: "If less than 10 units of product X left, activate 'last units' urgency". Integration with POS or ERP.
• Time-based: "If today is a national holiday in my country, activate holiday rule". Integration with public holidays calendar.
• Web traffic: "If we get more than N visitors to our site today, show appreciation on screen". Integration with analytics.

These rules aren't for everyone. A typical SMB doesn't need them. But franchises or businesses with sophisticated ops use them to automate context-driven responses in real time.

Common mistakes when scheduling (and how to avoid them)

Time ROI: how many hours you reclaim with scheduling

Simple maths for a hospitality SMB changing menu across time blocks 3 times per day (breakfast → lunch → dinner), 7 days per week:

If your hourly value is £15, that's ~£630/year reclaimed. With 5 locations, ~£3,150/year. For SMBs with more complex calendars, savings are higher. And that's before counting the cost of "forgets" (a day with the wrong promo all day can cost £50-200 in lost sales).