How meeting fairness calculator Works
The burden metric
Hours outside 8–18 local, per meeting, per zone — the number that predicts resentment. A 23:00 call for one side and 14:00 for the other transfers 5 hours of monthly life per weekly meeting from one team to the other. Making the number visible is most of the fix; teams argue less about arithmetic than about feelings.
The rotation patterns
±3-hour alternation (14:00 UTC one week, 17:00 the next) splits the burden for most zone pairs. Monthly rotation suits lower-cadence meetings. The asymmetric compromise (one side always early, the other always mid-day) is acceptable when paired with something concrete returned — the recorded sessions, the written summaries, the skipped-meeting allowance.
When async beats fairness
Past ~4 meetings a month, or with zero overlap, the honest answer is asynchronous: recorded updates, written decisions, and a monthly synchronous decision-meeting rotated fairly. Fairness engineering applies to the meetings that remain; the calendar itself is the thing to shrink first.