Try the example, then check the result.
Download the fictional material and follow the steps below. The video uses English illustrative diagrams; it does not present a live app recording. Product controls may vary by version.
Check the answer before applying the method to your own data. How we review guides ↗
Watch the complete lesson.
The video uses English illustrative diagrams; it does not present a live app recording. English captions. Product menus may differ in your account.
Quick answer. Check Calendar Settings for the primary time zone, then open the event editor and inspect that event's time zone. Use named zones and compare the displayed event time with its edit details; a display-zone change does not by itself move the event to a new instant.
Use the fictional practice file and independent answer check. Work in a permitted practice copy.
Before you start. Use the fictional no-guest event in the practice sheet. Work on a disposable event or a copy; do not alter a shared meeting to test this. The example date is 12 November 2026, away from a daylight-saving transition.
1. Record the time you expected
In the practice sheet, the fictional Workshop prep event is intended for 9:00 a.m. in America/New_York on 12 November 2026. Write down the calendar view's displayed time before changing anything. Keep the named zone with the time; an isolated clock reading cannot diagnose the mismatch.
Checkpoint: Intended event time and current display are recorded separately.
2. Inspect the calendar's primary zone
Open Google Calendar Settings and find the primary time zone in the Time zone area. Read the current named zone. If the calendar is showing events in America/Los_Angeles, the same event instant should display at 6:00 a.m. on this example date. Do not assume the offset stays fixed throughout the year.
Checkpoint: The primary display zone is known by name.
3. Inspect the event's own zone
Open the fictional event for editing and inspect the time and time-zone controls. Confirm that the intended event time is 9:00 a.m. in America/New_York. If the event itself has a different zone, decide whether the event was entered incorrectly before changing the calendar display. The two settings solve different problems.
Checkpoint: The event's zone and intended clock time are recorded.
4. Change only the setting that is wrong
If the event time and zone are correct but the grid is being viewed in the wrong zone, change the primary Calendar time zone to the intended display zone. If the event itself has the wrong zone, correct its time and zone in the event editor instead. Save only the intended change and avoid adding guests to this practice event.
Checkpoint: The changed setting matches the diagnosed cause.
5. Compare the grid and editor
Return to the calendar grid and open the event details again. For the practice case, a New York display should show 9:00 a.m. while a Los Angeles display should show 6:00 a.m. on 12 November 2026. Confirm that the event editor still describes the intended time and zone, rather than judging from one grid label alone.
Checkpoint: The event and display-zone readings agree for the example date.
Verify the result
For 12 November 2026, 9:00 a.m. America/New_York and 6:00 a.m. America/Los_Angeles represent the same instant. The named event zone and named primary calendar zone explain which time the grid displays. This arithmetic is the expected practice answer; the live result must be checked in your Calendar session.
If it still does not work
If the grid still appears wrong, check whether a secondary time zone is also shown, whether you are editing the intended event rather than another copy, and whether the event was entered with a different named zone. Avoid a daylight-saving transition date while diagnosing. Do not infer what an invited guest sees from your own display.
Official sources
- Change the Google Calendar time zone (checked 1 November 2026).
- Create an event in another time zone (checked 1 November 2026).
The branded video panels are illustrative diagrams unless a panel is explicitly marked as an actual app capture. The current controls and result must be checked in your own account; an illustration is not proof of an observed live result.
Practice downloads.
The exercise files contain invented information. Save a local copy before editing.