Barq Meet
Create your free link

How to schedule meetings across time zones

On this page

Whose time zone controls the available hours?

The availability schedule's zone controls the hours you offer, while the guest's selected zone controls the labels they see. A schedule offering 18:00 to 21:00 in Asia/Karachi keeps those Karachi hours even when a visitor selects America/New_York. The instant stays consistent.

We start the guest display with the browser's detected zone, falling back to UTC when no zone is supplied. Guests can change the selection themselves. Don't assume a browser on a borrowed laptop is already set to the visitor's current location, particularly when that person is traveling or using a shared computer.

If the booking link isn't ready yet, set up its schedule and calendar connection first. Then test one dated slot in both zones instead of comparing two screenshots taken on different days.

How does daylight saving change cross-zone meeting times?

A fixed host hour can appear at a different guest hour when one location changes clocks and the other doesn't. Karachi 18:00 is New York 08:00 on 6 March 2026, then 09:00 on 9 March 2026. Convert the date too.

DateAsia/Karachi offerKarachi offsetAmerica/New_York equivalentNew York offset
6 March 202618:00 to 21:00UTC+05:0008:00 to 11:00UTC-05:00
9 March 202618:00 to 21:00UTC+05:0009:00 to 12:00UTC-04:00

Method: computed with Luxon using Asia/Karachi and America/New_York for each stated date, not a manually maintained fixed offset. Use named zones for future dates so the conversion follows the runtime's time-zone rules, including offset changes that a saved fixed difference between two cities cannot represent.

We label repeated wall-clock times with their UTC offsets when a daylight-saving transition makes the same local hour occur twice. That lets a guest distinguish two starts that would otherwise have identical clock labels.

Where do working hours overlap on a real date?

For 09:00 to 17:00 working days on 9 March 2026, London and New York overlap from 13:00 to 17:00 UTC. That's 13:00 to 17:00 in London and 09:00 to 13:00 in New York. Four hours overlap. The workweek-by-country guide is a starting point for checking working days, with each participant's actual hours confirmed independently.

London and New York share four working hours on 9 March 2026

2026-03-09 (UTC axis) · Axis in UTC · 09:00–17:00 local working hours

00:0006:0012:0018:0024:00

London (Europe/London)

New York (America/New_York)

Overlap: 13:00–17:00 London / 09:00–13:00 New York

Solid neutral: working hours. Teal with outline: shared hours.

London and New York share four working hours on 9 March 2026. 2026-03-09 (UTC axis). Overlap: 13:00–17:00 London / 09:00–13:00 New York
ZoneIANAWorking hours (local)Working intervals (UTC, 2026-03-09)Shared hours (local)
LondonEurope/London09:00–17:0009:00–17:0013:00–17:00
New YorkAmerica/New_York09:00–17:0013:00–21:0009:00–13:00

Method: Luxon computes each named zone's 09:00 to 17:00 interval on the figure's common UTC date axis, then intersects the intervals. The figure shows clock-hour overlap, not holiday eligibility or anyone's calendar availability.

Karachi and New York don't share a 09:00 to 17:00 window on that March date. If a Karachi host offers 18:00 to 21:00 instead, the New York guest gets the 09:00 to 12:00 choices above. That's a deliberate evening exception for the host, who should agree to those hours before sending the candidates instead of assuming that a correct conversion makes them convenient. The London-to-Lagos meeting planner compares dated working-hour overlap; confirm individual calendars after choosing a candidate window.

Choose an exception you can keep. A conversion can tell you that a meeting is possible at midnight; it can't make midnight a reasonable working hour.

How should I change my schedule while traveling?

Use a independently zoned schedule when your offered hours should follow the travel location, or convert temporary hours into the existing schedule zone for a date override. Overrides retain their parent schedule's zone. They don't add a travel-zone field.

Suppose your schedule remains in Asia/Karachi but you're offering a New York morning on 9 March 2026. Entering 09:00 in an override means 09:00 Karachi, not 09:00 New York. To offer 09:00 New York, the corresponding Karachi start is 18:00.

