Timezones & DST
Numeric offsets break clocks twice a year. QueueTempo stores every recurring schedule with an IANA timezone and documented spring-forward and fall-back behavior, previewing the affected times in advance.
A 9:30 Tempo means 9:30 local, forever. On spring-forward, a nonexistent local time moves forward by the DST gap to the next valid instant. During fall-back overlap, the earlier occurrence wins and only one post is created.
Every-N-hours cadences anchor to elapsed duration, so their displayed wall time may legitimately shift after a transition, and the product tells you that in the preview rather than hiding it.
Each Organization and Tempo carries its own zone. An agency in Chicago running a Lisbon client's account stops doing mental arithmetic at 2 AM UTC.
Straight answers
Offsets silently misplace recurring events across DST. IANA identifiers let the engine resolve the correct instant for every future date, which is what wall-clock schedules actually promise.
IANA tzdata updates track legal changes; recurrence resolution uses current rules, and previews reflect them going forward.
Yes, per-Tempo timezone is a first-class setting, independent of the Organization default.
Keep reading
Set the next beat
Start free, describe your brand once, and watch the next ten post times appear before anything goes live.