Fair means nobody always pays with sleep
A fair meeting time is one where every required person is inside a normal working day, or the meeting is replaced with writing. Unfair defaults look efficient: "9am Pacific" for a global team, a rotating late call that somehow lands on the same two people, or a "quick sync" that becomes the only decision channel. The method below starts from overlap math, then decides whether a live call earns the slot.
Thesis
If shared daytime is under about ninety minutes, prefer async. Use live time for decisions, pairing, and reviews that stall without voices in the same hour. Everything else should move in writing with a named owner and a real deadline.
Method: five steps before you send an invite
- List who must be live. Required voices only. Optional attendees get the recording or the written note.
- Map working hours per person, not per city stereotype. Someone in London on a 07:00 start is not the same as someone on 10:00.
- Find the shared daytime window with the Meeting Time Finder. If the roster has different hours, use the Team Time Zone Planner.
- Convert one candidate with the Time Zone Converter and paste local clocks into the invite.
- Decide call vs async. Thin overlap? Write the decision brief instead. Thick overlap? Book the shortest slot that covers the decision.
Worked example A: two zones with real overlap
Cast: product in Berlin (09:00 to 17:30), engineering in New York (09:00 to 17:30). Shared window is roughly 13:00 to 15:30 UTC.
| Choice | Verdict |
|---|---|
| 14:00 UTC, 30 minutes, decision agenda | Fair |
| 16:00 UTC weekly standup | Unfair to Berlin; ends after their day |
| "Whenever works" without a zone | Unfair to everyone; becomes Slack thrash |
Protect 13:00 to 15:00 UTC for decisions. Move status to writing. Collaboration defaults live in timezone collaboration without chaos.
Worked example B: three regions, almost no three-way overlap
Cast: Berlin, New York, Manila. Pairwise overlaps exist; a comfortable three-way hour does not.
| Instinct | Better default |
|---|---|
| Force a 21:00 Manila call weekly | Relay: Manila → Berlin morning notes, Berlin → New York overlap for decisions |
| "Just this once" late call for everyone | Rotate who takes the pain, record it, and require a written brief first |
| Book 60 minutes because calendars look empty | Book 25 minutes; empty calendar is not empty attention |
Run Meeting Time Finder with three zones. If the tool returns a thin sliver or nothing, that is the answer: do not invent fairness with midnight heroics.
What belongs in the invite
- Purpose in one line (decision, review, or unblock)
- Local clocks for every required person
- Link to the doc or ticket that must be read first
- Exit criterion ("we leave with A or B chosen")
If you cannot name the exit criterion, you are booking a status meeting. Cancel it and send a written update instead.
Tradeoffs
| Pressure | Cut first | Protect |
|---|---|---|
| Thin overlap | Recurring status calls | One decision slot per week max |
| Client insists on their morning | Optional internal attendees | Required client voices only |
| "We need everyone" | Spectator invites | Decision owners + async summary |
| DST flip week | Assumed offsets | Re-run converter for the real date |
When async is the fairer meeting
Use a written brief when the ask is information, approval with clear options, or a blocker with one owner. Template for stuck work: blocker update. If the next move is still vague after writing, clarify the action before you spend overlap: why remote workers need a clear next action.
What to refuse
- Defaulting every decision to the loudest region's morning
- Invites without local clocks for each required person
- Sixty-minute holds for a ten-minute decision
- Treating empty overlap as a scheduling failure instead of an async signal
Fair scheduling is a constraint, not a personality trait. Run the overlap, book less, write more.