Time zone research

Why Southern Hemisphere Meetings Drift Twice as Far

It is natural to assume that daylight saving affects everyone equally, since most zones shift by one hour. Our measurement shows that the amount of drift a participant experiences depends on how many independent shift events the anchor and their zone cross. A northern anchor paired with a southern zone crosses two, which doubles the spread.

By BeanNest Studio Reviewed September 20, 2026

What this guide helps you decide

Two participants in zones that both observe daylight saving see different amounts of drift. Why?

This research compares measured drift between northern and southern zones against a fixed anchor. It does not claim a universal ratio and does not describe any organisation's scheduling policy.

Try it on the anchor product: BeanNest Time /, BeanNest Time /meeting-planner/.

The measured comparison

Anchoring a weekly meeting to Vancouver, a London participant showed two shift values with a spread of sixty minutes. A Sydney participant showed three shift values, 1020, 1080, and 1140 minutes, with a spread of one hundred twenty minutes.

Why the hemisphere matters

Vancouver advances its clocks in the northern spring and returns in the northern autumn. Sydney advances in the southern spring and returns in the southern autumn, which fall in the opposite halves of the calendar year. The two schedules therefore cross twice per year rather than coinciding.

How the crossing produces three values

Between the crossings the two zones are both in or both out of daylight saving, so the shift is at a middle value, 1080 in this case. Just after one zone has changed but before the other has, the shift moves to 1020 or 1140. The two independent change dates create three distinct states across the year.

The practical consequence

Southern participants see the largest movement because their shift dates are least likely to align with a northern anchor. A meeting planner that only knows about northern DST dates will misjudge every southern participant for weeks around each transition.

Zones with no DST avoid this entirely

Tokyo showed a spread of sixty minutes against the same anchor, and Kolkata also showed sixty, despite neither zone observing daylight saving. The movement comes entirely from the anchor changing. A meeting anchored to a no-DST zone with no-DST participants does not drift at all, which our evidence set confirms with three zero-transition zones.

Reading the evidence directly

Our evidence file records each zone's January and July offset, its transition count, and every transition with its from and to offsets. The southern doubling is visible as a transition count and as the distinct shift list rather than as a narrative, so a reader can verify it without trusting this prose.

Why the number of crossings decides the spread

Each time either zone changes offset, the difference between them moves to a new value. Two northern zones changing on nearby dates cross together, producing two values. A northern zone and a southern zone change in opposite halves of the year, so their changes are separated by months and produce three values: one when both are in, one when both are out, and one while they are split. The spread follows directly from the count.

Why northern anchors are common and costly

Most scheduling tools and most teams anchor to a northern city because that is where the organising group sits. That choice maximises the chance that the other participant's zone changes in the opposite season, which is precisely the case that produces the widest spread. Anchoring to a zone that does not observe daylight saving would remove the effect for participants in similar zones entirely, which the three zero-transition zones in the evidence set demonstrate.

How to read the crossing directly

The transitions array in the evidence file lists each change with its instant and offsets. For a given pairing, comparing the two arrays shows which changes happen close together and which are months apart. That comparison is the mechanical explanation of the measured spread, and it can be performed on the file without trusting this prose.

What this does not claim

The measured spread describes one anchor and one target per pairing, for one year. It is not a universal ratio and it would change if the anchor moved or if either zone changed its rules. The guides present it as a measured example that illustrates the mechanism, which is the strongest claim the evidence can support.

Why the anchor choice dominates the result

Every pairing in the model is measured against one anchor, so the anchor's transition dates appear in every pairing. Choosing a northern anchor therefore guarantees that any southern participant will be split for part of the year. Moving the anchor to a zone without transitions would remove the anchor's contribution entirely, which is what the no-transition zones in the evidence set demonstrate.

How many distinct states the year visits

Two zones that both change offset visit one state while both are in standard time, one while both are in daylight time, and one while they are split. A northern and a southern zone therefore visit three states, which is exactly what the Sydney pairing measured at 1020, 1080, and 1140 minutes. The number of states follows from the number of independent change dates rather than from the zones' locations.

What the spread figure actually communicates

The spread is the difference between the largest and smallest shift across the year, so it measures how much a participant's local time moves relative to the anchor. A spread of one hundred and twenty minutes against sixty for the northern pairings means the southern participant experiences twice the movement. That comparison is the useful output rather than any single shift value.

Why the guide does not recommend an anchor

Choosing an anchor is a scheduling decision that depends on who attends and where they are, which the evidence set does not know. The guide reports what the choice costs in measured drift and leaves the decision to the reader. Publishing a recommendation would go beyond what the evidence supports.

How the comparison is set up

Every pairing measures a weekly meeting anchored to the same fixed local time in the same reference zone against a different target zone. Holding the anchor and the time constant means the only variable is the target's transition pattern, so the difference in spread is attributable to the target rather than to the model. That control is what makes the Sydney result comparable with the London result.

What the two transitional zones show together

London and Sydney both change offset twice, and both produce movement relative to the anchor, yet Sydney produces a wider spread. The difference is the dates, not the count, which is why a guide that only counted transitions would miss the effect. Comparing the two targets is what isolates the timing as the cause.

How the split period looks from each side

During the split, one zone has changed and the other has not. A participant in the zone that changed sees the meeting move by an hour; a participant in the zone that has not yet changed sees it stay where it was. The asymmetry lasts until the second zone changes, which is why the effect is temporary but recurring twice a year.

What a reader should take away

The measured spread quantifies how much a schedule moves for a given anchor and target, and the mechanism explains why a southern target moves more. Together they let a reader predict that a southern participant will need attention around two periods a year, which is a concrete planning input rather than a general warning.

How a reader can predict the case for their own pairing

Read both zones' transition instants from the evidence file and compare them. If the changes cluster in the same weeks, expect two shift values; if they are separated by months, expect three. That comparison requires no calculation beyond reading the instants, and it generalises to any pairing the file covers.

Why the measured spread is reported in minutes

Minutes make the comparison precise and directly usable, since a shift figure can be applied to a meeting time without conversion. The three Sydney values of 1020, 1080, and 1140 minutes correspond to seventeen, eighteen, and nineteen hours, a difference a scheduler can act on immediately.

First-party evidence and provenance

How we checked this

We derived every offset and transition from the runtime's own time-zone database by sampling the zone offset hourly across the calendar year, then modelled a weekly meeting pinned to a fixed local wall-clock time in a reference zone. The generator is in this repository and the evidence file is its output. For this guide we compared transition counts and distinct shift values between a northern anchor and each target zone, which is what shows the southern doubling rather than asserting it.

Method: We derived every offset and transition from the runtime's own time-zone database by sampling the zone offset hourly across the calendar year, then modelled a weekly meeting pinned to a fixed local wall-clock time in a reference zone. The generator is in this repository and the evidence file is its output.
Environment: Node.js on a desktop workstation, using the bundled IANA time-zone data. No network call, no hard-coded offset table, and no user data.
Captured: September 20, 2026
Reviewed by: BeanNest Studio

Repository evidence artifacts:

tools/research-evidence/time/transitions-2026.json
tools/research-evidence/time/README.md