# Schedule a Meeting Across Time Zones: A Fair 5-Step Method > How to schedule a meeting across time zones: one reference clock, real working hours, the overlap, rotation when there is none, and the daylight saving traps. _Source: https://professionalstoolkit.com/articles/schedule-meeting-across-time-zones — The Professional's Toolkit · updated October 2026_ --- To schedule a meeting across time zones without someone joining at midnight, work in one reference clock, map everyone's working hours onto it, and pick from the overlap. If there is no overlap, rotate the inconvenient slot instead of handing it to the same person every week. Then send the invite from a calendar, so each guest sees the time in their own zone. Most scheduling mistakes come from converting times by hand, from vague labels like EST, and from forgetting that clocks change on different dates in different countries. **4 hours** — The New York to London gap for a few weeks each year, instead of the usual 5 - **2nd Sun. of March** — US daylight saving time begins, 2 a.m. local - **1st Sun. of Nov.** — US clocks fall back to standard time - **3 zones** — Shown at once in Google Calendar or recent Outlook ## Why time zones make a simple meeting hard A meeting between two people in the same office needs one thing: a free hour on both calendars. Across zones you need three. The hour must be free, it must fall inside everyone's working day, and everyone must read the same moment from the invite. Each extra city shrinks the window. Two coasts of the US still share most of a day. New York and London share a few hours. Add Bangalore or Sydney and the shared window can vanish entirely. The harm is quiet. Nobody complains about one early call. The cost shows up later as a teammate who always takes the 6 AM slot, a client who shows up an hour late, or a group thread with twenty replies about Tuesday. **Group scheduling is a fairness problem as much as a math problem.** The method below handles both. ## How to schedule a meeting across time zones in five steps The method works with a pencil, a spreadsheet, or a time zones meeting planner. The tool matters less than the order. 1. **Pick one reference clock.** Use UTC, or the organizer's city, and write every candidate time in it first. Converting each person's time to each other person's time multiplies the errors. 2. **List everyone's real working hours.** Ask for them; do not assume nine to five. Some people start at seven to overlap with another region, and some never take calls on Friday. 3. **Find the overlap.** Line the hours up side by side in the reference clock. The shared window is often one to three hours long, sometimes zero. 4. **Choose the slot, or rotate it.** If a window exists, take its middle, not its edge. If none exists, alternate who gets the early or late slot, or split into two smaller meetings. 5. **Send a calendar invite, not a time in text.** A calendar event carries its zone with it. Google Calendar shows an event in each invitee's local time zone, even when they are in a different zone from you [1]. > 💡 **Pick the middle of the overlap:** A slot at the edge of the shared window becomes impossible the moment one person's day shifts. The middle survives small changes. Step 5 is where most of the protection comes from. A line in an email such as *3 PM Eastern* asks every reader to do the arithmetic again. An invite does it once, correctly, for everyone. If you must write a time in text, name a city rather than an abbreviation, and add the reference time beside it. ## A worked example: four cities, one call Say a small agency has staff in San Francisco, New York, London and Bangalore, and needs a weekly call in July. Lay a few candidate slots in UTC across all four local clocks. | UTC | San Francisco | New York | London | Bangalore | |---|---|---|---|---| | 12:00 | 5:00 AM | 8:00 AM | 1:00 PM | 5:30 PM | | 15:00 | 8:00 AM | 11:00 AM | 4:00 PM | 8:30 PM | | 16:00 | 9:00 AM | 12:00 PM | 5:00 PM | 9:30 PM | No slot fits a normal workday for all four. That is the honest answer, and it is common. The 15:00 UTC row costs San Francisco an early start and Bangalore an evening. The 12:00 row is easy for Europe and India but brutal for California. The fair fix is to rotate. Run the call at 15:00 UTC one week and 12:00 UTC the next, so the pain moves around. Another option is two calls: Bangalore and London in the morning UTC, New York and San Francisco later, with one person who attends both. Notice the half hour in Bangalore. India runs on a half-hour offset, which is exactly the kind of detail that breaks mental math. > 💡 **Name a city, not an abbreviation:** Write New York time or London time instead of EST or GMT. City names stay correct all year, abbreviations do not. ## Daylight saving time: the weeks the math changes The table above is only true in July. Clocks move, and they do not move together. In the United States, daylight saving time begins on the second Sunday in March and ends on the first Sunday in November, both at 2 a.m. local time [2]. The same page notes that Hawaii and most of Arizona do not observe it. Europe changes its clocks on the last Sundays of March and October. So for a few weeks each spring, and for one week each autumn, the gap between New York and London is four hours instead of five. In 2026, for example, London fell back on October 25 and New York on November 1. For that week, a recurring 10 AM New York call landed at 2 PM in London, not 3 PM. It gets stranger. Places that skip daylight saving entirely, such as India or most of Arizona, shift relative to everyone else twice a year without touching their own clocks. > ⚠ **Recheck recurring calls in March and Oct.:** The US moves its clocks weeks before Europe in spring, and a week after Europe in autumn, so a fixed meeting shifts by an hour for some attendees. Times written by hand in docs or emails will be wrong for those weeks. A recurring event created in a calendar handles this correctly, because it is anchored to the organizer's zone. The risk sits with anything written by hand: a team wiki page that says *the call is at 3 PM London time*, an email signature with *office hours 9-5 EST*, or a spreadsheet with fixed offsets. ## Common mistakes when scheduling a meeting across time zones ### Writing EST in July EST means Eastern Standard Time, which is not in use in summer. People write it all year and mean whatever New York is doing. Most readers guess right, but software and careful readers do not. Write ET, Eastern, or simply *New York time*. ### Converting by hand Every manual conversion is a chance to be off by an hour. Let the calendar show extra zones instead. Google Calendar lets you add a secondary and a tertiary time zone to the left of the grid [1]. Recent Outlook for Microsoft 365 can display up to three time zones in the calendar [3]. ### Ignoring the date line A Monday morning call from Los Angeles is Tuesday in Tokyo and Sydney. Teams in Asia-Pacific lose Friday afternoon meetings with the Americas, because it is already Saturday there. Check the day, not just the hour. ### Asking the group in a thread *What time works for everyone?* invites a long thread in which each person answers in their own clock. Collect availability in one place instead: a shared grid, or a poll that shows each person the options in their local time. ### Always favoring headquarters When the organizer's city wins every time, people at the far end stop joining live. Rotation, recordings, and written updates keep them in. ## When group scheduling gets too hard to do by hand The manual method holds up for a few people and a recurring meeting you set once. It starts to strain when you schedule often with people outside your company, whose calendars you cannot see. It also strains when the group is larger than five or six, or when clients book you from zones you never planned for. At that point you need two things the method cannot give you: each guest seeing your options in their own clock, and votes collected in one place. The free route, with a time zones meeting planner and the extra zones in your calendar, is laid out step by step in [our time zone meeting planner guide](/articles/time-zone-meeting-planner). For a side-by-side of the products built for this, see [the group scheduling tools compared](/articles/group-scheduling-tools). ### Tools that do it for you Three of the tools we compared run group polls on a free plan. SavvyCal shows every poll slot in each voter's own time zone, and the booking pages of YouCanBookMe and TidyCal detect the visitor's zone and show your hours in local time. ### SavvyCal — solves this Its meeting polls let you propose several slots; each voter sees them converted to their own local time and votes, and a teammate option keeps out times your own side cannot make. - Where it stops: Collective links for several hosts need a paid plan; the Free account runs polls but cannot take bookings. - Plan: Free account (polls); Basic (collective links) - How SavvyCal does it: [How SavvyCal polls work](https://professionalstoolkit.com/articles/savvycal-meeting-polls) - More: [SavvyCal](https://professionalstoolkit.com/tools/savvycal) SavvyCal converts every poll slot into each voter's local time, which removes the conversion step for the group. Its [free meeting polls](/articles/savvycal-meeting-polls) are the closest match to steps 3 and 4 above. ### YouCanBookMe — solves this A meeting poll on Free lets you offer up to 50 time slots for participants to answer, and the booking page detects each booker's time zone and shows your availability in their local time. - Where it stops: Group sessions are not on Free and cap at 50 people per slot. - Plan: Free (polls); Individual (group sessions) - How YouCanBookMe does it: [Set up YouCanBookMe step by step](https://professionalstoolkit.com/articles/how-to-use-youcanbookme) - More: [YouCanBookMe](https://professionalstoolkit.com/tools/youcanbookme) ### TidyCal — solves this Date polls on every plan: voters pick dates, you choose the final time, and TidyCal creates one booking per voter, checking busy times on your connected calendars. Booking pages convert your hours to each visitor's time zone. - Where it stops: Polls cannot collect payment; collective meetings need Agency Lifetime or Pro. - Plan: All plans (date polls); Agency Lifetime or Pro (collective) - How TidyCal does it: [Set up TidyCal step by step](https://professionalstoolkit.com/articles/how-to-use-tidycal) - More: [TidyCal](https://professionalstoolkit.com/tools/tidycal) TidyCal goes one step further after the vote: once you pick the final time, it [creates a booking for each voter](/articles/how-to-use-tidycal), so nobody has to retype the invite. ## FAQ **What is the best time for a meeting across time zones?** The middle of the window where everyone's working hours overlap, written in one reference clock. If no window exists, there is no single best time: rotate the slot between regions or split the meeting. **Should I use UTC or my own time zone as the reference?** Either works, as long as it is one clock for the whole plan. UTC never shifts for daylight saving time, which makes it the safer choice for recurring meetings that span the US and Europe. **Is a time zones meeting planner enough for group scheduling?** For a fixed internal team, yes: you find the window once and set a recurring invite. For groups outside your company, whose calendars you cannot see, a meeting poll collects availability faster than a grid. **How do I avoid confusion when people are in different time zones?** Send a calendar invite, which shows each person the event in their own zone, and name cities rather than abbreviations in any written time. ## The bottom line Time zones turn a free hour into a shared-window problem, and the fix is a habit, not a gadget. Work in one reference clock, collect real working hours, choose from the middle of the overlap, and rotate when there is none. Send a calendar invite rather than a time in text, and recheck recurring meetings in the weeks when the US and Europe change their clocks on different Sundays. When you schedule with outside groups often, a poll that shows each person their own local time removes the arithmetic altogether. ## Sources [1] Google Calendar Help — https://support.google.com/calendar/answer/37064?hl=en (Nov 2026) [2] NIST — https://www.nist.gov/pml/time-and-frequency-division/local-time-faqs (Nov 2026) [3] Microsoft Support — https://support.microsoft.com/en-us/outlook/getstarted/manage-time-zone-settings-in-outlook (Nov 2026)