Three cities, three clocks, one meeting invite. "Let's meet at 10am" sounds simple until someone asks "your 10am or mine?" and the thread spirals into screenshots of world clocks, someone joining half-asleep at 6am, or a call getting missed entirely because one side quietly shifted an hour for Daylight Saving while the other didn't.
Finding a genuinely fair meeting time across time zones isn't about luck — it's about working from a common reference point and knowing which hours actually overlap with everyone's working day. This guide covers the manual method, the shortcuts, and the mistakes that quietly send people invites for the wrong hour, or the wrong day entirely.
The best meeting time across time zones is the hour that falls within standard working hours, roughly 9am to 5pm, for the largest number of participants at once. Convert every participant's working hours into UTC, find where those ranges overlap, then convert the overlapping UTC hour back into each person's local time to confirm it works before sending the invite.
What does "best meeting time" actually mean?
"Best" isn't a single fixed hour — it depends entirely on who's in the call and what counts as a reasonable time for each of them. There are really three ways people approach it.
- Overlap-based scheduling finds the window of hours where every participant's normal working day intersects, then picks a time inside that window.
- UTC-anchored scheduling converts every local working day into Coordinated Universal Time first, so the comparison happens on one stable timeline instead of juggling several shifting local clocks at once.
- Rotation-based scheduling is used when there's no fair overlap at all, and instead the inconvenient hour is shared out, rotating which region has to join early or late each time.
All three start from the same two inputs — each participant's time zone and their normal working hours — the difference is only in how that information gets compared.
Why the right time matters
Picking a meeting time without checking the overlap properly doesn't usually cause an obvious error — it just quietly costs someone sleep, attendance, or focus. That shows up in a few common places:
- Remote and distributed teams. A recurring standup set without checking both sides' working hours ends up permanently inconvenient for whichever region is furthest away.
- Client and vendor calls. A sales or support call booked in the organizer's local time, without converting it, can land outside the client's office hours entirely.
- Global product launches. Coordinated announcements or releases timed in one region's clock can go live overnight, or a day early, for teams on the other side of the date line.
- Daylight Saving transitions. A meeting time that was correct in winter can silently shift by an hour in spring or fall if only one of the two locations observes the change.
Step-by-step: finding the best meeting time
Method 1: Manual overlap calculation
- List each participant's time zone and working hours. For example, New York (9am–5pm ET) and London (9am–5pm GMT).
- Convert one location's working hours into the other's local time. London's 9am–5pm GMT lands at roughly 4am–12pm ET, so the overlap with New York's 9am–5pm ET is 9am–12pm ET.
- Pick a time inside the overlap window. Any hour inside that shared range works for both sides without anyone joining outside their normal day.
Method 2: Using UTC as a common reference
- Convert every participant's working hours into UTC. This removes the need to compare multiple shifting local clocks directly against each other.
- Line up all the UTC ranges side by side. The hours where all, or most, of the ranges overlap are the candidate meeting times.
- Convert the chosen UTC hour back to each local time zone. This confirms the exact local time for every invite before it goes out.
Method 3: Using a meeting time planner tool
- Enter each participant's city or time zone into a planner. Most tools display all of them stacked on a shared timeline automatically.
- Scan the timeline for the shaded "working hours" overlap. A good planner highlights the hours that fall within a normal day for every location at once.
- Select the meeting slot directly from the timeline. This avoids manual UTC conversion entirely and automatically accounts for each region's current Daylight Saving status.
Common mistakes when scheduling across time zones
1. Ignoring Daylight Saving Time differences
Not every country shifts its clocks on the same date, and some don't observe Daylight Saving at all, so a meeting time that was correct a few weeks earlier can quietly drift by an hour for one side of the call.
2. Comparing local times directly instead of a common reference
Mentally converting several local clocks against each other at once is where most off-by-one-hour mistakes creep in; converting everyone into UTC first removes that guesswork.
3. Forgetting the meeting can land on a different calendar day
For time zones on opposite sides of the International Date Line, or simply far enough apart, a time that's "tomorrow morning" for one participant can still be "this evening" for another, so the invite needs to state the date for each time zone, not just the hour.
4. Always defaulting to the organizer's convenient hours
Scheduling every recurring meeting inside the organizer's own comfortable working hours pushes the inconvenient slot permanently onto whichever participant is furthest away, rather than sharing it fairly over time.
Real-world scheduling examples
A few common time zone pairings and where their working-hours overlap actually falls.
Manual calculation vs spreadsheet vs scheduling tool
A side-by-side look at how the three approaches to time zone scheduling compare.
| Factor | Manual calculation | Spreadsheet formula | Scheduling tool |
|---|---|---|---|
| Speed | Slow | Moderate | Instant |
| Handles Daylight Saving automatically | No | Only if formulas are updated | Yes |
| Scales to many participants | Difficult | Workable | Easy |
| Best for | A single one-off two-person call | Recurring internal reports or trackers | Recurring or multi-region meetings |
Skip the math: free meeting time planner
If juggling UTC offsets by hand isn't worth the time, the Rebrixe Meeting Time Planner works entirely in your browser: add each participant's city, see every time zone lined up on one shared timeline, and pick the overlapping working-hours slot instantly. No conversions, no account, no data sent anywhere.