The following are technical and operational notes about handling fall and spring time changes.
Each DST-ST or ST-DST transition has two components:
- The time change in your local computers, and
- Operational considerations
DST and Your Local Computers
The ContentDepot operates in coordinated universal time or UTC, which is an absolute standard that does not adjust for DST or "summer time." Likewise, the ContentDepot delivers UTC data via Network Time Protocol (NTP) on the satellite streams. Any time zone or DST offsets are applied at end devices - typically production computers or time-of-day displays synchronized via NTP.
Spring Time Change
The ContentDepot transition to DST is very straightforward:
- If your local computers have been updated with the latest DST patches, they will automatically step forward at 02:00:00 local time on Sunday, March 9, 2025 (check with your automation/playback system vendor to see if you need to do any special maintenance or procedures to accommodate this transition).
Operational Considerations
The ContentDepot headend will transmit stream setup data and commands for the 03:00:00 ET hour at the end of the 01:00:00 ET hour. We recommend you review your station schedule for the date of the time change to verify your local programming flow from 01:59:00 ET to 03:00:00 ET. In the ContentDepot, the 02:00:00 ET hour on the day of the time change does not exist and will not execute. The System will operationally step from 01:59:59 ET to 03:00:00 ET.
The only operational function in your ContentDepot file storage receivers affected by DST offset is the automated deletion of files based on their kill dates. The SFX 4104 receivers still operate on the "old" DST transition dates, but deleting files an hour later for three weeks won't make any difference in local operation. Displays and log entries will be incorrect for three weeks, but that's easily remedied, if desired, by hand-setting the time zone an hour "ahead" at a convenient time. There is no operational affect of any DST change in your stream decoders—they always function in UTC.
Fall Time Change
The ContentDepot transition to standard time is very straightforward:
- If your local computers have been updated with the latest DST patches, they will step back one hour at 02:00:00 local time on November 2, 2025 (check with your automation/playback system vendor to see if you need to do any special maintenance or procedures to accommodate this transition).
Operational Considerations If you use ContentDepot stream programs overnight on Saturdays (including early Sunday morning):
- Each producer will generate an extra live program hour to fill the 01:00 EST hour. You do not have to subscribe to this hour; if you are subscribed to a program that starts at 01:00 EDT, you will get the 01:00 EST program automatically.
- Program cueing will operate normally in the 01:00 EDT hour and in the 01:00 EST hour for all live programs.
- The NPR Breaking News transmission has been extended to be 25 hours long.
If you play ContentDepot file programs overnight, check your program's portal page. In some cases, the producer has generated a special "extra" hour of their program and uploaded it into the "evergreen" slot. Watch for messages from your program producer(s) for more information.
Also, please be aware that your station may receive a Receiver Conflict Report for 1:00 AM on the morning of the time change. These conflicts are intentional and do not require any action on your part. They are the result of the reversion to standard time. The PRSS NOC has made several special, repeat bookings for the hour of 1:00 AM to account for the time change. The result, however, is your station may receive a Receiver Conflict Report.
What Else Do You Need to Do?
The most important action you can take is make sure that your local production systems (including time-of-day displays) have the latest updates so that they'll properly step back (fall) or step forward (spring) . You should also check with your automation/playback system vendor to see if there are any special scheduling considerations for your particular installation.
.png)
.png)
.png)
