Timezone fairness means sharing the burden of awkward meeting times evenly across the team, rather than defaulting to one office's hours. The core moves are simple: default to async, find an overlap inside everyone's working day where you can, and when no fair slot exists, rotate the early or late call between regions.
Most distributed teams do not decide to be unfair. They simply default to the headquarters clock, because that is where the calendar invites originate. The trouble is that defaults compound. The same colleagues take the 6:00 AM call or the 10:00 PM call, week after week, while head office stays comfortable.
Why "default to HQ hours" quietly costs you
A single inconvenient meeting is nothing. A standing one is a tax. When every recurring sync sits inside London or San Francisco daytime, your colleagues in Sydney, Bangalore or Sao Paulo absorb the cost of distance on your behalf, in lost evenings and disrupted sleep.
Nobody sends the bill, so it stays invisible to the people setting the times. But it shows up in goodwill, engagement and, eventually, retention. The remote region starts to feel like a second-class part of the company: present, but always accommodating, never accommodated.
This is not a niche problem. In Buffer's 2023 State of Remote Work survey, 62 percent of respondents said the people on their immediate team were distributed across multiple time zones, so for most distributed teams the question of who absorbs the awkward hour is a live one.
The principle: distribute inconvenience, do not eliminate it
For teams spread across wide gaps, such as Europe and Australia, there is often no hour that sits inside everyone's working day. You cannot make distance disappear. The honest goal is not zero inconvenience; it is fairly shared inconvenience.
That reframing matters. Once you accept that someone will sometimes be uncomfortable, the only real question is whether it is always the same someone. Fairness is about turn-taking, not perfection.
Five practices that make scheduling fair
- Default to async first. The fairest meeting is the one you do not hold. A written update, a recorded video or a shared doc lets people contribute on their own clock. Reserve live time for genuine discussion and decisions.
- Find the real overlap. For the calls that must happen live, look for the window that lands inside everyone's working hours. It is often narrower than you assume, and it is the slot worth protecting for standing meetings.
- Measure who takes the unsociable slots. You cannot fix what you do not see. Keep a simple tally of which region gets the early-or-late end of each meeting. The pattern is usually starker than anyone expected.
- Rotate the pain. When no overlap exists, move the awkward hour around the team on a schedule, so this month's early risers are next month's people at a civilised time.
- Let people decline. Anyone should be able to opt out of a meeting outside their working hours without penalty, provided there is a recording or written summary to catch up from. If declining is punished in practice, the fairness is only on paper.
What "fair" looks like across the gap
A concrete example. A team split between London and Sydney has roughly an eight or nine hour gap depending on the season. There is no slot that is comfortable for both. The unfair version always picks London afternoon, which is the Sydney small hours. The fair version alternates.
| Approach | Who carries the cost | Verdict |
|---|---|---|
| Always HQ daytime | Remote region, every time | Erodes goodwill |
| Always "split the difference" | Both regions, mildly, every time | Predictable but tiring |
| Rotate the inconvenient slot | Each region, in turn | Fairest for standing calls |
| Async by default | Nobody is forced live | Best where it fits |
A rotation only works if it runs automatically. Pick the cadence once, write it down, and let it carry on without re-negotiation each cycle. For a practical pattern, see how to rotate meeting times across time zones.
Respect the edges of the working day
Fairness also means knowing where someone's day ends. A 7:00 PM invite that looks harmless from one desk can be a school run, a dinner or a hard boundary somewhere else. Some countries, including France, even legislate a "right to disconnect" that protects employees from after-hours work contact.
You do not need a law to behave well. Treating each person's working hours as real, and asking before you cross them, is most of the battle. For more on that line, see is it rude to schedule meetings outside someone's working hours?.
How Atlas helps
The reason teams default to HQ hours is that fairness takes effort: you have to picture everyone's local time at once and spot the genuinely shared window. Atlas does that for you. Pin each person on the world map, see the overlap where everyone is awake, and write the meeting straight to your calendar, so the fair choice is also the easy one.
Frequently asked
What is timezone fairness?
How do you make meeting times fair across time zones?
Why is it a problem to always schedule around HQ hours?
Should people be allowed to decline out-of-hours meetings?
Stop doing timezone math
Atlas finds the time everyone's awake and adds it to your calendar in one tap.
One-time purchase, yours forever.