Schedule a Google Calendar Event Across Time Zones and Verify the Time

First, check the date and offset

On January 21, New York observes UTC−5 and Los Angeles UTC−8. Therefore 11:00 AM New York and 8:00 AM Los Angeles are the same 16:00 UTC instant. The meeting lasts 30 minutes in every zone. Time-zone offsets can differ on other dates; use the date of the real meeting when repeating this workflow.

Swipe or scroll sideways to see every table column →

Create a private practice event

1. On a desktop browser, open Google Calendar and choose Create → Event → More options. Google's time-zone help describes this full event editor path.
2. Beside the event time, select Time zone. Search for New York and choose the city/time zone for the event. Do not change your calendar's primary time zone for this test.
3. Set the date to Thursday, January 21, 2027, the start to 11:00 AM, and the end to 11:30 AM. Name it Workshop handoff - fictional practice.
4. Leave Guests empty. Save the event only to your own calendar. This avoids sending an invitation while the time is unchecked.
5. Reopen the event and confirm its date, start, end, and New York event zone. Google's Calendar settings can show additional time zones or a world clock; choose Los Angeles for a second readout. The expected Los Angeles start is 8:00 AM. In our private practice, Calendar displayed the saved event at 5:00–5:30 PM in Prague while the editor retained 11:00–11:30 AM New York. That is consistent with 16:00–16:30 UTC on this date. We did not invite or inspect a Los Angeles recipient.
6. Compare against the table above. The downloadable ICS records 16:00–16:30 UTC as an independent reference. It does not prove what a recipient's account displays.

Pass check: the saved practice event represents 11:00–11:30 AM New York, 8:00–8:30 AM Los Angeles, and 16:00–16:30 UTC on the same date. A three-hour difference in the wrong direction usually means the event was entered in the calendar's current display zone instead of the intended New York event zone.

Common mistakes

• Changing the primary calendar zone: This affects how a calendar is displayed. Use the event-specific Time zone control for one meeting.
• Entering 11 AM while the active zone is Los Angeles: That describes 2 PM in New York on this date, three hours later than the intended handoff.
• Using an all-day event: An all-day event is not a 30-minute meeting with a specific instant.
• Checking only the abbreviation: Verify the city and the event date. Daylight-saving transitions and future rule changes can alter offsets.
• Adding guests before checking: Keep the practice event private; for a real meeting, inspect the event and at least one second zone before inviting people.

Sources and evidence

Reviewed 9 October 2026: Google Calendar Help on using different time zones and creating events. The fictional January 2027 conversion was independently calculated in the practice builder, and the ICS encodes the UTC instant. A private, no-guest practice event was created in an English Calendar UI. Its saved editor showed 11:00–11:30 AM New York, and the account's Prague calendar view showed 5:00–5:30 PM. The companion video includes genuine English Calendar captures of that editor and saved-event detail; other panels are illustrative diagrams. No invited-recipient display was tested. The time-zone selector's generic offset label showed a current-date offset, so check the event date and saved clock reading rather than trusting that label alone.