Scheduling a meeting across three or more time zones is one of those problems that looks trivial in a calendar app and turns out to be genuinely hard. The standard work hours of 9 AM to 5 PM, applied simultaneously in Los Angeles, London, and Tokyo, produce exactly zero overlap. Los Angeles starts its workday as London ends theirs, and Tokyo is already asleep. A four-zone team — say San Francisco, New York, Berlin, and Bangalore — has maybe two hours of mutual overlap, and those hours fall in the worst possible windows for someone. Companies that solve this problem badly burn out their distributed teams within a year. Companies that solve it well ship faster than their colocated competitors, because they can work around the clock. The difference is not luck; it is a small set of practices that any team can adopt.
The overlap math: when there is no good answer
The first step is to stop pretending a perfect meeting time exists. For a team spanning Los Angeles, London, and Tokyo, the honest answer is that no single slot falls within reasonable working hours for all three. Los Angeles 8 AM is London 4 PM and Tokyo 1 AM. London 9 AM is Los Angeles 1 AM and Tokyo 6 PM. Tokyo 9 AM is London midnight and Los Angeles 4 PM. Every option asks one city to take a hit.
The standard error is to optimize for the scheduler's time zone and let the others absorb the inconvenience. A New York-based project manager who books a 2 PM call for the team that includes Los Angeles, London, and Bangalore has scheduled a meeting at 11 AM Los Angeles (fine), 7 PM London (intrusive but acceptable), and 4:30 AM Bangalore (brutal). Over time, the Bangalore team disengages, the London team grows resentful, and the New York team wonders why their global colleagues seem checked out.
The fix is rotation. For recurring meetings, cycle the time slot through the participating time zones on a regular cadence — weekly for high-frequency meetings, monthly for lower-frequency ones. Week one: 8 AM Los Angeles, 4 PM London, 1 AM Tokyo (Tokyo takes the hit). Week two: 5 PM Los Angeles, 1 AM London, 10 AM Tokyo (London takes the hit). Week three: 7 AM Los Angeles, 3 PM London, midnight Tokyo (Los Angeles takes a small hit, Tokyo takes a big one). The pattern distributes the pain evenly. Document the rotation in a shared calendar so no one has to negotiate each week.
Async-first: the philosophy that makes overlap matter less
The deepest fix for time-zone pain is to need fewer meetings in the first place. Companies that run effectively across many time zones — GitLab, Automattic, Zapier, Doist — have built their cultures around asynchronous communication, where the default is written, the expectation is response within 24 hours rather than immediate, and meetings are reserved for the small subset of conversations that genuinely require real-time interaction.
GitLab's handbook, which is public and runs several hundred pages, articulates the principle bluntly: "If you can't write it down, you don't understand it well enough." Decisions are made in issues and merge requests, with full context in writing. Anyone in any time zone can contribute to a decision by commenting on the document, and the decision-maker can incorporate that input without blocking on a synchronous call. The result is that GitLab, with employees in more than 65 countries, holds fewer synchronous meetings than many colocated companies of equivalent size.
Adopting async-first requires investment in writing discipline. Status updates become structured documents, not hallway conversations. Decisions are recorded with their rationale, not just their outcome. Onboarding material is written once and updated continuously. The upfront cost is real — writing things down takes longer than saying them — but the compounding payoff is that information is searchable, accessible across time zones, and durable across employee turnover.
Daylight Saving Time: the chaos you forgot to plan for
Twice a year, in March and November, the time-zone math that you finally got working quietly breaks. The United States springs forward on the second Sunday in March and falls back on the first Sunday in November. Europe springs forward on the last Sunday in March and falls back on the last Sunday of October. Most of Asia, Africa, and South America does not observe DST at all. The result is a three- to four-week window each spring and fall where your scheduled meeting times drift by an hour relative to each other.
The failure mode is subtle. A recurring 9 AM London / 5 PM Tokyo meeting on the calendar stays at 9 AM London and 5 PM Tokyo in the calendar app — but in early November, when the U.S. has fallen back and Europe has not, the same calendar entry that worked in October is now an hour off relative to your U.S. colleagues who suddenly find the meeting at 8 AM instead of 9 AM. Calendar apps are getting better at handling this, but they are not perfect, and the people in the meetings are often worse.
The defense is awareness. Mark the DST transition weeks on the team calendar. Send a reminder the Monday before each transition confirming the meeting time in each local time zone. For meetings that fall in the transition window, double-check the actual local time for each participant before sending the invite. This is unglamorous work, but the alternative is the recurring experience of one person showing up an hour early or an hour late, which erodes trust in the team's scheduling competence.
Follow the sun: turning time zones into an advantage
The most ambitious distributed teams do not just tolerate time zones; they exploit them. A "follow the sun" workflow hands work from one time zone to the next as each office comes online. A bug reported at 9 AM San Francisco time gets triaged by the afternoon, handed off to the Bangalore team as they start their day, fixed overnight, reviewed by the London team as they start theirs, and merged before San Francisco logs back in. The total elapsed time is 24 hours, but no single person has worked more than their normal day.
Follow the sun works only for work that can be cleanly handed off: software development with clear tickets and code review, customer support with a ticket queue, content moderation with an inbox. It does not work for design work that requires iteration, strategic decisions that require debate, or any work that requires deep context shared across the handoff. Most teams are honest about which of their workflows are sun-followable and which are not.
The handoff discipline is the crux. Each handoff needs a written summary: what was started, what was finished, what is blocked, what the next team should pick up. Without this, the morning team wastes the first hour of their day reconstructing yesterday's context. The discipline compounds: a team that writes clean handoffs learns to write clean tickets, which makes the work itself clearer, which makes the handoffs easier, in a virtuous cycle.
Calendar hygiene: the small habits that prevent disaster
A few specific practices prevent most time-zone scheduling disasters. First, always display the meeting time in each participant's local zone in the invite — most calendar apps do this automatically if invitees have set their own time zones, but only if they have actually set them. A quick team exercise of confirming everyone's time zone setting in their calendar app prevents a surprising number of mishaps.
Second, use a time-zone picker tool (like timeanddate.com, World Time Buddy, or our Meeting Time Overlap Calculator) for any meeting involving three or more zones. The visual grid of overlapping work hours makes the trade-offs visible at a glance, and the saved link can be shared with participants so they can verify their own local time.
Third, default to recording any meeting with participants across more than two time zones. Someone will not be able to attend, and a recording with shared notes is dramatically more useful than a second-hand summary. Use an AI transcription service to produce a written record that anyone in any time zone can search and read at their own pace.
Fourth, protect the boundaries. A 6 AM or 10 PM meeting once a quarter is tolerable; the same meeting weekly will drive good people to quit. If your team's recurring meetings routinely fall outside one participant's 8 AM to 6 PM window, something is structurally wrong with the schedule, and rotating the time or moving the meeting async is the only durable fix.
Fifth, name a "meeting owner" for each recurring meeting who is responsible for the time-zone fairness. Without an owner, no one is accountable for rotation, and the schedule calcifies around whatever was convenient for the most powerful participant. With an owner, the rotation gets revisited, the DST transitions get caught, and the boundaries get protected. Distributed teams that solve this problem well almost always have someone whose implicit job it is to watch it.
Scheduling across time zones is not glamorous work, but it is the connective tissue of distributed teams. Done badly, it produces resentment, disengagement, and quiet attrition. Done well, it lets a team in five time zones operate with the speed and coherence of a team in one. The practices are simple, the discipline required is real, and the competitive advantage for teams that get it right is durable.