How to Schedule Meetings Across Time Zones Fairly

Someone on your team is always taking the 7 a.m. call, and it is usually the same person. When you schedule meetings across time zones without a clear rule, the burden quietly lands on whoever is too polite to complain, and resentment builds long before anyone says a word.

I have coordinated teams spread from Vancouver to Singapore, and the pattern repeats. The calendar invite looks neutral, but the time it picks is a decision about whose evening, whose school run and whose sleep matters least. This guide gives you a practical system for making that decision fairly and in the open.

Start with the overlap you actually have

Before you suggest a time, map the working hours of every attendee in one place. A simple table works better than any app, because it forces you to look at real hours rather than a coloured block.

In this example, London, Berlin and New York share a clean two-hour window from 14:00 to 16:00 UTC. San Francisco and Singapore share no working hours with each other at all. That is not a scheduling problem you can solve with a better tool. It is a structural fact, and the honest answer is that someone will be outside normal hours for any meeting that includes both.

Remember that daylight saving changes the table twice a year, and not on the same weekend. The United States shifts in March and November, while Europe shifts on the last Sundays of March and October. For two or three weeks each spring and autumn, your usual overlap moves by an hour.

How to schedule meetings across time zones fairly

Fairness here does not mean everyone is equally comfortable every week. It means the discomfort is shared and visible. Three rules make that happen.

Rotate the awkward hour

If a weekly meeting must include regions with no overlap, alternate the time. One week it runs at 08:00 in San Francisco, the next at 18:00 in Singapore. Put the rotation in the recurring invite description so nobody has to remember whose turn it is.

Set a hard edge on the day

Agree as a team that no recurring meeting starts before 07:30 or after 20:00 in anyone's local time. One-off exceptions happen, but a recurring call outside those limits is a sign the meeting should be split or replaced.

Name the cost in the invite

When you send an invite that falls outside someone's working hours, say so in the first line: "This is 19:00 for Priya, so we will finish on time." That single sentence tells the person their evening was noticed, and it puts gentle pressure on everyone to keep the call tight.

Why "just find a time that works" fails

The most common advice is to send a poll and pick the time with the most votes. It sounds democratic, and it is one of the main reasons the same people end up at the edges of their day. A poll rewards the majority region. If six people sit in Europe and two in Asia, the vote will land in European business hours every time, and the two in Asia will vote "available" at 22:00 because they do not want to look difficult.

I prefer a different default: the meeting owner proposes one time, explains the trade-off in a sentence, and invites objections for 24 hours. This puts responsibility on the person who called the meeting rather than hiding it inside a vote. It also gets decisions faster, since a poll with eight people across five zones can take three days to close.

A proposal message can be this short: "Proposing Tuesdays at 16:00 UTC. That is 8:00 for Lena in Seattle, so we will alternate with 07:00 UTC every other week. Reply by Thursday if this does not work." Four sentences, one decision, and the cost is out in the open. When someone does object, take it seriously and adjust once. If objections keep coming, that usually means the meeting has too many people or too many purposes, and splitting it into two smaller calls by region often solves the problem better than any new time.

Cut the meetings that do not need to be live

The fairest meeting across time zones is often no meeting. A status update that runs 30 minutes every Monday can usually become a written thread posted by 10:00 in each person's local time. Live time is best kept for decisions, disagreements and anything with emotional weight, like feedback or a change in plans.

Written updates work only if they are good, and a clear structure helps. Our guide to writing an email that gets answered in one reply covers the same principles: lead with the ask, give the context in two or three lines, and state the deadline in the reader's time zone, not yours.

For calls that stay live, keep them short. Research on video fatigue suggests concentration drops sharply after about 45 minutes on screen, and people joining at night drop faster. If you are curious about why, we explain it in why video calls wear people out faster than meetings.

Practical habits for the calendar invite

• Write times in two zones. "15:00 London / 10:00 New York" removes guesswork, especially around daylight saving weeks.
• Use UTC for teams of four zones or more. It is neutral and stops anyone treating their own city as the default.
• Record and summarise. If someone cannot attend because it is 02:00 for them, send a five-line summary within two hours, with decisions marked clearly.
• Avoid Friday afternoons in Europe and Monday mornings in Asia. For Asia-Pacific colleagues, a US Friday afternoon is already Saturday.
• Check public holidays. Golden Week in Japan, Lunar New Year across much of East Asia and Thanksgiving in the US each take whole teams offline for days.

For more on email, chat and remote work habits, see our full digital communication guides.

Frequently asked questions

What is the best time for a meeting across US and Europe?

For East Coast and Central Europe, 15:00 to 17:00 Berlin time, which is 9:00 to 11:00 in New York, gives the most comfortable overlap. If the West Coast joins, 17:00 Berlin is 8:00 in San Francisco, which is early but workable once a week.

How do you handle meetings with Asia and the US?

There is no shared working window between the US and East Asia, so rotate the meeting so each side takes the early or late call in turn. Many teams replace the weekly call with a written update and keep live calls for monthly planning.

Should meeting invites use UTC or local time?

For two or three zones, list local times for each city in the invite. For larger groups, use UTC as the reference and let calendar tools show local time, since that keeps everyone working from one neutral clock.