Digital signage scheduling: test time zones and DST
Buying screens for several locations? Check signage time zones, DST rules and player schedules before rollout. Includes a repeatable acceptance test.

Digital signage scheduling needs three decisions before rollout: the site time zone, the rule for repeated or missing local times, and who will test the intended player. A correct clock does not tell a screen which campaign to play. For a multi-location display project, review the content management system (CMS) schedule, player clock and display power timer together. Use an isolated sample for testing so a trial cannot interrupt a live location.
What changes on November 1, 2026?
For U.S. sites that observe daylight saving time (DST), NIST lists November 1, 2026, at 2 a.m. local time as the end of DST. The clock returns to 1 a.m. and repeats that hour. Hawaii and most of Arizona are exceptions. Check each site before applying the same change to every screen.
An overnight promotion scheduled for 1:30 a.m. therefore needs a clearer instruction than “start at 1:30.” Should it run on the first occurrence, the second, both, or according to another documented platform rule? That decision belongs in the schedule specification before someone presses publish.

Which time zone controls content scheduling?
Ask the supplier to trace a scheduled item from the editor to the physical screen. Record a named zone such as America/New_York when the platform supports it. Coordinated Universal Time (UTC) provides a shared time reference. A fixed UTC offset describes one offset; it does not describe a location's changing seasonal rules.
| Layer | Decision to identify | Evidence to request |
|---|---|---|
| CMS calendar | Is the start time interpreted in the site zone, account zone, editor zone or UTC? | Saved schedule with its interpretation visible |
| Player | Which local zone and time source does this endpoint use? | Configuration readback for the intended player |
| Content package | Does an embedded web page calculate its own dates or opening hours? | Page behavior on that endpoint, including its date source |
| Display timer | Can the panel be asleep while the player is scheduled to run? | Power schedule and a physical screen check |
| Operator record | Can different teams compare the same event unambiguously? | Event ID, UTC timestamp, local time and offset |
Do not let both the CMS and a web widget add an extra hour. Check that the player has received the new calendar, too. The offline playback test guide covers delivery to the player. This test checks how the player reads a schedule it already has.
How do you specify the repeated hour?
The following is an illustrative mapping for New York on November 1, 2026. It is a planning example, not a test result from a Gemdragon system.
| Event marker | Local timestamp with offset | Same instant in UTC | Required observation |
|---|---|---|---|
| A | 2026-11-01 01:30 −04:00 | 2026-11-01 05:30Z | Record which approved item is visible |
| B | 2026-11-01 01:30 −05:00 | 2026-11-01 06:30Z | Record which approved item is visible |
These are different instants with the same wall-clock label. Give test artwork an event marker so a photograph can distinguish A from B without relying on a camera's local clock. Keep the expected result alongside the observation. A log saying “01:30” without an offset cannot settle which occurrence it describes.

For a recurring local opening-hours schedule, ask whether the business wants the same wall-clock time after a transition. For a coordinated release across regions, ask whether the requirement is the same absolute instant. Write the choice explicitly. Neither can be inferred from a playlist's name.
What should the sample test include?
Use a spare player or an approved staging environment with the same relevant software versions. Ask the platform supplier for its supported method of simulating a transition. Do not change a production clock, disable certificate checks or alter a live network time service to force the experiment.
- Save the site zone, CMS interpretation, player version, content version and display timer settings.
- Define the expected item before the transition and at both occurrences of a repeated time. Include a boundary that crosses midnight at another location.
- Observe the actual screen and record an event ID plus UTC and local offset for each observation.
- Check a restart using the supplier's supported procedure. Verify the active item after startup rather than assuming the last frame was correct.
- Restore the staging configuration and document any unresolved behavior before rollout.
A missing spring hour needs its own test: ask what happens to an item whose local start never occurs. Possible platform behaviors must come from documentation or a sample result, not a guess based on the autumn test.
Why doesn't network time synchronization settle the whole problem?
NIST explains that its Network Time Protocol (NTP) service distributes UTC. The operating system supplies local-zone and DST corrections. An enabled NTP service is only one check. Confirm the zone rules, calendar settings and content that actually plays.
If time is accurate but the wrong campaign plays, inspect the schedule's zone and recurrence definition. If the campaign is correct but the screen is dark, inspect the display timer and signal path. Keep those findings separate from multi-screen synchronization, which asks a different question about alignment between screens.

Frequently asked questions
Can one schedule cover locations in different time zones?
It can only meet the project requirement if the platform's interpretation is known. Specify whether each site follows its own local business hours or a shared UTC instant, then test representative locations.
Should I enter a fixed UTC offset for every site?
Use the platform's supported location-zone method where available. If only a fixed offset is supported, document who updates it and how seasonal changes will be checked. Do not assume a fixed offset tracks DST.
Does a successful test prove all future clock changes will work?
No. Retain the tested versions, zone and recurrence conditions. Recheck when relevant software, zone rules or schedule logic changes.
Does the display itself need a scheduling app?
Scheduling may reside on an embedded player, an external player or another component. Identify that component before choosing hardware. A panel timer and a content calendar are separate controls.
Request hardware for your scheduling plan
Start your Gemdragon inquiry with screen count, site countries and installation format. Add operating hours and your CMS/player choice if known. The wall-mounted display catalog reference helps you discuss the physical format. Confirm the exact player and scheduling setup separately.
Discuss a scheduling display project. A redacted calendar example is useful if available; you do not need a finished schedule to start the hardware discussion.
Editorial scope: an original procurement checklist reviewed on October 20, 2026. Timestamp examples are illustrative. No Gemdragon scheduling, DST or recovery test result is claimed. Cover: photo-style AI scene illustration, not an actual customer installation.
Request a Quote

