Sometimes the grid has no perfect green column. That is useful information. It tells you that the team needs a decision about the meeting, rather than more creative timezone arithmetic.
Start with constraints people have actually agreed to
Ask each person for a normal work window and for commitments that cannot move. Do not infer availability from a city's sunrise, an office address, or the fact that someone answered a message late yesterday. A city is a time zone; it is not a person's consent to an early call.
Keep the request easy to answer: “What hours can we normally schedule within? Are any edges occasionally possible? Are there days we should avoid?” People should be able to describe a constraint without explaining private family or health details. Record the availability rule, not its personal justification.
Give the meeting a smaller job
Before asking someone to move their day, define the outcome. Is this a decision that requires live discussion, a relationship-building conversation, or a status update that could be read? A recurring hour-long call often contains several different jobs. Splitting them can leave a much smaller shared window to find.
For example, publish project status before the call and reserve 25 minutes for two decisions. Let people comment on the written status in their own working day. Use the meeting for disagreements that benefit from immediate conversation, then record the outcome for people who could not attend.
Complete the sentence “By the end of this call, we will have decided…” If you cannot finish it, pause the invitation and ask whether a short written update would do the job.
Rotate a specific burden
When an occasional outside-hours meeting is necessary and participants agree, make the pattern explicit. One month might favor the Americas; the next might favor Asia-Pacific. The aim is not mathematical symmetry at any cost. The aim is to avoid the same people absorbing an invisible inconvenience every time.
A useful rotation has an owner, a short horizon and a review date. Publish the next three or four occurrences with everyone's local dates and times. A slot that looks “early” in one place may already be the next calendar day somewhere else. Check the dates individually, especially around daylight saving transitions.
Measure more than the clock hour
Two people joining at 07:00 do not necessarily bear the same burden. Consider frequency, meeting length, ability to participate effectively and whether the person is already supporting other regions. Ask about the pattern, rather than declaring it fair because a spreadsheet balances.
A lightweight review can use three questions: Was the time workable? Could you contribute? What should change next cycle? An organizer can note which region took the awkward slot and the next agreed preference without storing sensitive explanations.
Make a missed meeting safe
A rotation fails if people must join every call to learn what happened. Give each meeting a written decision record: the decision, rationale, owner, next action and a deadline for raising an overlooked issue. State whether the absent person's input is needed before the decision becomes final.
A recording may be useful with participants' agreement, but a recording alone makes the next person search through the whole conversation. A concise written outcome is easier to use across schedules and connection speeds. Put it where the team already finds project work.
A sample agreement to adapt
We will first look for a 30-minute overlap inside agreed work windows. If none exists, the owner will propose an async decision or two smaller calls. Any occasional outside-hours slot requires agreement, rotates by region, and gets a written outcome within the organizer's next workday.
This is a starting point, not a universal policy. Review it when the team changes location, when someone reports a recurring burden, and before the next season's clock changes. The planner helps expose the time tradeoffs; the team makes the human decision.