Rotating meeting times: the fairest way to run a global standup

A team in San Francisco, London and Singapore has no civilised common hour. Someone is always asked to be on a call before breakfast or after dinner. Pick a fixed time and one region quietly resents it for years. Rotation fixes that, not by finding a magic slot, but by sharing the discomfort evenly and making it predictable.

Why a fixed time quietly fails wide teams

When a team spans more than about eight hours of offset, the overlap of normal working hours shrinks to nothing. A single recurring time then permanently favours whoever sits in the middle and permanently penalises the edges. The cost is invisible on the calendar but real in practice: the same people miss dinners, log on at dawn, or simply stop showing up. The trend is measurable, too: Microsoft's 2025 Work Trend Index found that meetings after 8 PM were up 16% year over year, with global and flexible teams accounting for much of the increase.

Rotation accepts the hard truth: there is no fair fixed time, so fairness has to come from taking turns instead.

How do you set up a fair meeting rotation?

The method is simple and worth doing on paper once before you automate it.

1. List each region and its working window. Write down everyone's local time for a few candidate slots so the trade-offs are visible.
2. Pick two or three tolerable slots. Each should be comfortable for at least part of the team and merely awkward, never brutal, for the rest. Avoid anything past roughly 9 PM or before 7 AM for anyone.
3. Assign them in a fixed cycle. Each region takes the least convenient slot in turn, so over a full rotation the burden lands on everyone roughly equally.
4. Anchor to one reference zone. Express the schedule in UTC or one home city, then let each person read their own local time. This keeps daylight saving from silently breaking the plan.

A concrete example rotation

Take that San Francisco, London and Singapore team. Two slots are tolerable: one kind to the Americas, one kind to Asia. You alternate, and over a fortnight nobody is favoured twice in a row.

London never draws a bad slot here, which is the reality of sitting in the middle. San Francisco and Singapore each take one midnight or pre-dawn call per fortnight rather than one of them taking it every single week. That asymmetry is honest, and it is far easier to accept than a fixed time that pretends the problem does not exist.

Publish it, and make it predictable

A rotation only works if people trust it. Predictability is the whole point.

• Publish months ahead. Put the full cycle in a shared doc and on every invite, so anyone can look forward and know which slot falls to them in, say, eight weeks.
• Make it boring. A simple alternating pattern people can recite from memory beats a clever optimised schedule no one can predict.
• Send calendar invites in local time. Each person's calendar should show their own clock, not a converted figure they have to trust. Atlas writes the event to your calendar so every attendee sees the correct local time automatically.

Pair it with async so missers stay informed

No rotation is truly fair if skipping a hostile slot means falling behind. Nobody should join a 1 AM call out of fear of missing out.

Record every meeting and post a short written summary, decisions, owners and next steps, to a shared channel within the hour. That way the rotation governs who attends live, but information reaches everyone regardless. If most of your updates are status anyway, consider whether a daily live call is even needed; our guide to the daily standup across time zones covers async-first alternatives.

When rotation is not the answer

Rotation suits teams that genuinely need to meet live and have no usable overlap. If your spread is narrow enough to find one decent shared hour, just use it. And if a meeting is purely informational, drop the live element entirely and go async. Rotation is for the hard middle ground: real-time collaboration across a punishing spread, where the only fair move is to take turns.