How to Schedule Meetings Across Time Zones: 12 Rules That Work
By WordTimezone · Updated October 7, 2026 · 4 min read
Scheduling across time zones is a solved problem on paper and an unsolved one in practice: the maths is easy, but fairness, daylight saving, weekends and habits are not. These twelve rules are what experienced remote teams do to keep meetings humane. They are written for any mix of zones — a team in India and the US, one spread across Europe, or a company with people on four continents.
The 12 rules
- Write the time zone in every invite. “10 AM” means nothing across borders. Put the zone and a second zone for the other side: “3 PM ET / 12:30 AM IST (next day)”. Use ET, CT or PT rather than EST/CST/PST so the summer–winter switch does not matter.
- Find the golden hours first. Before proposing a time, list each person’s working hours in UTC and look for the overlap. If nothing overlaps, you are in a “no golden hour” situation and need async-first habits (rule 4).
- Rotate the pain. If one team always takes the early morning, resentment follows. Alternate meeting times so everyone shares the unpopular slots; keep a visible rota.
- Default to async. Status updates, reviews and announcements rarely need live attendance. Write them down, record a short video, and keep live time for decisions and discussion.
- Protect sleep and weekends. Set a rule such as: no required meetings before 7 AM or after 9 PM local, and remember that a weekday in one country can be a weekend in another — Friday is part of the weekend in Saudi Arabia, and Monday morning in Sydney is still Sunday evening in New York.
- Mind the daylight-saving weeks. Clocks change on different dates in different countries (in 2026: US March 8 and November 1, Europe March 29 and October 25), so recurring meetings shift for some people. Re-confirm those weeks.
- Use a zone-aware calendar. Create events in a named zone (e.g. New York), not a fixed offset, so each invitee’s calendar converts it correctly — including after daylight-saving changes.
- Keep one shared reference. Pick UTC or the team’s “home” zone for internal schedules and always convert from that one. It removes the “whose time?” argument.
- Share the plan visually. A grid that shows everyone’s hours side by side beats mental arithmetic. Use a meeting planner and paste the link into the invite.
- Keep meetings short and recorded. A 25-minute call with notes and a recording is easier for someone in a bad time zone than a 60-minute call.
- Name owners and deadlines in writing. After the call, send decisions, owners and dates in a message. Colleagues who were asleep can act on them when they wake.
- Review the setup quarterly. Teams change: people move, join and leave. Re-check the golden hours and the rota every few months.
A worked example: India, Germany and New York
Three people: Priya in India, Jonas in Germany and Maya in New York. Normal working hours are 9–6 for each. Converting to a shared reference makes the problem visible:
| Person | Working hours (local) | In UTC (October 2026) |
|---|---|---|
| Priya, India (UTC+5:30) | 9:00 AM – 6:00 PM | 03:30 – 12:30 |
| Jonas, Germany (UTC+2 until Oct 25) | 9:00 AM – 6:00 PM | 07:00 – 16:00 |
| Maya, New York (UTC−4 until Nov 1) | 9:00 AM – 6:00 PM | 13:00 – 22:00 |
UTC = local time minus the offset. The Germany and New York offsets change on different dates (Oct 25 and Nov 1).
India and Germany overlap from 07:00 to 12:30 UTC, and Germany and New York overlap from 13:00 to 16:00 UTC. All three overlap nowhere — so the team uses two shorter calls and a written handoff instead of one all-hands meeting. You can reproduce this in seconds with the meeting planner.
Frequently asked questions
What is the best way to schedule a meeting across time zones?
List each participant’s working hours in a shared reference such as UTC, find the overlap, propose a time in two zones, and create the event in a zone-aware calendar.
How do you choose a fair meeting time for a global team?
Rotate the inconvenient slots between regions, avoid very early or late hours for anyone, and use async updates so fewer decisions depend on a live call.
What time zone should I write in a meeting invite?
Use ET/CT/PT (not EST/CST/PST) for US times and add at least one other participant’s zone or a UTC time.
Do daylight-saving changes affect recurring meetings?
Yes. Countries change on different dates, so the gap between two cities can shift by an hour for a few weeks. Re-confirm recurring meetings around those dates.