How to Schedule a Meeting Across Time Zones: A Cheat Sheet

To schedule a meeting across time zones, list every attendee's city and working hours, convert them to one reference clock (UTC), pick a slot inside the shared window and send a calendar invite instead of a typed time. For New York, Berlin and Istanbul that window is two hours in summer and one hour in winter.

That last detail is where most scheduling goes wrong. Time differences are not fixed numbers: they change on dates that differ from country to country, and a slot that worked in September can land outside someone's working day in November. According to Microsoft's 2025 Work Trend Index, nearly a third of meetings now span multiple time zones, and meetings starting after 8 p.m. rose 16% year over year. Getting the slot right is no longer an edge case.

This guide gives you a six-step method, a worked New York–Berlin–Istanbul example, a 2026–2027 daylight saving cheat sheet, a fair rotation rule for recurring calls and a comparison of the tools that do the math for you.

Table of Contents

• Why Scheduling Across Time Zones Goes Wrong
• How to Schedule a Meeting Across Time Zones in 6 Steps
• Worked Example: New York, Berlin and Istanbul
• The 2026–2027 Daylight Saving Cheat Sheet
• A Fair Rotation Rule for Recurring Meetings
• Anchor Recurring Meetings to the Right Clock
• Meeting Time Zone Planner Tools Compared
• Write the Invite So Nobody Has to Convert Anything
• How Meeyra Handles Scheduled Meetings Across Time Zones
• Frequently Asked Questions

Why Scheduling Across Time Zones Goes Wrong

The cost of a badly placed slot is measurable. A study of more than 12,000 employees at a Fortune 100 company, published in Organization Science in 2024, found that each extra hour of time difference cut synchronous communication by about 11%, and that one lost hour removed 19% of the shared business-day overlap. The researchers used daylight saving changes as a natural experiment, which is exactly the mechanism that catches schedulers off guard.

Almost every failed cross-border meeting traces back to one of four mistakes:

• A bare time. "Let's meet at 10:00" means nothing across borders. Someone converts it wrong, or not at all.
• An ambiguous abbreviation. CST is Central Standard Time in the US (UTC−6), China Standard Time (UTC+8) and Cuba Standard Time (UTC−5). IST is India (UTC+5:30), Ireland in summer (UTC+1) and Israel in winter (UTC+2). The IANA time zone database, which every major operating system uses, identifies zones by city names such as America/New_York for exactly this reason.
• Daylight saving mismatches. The US and Europe change their clocks on different Sundays, and many countries never change at all. For a few weeks each year, the gap you memorized is wrong by an hour.
• Floating times. A calendar entry saved without a time zone shows the same clock time to everyone, so an event created as "15:00" appears at 15:00 in New York and in Istanbul. The calendar standard, RFC 5545, distinguishes floating times from UTC times and times tied to a named zone; only the last two survive a trip across time zones.

How to Schedule a Meeting Across Time Zones in 6 Steps

1. List cities, not abbreviations

Write down where each attendee actually is: "New York", "Berlin", "Istanbul". A city carries its daylight saving rules with it; "EST" or "GMT+3" does not. If someone is travelling, use the city they will be in on the meeting date.

2. Collect real working hours

Do not assume everyone works 9:00 to 18:00. Some start at 7:00 to finish early, some block school pick-up, and some teams keep a no-meeting afternoon. Ask once and store the answer in your team profile or calendar working-hours setting.

3. Convert everything to UTC and find the overlap

Put each person's working day on one UTC timeline. The shared window is where every bar overlaps. For three or more locations, a visual planner (compared below) is faster than mental math and removes arithmetic errors.

4. Check the date, not just the hour

Before you pick a slot, check whether any attendee's country changes its clocks between today and the meeting date. The cheat sheet below lists every change through 2027 for the regions people ask about most.

5. Send a calendar invite, not a typed time

A proper invite stores the start time in UTC or with a named zone, and each attendee's calendar converts it to local time. Add the time in words as well, following the invite checklist below, so people reading the email on a phone see it immediately.

6. Confirm, then protect the slot

Ask attendees to accept the invite rather than reply "OK". An accepted invite confirms the time zone worked on their side. For recurring meetings, note the next clock change in the invite description so nobody is surprised.

Worked Example: New York, Berlin and Istanbul

Here is the calculation for a team with one person in each city, all working 09:00 to 18:00 local time. Istanbul has used UTC+3 all year since 2016, so every seasonal change in this table comes from New York and Berlin.

Three lessons fall out of this table:

