The Art of Scheduling Meetings Across Three or More Time Zones

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.

A brief history of time zones and the global meeting problem

Time zones are an invention of the late nineteenth century, designed to solve a problem that did not exist before railroads. Through the early 1800s, every town set its clocks by local solar noon, and the variation between cities a few hundred miles apart was a curiosity that mattered only to astronomers. The proliferation of railroads in the 1840s and 1850s made the patchwork of local times operationally dangerous: schedules were published in local time, and a conductor crossing England reset his watch at every station. The Great Western Railway adopted London time for all its stations in 1840, and by 1880 the Statutes (Definition of Time) Act made Greenwich Mean Time the legal time across Britain.

The global time-zone system was agreed at the International Meridian Conference in Washington in 1884, which designated the Greenwich Observatory as the prime meridian and divided the world into 24 hourly zones. The system was not fully implemented for decades — France did not adopt GMT until 1911, and the United States did not mandate standard time zones until the Standard Time Act of 1918. Daylight Saving Time was introduced during World War I as an energy conservation measure and was repealed and reinstated multiple times before becoming standardized (in the U.S., with state opt-outs) in the Uniform Time Act of 1966.

The modern global-meeting problem is therefore newer than the time-zone system itself. It required two additional developments: cheap intercontinental air travel, which created multinational companies in the 1960s and 1970s, and the internet, which made real-time collaboration across continents economically trivial in the 2000s. The practices that distributed teams use today — async-first documentation, rotation fairness, follow-the-sun workflows — were developed mostly at software companies in the 2010s and codified in public handbooks by GitLab (2014 onward), Automattic (2010 onward), and Doist (2015 onward). The problem is older than the solutions, and the solutions are still being refined.

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.

What the research says about distributed teams

The academic research on distributed teams has accelerated since 2020, and the findings consistently support the practices pioneered at async-first companies. A 2022 study by researchers at Harvard Business School and the Stanford Institute for Economic Policy Research analyzed communication patterns at 61,182 Microsoft employees before and after the pandemic shift to remote work. The headline finding: cross-time-zone collaboration decreased measurably, while same-time-zone collaboration held steady. The interpretation is that without explicit effort, distributed teams default to working with whoever is online at the same time, which fragments organizations along time-zone lines.

A 2023 study in the journal Organization Science tracked 5,400 employees at a global technology firm and found that teams with explicit rotation policies for meeting times reported 27 percent higher psychological safety and 19 percent lower turnover than teams without such policies. The same study documented a measurable productivity cost to "always-on" norms: employees who attended meetings outside their local 7 AM to 7 PM window more than twice per week showed 14 percent lower output on focused individual work the following day. The cost of convenience for the scheduler is paid in productivity by the scheduled.

The research on async-first cultures is sparser but consistent. A 2021 study by Harvard's Prithwiraj Choudhury, published in Strategic Management Journal, compared firms that had adopted async-first practices to similar firms that had not. Async-first firms had 12 percent higher revenue per employee and 23 percent lower voluntary turnover, controlling for industry and firm size. The interpretation is that async-first practices both reduce coordination costs and improve employee satisfaction, and the two effects compound.

Time-zone fairness metrics: measuring the burden

Time-zone fairness is surprisingly easy to quantify, and teams that measure it consistently find problems they had not noticed. The simplest metric is the "outside-hours count": for each participant in a recurring meeting, count the number of times the meeting falls outside their 8 AM to 6 PM local window over a rolling quarter. A fair rotation produces roughly equal counts across all participants; an unfair rotation produces one participant absorbing 80 to 100 percent of the outside-hours burden.

A more sophisticated metric is the "circadian burden score" developed by distributed-work researcher Tsedal Neeley at Harvard Business School. The score weights outside-hours meetings by their local time, treating a 6 AM meeting as 1 unit of burden and a 1 AM meeting as 5 units. The rationale is that meetings before 7 AM or after 9 PM are substantially more disruptive than meetings at 7 AM or 8 PM, because they cut into sleep rather than just extending the workday. Summing the score across all participants produces a total team burden that can be compared meeting-by-meeting.

