How to Schedule Meetings Across Time Zones: A Practical Guide for Remote and Global Teams
By Vclock · · 7 min read
Remote work has made it normal for one team to be spread over several continents. That is a real advantage, but it comes with a very practical problem: when everyone is asleep or at dinner at a different time, finding a good moment for a meeting is hard. Most teams solve it badly at first, with the same person always taking the early call or the late one, and a calendar full of invitations that nobody quite trusts.
This guide shows a practical way to schedule meetings across time zones. It covers how to find the overlap in working hours, how to share times so that nobody gets confused, how to share the inconvenient slots fairly, what to do when clocks change, and how to cut down on live meetings altogether. If you want the maths behind the conversions, read our guide to converting time zones first.
Start with the overlap, not the meeting
Before you propose a time, find out when working hours overlap. Take a normal working day, for example 9:00 AM to 6:00 PM, for each place, and convert them to one common time. The hours that fall inside everyone's day are your overlap, and there may be very few of them.
Here is an example for a team in New York, London and India during the northern summer. New York is UTC-4, London is UTC+1 and India is UTC+5:30. London is five hours ahead of New York, and India is nine and a half hours ahead. When it is 9:00 AM in New York, it is 2:00 PM in London and 6:30 PM in India. That is the only slot in which all three are in a working day, and it already means that the Indian team is at the end of its day. Seeing it laid out like this saves a lot of arguing.
The time zone converter on this site has a meeting planner that does it for you. You add the places, and it highlights the hours when each person is within normal working time. For the most common pairs there are ready tables, for example EST to PST, and the world clock shows the live time in any country.
Be fair about who takes the awkward hours
When there is no comfortable slot, someone has to take an early morning or a late evening. The worst thing a team can do is let it always be the same people, usually the ones furthest from the head office. It breeds resentment and burnout, and it quietly tells people that their time matters less.
- Rotate the inconvenient times, so each location takes its turn.
- Keep a simple list of whose turn it is, and put it where the whole team can see it.
- Avoid asking anyone to join before 7:00 AM or after 9:00 PM for a regular meeting.
- Offer time off in return, or a later start the next day, when someone takes a late call.
- Record the meeting, so that people who cannot join can catch up.
Share times so that nobody can misread them
Most scheduling errors come from unclear times. A message that says 3:00 PM on Tuesday means different things in different places. These habits remove the doubt:
- Write the weekday, the date and the time. A date prevents mistakes when one person is already in tomorrow.
- Name the city or the offset, not an abbreviation. Say 3:00 PM London time, not 3:00 PM BST or IST, which can mean more than one zone.
- Add UTC for important events, for example 14:00 UTC.
- Use 24 hour time for international teams, so that 2:00 PM and 2:00 AM are never confused.
- Send a calendar invitation, which adjusts to every person's own time zone automatically, instead of pasting a time into a chat.
It also helps to make sure that everyone has set their own time zone correctly in their calendar. A wrong setting on one laptop is a common cause of a missed meeting.
Watch out for daylight saving time
Clock changes are the quiet enemy of global schedules, because countries change on different dates. The United States and Canada change in March and November, while the United Kingdom and the European Union change at the end of March and the end of October. For a few weeks in spring and one week in autumn, the gap between New York and London is four hours instead of five. A recurring meeting set up in one place can suddenly land an hour earlier or later for someone else.
When you create a recurring meeting, check what it looks like in every zone for the weeks around the clock changes. Our daylight saving time page lists the dates for the US, the UK, Europe, Australia and New Zealand, and our guide to time zones explains why the offsets move. Remember too that the southern hemisphere changes in the opposite direction.
Check holidays before you send the invitation
A Monday morning call that looks fine on the calendar may fall on a public holiday for part of the team, such as a bank holiday in the UK or Thanksgiving in the United States. Keep a shared calendar of the holidays for every country on the team, and check it before you plan something important. We explain how these days differ in our guide to public holidays and bank holidays, and you can see the dates for several countries on our holidays page.
Use fewer live meetings
The best way to cope with time zones is to need fewer meetings that depend on them. Many teams that work across the world rely on asynchronous communication, which means that people share information in writing, on their own schedule, and answer later.
- Replace status meetings with a short written update that people can read when they start their day.
- Write decisions down in one place, so people in other time zones do not have to ask what was decided.
- Share an agenda before the meeting and notes after it.
- Record talks and demos, and add a written summary.
- Agree how fast people should reply, for example within one working day, so that a question is not left waiting.
Keep live meetings for the things that need real-time discussion, such as brainstorming, difficult conversations and getting to know each other.
Agree on core hours
If your team is spread over many time zones, a small window of core hours, when everyone is expected to be available, makes planning much easier. It might be only two or three hours long. Outside the core hours, people can work when they like. Publish the core hours, and write them in each person's own local time, so that there is no guesswork.
Build a simple team routine
- List every team member's city, time zone and normal working hours in one shared page.
- Find the overlap, and name the core hours.
- Choose a regular slot for the weekly live meeting, and rotate the awkward one if there is no comfortable choice.
- Set up the recurring meeting with an invitation, and check the dates around the clock changes.
- Keep a shared calendar of holidays and days off.
- Review the setup every few months, because people move and teams grow.
Mistakes to avoid
- Choosing the time that suits the head office and calling it neutral.
- Using abbreviations such as IST, CST or BST in an invitation.
- Forgetting the date change when one person is in tomorrow.
- Letting the same people take every early or late call.
- Ignoring the weeks when clocks change on different dates.
- Scheduling over a public holiday.
- Using a live meeting for something that could have been a message.
The bottom line
Working across time zones is mostly about being clear and fair. Find the real overlap, share times with the weekday, the city and UTC, check the clock changes and the holidays, rotate the awkward slots and move as much as you can into written updates. Start with the time zone converter to see the hours side by side, and the rest of the plan falls into place.
Frequently asked questions
How do I find the best meeting time across time zones?+
Convert each person's normal working hours to one common time and look for the overlap. Then pick a slot inside it, and rotate the inconvenient slots if there is no comfortable one. A meeting planner shows the hours side by side.
What is the best way to write a meeting time for an international team?+
Give the weekday, the date and the time, name the city or the UTC offset instead of an abbreviation, and add UTC for important events. Send a calendar invitation so that it adjusts to each person's time zone.
How does daylight saving time affect international meetings?+
Countries change their clocks on different dates, so the gap between two places can change by an hour for a few weeks. Check recurring meetings around the clock changes, especially between the US and Europe.
What are core hours?+
Core hours are a short window, often two or three hours, when everyone on a distributed team is expected to be available. They make it easier to plan meetings, and people can work flexibly outside them.
How can a remote team reduce the number of meetings?+
Use written updates, shared documents and recorded talks, and agree how quickly people should reply. Keep live meetings for discussion and decisions that need real-time conversation.
How do I share the inconvenient meeting times fairly?+
Rotate the early and late slots so every location takes its turn, keep a visible list of whose turn it is, avoid extreme hours for regular meetings and record the meeting for those who cannot attend.