Check Campaign Schedules Before Daylight Saving Changes
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A campaign fixed to headquarters time can reach customers an hour earlier or later after a clock change. When headquarters and customer regions change clocks on different dates, a familiar time difference can disappear temporarily. When only one region changes clocks, the new difference can persist.
The task is not to move every campaign by an hour. It is to preserve each campaign’s intended timing, verify the saved occurrences, and record where any correction starts and ends.
The worked example below uses fictional campaigns, staff, and operational records with factual calendar conversions. A London team reviews a Monday New York reminder, a separate one-off, and a Monday Dubai reminder. The Dubai case shows why correcting the first affected send does not resolve an entire recurrence.
1. Decide which clock the campaign should follow
Write down the business intention before calculating anything. Campaigns sharing a send time today may need different treatment after a transition.
- Customer-local commitment: A reminder should arrive at 09:00 in the customer’s business time zone. Headquarters time may need to change.
- Headquarters commitment: An announcement follows a headquarters event. Customer-local time may move, provided it remains suitable.
- Shared event instant: Regional reminders refer to the same event. Preserve their relationship to that event rather than shifting regional copies independently.
In a hypothetical campaign, “Monday at 09:00 in America/New_York” becomes testable when paired with an occurrence date. “Monday morning” leaves both the time and zone unresolved.
Confirm reply coverage too. Preserving customer-local timing may move responses outside headquarters staffing hours. Resolve that staffing question explicitly rather than letting an old schedule silently determine customer contact hours.
2. Inventory occurrences within an explicit review horizon
Find the relevant regional transitions. For a temporary mismatch, include every scheduled occurrence between the transitions, plus a baseline before and a check after. For a difference that persists, set a review end date and assign responsibility for later occurrences.
Include one-off sends, recurring campaigns, regional copies, event-linked follow-ups, and postponed sends. Record each saved date and time, displayed zone, audience, owner, and recurrence membership. A delayed send can cross midnight, so times alone are insufficient.
Use named zones such as Europe/London, America/New_York, and Asia/Dubai. Keep the numerical offset in a separate, date-specific field. A permanent offset cannot represent a zone whose rules change seasonally.
If the saved timestamp’s zone is unclear, mark the entry unresolved. Do not infer it from an operator’s location or device settings. Use a confirmed customer business zone or stated preference rather than assigning a zone from a phone prefix.
This hypothetical review assumes all saved schedules follow London wall-clock time. A schedule fixed to UTC would behave differently. Its New York horizon is 2–30 March 2026; its Dubai horizon is 23 March–6 April 2026, with later Dubai Mondays explicitly left as an open follow-up.
3. Calculate the dated difference, not the usual difference
The calendar inputs follow the IANA Time Zone Database, using its historical 2025b North America, Europe, and Asia rule files. That release makes this example reproducible; it is not presented as the latest version. Check current time-zone data for operational decisions because rules can change.
- America/New_York: On 8 March 2026 at 07:00 UTC, the offset changes from UTC−05:00 to UTC−04:00.
- Europe/London: On 29 March 2026 at 01:00 UTC, the offset changes from UTC+00:00 to UTC+01:00.
- Asia/Dubai: The offset remains UTC+04:00 throughout the review horizons.
The London–New York difference changes from five hours to four, then returns to five. The overall mismatch lasts 20 days and 18 hours: 8 March at 07:00 UTC through 29 March at 01:00 UTC. The Monday recurrence has exactly three affected occurrences within that interval: 9, 16, and 23 March. The 12 March one-off is separate.
Calculate in two steps: UTC = customer-local time minus customer offset; then headquarters time = UTC plus headquarters offset. Carry any date change through both steps.
For the fictional New York campaign on 16 March, 09:00 minus an offset of −04:00 gives 13:00 UTC. London is still UTC+00:00, so the correct headquarters time is 13:00. Leaving the saved time at 14:00 London would reach New York at 10:00.
On 30 March, 09:00 New York remains 13:00 UTC, but London is UTC+01:00. The headquarters equivalent returns to 14:00. Extending the temporary 13:00 correction would send an hour early.
Dubai behaves differently. Its 09:00 target is 05:00 UTC both before and after London’s transition. That means 05:00 London on 23 March, but 06:00 London on 30 March and 6 April. Keeping 05:00 London after the transition would reach Dubai at 08:00. This difference does not revert when the New York mismatch ends.
4. Use this filled clock-change checklist
Hypothetical operating record: All campaign settings, names, approvals, and evidence below are fictional. Calendar conversions use the cited rules. Every saved value is in Europe/London, and every target is 09:00 customer-local. The table records proposed decisions; the sign-off records simulated checks after authorised changes.
| Occurrence | Customer zone and dated offset | UTC; London equivalent | Saved London time | Reviewer and decision |
|---|---|---|---|---|
| New York Monday, 2 March 2026 | America/New_York; −05:00 | 14:00; 14:00, +00:00 | 14:00 | Maya: unchanged; baseline. |
| New York Monday, 9 March 2026 | America/New_York; −04:00 | 13:00; 13:00, +00:00 | 14:00 | Maya: correct to 13:00. |
| New York one-off, 12 March 2026 | America/New_York; −04:00 | 13:00; 13:00, +00:00 | 14:00 | Theo: correct to 13:00; check for duplicates. |
| New York Monday, 16 March 2026 | America/New_York; −04:00 | 13:00; 13:00, +00:00 | 14:00 | Maya: correct to 13:00. |
| New York Monday, 23 March 2026 | America/New_York; −04:00 | 13:00; 13:00, +00:00 | 14:00 | Maya: correct to 13:00; last Monday exception. |
| New York Monday, 30 March 2026 | America/New_York; −04:00 | 13:00; 14:00, +01:00 | 14:00 | Theo: unchanged; after-mismatch check. |
| Dubai Monday, 23 March 2026 | Asia/Dubai; +04:00 | 05:00; 05:00, +00:00 | 05:00 | Lina: unchanged; before-transition baseline. |
| Dubai Monday, 30 March 2026 | Asia/Dubai; +04:00 | 05:00; 06:00, +01:00 | 05:00 | Lina: correct to 06:00. |
| Dubai Monday, 6 April 2026 | Asia/Dubai; +04:00 | 05:00; 06:00, +01:00 | 05:00 | Lina: correct to 06:00; horizon endpoint, not correction endpoint. |
Filled sign-off and follow-up:
- Reference: IANA tzdb 2025b regional files linked above; Theo records the reference used. This is not a claim of live source retrieval.
- Authorisation: Fictional campaign owner Priya approves the six occurrence-level corrections before execution.
- Saved-value evidence: The fictional review register records reopened values of 13:00 London for the three affected New York Mondays and its one-off; 06:00 for both affected Dubai Mondays. Unchanged entries match the table.
- Duplicate check: Theo records one active occurrence per intended audience and date within the reviewed horizons.
- Bounded disposition: Nine occurrences reviewed: three verified unchanged and six corrected and rechecked. This does not close either recurrence indefinitely.
- Open Dubai follow-up: Lina must review the Mondays from 13 April through 1 June by 7 April 2026, using date-specific conversions and inspecting saved values. Priya must authorise resulting changes. Approval of those later occurrences remains pending; their execution state must be confirmed rather than assumed paused.
- Next boundary: The follow-up must assign the next review horizon and owner before closing. Do not restore Dubai to 05:00 London merely because the New York exceptions ended.
Reuse the fields and decision structure, not the dates. A horizon limits what the record proves; it does not remove responsibility for later scheduled sends.
5. Choose the smallest authorised correction
For a one-off, changing that occurrence is usually easier to review than editing a shared rule. For a recurrence, establish what the scheduling environment supports before choosing between a customer-zone rule and explicit dated exceptions.
A customer-zone recurrence may reduce manual conversion work. Exceptions make a short mismatch visible but can be forgotten or duplicated. Check the workspace and current plan for availability, and inspect future occurrence values using the methods actually provided. These are recommended operating practices, not claims about specific Alactic controls.
In the hypothetical record, occurrence-level changes bound the New York adjustment neatly. The Dubai changes address only two dates; its continuing requirement needs the assigned follow-up. If changing the whole Dubai rule instead, verify its effective start and inspect later occurrences before signing off.
Do not shift the entire calendar. Some campaigns intentionally follow headquarters time; others may already be correct. Check audience overlap before replacing regional copies. A proposed correction is not authorisation to execute it.
6. Check ambiguous times and message readiness
Near a transition, local times can be skipped or repeated. A bare timestamp may not identify a valid, unique instant. Establish the intended offset and occurrence, or move a routine campaign to an unambiguous staffed period. Event-linked messages must retain their relationship to the event.
Review message text as well as schedule data. A correctly scheduled reminder can still name the wrong appointment time or omit an essential zone. Confirm reply coverage and a clear human escalation path where automation is involved.
For WhatsApp, correct timing does not establish recipient permission or override an opt-out. Keep campaign preparation, template review, and actual delivery as separate states.
Approved templates are used to initiate Platform conversations and outside the 24-hour customer-service window, which opens or resets with a user message. Check the current WhatsApp Business Messaging Policy for precise requirements. Template approval does not guarantee delivery.
7. Recover carefully if the mismatch is discovered late
Establish the occurrence’s actual state before creating a replacement. A draft, queued send, and already processed send require different responses.
- Contain: Where authorised and available, pause or cancel affected future occurrences without disturbing unaffected audiences.
- Reconcile: Use available records to distinguish pending recipients, recorded sends, and uncertain statuses.
- Decide: Correct pending sends, postpone, or skip the occurrence according to its remaining usefulness.
- Verify: Establish that the original and replacement are not both active for the same recipients.
An uncertain status is not proof that nothing happened. Hold the replacement until the team can make an informed decision.
If a message already went out at the wrong hour, an explanation may create unnecessary additional contact. Consider a correction when the content itself needs clarification, such as an incorrect event time. Repair later affected occurrences separately.
8. Close the reviewed dates, not the whole calendar
Can another operator reconstruct the intended local time, dated conversion, authorised decision, and final saved value for every inventoried occurrence? Can they identify both temporary-exception endpoints and continuing obligations?
Close individual entries as verified unchanged, corrected and rechecked, or held pending clarification. Separately list future dates outside the horizon, their owner, and the review deadline. A pending review is not evidence that a send has been paused.
In this example, the New York temporary exceptions end on 23 March, with 30 March checked. Dubai is verified only through 6 April, and its later Mondays remain an open follow-up. That distinction makes the record useful to the next operator.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications