An interview invitation that says 10 a.m. can look wonderfully definite until the candidate and organizer are in different places. A calendar may display a local time while an email repeats the organizer's original wording. Before planning the morning around either number, connect the full date, the intended time zone and the actual event. The useful result is one confirmed appointment represented consistently in the message, calendar and candidate's plans.

Hypothetical referenceDate and named zoneInterpretation
Organizer-confirmed appointment15 January 2026,10:00 Europe/LondonThe intended instant in the example
Candidate’s corresponding appointment15 January 2026,18:00 Asia/Hong_KongSame instant, date-specific conversion
Manual note saying only10:00Zone unspecifiedInsufficient evidence; clarify before setting a reminder

Establish what the organizer intended

Read the invitation for the complete calendar date, time and time zone. If it gives only an abbreviation or a number whose meaning you cannot establish, ask the organizer to confirm. Use the actual named zone or location they intend rather than guessing from the company's headquarters, an email signature or the place where a previous interviewer worked.

A short clarification can be specific and courteous: please confirm the full date and the time zone intended for the interview, so that I can check my local calendar display. That question is about the appointment, not a request for the organizer to troubleshoot every setting on the candidate's device. It is much easier to answer before the interview day than after two people have planned for different moments.

Distinguish an event from a number you typed

An event invitation carrying time-zone information and a manually entered note saying 10 a.m. are not interchangeable evidence. If you created your own calendar entry from an email, check which zone the entry uses. Do not assume that typing the organizer's number into your local calendar preserves the intended appointment.

Google Calendar's computer help explains that events can be created with a specified time zone and that users see events in local time. It also provides an event-level time-zone setting. That makes it important to compare the actual event and its intended zone, rather than adjusting the displayed number until it resembles the wording in an email. Changing a display or manually recreating an entry can leave the original ambiguity unresolved.

Check the full date on your side

When locations differ, confirm the date as well as the hour shown to you. Read the complete local appointment rather than lifting a time from a notification preview. If the result seems surprising, return to the confirmed intended zone and actual event details before making a manual correction.

Use a calendar or time-zone tool that handles the relevant date, and avoid relying on a remembered fixed difference between two cities. Google Calendar describes its handling of daylight saving time through UTC and notes that time-zone changes can sometimes affect events created before it knew of the change. A calendar display is useful, but a discrepancy still deserves clarification rather than a guess about which number must be right.

Recheck if you will be somewhere else

The candidate's physical location on interview day may differ from the one used while arranging it. If travel is involved, review how the calendar will display the event in the place where you expect to join. Google Calendar offers primary-zone settings and an option to ask about updating the primary zone when traveling; the actual settings in use need attention rather than an assumption that every device changes in the same way.

This is also a practical moment to identify the intended joining location and ensure the meeting link belongs to the confirmed appointment. If the organizer sends a replacement event, distinguish it from an older entry instead of retaining two similar reminders without knowing which is current. A changed meeting time should be confirmed as a changed appointment, not inferred from a notification whose context is unclear.

Work through one explicitly hypothetical invitation

Imagine an organizer confirms an interview for 15 January 2026 at 10:00 in Europe/London, while the candidate will join from Hong Kong using Asia/Hong_Kong. This is an invented appointment. For that date, the same instant corresponds to 18:00 on 15 January in Hong Kong. UK government clock-change information and the Hong Kong Observatory’s time definition support the date-specific interpretation; a local time-zone conversion was also checked. No invitation was sent and no calendar display was tested.

With Google Calendar’s documented event-zone behavior, the candidate should inspect an invitation carrying Europe/London as its event zone and compare the corresponding Hong Kong display with that confirmed appointment. Typing 10:00 into an Asia/Hong_Kong entry would describe a different moment. The useful final note keeps both full dates, both named zones and the joining link together. If the actual invitation disagrees, ask the organizer; do not shift its time until it merely looks familiar. Recheck a changed date rather than preserving this example’s eight-hour difference.

Let the reminder support the confirmed appointment

Once the date and zone are settled, check the reminder against that event. A personal preparation block can be added separately so that its timing does not obscure the actual start. Keep the organizer's confirmation accessible through the normal correspondence route in case an inconsistency needs to be explained.

Sources & further reading

Published sources for the details and examples discussed in this story.