The short version
- A rotation spreads the cost of bad meeting times evenly. It does not reduce the cost, and on some pairs the cost is someone's whole evening.
- Rotate the meetings that genuinely need live time. For the rest, the fair answer is to stop holding them.
- Build the rotation on a fixed cycle with the slots published a quarter ahead. Ad hoc fairness is not fairness.
- Whoever takes the bad slot should not also be the one taking notes. That is two costs on one person.
Every global team eventually has the meeting times conversation. One office has been taking the 22:00 call for a year, someone says so out loud, and the response is a rotation. That is an improvement and it is not the answer.
The arithmetic of a bad slot
A weekly call at 22:00 is not one hour. It is the hour, plus not being able to plan the evening, plus the poorer sleep, plus a worse next morning. People describe a late call as costing them the evening, and they are being accurate rather than dramatic.
A rotation divides that cost by the number of offices. With three zones on a fair rotation, each office gets the bad slot every third week. That is genuinely better than one office getting it every week, and it is still a recurring cost you are choosing to pay.
So the first question is not how to divide the cost. It is whether to incur it.
Which meetings actually need live time
Go through every recurring cross zone meeting and classify it. There are only three honest categories.
| Type | Needs live time? | What to do |
|---|---|---|
| Status | No | Write it. Nobody should lose an evening to this. |
| Decision with disagreement | Usually | Rotate it, keep it short, agenda published in advance |
| Discussion and relationships | Yes | Rotate it, and protect it. This is what live time is for. |
Most teams find the first row is the majority of their cross zone meeting load. Removing it shrinks the rotation problem to something a rotation can actually solve. The mechanics are in replacing meetings with written updates.
Building a rotation that holds
For what is left, four rules.
- Fixed cycle, published a quarter ahead. People need to plan around a bad evening. A rotation decided each month is worse than a fixed bad slot, because nobody can book anything.
- Rotate by office, not by person. Otherwise the most junior or most agreeable people end up taking it repeatedly.
- The office in the bad slot does not take notes. Give the writing to whoever is in their working day. Two costs on one office is how rotations quietly stop being fair.
- Nothing consequential is decided in a slot someone is missing. If a zone is excluded, the meeting proposes and the decision is confirmed in writing afterwards.
And write down the cap. Something like: no one takes a slot outside 08:00 to 19:00 local more than once a fortnight. A cap stops the rotation from expanding as the company grows.
The better fix
The reason status meetings survive on distributed teams is not that anyone likes them. It is that they are the only reliable moment when people find out where things stand, and removing them without a replacement leaves everyone guessing.
So the replacement has to work before the meeting can go. This is what StandIn is built for. At the end of the day each person spends about ninety seconds on a brief: what moved, what is open, what is blocked, what is next, mostly drafted from the work itself. Anyone in any zone can then ask where something stands and get an answer from that brief, in the person's words, with a source under it. It never guesses, and when the answer is not there it says so and names who to ask.
What remains is one decision slot per seam per week, which is a rotation small enough to be genuinely fair. See working across time zones and why rotating meetings treats the symptom.
Common Questions
Should we record meetings for the people who cannot attend?
A recording is better than nothing and much worse than five lines of written outcome. Nobody watches a fifty minute recording to find one decision. Write the decisions and what they mean, and keep the recording as backup.
What if one office is much larger than the others?
Rotate by office anyway. Weighting by headcount means the smallest office is always the one awake at midnight, which is how distributed teams lose their satellite hires.
Can we pay people for out of hours calls?
Some companies do and it changes the conversation for the better, because a cost with a price attached gets scrutinised. It does not remove the cost, and in some jurisdictions it creates obligations worth checking first.
How do we handle a genuinely urgent cross zone issue?
Have a named on call person per zone and a written definition of what qualifies. Urgency should reach a named individual, not a whole team's evening.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.