How to Plan a Meeting Across Three Time Zones
A practical scheduling workflow for remote teams spread across regions and working hours.
Choose one anchor city as the reference point
When planning across multiple time zones, pick the city where the decision-maker or the majority of attendees are located and use it as the reference point. Find a time that works for that city first, then check whether the same time is reasonable for other locations. This prevents the common mistake of trying to find a perfect middle point that ends up being inconvenient for everyone. The anchor city time is the one you commit to, and other attendees adapt around it, which simplifies scheduling and reduces back-and-forth messages asking what time works for each person.
Avoid the edges of the working day for international calls
Very early morning and late evening slots are technically available but consistently problematic for at least one location in a multi-timezone meeting. A slot between 10 AM and 3 PM in the anchor timezone usually has the best overlap with reasonable working hours in nearby regions. Avoid booking important decision-making calls at the edges of the day for any participant, because fatigue and distractions at those hours affect meeting quality even when attendance is technically possible. When one attendee has to join at 7 AM or 10 PM, their engagement and contribution are usually lower than during core hours.
Check for seasonal daylight saving time changes
Daylight saving time is observed in different weeks by different countries, which means the offset between two cities can shift by one hour during transition periods each spring and autumn. A recurring meeting time agreed upon in winter may arrive at the wrong time for one participant after clocks change. Always verify offsets using a live world time tool rather than relying on memory, and recheck the offset when scheduling meetings that will recur across months where one or both regions observe clock changes. This small habit prevents the recurring issue of someone joining a meeting at the wrong time.
Include every attendee local time in the invite
When sending the meeting invite, include the local time for each attendee city in the invite description — not just the organizer local time. Something as simple as "10:00 AM Bangkok / 11:00 AM Ho Chi Minh City / 3:00 PM Sydney" removes all ambiguity and prevents follow-up messages asking for confirmation. Calendar apps show meeting times in the viewer local time automatically, but explicit confirmation in the invite body is helpful for participants who travel frequently or whose calendar time zone settings may not reflect their current location.
Productivity tools are most effective when they help you make a fast decision and move on. Use them to remove friction, not to create a bigger planning ritual than the task itself. Whether you are comparing time zones, shortening a link, or converting a document, keep the workflow simple: enter the source data, confirm the output, and copy only the result you actually need. A good habit is to keep one repeatable process for each type of task so you do not reinvent the same decision every time.
If a tool affects other people, such as a meeting time or a shared link, double-check the final output before you send it. A few extra seconds of review is much cheaper than fixing a confusing message later.
Frequently asked questions