Time zone math for distributed teams: the survival guide

Most problems people blame on "remote work" are actually time zone problems. When a team is spread across 4–10 time zones, the daily friction isn't bandwidth, isn't culture, isn't even communication tooling — it's that nobody can find a meeting time that works for everyone, and the workarounds for that fact compound into burnout, missed deadlines, and quietly stalled projects.

This is the survival guide for the math of running a distributed team. It's not a manifesto about remote work being good or bad. It's the specific patterns that work when your team genuinely cannot all be awake at the same time.

The 'overlap hours' formula

For any two team members in two time zones, their overlap hours are roughly:

Overlap = max(0, 8 - |zone difference|)

Assuming both work an 8-hour day. So San Francisco (PST) and New York (EST) — 3 hours apart — have about 5 overlap hours. San Francisco and London — 8 hours apart — have effectively zero overlap during normal business hours. Either one person stretches early or the other stretches late; there's no fully-inside-business-hours overlap to find.

For three or more team members, the math compounds quickly:

The math is non-negotiable. A team across 16+ hours of time-zone spread cannot all be awake at once during business hours. The choice isn't "can we?" — it's "who stretches, and how often."

The three meeting patterns that actually work

1. Rotation: the burden moves

Pick a meeting time that's inconvenient for someone, but rotate which person carries the inconvenience week-to-week. A weekly engineering sync at 7 AM SF / 3 PM London / 8:30 PM Mumbai might rotate to 4 PM SF / 12 AM London / 4:30 AM Mumbai the next week. Each region takes the bad slot every third or fourth week.

Rotation is the most psychologically fair pattern: nobody is permanently on the bad end. But it requires discipline — the rotation must actually rotate, and managers must defend it when single-week pressure makes someone want to 'just do it at the easy time this week.'

2. Hub-and-spoke: regional sub-meetings

Instead of one meeting for everyone, run two regional meetings — one for Americas/EMEA, one for EMEA/APAC, with EMEA attending both. A senior person attends both as the connection point.

This costs the connector person two meetings instead of one, but everyone else gets a working-hours meeting. For company-wide all-hands, you can record one and have the other watch the replay with a comment thread for follow-up. Don't pretend the replay is the same as attending — it isn't — but it's better than half the company sleeping during a meeting they're nominally part of.

3. Pure async: documents and Loom videos replace meetings

For most team coordination — status updates, design discussions, decision documents, project planning — meetings can be replaced entirely by written or recorded async work. The trade is: more written work upfront, no live overlap required.

Async meetings work when there's a strict format. The format that works for most teams:

• •A document with the meeting topic, context, and pre-read material posted at least 24 hours before the "meeting time."
• •Each participant reads and leaves comments within their working day before the deadline.
• •A 15–30 minute live wrap-up call at the overlap hour to resolve any remaining open threads. Not everyone attends; only the people with open threads.

Asynchronous-first teams ship more in calendar weeks because they don't accumulate scheduling debt. The trade-off is that the writing has to be good — vague pre-reads produce vague async meetings.

The hidden cost: DST transitions

Twice a year, the US and Europe shift DST on different weekends — meaning for a 1–3 week window each spring and autumn, the time-zone gap between regions is one hour off the usual. A meeting that's at 4 PM London / 11 AM New York in mid-February might be at 4 PM London / 10 AM New York in mid-March (US shifts first), then back to 4 PM London / 11 AM New York at the end of March (UK catches up).

Calendar tools handle this transparently if the meeting was created with explicit time zones. They handle it badly if the meeting was created at "11 AM Eastern" without specifying which DST regime. Two hours of confusion per year is the median cost of getting this wrong.

India, half-hour offsets, and the assumption everybody else gets wrong

India is UTC+5:30 — half an hour off the nearest hour. This breaks meeting-time math in a specific way: when someone says "the meeting is at the top of every hour London time," the corresponding India time is at the half-hour. A 9 AM London meeting is 2:30 PM Mumbai, not 2 PM. The half-hour offset is the source of most cross-region scheduling errors that affect Indian teammates.

Other half-hour and quarter-hour zones include Newfoundland (UTC-3:30), Iran (UTC+3:30), Afghanistan (UTC+4:30), Nepal (UTC+5:45), Myanmar (UTC+6:30), parts of Australia (UTC+8:45 in Eucla, UTC+9:30 in Adelaide), and Chatham Islands (UTC+12:45). If your team includes any of these, the time-zone math gets weird in predictable ways — use a tool that respects the offset.

Cultural workday conventions that change everything

A 9-to-5 schedule is one of many. The work-hours assumptions baked into "find an overlap" calculations need adjustment for several regions:

• •Sunday-to-Thursday workweeks: Israel, UAE, Saudi Arabia, and several other countries. Friday is the equivalent of Saturday in the US — most professionals aren't working. A "Friday afternoon ship review" is the local equivalent of "Saturday afternoon ship review" for those teammates.
• •Mid-day breaks: Spain and parts of Latin America traditionally take 2–3 hour mid-day breaks. The 14:00–16:00 slot is empty. Calls scheduled then will have low attendance.
• •Late workday endings: Japan, Korea, and parts of Southern Europe have culturally later workday endings — 18:00–20:00 is normal. Scheduling 17:30 calls is acceptable; scheduling 19:30 calls is fine in some regions and aggressive in others.
• •Early morning starts: Northern Europe and the US Northeast often start meetings at 08:00 or earlier. Scheduling 07:30 calls is normal there; in Spain or India, the same time feels brutal.

Working hours boundaries — and the right way to set them

Healthy distributed teams write down a "core hours" or "expected response time" policy explicitly. Examples that work:

• •"Core hours: 10 AM – 4 PM in your local zone. Meetings only inside core hours; async outside."
• •"Expected response time: 24 hours during weekdays. Slack pings outside your zone's working hours don't expect immediate reply."
• •"Meeting-free Fridays: no recurring meetings on Fridays; protected for deep work."

The point of writing it down is removing ambiguity about whether you're 'on' at 9 PM your time because someone in another zone is pinging during their workday. Without a written policy, the default expectation is 'always on' and that's how distributed-team burnout happens.

The 'low-bandwidth backbone' principle

The best distributed teams treat synchronous time as expensive and scarce. They build their workflows around the assumption that the team can never all be online simultaneously — so synchronous communication is reserved for things that genuinely require it (decision-making with multiple stakeholders, high-trust 1:1s, brainstorming sessions). Everything else — status, updates, planning, code review, documentation — flows through written and asynchronous channels that don't depend on anyone being awake.

Teams that try to run a distributed team like a co-located team — with daily standups and frequent live meetings — burn out their members in the time zones with the worst overlap. Teams that genuinely embrace async tend to retain people in those zones much longer.

The pragmatic takeaway

Time-zone math for distributed teams is mostly about accepting constraints rather than optimizing them. You cannot make a 12-hour gap disappear. What you can do is decide who pays the cost of crossing it, rotate that cost fairly, and replace as many sync meetings with async work as possible. The technical tools — meeting planners, world clocks, time-zone converters — exist to make the math visible. The hard part is the policy decisions about who stretches their day and when.

If you're running a distributed team and finding that scheduling is the dominant frustration, that's the signal that you've drifted into running it like a co-located team. The mental shift is: synchronous time is the scarcest resource, and the team's job is to spend it like it's expensive.