• Winter is the squeeze. When New York moves to standard time on 1 November, Istanbul's end of the shared window lands on its last working hour, 17:00–18:00. One hour a day is enough for a decision meeting, not for a workshop.
• Berlin moves twice in autumn. In the gap week, the same New York slot shows up an hour earlier in Berlin, then returns to its usual time after the US change. If you only check the time difference once a year, this is the week you miss.
• Stretching one edge doubles the window. In winter, if New York starts at 08:00 or Istanbul stays until 19:00, the shared time grows from one hour to two. Who stretches is a fairness question, covered in the rotation rule below.

To read an overlap for a specific day, lay out the hours on a UTC grid. This is the winter grid for the same team:

The 2026–2027 Daylight Saving Cheat Sheet

Clock changes are the single biggest source of meetings that land at the wrong time. These are the dates for the regions that matter most for scheduling across time zones, computed from the IANA database:

The US dates are set in federal law at 15 U.S.C. § 260a; the EU dates come from Directive 2000/84/EC. Several important economies do not change their clocks at all: Türkiye (UTC+3), the United Arab Emirates (UTC+4), India (UTC+5:30), China (UTC+8), Japan (UTC+9), Brazil (no daylight saving since 2019), most of Mexico (since 2022), Arizona (outside the Navajo Nation) and Hawaii.

The weeks to watch are the gaps between the US and European changes. In 2026, the US–Europe difference is one hour smaller from 8 to 28 March and from 25 to 31 October. In 2027, the same happens from 14 to 27 March and from 31 October to 6 November. During those weeks New York is five hours behind Berlin instead of six, and four hours behind London instead of five.

Do not plan around the rules disappearing. In the US, the House passed the Sunshine Protection Act, which would make daylight saving time permanent, by 308 votes to 117 in July 2026; the bill still needs the Senate. In the EU, the European Parliament voted to end seasonal clock changes in 2019, but the Council has made no further progress on the file, and the Commission has already published the EU change dates through 2031. Until a new law actually takes effect, the dates above apply.

A Fair Rotation Rule for Recurring Meetings

Scheduling a call across time zones is a fairness problem before it is a math problem. When a shared window exists, use it. When it does not, rotate the inconvenience instead of assigning it to the same people every week.

Add a colleague in San Francisco to the example team and the shared window disappears: a 09:00–18:00 day in California never overlaps a 09:00–18:00 day in Berlin or Istanbul, in any season. Use a simple burden score to compare options:

• 0 points: the meeting starts between 09:00 and 17:00 local time
• 1 point: it starts at 08:00 or 18:00
• 2 points: it starts at 07:00, 19:00 or 20:00
• 3 points: it starts at 06:00, 21:00 or 22:00
• Never for a recurring meeting: 23:00 to 05:00

Two candidate slots for the four-city team:

Alternate A and B week by week and the total burden splits roughly evenly. Five rules keep the rotation honest:

1. Nobody takes a 2-point slot twice in a row. Alternation is the whole point.
2. Keep a monthly tally. A shared sheet with each person's points ends most arguments before they start.
3. The organizer is not exempt. If you set the meeting, you rotate too.
4. The person in the middle chairs. New York scores zero in every slot here, so that seat takes notes and sends the summary.
5. Every late slot has an async alternative. People who skip a 20:00 meeting read the notes instead of losing the decision.

The fairness point is not only about comfort. The same Organization Science study found that employees who work under stricter limits on working hours were less likely to communicate outside business hours, and that women were less likely to do so than men. A schedule that always relies on the same people staying late quietly favours those who can.

Anchor Recurring Meetings to the Right Clock

Calendar apps anchor a recurring series to the time zone it was created in. When that zone changes its clocks, the meeting keeps its local time there and moves for everyone else.

Suppose a New York manager creates a weekly Tuesday meeting at 09:00 New York time:

• Until 20 October 2026, Berlin sees it at 15:00 and Istanbul at 16:00.
• On 27 October, Berlin sees it at 14:00, because Europe has changed and the US has not.
• From 3 November, Berlin is back at 15:00 and Istanbul has moved to 17:00 for the rest of the winter.

Nothing is broken; the calendar is doing what it was told. The fix is to choose the anchor deliberately. Anchor a recurring meeting to the time zone of the least flexible attendee, or of the majority, and add a line in the description that lists the dates when the meeting will move for everyone else.

Meeting Time Zone Planner Tools Compared

You do not need a paid tool to schedule a meeting across time zones, but the right tool removes the arithmetic. The options fall into four groups: visual converters, calendars, booking links and group polls. Features and free tiers below were checked against each vendor's own documentation in September 2026.

Which one to use depends on the situation:

• Recurring internal meeting with three to six people: a visual planner to find the window, then your calendar with two or three time zones shown.
• One-to-one with an external contact: a booking link, so they pick from your availability in their own time.
• A group whose availability you do not know: a poll with time zone support switched on.

