Recurring meeting drift

Questions

FAQ

What does "drift" actually mean here?

If your meeting is 9am New York every Monday, the Sydney teammate's local time isn't constant — it shifts by an hour twice a year because New York and Sydney transition into and out of DST on different dates. The drift table shows you exactly which weeks each teammate's local meeting time changes, so you can warn them in advance.

Why are some weeks highlighted?

A highlighted cell marks a DST transition: the UTC offset for that target zone changed compared with the previous week. That's the moment a recurring meeting actually moves for that person — the day they show up an hour early or an hour late if no one warned them.

Does the meeting time stay constant in the source zone or shift?

It stays constant in the source zone. If you specify 9am Monday New York, every row resolves to 9am Monday New York — and every target zone's local time is computed from that moment. This is the standard behaviour calendar apps assume; it's what causes the surprise drift for everyone else.

Can I model a meeting that drifts in the source zone too?

Not in this tool. If your meeting is anchored to UTC instead of a city (common for global engineering on-call), every teammate including the host sees drift. For that case, use the Time Zone Converter with a fixed UTC time and rotate through the dates manually.