Time Zone Conversions for Remote Teams: Offsets, DST, and Half-Hour Zones

Remote teams lose more hours to time zone confusion than to almost any other scheduling problem. A standup that takes 15 minutes to run can cost a distributed team an hour of wasted asynchronous back-and-forth if the conversion is wrong by a single day.

The Three Failure Modes

Failure	What goes wrong	Typical cost
Day boundary error	“Tuesday 9 a.m. PT” is actually Wednesday in Sydney	Someone misses the meeting entirely
DST mismatch	US and EU switch on different dates, so the offset changes for 2–3 weeks twice a year	Meetings off by one hour with no warning
Half-hour offsets	India (+5:30), Newfoundland (−3:30), Nepal (+5:45) are not whole hours	Recurring 30-minute misalignment

The second one is the one that catches experienced teams. The United States moves to daylight saving on the second Sunday in March and back on the first Sunday in November. The European Union switches on the last Sunday in March and the last Sunday in October. Between those dates, the gap between New York and London shifts from 5 hours to 4 hours — and back again in the autumn. A remote team scheduling around date and time calculations should treat those transition weeks as the highest-risk period of the year.

The Offsets Worth Memorizing

These are the standard-time offsets, which is what you should use as a baseline before adjusting for DST:

Region	Standard offset from UTC	Notes
US Pacific	−8	DST: −7
US Eastern	−5	DST: −4
UK	0	DST (BST): +1
Central Europe	+1	DST (CEST): +2
India	+5:30	No DST — offset is constant year-round
Japan	+9	No DST
Sydney	+10	DST: +11 (southern hemisphere, opposite season)

The southern hemisphere detail matters more than it looks. Sydney observes daylight saving during the northern winter, which means the Sydney–New York gap swings between 14 and 16 hours across the year — twice as much variation as a transatlantic pair.

Example: Scheduling a Recurring Standup

Suppose a team spans San Francisco, Berlin, and Bangalore, and wants a daily standup at a reasonable hour for everyone.

Anchor the meeting in UTC, not in anyone’s local time. Pick 14:00 UTC.
San Francisco: 06:00 (DST) or 07:00 (standard) — early but workable.
Berlin: 16:00 (CEST) or 15:00 (CET) — comfortable.
Bangalore: 19:30 — late but consistent, because India never shifts.

Notice that only the DST-observing locations move. Anchoring in UTC means the meeting time is stable as a global event, and the local drift is confined to the two cities that shift.

Practical Rules That Reduce Errors

Always write the offset, not just the zone name. “14:00 UTC” is unambiguous; “2 p.m. CET” is not during the transition weeks.
Put the date on both sides of a cross-day conversion. If a converted time lands on a different calendar day, state both dates explicitly.
Stop converting manually for recurring events. A converter that accounts for DST transitions will not forget the March and November changes.
Record meeting times in the invite as UTC first, then let the calendar tool render local times.

You can check any specific conversion, including the half-hour and quarter-hour offsets, with our time duration calculator. For meeting-length arithmetic — how much overlap two working days actually share once you account for the offset gap — the calculator handles the subtraction across midnight without the manual day-boundary error.

Frequently Asked Questions

How many time zones are there?

Twenty-four nominal zones of one hour each, but over 38 distinct offsets are in use because of half-hour and quarter-hour zones and political boundaries. China uses a single offset across five geographic zones.

Why does India use +5:30?

India adopted a half-hour offset to split the difference between the eastern and western parts of the country, keeping both within a reasonable margin of solar noon.

Do any countries not observe DST?

Most of the world. China, India, Japan, and most of Southeast Asia do not. In the European Union, the practice is under periodic review but remains in force.