How to Schedule Meetings Across Time Zones Without Annoying Half the Team
· 8 min read · Officeagent research
Try it on a real task
Routing slip · Officeagent
Status: Ready
Action requested
Pick a task above and press RUN IT. Officeagent handles it end to end; you approve the send.
Reading page /
☐ Approve · nothing sends without you
In the product you edit the draft right here; the agent learns your correction.
Officeagent drafted, you approved, it executed.
Sample data · Officeagent always waits for your approval before anything is sent
To schedule meetings across time zones, work in UTC offsets rather than city names, find the genuine overlap in everyone's working hours before proposing anything, rotate which region takes the inconvenient slot on recurring calls, and always send the invite with the time zone stated for each participant. Let the calendar do the conversion, and never ask a participant to convert a time themselves.
Everything that goes wrong with cross-time-zone scheduling comes from one of three causes: a human did the arithmetic, a daylight saving change moved the meeting for half the participants, or somebody optimized for the organizer's convenience without noticing. All three are avoidable.
Find the overlap before you propose anything
Start by writing down each participant's working hours in their own local time, then converting all of them to a single reference (UTC is the usual choice). What you are looking for is the window where everybody is genuinely working, not the window where the meeting is technically possible.
Some overlaps are comfortable and some barely exist. US East Coast and Western Europe share a real window: 9am to noon in New York is 2pm to 5pm in London, which works for everyone. US West Coast and Central Europe are tighter: 8am in San Francisco is 5pm in Berlin, and that is roughly the whole overlap. US and India, or US West Coast and Australia, have essentially none inside standard hours, and you should stop looking for a slot that hurts nobody, because there isn't one.
| Pairing | Comfortable overlap in standard business hours | Practical approach |
|---|---|---|
| US East and US West | Roughly 11am to 5pm Eastern | Easy. Avoid before 8am Pacific. |
| US East and Western Europe | Roughly 9am to noon Eastern | The best cross-continental window there is. |
| US West and Western Europe | Roughly 8am to 10am Pacific | Narrow. Protect it and book early. |
| US and India | Effectively none in standard hours | Someone works early or late. Rotate it. |
| US West and Australia East | Effectively none in standard hours | Late afternoon Pacific hits next-morning AEST. Rotate. |
When there is no good time, rotate it
For a one-off, pick the least bad slot and acknowledge the cost out loud to whoever is taking it. For anything recurring, rotate. A weekly call that is always 7am for the same team builds quiet resentment over a year, and the fix costs nothing: alternate between a slot that suits one region and a slot that suits the other, on a schedule everyone can see.
The other lever is to hold fewer synchronous meetings across impossible gaps. A recurring status call between regions with no overlap is usually a document that wants to be written rather than a meeting that wants to be held. Reserve the painful slot for the conversations that genuinely need to be live, and make sure whoever gets up early gets a real decision out of it.
Daylight saving is where recurring meetings break
This is the failure mode people do not see coming. The US moves its clocks on different dates from Europe, so for roughly two weeks in March and one in late October a recurring US-Europe meeting sits at a different relative time than it did the week before. In the southern hemisphere the shift goes the opposite direction. Arizona and Hawaii do not observe daylight saving at all, and neither do most countries near the equator or, as of recent years, most of Mexico.
Two rules handle it. First, anchor a recurring meeting to one location's local time and say which one in the invite title or description: "10:00 New York" tells everyone what happens in March. Second, if a specific participant absolutely cannot move (a school run, a childcare handoff, a hard stop), check the invite in the changeover weeks rather than assuming. Calendar tools handle the conversion correctly, but they cannot know that a shift from 4pm to 5pm in Berlin broke somebody's evening.
Write the invite so nobody has to calculate
Send the calendar invite rather than a time in an email body. A proper invite carries the time zone, so every participant's calendar renders it in their own local time and no one converts anything. If you must state times in prose (for a proposal to someone outside your company, say), state the offset explicitly and give both ends: "Thursday 2pm New York, which is 7pm London."
- Always send a calendar invite, not a bare time in an email.
- Set your own calendar's time zone correctly, then trust it.
- Name the anchor city in the title of anything recurring.
- Never write a bare "3pm" to someone in another region.
- Avoid abbreviations like CST and IST, which are ambiguous. Use city names.
- Attach the agenda to the invite, so an early or late attendee knows what they got up for.
What scheduling tools do and do not solve
Booking links, the schedulers built into Google Workspace and Microsoft 365, and auto-scheduling tools all handle the conversion correctly. That is genuinely solved and you should not be doing arithmetic in 2026.
What none of them solve is judgment. Nothing stops a booking tool from offering a technically valid 7:30am slot to someone whose working hours it was never told about, and nothing makes it notice that the same person has taken the bad slot four weeks running; it is the gap we walk through in Officeagent versus Calendly. Set working hours per person in whatever tool you use, set a rule about which hours are acceptable to book, and check recurring series periodically. If you are still deciding which tool to buy, we compared the options honestly on the best AI scheduling assistant page, including the free ones you may already own.
The other thing a scheduling tool cannot do is the negotiation. A meeting with three people across two companies and three time zones does not get resolved by sending a link, because the other side is not going to click yours. Somebody has to read the thread, work out the real constraints, propose specific times that respect everyone's hours, absorb the reschedule, and send the invite with the agenda attached. That is administrative work, and it is what Officeagent does: it drafts the reply with workable times and books it once a human approves. The mechanics are on the meeting scheduling page.
A short checklist for cross-time-zone meetings
- Confirm each participant's working hours, not just their time zone.
- Find the true overlap before proposing a time.
- If there is no comfortable slot, name that and rotate the burden.
- Anchor recurring meetings to one city and put it in the title.
- Check the March and October changeover weeks.
- Send an invite with an agenda, never a bare time in prose.
- Record it or write the notes for whoever legitimately could not attend.
That last point matters more as teams spread out. When a genuine overlap does not exist, a written record is what keeps the person in the other hemisphere from being second class, and the same discipline that makes a good set of meeting minutes is what makes an asynchronous team work at all. It is one of the practical differences between a company that hires people who work from anywhere and one that only says it does.
Frequently asked questions
What is the best time to schedule a meeting across time zones? For US and Western Europe, 9am to noon US Eastern is the strongest window. For US-only teams spanning coasts, 11am to 4pm Eastern works for everyone. Where regions have no overlap in standard hours, there is no best time, only a least bad one that should rotate between the parties.
How do I avoid daylight saving time problems in recurring meetings? Anchor the series to one location's local time and name that city in the invite title, so participants know which side shifts. Then check the series during the changeover weeks in March and late October, when the US and Europe are out of step for one to two weeks.
Should I state the time zone when proposing a meeting time? Always, and use a city name rather than an abbreviation, since CST and IST both refer to more than one zone. Better still, send a calendar invite instead of a time in prose so each person's calendar does the conversion for them.
How many time zones is too many for one meeting? Three is where it gets genuinely hard, because someone is almost always outside comfortable hours. Beyond that, ask whether the meeting needs to be synchronous. A recurring cross-region status call is usually a written update with a live decision meeting attached at a much lower frequency.
Do AI scheduling tools handle time zones automatically? Yes, all the mainstream ones convert correctly and will not make an arithmetic mistake. What they do not do is exercise judgment about whether a technically valid slot is a reasonable one, so set working hours for every participant and review recurring series yourself.