How to schedule across time zones without annoying your team

A meeting that is 10am for you might be 2am for someone else. When a team is spread across San Francisco, London and Singapore, there is no universally good hour, only a narrow band when everyone is awake and at their desk. Most scheduling friction comes from ignoring that band and defaulting to the organiser's convenience. Here is how to do it properly.

Start from working hours, not clocks

The instinct is to convert times in your head: "10am here is 6pm there, that works." It usually doesn't. The right unit is not the clock, it's each person's working window. Write down each teammate's city and their normal hours, say 9am to 6pm, and you immediately see where the day genuinely overlaps versus where someone would merely be technically awake. This is an increasingly common situation: in Buffer's 2023 State of Remote Work survey, 74% of respondents said their company operates across multiple time zones.

For a step-by-step method of finding that overlap, see our guide on how to schedule a meeting across time zones. The short version: line everyone up against one reference such as UTC, find the stretch where all the working windows are still open, and pick a time inside it.

Aim for the middle of the overlap

If the only shared window is 4pm to 6pm in London, schedule for 4:30pm, not 5:55pm. A buffer means an overrun or a dropped call doesn't push someone straight past the end of their day. The edges of the overlap are where goodwill quietly leaks away.

Rotate the inconvenience

Some teams simply have no civilised overlap, for example a group split between the US West Coast and India. When that happens, the worst thing you can do is permanently assign the bad hour to one region. Asking the same person to join at 10pm every week is how resentment builds.

Rotate it. One week the call is friendly for the Americas; the next it favours Asia. Publish the rotation so it feels deliberate and shared rather than arbitrary. Fairness is less about finding a perfect time and more about distributing an imperfect one evenly.

Default to async; reserve live time for real discussion

The most reliable way to schedule fewer painful meetings is to hold fewer meetings. Status updates, FYIs and simple decisions rarely need everyone in a room at once. Move them to a written update, a recorded video, or a threaded discussion, and protect your scarce overlap for the conversations that actually benefit from being live: debate, planning, relationship-building.

Quote times so nobody mis-reads them

When you do send the invite, never write a bare "let's meet at 3." Spell out the time in each person's own zone, for example "9am San Francisco / 12pm New York / 5pm London." If you use a single reference, use UTC rather than GMT, because GMT is ambiguous in summer (see UTC vs GMT). Clear notation prevents the classic "I thought it was an hour later" no-show.

Mind daylight saving

The offset between two cities is not constant. Because countries change their clocks on different dates, the gap between, say, New York and London is one hour different for about three weeks each spring and autumn, so a recurring call silently drifts. Keep our DST 2026 dates to hand, and always confirm the local time on the real meeting date in late March and late October.

Let Atlas carry the overhead

Every step above is bookkeeping a tool should handle. Atlas pins each teammate on a world map, shades their working hours, and shows you the overlap windows at a glance, with daylight saving already accounted for. When you pick a time, one tap writes it to your calendar in everyone's correct local time. You keep the judgement, like rotating the awkward slot; Atlas removes the arithmetic.