6 min read

How to schedule meetings across three time zones

Schedule across three or more time zones with overlap checks, async defaults, rotation rules, and invite wording that makes the tradeoff visible.

When this helps: Use this when two-way conversion is not enough and a third region changes the meeting tradeoff. 6 min read Updated 2026-06-14

The constraint is fairness

Three-time-zone meetings usually fail because one team absorbs the human cost. Start by listing each side working hours, required attendees, and decision owners, not by converting one preferred time.

Use async by default for status

If the meeting is mostly reporting, use async updates. Reserve live time for decisions, conflict resolution, and high-context discussion.

Rotate unavoidable pain

When no shared working-hour overlap exists, rotate the inconvenient slot and document the rotation rule.

Name the meeting purpose

A status meeting, decision meeting, and conflict-resolution meeting do not need the same scheduling standard. Move status async before asking three regions to attend live.

Document the rotation

If someone must take an early or late slot, write the rotation rule in the invite notes so the same region does not keep that edge-of-day slot by default.

Recommended starting point

Find the narrowest shared working-hour overlap first. If it is less than the meeting length, change the format before changing people’s working hours.

Common failure

The common failure is optimizing for the organizer timezone and discovering too late that the third region has no workable slot.

Use useChrono for the exact date

Use the world clock to list local times, then use the planner for the two hardest endpoints before deciding whether the meeting should be async.

Decision notes

  • If one region has no overlap, do not keep searching for a perfect slot. Change the meeting format.
  • For recurring meetings, publish the rotation schedule before the first call so the tradeoff is visible.
  • If the meeting is mainly reporting, use written updates and reserve live time for unresolved decisions.
  • When three regions are required, test the two hardest endpoints first; the third region often exposes the real constraint.
  • If the meeting has optional observers, remove them before deciding that the full group needs one live slot.
  • For handoffs, use regional notes plus one short decision call instead of a full global status meeting.