How to Schedule Meetings Across Time Zones — The Complete Guide

Your San Francisco developer, Berlin designer, and Tokyo client are all staring at the same blank calendar invite. Nobody wins. Here's how to fix it.

You send a calendar invite. San Francisco replies: "This is 2 AM for me." Berlin says nothing because they already left for the day. Tokyo confirms, then misses the call because of daylight saving time you forgot to account for. Sound familiar?

Scheduling meetings across time zones is one of those problems that sounds trivial but genuinely costs remote teams hours of frustration every week. This guide covers the strategies that actually work, and how to stop doing this math manually.

Why time zone scheduling goes wrong so often

The obvious answer is that people use their own local time as the reference point. "Let's meet at 3 PM" — 3 PM where? When someone from each of five countries reads that message, they mentally insert their own city, and five different meetings happen in five different heads.

The less obvious problem is daylight saving time. The US, the EU, Australia, and most other regions change their clocks twice a year — but not on the same date. There's a window of several weeks each spring and autumn when the offset between, say, New York and London changes by an hour. This catches experienced remote workers off guard all the time.

Then there's the holiday problem. Your Monday 10 AM UTC slot is perfect — until you notice it's Labor Day in the US, a bank holiday in the UK, and Golden Week in Japan. You just scheduled an empty room.

The overlap window problem: reality check for global teams

For many global teams, there is no perfect time. Let's be honest about the math:

A team spanning San Francisco (UTC−8), London (UTC+0), and Tokyo (UTC+9) has a 17-hour spread. If everyone works 9 AM–6 PM in their local time, the "ideal overlap" — where all three are in their work hours simultaneously — is exactly zero hours.

This doesn't mean scheduling is impossible. It means someone has to compromise. The goal shifts from "find a time everyone loves" to "find the fairest time where the discomfort is shared." Tools that score slots by coverage let you see this clearly instead of guessing.

For San Francisco + London + Tokyo specifically, the best realistic slots are typically early morning San Francisco time (around 8–9 AM PT): London is at 4–5 PM, which is end-of-day but still business hours; Tokyo is at 1–2 AM, which is outside hours. That's 2 out of 3 — the best you'll get without a later Tokyo shift.

The strategies that actually work

Always specify time zones explicitly. Never write "10 AM Monday." Write "10 AM PT / 6 PM GMT / 3 AM JST+1 on Tuesday." This is annoying to type, but it eliminates misunderstanding entirely. Calendar tools like Google Calendar and Outlook handle this automatically when you add attendees — their meeting shows in each person's local time.

Rotate the inconvenience. If someone always takes the 5 AM call and someone else always gets 2 PM, that's not a distributed team — that's an employer/employee dynamic in disguise. Good remote teams rotate who carries the odd hours, on a documented schedule.

Use asynchronous-first culture as a fallback. Not everything needs a meeting. Video messages (Loom), shared documents with comment threads, and async standups (Geekbot, StatusHero) can replace a surprising number of meetings. Reserve synchronous calls for decisions that genuinely benefit from real-time discussion.

Book standing meeting slots well in advance. Recurring meetings set weeks ahead let team members plan their schedules around them. Ad-hoc calls across time zones are always harder because someone's day is already structured.

Using a meeting planner tool: what to look for

Most time zone converters just show you what time it is somewhere else. A proper team meeting planner does the intersection math for you: given each person's work hours and timezone, which slots have the most overlap?

The features that matter:

• Holiday awareness. Tools like Toolozo's Team Meeting Planner automatically fetch national holidays for each team member's country. A slot that looks available on paper disappears if half the team is off for a bank holiday.
• Visual heat map. A color-coded week grid instantly shows you where the overlap concentration is — green cells mean "this is likely to work," red means "don't even try."
• Per-person local time display. Each suggested slot should show every team member's local time, so you can confirm "7 AM for Sarah" before hitting send on the invite.
• Configurable work hours. Not everyone works 9–5. Part-time team members, shift workers, and people with school pickups all have custom availability. A good tool lets you set exact hours per person.

The etiquette side of cross-timezone meetings

Scheduling the meeting is half the problem. Running it well across time zones is the other half.

Always record the meeting. The person who had to join at 6 AM or 11 PM deserves a recording they can reference. This also removes the pressure of being "present" at an unusual hour — if something comes up, they haven't lost the content.

Share an agenda 24 hours ahead. Time-zone-aware preparation matters. If your Singapore colleague is joining at midnight, they want to know whether this is a 15-minute update call or a 90-minute workshop before they commit.

Name the timezone in the meeting title. "Weekly sync (9 AM PT / 5 PM GMT)" in the calendar title is a gift to your team. It prevents the "is this my 10 AM or my 11 AM?" moment that happens every time DST changes.

End on time. For someone dialing in at an unusual hour, every minute past the scheduled end feels worse than it would during business hours. Keep it tight.

Find the best slot automatically

Instead of doing all this math in your head, Toolozo's Team Meeting Planner handles it in seconds. Add your team members, set their timezones and work hours, pick a week, and the tool fetches public holidays automatically and shows you a ranked list of the best slots — with each person's local time displayed on every suggestion.

No signup. No backend. Everything runs in your browser, so no data leaves your device. It's the fastest way to stop guessing and start scheduling.