We keep each schedule's zone explicit so a date exception doesn't silently reinterpret the weekly hours. The availability schedule reference covers overrides; meeting buffers protect preparation time around those international calls. The meeting-time planning guide starts with preparation and participant availability instead of claiming one hour works best for everyone.

Will calendar invitations show everyone's local time?

A confirmed invitation describes one booked instant, which each calendar displays according to its own time-zone settings. A Karachi 18:00 booking on 9 March 2026 should correspond to New York 09:00 on that date. Check the calendar's selected zone.

Use one test appointment to verify that relationship. Inspect the guest confirmation, the host calendar and the guest calendar instead of treating a zone abbreviation in a message as the entire booking record.

A guest changing display zones before booking hasn't rescheduled anything. Once the appointment exists, changing its actual instant requires the booking's reschedule action. That distinction matters when someone says the time "moved" after a browser or calendar setting changed. For a suspicious displayed hour, check the booking page's time zone before moving an appointment that may already represent the right instant.

Checking a cross-zone booking and fixing mistakes

Test a single dated slot in the host and guest zones before sharing an international offer. Read the local date alongside the hour, particularly when the conversion crosses midnight. Use the picker deliberately. The Chicago-to-London meeting planner compares dated working-hour overlap; confirm individual calendars after choosing a candidate window. For a conversation spanning dated London and Tokyo hours, check the shared workday before repeating a familiar start in another season.

SymptomLikely causeFix
One-hour discrepancy on a later dateOffset changed between datesConvert the actual meeting date in named zones
Travel override appears at the wrong hourEntered in the schedule's original zoneConvert it or use a independently zoned schedule
Guest sees UTCBrowser supplied no zoneChoose the intended display zone
Same local hour appears twiceRepeated time at a clock changeUse the UTC-offset labels

This is single-host scheduling; it won't search every team member's calendar for group overlap. Review the account's scheduling features, then create a booking link for guests in other zones using hours you've checked in both locations.

Steps

  1. Open Events and choose Availability

    Open the schedule and set its named time zone. Weekly hours and date overrides are interpreted in that zone.

  2. Assign the schedule to the event

    Under When people can book, select the schedule whose hours you intend to offer. A guest display-zone change does not alter these hours.

  3. Compare a dated slot in both zones

    Open the public page and use its time-zone picker. Check the calendar date as well as the clock time for each person.

  4. Adjust travel hours deliberately

    Convert temporary hours into the existing schedule zone for a date override, or create a schedule in the travel zone. Overrides do not carry a separate zone.

  5. Verify a test invitation

    Book with an inbox you control and inspect the start instant in both calendars. Cancel the test after confirming that the local times describe the same appointment.

Frequently asked questions

Does changing the guest time zone move an existing meeting?

No. Choosing another display zone changes how the same slot is labeled. To change a booked appointment's actual start, use its reschedule route; switching the time-zone picker isn't a request to move the meeting. Compare the confirmed start as an instant and the full local date on both sides, instead of treating a different displayed hour as proof that the guest rescheduled an existing appointment.

What happens if the browser cannot detect my zone?

The guest view uses UTC when browser detection supplies no zone. Choose your intended location in the picker before selecting a time, especially on a shared computer whose browser settings may differ from where you're working. Choose the intended named zone in the guest display and inspect the converted date, especially when traveling or booking from a device whose configured location differs from where you will attend.

Can this find a common time for every colleague?

No. This booking flow offers one host's availability to a guest. It doesn't combine several hosts into a collective event, so arrange group overlap yourself or choose a scheduler designed to check everyone's calendars together. Agree the required attendees independently or choose documented collective scheduling, because displaying one host's eligible starts in another zone doesn't inspect every colleague's diary or calculate a shared team opening.

Create your free booking link

Sign in with Google, create an event and share your link.

Create your free link