Schedule Meeting Across Time Zones and Scheduling Meetings in Different Time Zones for Distributed Teams

Step 1. Write the zone, always

A bare "15:00" in an email is not a time, it is a guess with a 50% success rate. Write the zone by name and include the date: "15:00 Europe/London, Thursday 24 September".

Use IANA names rather than abbreviations. "CST" is used for at least two different offsets around the world, and "EST" in June is wrong for New York because the country is on daylight time. Names like America/New_York or Asia/Singapore carry the rules, not just an offset.

Step 2. Work from one absolute instant

Pick the instant once, then convert it for every attendee from that single reference rather than converting from one local time to the next. Chained conversions are how a meeting ends up an hour out for exactly one person, which is always the person you needed most.

Step 3. Check the date, not just the hour

Anything involving Asia and the Americas crosses midnight. A Monday 17:00 in San Francisco is Tuesday morning in Singapore, so the invitation has to name both dates or somebody will block the wrong day. Spell it out for each attendee instead of assuming they will notice.

Step 4. Choose an hour that is defensible for everyone

Do not offer your own comfortable afternoon by default. Look at the overlap of everybody's working hours and pick from that, and when the overlap is narrow, say out loud who is taking the inconvenient end this time. The usual overlap windows are in the best meeting time for multiple time zones table below.

Best meeting time for multiple time zones

There is no universally best hour, only the overlap your geography allows. The table assumes a 09:00 to 17:00 working day in each region; offsets move when countries change their clocks on different dates, so confirm the local hour for the actual date.

How to read the overlap table

Three practical rules fall out of the table.

• Two regions to the east and west of the Atlantic almost always have a window, and it sits in the American morning and the European afternoon. That window is the one to protect.
• Asia with the Americas has no overlap of working hours at all. Somebody is starting early or finishing late, and the only honest question is who, and how often.
• Any pair with a one-hour overlap needs that hour defended, because a single recurring meeting placed elsewhere will quietly move to the edge and stay there.

Where a pair shows no overlap, do not split the difference into the middle of somebody's night. Pick one side to take an early start or a late finish, name it, and rotate it. A 3am compromise is a meeting that nobody performs well in and everybody resents.

Daylight saving is the trap that looks like a bug

Countries change their clocks on different dates, and some do not change at all. For a few weeks each spring and autumn the gap between two cities is not what it was last month, so a meeting agreed in March for April can be an hour off, and a recurring series drifts for half the participants.

Two rules keep you out of it. Store and reason about absolute instants, never offsets. And when a meeting is agreed near a changeover date, confirm the local time for each attendee explicitly rather than assuming the gap held.

Let the other side pick, in their own zone

Every step above is manual work that a booking page removes. Times are stored as absolute instants and converted when something is displayed, so the visitor sees your availability in their own zone, detected in their browser, with the zone named beside every time and a full selector if they are travelling.

Because conversion happens at render time, a clock change between booking and meeting needs no correction: the instant did not move, and each side's local hour is recalculated with the rules in force for that date. Confirmations and reminders follow the same rule, so the copy your client keeps says the right hour in their own zone.

For a meeting that needs several of your people across regions, a collective booking page intersects their real availability first, so only times where the whole group is free are ever offered. That is the case that breaks hand scheduling completely.

See collective scheduling software for what that looks like, or go straight to how it works.

The four-line checklist

• Every time written with an IANA zone name and a date
• One absolute instant as the reference for all conversions
• The date checked separately for attendees on the other side of midnight
• The awkward hour rotated, and the rotation said out loud

Scheduling meetings in different time zones every week

Arranging one meeting across zones is a puzzle. Arranging them every week is a policy question, and without a policy the answer defaults to the same thing every time: whoever is furthest from head office takes the bad hour, permanently. Three habits fix that.

Set a company meeting window

Decide the hours in which cross-region meetings may be booked at all, and publish them. A window stops the negotiation starting from scratch every time, and it makes the cost visible, because the window will be uncomfortably narrow and that is the honest picture of your geography.

• Write the window as local hours for each region, not as one zone's hours
• State which meetings may break it, and who may approve that
• Apply it to bookings automatically rather than relying on goodwill

In ScheduleMeeting that is company hours plus holidays, set once by an admin and applied on top of every person's own working hours, on every booking page in the organization at the same time.

Rotate the awkward hour, and say so out loud

Where the overlap does not contain a reasonable hour for everyone, somebody takes an early start or a late evening. The failure is not that it happens, it is that nobody tracks it, so it is always the same person.

• Name the rotation in the invitation: this month the early start is ours
• Keep it visible in a shared note, so the pattern cannot quietly settle
• Watch for the person who never complains, who is usually the one always taking it
• Put a floor under it, an hour before which nobody is asked to attend, and honor it

A rotation written down survives a manager change. A rotation kept in someone's head does not.

Reduce the number of meetings that need an overlap

• Replace status meetings with written updates read in local working hours
• Record decisions and their reasoning, so a person in another region does not have to attend to stay informed
• Split a meeting that needs three regions into two meetings that each need two
• Keep the genuinely synchronous work (decisions, negotiation, anything with disagreement in it) and move the rest to text

Every meeting you remove from the overlap window gives the remaining ones room. For customer-facing teams the same logic applies to demos and interviews: a round robin booking link lets the rep or recruiter whose working day covers the visitor's zone take the meeting, so nobody has to stay up for a prospect on the other coast.

How do you schedule a meeting with people in different time zones?

Pick one absolute time, write it with a named zone and the date, and let each attendee see it converted into their own zone instead of converting it for them. Choose from the overlap of everyone's working hours, rotate the inconvenient end when the overlap is narrow, and send a booking link so people pick a slot in their own local time.

When several of your people must attend together, a collective booking page only offers the times when all of them are free, which is the case hand scheduling across regions gets wrong most often.