Anyone who has worked with a remote team, a client overseas, or a supplier on another continent knows the quiet dread of picking a meeting time. Choose wrong and someone joins bleary-eyed at 5 a.m. or gives up their dinner. Get it right and collaboration flows. Learning how to schedule a meeting across time zones is one of the most valuable soft skills of modern work, and it is far more of a system than a guess.
This guide walks through the whole process: how to map everyone's working hours onto a single timeline, how to find the overlap where a meeting is humane for all, how to handle the chaos of daylight saving, and how to lock a time so it never drifts. With a time zone converter and a clear method, you can plan a call in under a minute.
Start by Mapping Everyone's Working Hours
The core of good scheduling is not finding a single "correct" time; it is finding the window where every participant is awake, alert, and ideally still within normal working hours. To do that, you first need to know where everyone actually is and what their local clock reads when yours reads a given hour.
Begin by listing each participant's city and its current UTC offset. Remember that a city's offset can shift with daylight saving, so use the live value rather than a half-remembered one. Our explainer on how time zones work covers the offset system if you need a refresher, and the world clock lets you see several cities at once.
Find the Overlap Window
Once you can see everyone's local time side by side, the goal is the overlap: the band of hours during which all participants are comfortably at their desks. For two nearby zones this is generous. For zones on opposite sides of the planet it can shrink to almost nothing, and you may have to accept that someone joins early or late.
A Simple Overlap Method
Here is a reliable routine for finding a workable slot:
- Pick a reference zone. Choose one participant's zone, or better, use UTC as a neutral baseline.
- Convert each person's 9-to-5 into that reference. Write out when each participant's working day starts and ends on the shared timeline.
- Look for the common band. The hours where all the working days overlap are your candidate slots.
- Favour the middle of the overlap. A time near the centre gives everyone breathing room rather than squeezing against the edge of someone's day.
- Confirm each local time. Run the chosen moment through the time zone converter to see exactly what each person's clock will read.
When the overlap is genuinely tiny, be honest about it and share the burden fairly, which we cover next.
When There Is No Good Overlap
Some combinations simply have no comfortable common hour. A team split between the US West Coast and East Asia, for instance, faces a gap of roughly 15 to 16 hours, so one side's workday barely touches the other's. This is a real constraint, not a failure of planning, and it comes up constantly, as our guide to calling between the US and Asia explains.
When no slot pleases everyone, apply these principles:
- Rotate the pain. Alternate who takes the early or late call so the same person is not always inconvenienced.
- Prefer edges of the day. Early morning for one side often meets late evening for the other; that is usually kinder than the middle of the night.
- Record and summarise. If a live meeting is genuinely brutal for someone, consider an asynchronous update instead.
- Keep it short. A tight, well-run 30 minutes respects the person who had to stretch their day.
The Daylight Saving Trap
The single biggest cause of botched cross-zone meetings is daylight saving time. Because different regions change their clocks on different dates, and some never change at all, the gap between two cities is not constant. A recurring call that works perfectly in January can suddenly be an hour off in March when one region springs forward before the other.
Consider the US and Europe. The US moves its clocks forward in early March, but the EU waits until the last Sunday of the month. For those few weeks, the usual difference between New York and London is off by an hour, quietly derailing standing meetings. We break this down fully in what is daylight saving time. The lesson: never treat a time difference as permanent, especially around the spring and autumn changeovers.
Anchor Recurring Meetings to UTC
The professional fix for the daylight saving trap is to stop thinking in local time for recurring events and anchor them to a fixed reference instead. Coordinated Universal Time never observes daylight saving, so a meeting pinned to a specific UTC time stays at that absolute moment forever, no matter what local clocks do.
In practice, decide the meeting time in UTC, then let each participant translate it into their own local clock. Because UTC is constant, the meeting will not drift when one region changes its clocks, even though the local reading for some participants will shift by an hour. You can watch the current standard on our UTC time display, and if you are curious why UTC is chosen for this role, our piece on why servers use UTC explains the same logic that keeps global software in sync.
Communicate the Time Clearly
Even a perfectly chosen slot fails if it is communicated ambiguously. "Let's meet at 3" is an invitation to disaster when participants span continents. A few habits prevent almost all confusion:
- Always name the zone. Write "3 p.m. New York time (UTC-4)" rather than just "3 p.m."
- Include each participant's local time. Spelling out "9 p.m. in London, 6 a.m. in Sydney" removes all doubt.
- Use a calendar invite. Good calendar tools store the event in an absolute time and display it correctly in each attendee's zone automatically.
- Share a converter link. Letting people confirm for themselves with the time zone converter heads off mistakes.
A Worked Example
Suppose you need to gather colleagues in San Francisco, London, and Singapore. San Francisco is around UTC-7 in summer, London around UTC+1, and Singapore at UTC+8. Mapping their working days onto a shared timeline reveals a painfully thin overlap. San Francisco's morning is London's late afternoon and Singapore's late evening. A slot at 8 a.m. in San Francisco lands at 4 p.m. in London and 11 p.m. in Singapore, which just barely works if the Singapore colleague is willing to stay up. There is no perfect answer here, only the least-bad one, which is exactly why mapping and honesty beat guessing.
Conclusion
Scheduling across time zones is a repeatable craft, not a gamble. Map everyone's working hours onto one timeline, hunt for the overlap, share the burden fairly when there is none, and always account for daylight saving by anchoring recurring meetings to UTC. Finish by communicating the time unambiguously with the zone spelled out. Do that consistently and the dreaded 5 a.m. call becomes a thing of the past. Start your next plan with the time zone converter, glance at the world clock to see who is awake, and explore every tool on the thetimezone.us homepage.