Use a dated calendar invitation with the intended city-based time zone and confirm each person’s local view.
For a meeting across time zones, agree a full date, a start time in a named city zone and a duration. Then send a proper calendar invitation and ask each person to check their local display. Do not rely on “tomorrow at three” or a remembered hour difference.
The date matters as much as the clock. A meeting can fall on another calendar day for someone elsewhere. Daylight-saving changes can also alter the difference between two places during the year.
Write the meeting facts before offering times
Note who needs to attend, where each person expects to be and how long the call needs. Ask for a city and country when a place name is ambiguous. A colleague travelling next week may not be using their usual home time zone.
Choose two or three reasonable options, with dates written in words rather than an ambiguous numeric format. Include the year when planning ahead. An option such as “the agreed Tuesday, 14:00 in the selected city zone, for 30 minutes” gives the calendar a clear job once the actual date is entered.
Respect ordinary waking and working hours without assuming everyone follows your schedule. Ask whether the proposed local time is workable. Seeing an empty calendar does not mean a person is willing or available to join.
Choose the event’s zone deliberately
When creating the event, inspect its time-zone field as well as the visible start time. Search for the relevant city or region using the calendar’s supported picker. Do not replace a city zone with a fixed offset unless you specifically understand and need that behaviour.
Google Calendar’s time-zone instructions describe setting an event’s zone and displaying additional zones. Google also warns that later regional time-zone rule changes can affect events created before the change was known. An invitation is useful, but an old saved event still deserves a check.
Use a timed event for a meeting with a specific start. An all-day item is a different kind of reminder. Check the end time too, especially when the call crosses midnight in the organizer’s or an attendee’s local display.
| Detail | What to confirm |
|---|---|
| Date | The full calendar date in each participant’s view |
| Event zone | The intended city or region in the event settings |
| Start and finish | The local display and the agreed duration |
| Location | The correct online joining link or physical address |
| Repeating meetings | Future occurrences around seasonal changes and travel |
Confirm the invitation instead of copying clock times
A calendar invitation lets supported receiving calendars show the same meeting in local time. Microsoft’s Outlook guidance explains that meeting times are stored using UTC and displayed in the respective local zones. The practical check is whether each person sees the expected local date and time.
Ask a participant to open the actual invitation, not only a screenshot or a forwarded sentence. If their display differs, compare the organizer’s event zone, their calendar’s display zone and the full date. Repeatedly editing the hour without identifying the setting can make the problem harder to follow.
A one-off calendar download is not always an updating invitation. Our calendar-download guide explains the difference between keeping a snapshot and following later changes. Use the organizer’s supported invitation route when people need updates.
Allow for travel and repeating meetings
Decide what should stay fixed for a repeating call. Is it always at the organizer’s usual local hour, or is it meant to track another location? When regions change their clocks on different dates, some participants may temporarily see a different local hour.
Open a few future occurrences, particularly around known seasonal clock changes, rather than checking only the first one. Confirm the intended pattern with the group. For a long-running international meeting, review inconvenient periods and agree whether to rotate the burden.
Apple’s iPhone Calendar guidance distinguishes scheduling an event in a particular zone from changing which zone the calendar displays. If you travel, check that display setting before assuming the organizer moved the meeting.
A device with an incorrect date or time zone can also confuse the display. Use the supported settings for the device you own. On a managed work device, ask the administrator when you cannot change the relevant setting.
A fictional call between travelling relatives
Imagine a fictional family arranging a call while one relative is travelling. They initially agree “Sunday evening”, but that description refers to different local periods. They stop and confirm the traveller’s city, the full date and a comfortable local period for everyone.
One person creates a 30-minute event using the intended city zone. Each relative opens the invitation in their own calendar and replies with the local date and start time they see. No one invents a permanent hour difference between the two countries.
When the traveller changes plans, the organizer updates the existing event and asks everyone to check again. The family keeps one current invitation rather than making several separate copies with slightly different clock times.
Keep changes and preparation easy to follow
If an invitation update does not arrive, compare the organizer’s current event with the attendee’s version. Our invitation-update guide explains why changing the appointment and deleting a personal copy are different actions. Keep the joining details in the current event.
Before sharing your screen during the call, use our privacy preparation checklist for visible files and notifications. Your immediate next step is simpler: send one clearly dated invitation and confirm the local display with the people attending.
Sources and verification
Editorial review 2026-10-18. Source check dates are recorded separately. Notes describe what each source supports and its limits.
View sources
- Google: Use Calendar in different time zonesChecked Events can have selected time zones; additional zones can be displayed; changing regional rules can affect existing events.
Limits: No real city offset is asserted; calendar conversion still depends on correct settings and current rules. - Microsoft: Manage time zone settings in OutlookChecked Outlook stores calendar meeting times using UTC and displays them at local times; zone-display settings vary by version.
Limits: Outlook documentation is an example, not a guarantee about every receiving app or imported snapshot. - Apple: Schedule or display events in a different time zone on iPhoneChecked Event time-zone selection and display-zone behaviour are separate settings.
Limits: Instructions depend on current iPhone software and connected calendar accounts.