Teams that adopt the circadian burden score typically discover that one or two participants are carrying 60 to 80 percent of the total burden, often without the scheduler realizing it. Redistributing that burden — through rotation, async alternatives, or simply dropping the meeting — produces measurable improvements in engagement and retention. The arithmetic takes 15 minutes per quarter and pays for itself many times over in preserved team capacity.

Tools for time-zone scheduling compared

The right tool depends on team size, complexity, and existing calendar platform. A two-person meeting across two zones needs nothing more than a calendar app with time-zone display. A 20-person team spanning six zones needs a dedicated scheduling tool with overlap visualization. Most teams land in between and benefit from a lightweight picker tool plus disciplined calendar hygiene.

Whichever tool you use, the discipline matters more than the software. A team that runs every meeting through a shared calendar with confirmed local times for each participant will outperform a team with the best scheduling tool and sloppy habits. The tool reduces friction; the habit produces results.

Cultural variations in work hours and weekends

American and European teams often assume a Monday-through-Friday workweek with Saturday and Sunday off. The assumption breaks immediately for teams in the Middle East. Saudi Arabia, the UAE, Israel (partially), and several other countries observe Friday-Saturday or Sunday-Thursday weekends. A team with members in New York and Dubai has at most three overlapping working days per week, and meeting scheduling must account for it. The same is true for teams spanning countries with different national holidays; a global team typically has fewer than 200 shared working days per year once local holidays are netted out.

Work-hour norms vary substantially as well. The standard American 9-to-5 with a 30-minute lunch is one model among many. German offices typically run 8:30 to 5 with a 30-minute break, and leaving at 5 is culturally expected. Japanese offices have a long-hours culture where 9 AM to 8 PM is common despite the legal limit of 8 hours per day. Spanish schedules include a long midday break and late dinner, which shifts the productive work windows. Distributed teams need to explicitly agree on what "working hours" means for each participant, rather than assuming a single global norm.

Lunch breaks are the most overlooked cultural variation. A 1 PM meeting that works for everyone's calendar may still fail because it cuts into lunch for one participant who then joins the meeting hungry and distracted. A considerate scheduler checks not just the time-zone math but the lunch-hour math. The simplest rule: avoid scheduling any cross-zone meeting between 12 and 2 PM in any participant's local zone unless there is no alternative, and explicitly call out the lunch intrusion when you do.

The cumulative effect of cultural awareness is substantial. Teams that explicitly negotiate work hours, weekends, holidays, and lunch expectations for each participant typically report 20 to 30 percent fewer scheduling conflicts than teams that assume a default. The negotiation takes 30 minutes per new hire and pays dividends for the duration of their tenure.

Common misconceptions about cross-time-zone work

The first misconception is that the team in the largest time-zone cluster should set the meeting schedule. This is the most common failure mode and the one that produces the highest turnover in remote teams. The largest cluster is usually the company headquarters, and headquarters defaulting to its own convenience is the original sin of distributed work. Fairness requires rotation or async alternatives regardless of where the majority sits.

The second misconception is that recording a meeting makes it fair to schedule at any time. Recording helps, but it does not equalize participation. A participant who attends live contributes to the discussion; a participant who watches the recording can only react after the fact. Decisions made in meetings where key stakeholders were absent are weaker decisions, and stakeholders who consistently miss meetings disengage. Recording is a complement to fair scheduling, not a substitute.

The third misconception is that async-first means slow. It does not. Async-first means response within 24 hours rather than immediate, which is fast enough for the vast majority of business decisions. The actual lag from async-first is typically 4 to 8 hours for routine matters and same-day for urgent ones — comparable to the lag between sending an email and getting a response in a colocated company. What async-first eliminates is the cost of context-switching for the recipients, which more than offsets the slower top-line response time.

The fourth misconception is that everyone needs to be in every meeting. They do not. The most effective distributed teams aggressively triage meeting attendance, inviting only the people whose input is required for the decision and relying on written updates for everyone else. A weekly team meeting with 15 attendees is almost always worse than a weekly written update plus a smaller decision meeting with 4 attendees. Reducing meeting size is the single most effective way to make the remaining meetings easier to schedule across time zones.

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.