How to Schedule Meetings Across Timezones

There's a weekly product sync I sat in on for a few months. Six people, four of them in New York, one in London, one in Sydney. It ran at 10am Eastern, which is a perfectly civilized hour if you live in New York. For the guy in Sydney it was midnight. Every Tuesday, without fail, he joined from his kitchen in the dark, kids asleep, and said maybe four sentences before signing off to go to bed.

Nobody chose that on purpose. The meeting had been set when the team was all American. London joined and 10am still worked for them. By the time Sydney came aboard, the slot was just "when the meeting is," so he ate midnight every week and everyone else's day went untouched. This ran for over a year before anyone thought to ask whether it was fair.

That's the quiet default on most distributed teams. Somebody always takes the bad hour, it's almost always the same somebody, and the reason is never a decision. It's just where the meeting landed once and never moved.

First, cut the meetings that don't need to be live

Before you get clever about scheduling, get ruthless about what's on the calendar at all. The best fix for a painful meeting time is deleting the meeting.

Most of what teams meet about doesn't need everyone in a room at once. Status is better as a written update. Most decisions are better made in a doc than argued out in the one window everyone happens to be awake. Every meeting you kill is one fewer slot you have to find a fair time for, and on a spread team the scarcest thing you own is the handful of hours your timezones overlap. Spend them on the meetings that genuinely need to be live, and nothing else.

What survives that pruning is your real synchronous core: the design argument that only resolves face to face, the brainstorm where six people riff off each other, the tense conversation that reads better with tone attached. Those are worth scheduling well. And scheduling them well starts with an honest look at your overlap.

Know your actual overlap window

Pull up everyone's real working hours, in their own timezones, and find the block where they line up. For a lot of teams this is a sobering exercise, because the answer is smaller than they assumed, and sometimes it's zero.

A team split between San Francisco and Berlin has roughly a two-hour overlap. About 8am to 10am Pacific is 5pm to 7pm in Berlin, and that's the whole of it. Add Bangalore and the three-way overlap basically evaporates. There is no hour of the day when San Francisco, Berlin, and Bangalore are all comfortably at their desks, and no amount of goodwill conjures one.

Knowing that number changes how you behave. If your team shares six overlap hours a day, you can be relaxed about meeting times. If you share ninety minutes, those ninety minutes are the most valuable real estate the team has, and you should treat booking into them like spending money. This is downstream of a choice most teams made without noticing. Your hiring map is a timezone footprint, and it fixed the size of this window long before you tried to book anything into it.

Rotate the pain instead of parking it on one person

Here's the part most teams get wrong, and the guy in Sydney is the example.

When there's no kind hour for everyone, somebody has to take an unkind one. That's arithmetic across a wide enough spread, and there's no arguing with it. The failure isn't that the bad hour exists. The failure is handing it to the same person every single time and quietly treating it as their problem for living where they live.

So rotate it. If a meeting has to sit at the edge of someone's day, change which edge and whose day. This month the recurring sync runs at a time that's early evening in Sydney and early morning in New York. Next month you flip it, and New York takes the awkward slot while Sydney gets it in daylight. Nobody loves the rotation, and that's the point. The pain is real, so you share it, instead of deciding that one teammate's evenings matter less because fewer people happen to live in that timezone.

I've watched this single change do more for how a far-flung teammate feels about the team than any offsite. It's a small logistical thing that says a large one: your time counts the same as everyone's. The version where London and New York keep their comfortable mornings forever and Sydney eats midnight in perpetuity says the opposite, and people hear it, even when nobody puts it into words.

Give the meetings a home and protect the rest

Once you've found fair times, batch them. Scattering meetings randomly through the overlap window does its own damage, because a meeting costs more than the minutes it occupies.

A single call dropped into the middle of an afternoon eats the two hours around it. You can't start anything that needs focus at 1:40 when a meeting looms at 2. So on the days you have synchronous work, cluster it, and leave the rest of the overlap clear for the deep work remote is supposed to make possible. A team that meets from 9 to 10:30 and then goes quiet ships more than one with the same number of meetings sprinkled across the day like landmines.

When you send the invite, anchor the time properly. "Sync at 3" in a channel spanning five zones is exactly the ambiguity that costs a team a day. Write it as 3pm ET, or let the invite render each person their own local time. Calendar tools handle this well enough, but the reminder you drop in Slack an hour before does not, and that reminder is where people get tripped.

When there's no overlap at all, stop trying to meet

Sometimes you do the math and the honest answer is that no fair time exists, because there's no shared waking hour to be fair about. Team's in California and India, and any live meeting is somebody's night no matter how you rotate it.

Don't force it. A team with genuinely zero overlap should not be running regular synchronous meetings, because every one of them is a sacrifice, and sacrifices don't survive a weekly cadence without someone quietly burning out. This is where you lean hardest on async: record the walkthrough instead of presenting it live, settle decisions in docs, and save the rare truly-synchronous meeting for the moment it earns waking someone up. When you do wake someone up, make it worth their while, and never for something a five-minute recording would have covered just as well.

The teams that handle this best don't have clever scheduling tricks. They accepted that their overlap is a fixed, small budget, spent it deliberately on the few things that need it, and shared the cost of everything else instead of billing it all, month after month, to whoever happens to live furthest from headquarters.

Make Every Meeting Time Mean One Thing

The whole point of scheduling fairly falls apart if "let's meet at 3" means a different hour to everyone who reads it. Timely converts every time mention in Slack to each reader's own timezone automatically, so the slot you picked reads correctly whether your teammate opens it in New York or Sydney, and the reminder you post an hour before lands right without anyone doing the arithmetic.

Add Timely to Slack — Free · See how it works