Scheduling for execs in three regions: a chief-of-staff workflow

When leadership spans three regions, ad-hoc scheduling fails fast. Every booking becomes a small negotiation, someone always loses an evening, and the chief of staff becomes a human time-zone calculator. The fix is to stop solving each meeting and start running a system that makes most decisions for you.

Why three regions breaks ad-hoc scheduling

With two regions you can usually find a humane overlap and forget about it. Add a third and the maths turns hostile: an Americas leader, a European leader and an Asian leader rarely share more than an hour or two of mutual daytime, and that band drifts twice a year as daylight saving shifts at different dates. Solve each meeting by hand and you will make small errors constantly, and the cost of those errors lands on the most senior calendars in the company.

A standing system removes the per-meeting decision. You design it once, publish it, and only revisit it when someone relocates or the team composition changes. This is no edge case either: in Buffer's 2023 State of Remote Work report, 62% of respondents said people in their immediate teams were distributed across multiple time zones, so a system that handles the spread is fast becoming the default need rather than the exception.

Step 1: Keep one source of truth for each person's zone

The single most common cause of a mis-booked executive meeting is a stale time zone. People travel, relocate, and split their year across cities. If three different assistants each hold their own guess, you will eventually book a 6:00 AM call for someone who moved.

Maintain one shared record: each leader, their home city, and their current working zone. Update it the moment anyone relocates or starts an extended trip. A live map you can glance at beats a spreadsheet that goes stale, which is exactly what Atlas is built for, pinning each person and showing their real local time at a glance.

Step 2: Set standing core hours for leadership

Find the band where all three regions overlap and protect it. With the Americas, Europe and Asia represented, that band is usually narrow, often the European morning or late afternoon. Declare it as leadership core hours: the only window in which synchronous, all-hands-of-leadership work is booked.

Everything outside that band defaults to async by design: written updates, recorded video, decisions logged in a doc. For the full method of finding and defending that window, see core collaboration hours.

Read across the table and the lesson is plain: Europe is the natural pivot, so the realistic shared band sits in the European late afternoon, which is the Americas morning and the Asian evening. Pick the kindest one-to-two-hour slice of that and make it sacred.

Step 3: Batch regional 1:1s into the right windows

Most of a leader's meetings do not need all three regions. A leader's 1:1s with their own regional reports belong in that leader's own daytime, not in the precious shared band. Reserve the overlap strictly for things that genuinely need everyone.

• Americas 1:1s sit in the Americas afternoon, when Europe and Asia are off the clock anyway.
• Asian 1:1s sit in the Asian morning, before the late-day overlap with Europe.
• The shared band stays clear for cross-region decisions, leadership syncs and anything requiring live debate.

Batching also protects focus. A leader whose 1:1s are clustered keeps long unbroken stretches for deep work, rather than a calendar shredded into fragments by meetings booked at random.

Step 4: Rotate the global leadership call

Some meetings simply cannot fit a humane shared band, the genuinely global leadership call being the obvious one. When no slot is fair to everyone, the fair move is to share the inconvenience.

Rotate the call on a fixed cadence so each region takes its turn at the awkward hour. Publish the rotation a quarter ahead so nobody is surprised. Crucially, never let attendance at the unsociable slot become an advantage: record every session and circulate a written summary, so the person who skipped a 10:00 PM call loses nothing.

Putting the system on autopilot

Once the four pieces are in place, the chief of staff's job shifts from calculating to maintaining. You are no longer solving each booking; you are keeping the time-zone record current, defending the core-hours band, and running the rotation. The recurring decisions are made.

The one thing worth doing live, every time, is reading each person's actual local time rather than doing offset arithmetic in your head, half-hour zones and daylight saving make mental maths unreliable. Pin every leader on a single map and the awake-or-asleep question answers itself, which is the part of this whole workflow that Atlas removes entirely.