If you are choosing a video platform at the same time, our guide to setting up an online meeting covers the host side from account to first call.

Write the Invite So Nobody Has to Convert Anything

Even with a perfect calendar entry, many people read the time in the email preview first. Write it so that nobody has to do arithmetic:

• Lead with the date and weekday: "Tuesday, 27 October 2026".
• List every city, attendees' first: "16:00 Istanbul · 14:00 Berlin · 09:00 New York (13:00 UTC)".
• Use the 24-hour clock or unambiguous a.m./p.m. The US National Institute of Standards and Technology notes that 12 a.m. and 12 p.m. are ambiguous and should not be used; write "noon" or "12:00".
• Write "ET" or "CET", not "EST" or "CEST", unless you are sure. "EST" in July is technically wrong, and people will correct you instead of reading the agenda.
• Flag clock changes. "Note: the US changes clocks on 1 November, so from 3 November this call is at 17:00 Istanbul."
• Attach the calendar file. The typed time is for reading; the invite is what people's calendars rely on.

For sales and client calls, the cultural side of timing matters as much as the arithmetic. Our guide to video calls with international clients covers who should take the awkward hour in a first meeting, plus typical windows for common trade corridors.

How Meeyra Handles Scheduled Meetings Across Time Zones

Meeyra was built for meetings where people are in different countries, so scheduling follows the same rules as this guide:

• You pick the time in your own local time. When you schedule a meeting from your dashboard, Meeyra detects your time zone from your browser and stores the start time in UTC.
• Invitees see the time in their own calendar. Each invitee (up to 20 per meeting) receives an email with the time labelled by your city (in their own language if they use Meeyra), plus an .ics calendar file that uses UTC timestamps, so Google Calendar, Outlook or Apple Calendar shows it in their local time. An "Add to Google Calendar" link is included as well.
• Reminders and changes follow the attendee. Everyone gets a reminder 15 minutes before the start. If you reschedule, invitees are notified and the calendar entry is updated rather than duplicated.
• Guests join from the browser. Invitees do not need to install anything or create an account to join from the link.

Finding the hour is often only half the problem in an international team; the other half is language. Once everyone is in the room, Meeyra can translate speech live across 42+ languages, so the Berlin engineer, the Istanbul sales lead and the New York client each speak their own language. See how meeting translation works, browse the full feature list, or read our step-by-step guide to hosting a multilingual meeting.

Frequently Asked Questions

What is the best time for a meeting between the US East Coast and Europe?

For New York and Berlin, the shared working window is 09:00–12:00 in New York, which is 15:00–18:00 in Berlin for most of the year. During the few weeks when the US and Europe change clocks on different dates, the gap shrinks to five hours and the window runs from 14:00 to 18:00 Berlin time.

How do I find a meeting time across three or more time zones?

Convert each person's working hours to UTC, lay them on one timeline and look for the hours where every bar overlaps. A visual planner does this in seconds. If no overlap exists, rotate between two slots so the inconvenience is shared.

How do I send a meeting invite for a different time zone?

Create the event in your calendar with the correct date and time, then send it as an invite rather than typing the time into an email. Calendar invites store the time in UTC or with a named time zone, and each recipient's calendar shows it in their local time.

Does Türkiye change its clocks for daylight saving time?

No. Türkiye has stayed on UTC+3 all year since 2016. Its difference from Berlin is one hour in summer and two hours in winter, and its difference from New York is seven hours in summer and eight in winter.

What happens to recurring meetings when daylight saving time changes?

A recurring meeting keeps its local time in the time zone it was created in. When that zone or an attendee's zone changes its clocks, the meeting moves by an hour for attendees elsewhere. Check your series before each change in March, April, October and November.

Is the US or the EU ending daylight saving time?

Not yet. The US House passed the Sunshine Protection Act in July 2026, but the Senate has not, and the EU proposal to end clock changes has been stalled in the Council since 2019. For 2026 and 2027, plan with the normal March and October–November changes.

Should I write EST or ET in a meeting invite?

Write ET (Eastern Time) unless you know which one applies. EST is only correct in winter; from March to November New York uses EDT. Listing city names, such as "09:00 New York", avoids the problem entirely.

What is the fairest way to schedule meetings across time zones?

Use the shared window whenever one exists. When it does not, rotate between two or three slots, never give anyone an early or late slot twice in a row and keep a simple monthly tally of who took the inconvenient hours.

Before You Hit Send

Check three things: every attendee's city is on the invite, no clock change falls between today and the meeting date, and the slot sits inside everyone's working day, or the burden is on the rotation list. Do that, and scheduling a meeting across time zones takes two minutes instead of an email thread.

When the time is set, the next step is making sure everyone understands each other. Create your Meeyra account, schedule the meeting and send the invite from your browser.