WORK SYSTEMS
Set up three time zones, check the revised rollout, and use a worked New York–London–Los Angeles schedule to handle October’s daylight-saving mismatch.
Add a third display time zone if you regularly coordinate across three regions. Then decide which city’s local time your recurring meeting should preserve. The extra column helps you see the answer; it cannot choose that rule for you. In 2026, London changes clocks on October 25 and New York on November 1, so their usual time difference temporarily shrinks by an hour.
Google announced a third time-zone column for Calendar on the web on September 25. It applies to Day, Week, custom multi-day and Find a Time views. The feature is intended for Workspace customers, Workspace Individual subscribers and personal Google accounts.
The October 1 update extends Rapid Release completion to October 13 and gives Scheduled Release an October 18–22 window. A lower rollout paragraph still says October 19. Those statements differ; this guide follows the dated update and does not promise an exact account-level arrival day. If the third selector is absent today, keep your existing display and use the dated worksheet below until it appears.
On the desktop website, open Settings, then General and Time zone. Enable additional time zones; choose the second zone and, when available, the third. Search by city so you choose the location’s rules rather than assuming an offset stays fixed. Use short labels such as NYC, LON and LA.
The display zone is how you read the calendar; the event zone is the location used when setting an appointment. Google shows invited people the event in their own local time. Before editing a recurring series, write down whether the agreement is “11:00 New York” or “16:00 London.” Those are different promises around a clock change.
This is a hypothetical 30-minute weekly meeting, anchored at 11:00 in New York. Method & Miles calculated each occurrence separately using America/New_York, Europe/London and America/Los_Angeles. UK and US transition dates were checked against GOV.UK and NIST. These are computed examples, not a hands-on test of a Calendar account.
| Monday | New York | London | Los Angeles |
|---|---|---|---|
| October 19, 2026 | 11:00–11:30 EDT | 16:00–16:30 BST | 08:00–08:30 PDT |
| October 26, 2026 | 11:00–11:30 EDT | 15:00–15:30 GMT | 08:00–08:30 PDT |
| November 2, 2026 | 11:00–11:30 EST | 16:00–16:30 GMT | 08:00–08:30 PST |
On October 26, copying the usual “16:00 London” into a separate appointment would produce 12:00 New York, an hour later than this agreement. The correct conversion for the agreed New York anchor is 15:00 London that week. The US dates here concern these two cities, not every US location.
Our decision matrix separates a local-time promise from a convenient display. Choose once with participants, then check the affected occurrences rather than shifting the whole series to make the columns look familiar.
| Constraint | Anchor to preserve | What to accept or change |
|---|---|---|
| A New York client needs the same local slot | New York local time | London moves one hour earlier in the gap week |
| A London participant has a fixed afternoon window | London local time | US attendees move one hour later in the gap week |
| All attendees have flexible windows | An explicitly agreed city | Check each local start and end before confirming |
| No slot fits every participant’s window | No permanent anchor yet | Negotiate an exception or replace that occurrence with an asynchronous decision |
For a completed comparison, assume New York accepts 10:00–16:00, London 09:00–17:00 and Los Angeles 08:00–16:00. These are illustrative availability windows, not measured working hours. On October 26, 09:00 New York fails because Los Angeles would be 06:00. An 11:00 start is 15:00 London and 08:00 Los Angeles, so the full 30 minutes fits all three stated windows. A 13:00 New York start reaches London at 17:00 and fails once the meeting’s duration is included.
That gives you a concrete selection rule: test the end time as well as the start, then preserve the city tied to the least flexible real commitment. A good-looking blank slot is only a candidate until every attendee’s constraint is checked.
The following invitation text is filled in for the hypothetical October 26 occurrence. Replace the example people and constraints with your own; do not reuse its conversions for another date or city.
Project handoff — Monday, October 26, 2026
Duration: 30 minutes. Anchor: 11:00 America/New_York (EDT). Local times: London 15:00 GMT; Los Angeles 08:00 PDT. Goal: agree the owner and deadline for the launch handoff. Please check this specific occurrence in your calendar. London’s start is one hour earlier than October 19; the New York agreement is unchanged. If this falls outside your availability, reply with a workable local window before we confirm.
For the November 2 occurrence, keep the New York start at 11:00 but update the note to EST, London 16:00 GMT and Los Angeles 08:00 PST. Writing an abbreviation from memory is less useful than checking the actual dated event. This completed note makes the chosen anchor and temporary exception visible to people who never open a three-column view.
Review October 19, October 26 and November 2 side by side. Confirm the event’s intended zone, each participant’s local date, and both start and end. Ask a participant in the other region to confirm the same occurrence if the meeting is important. If the third column is unavailable, the two-zone display plus the worksheet can still support the decision.
Separate a mistaken display setting from a genuinely wrong appointment before making changes. If only the gap-week occurrence needs a different time, agree the exception and review the scope of the edit before saving. A blanket series shift can fix one week while moving the rest away from the agreed local anchor.
Use this method for these three cities and dates as written. For another location, especially one with recently changed time rules, calculate again with current local guidance. More visible clocks reduce mental arithmetic; a clear anchor and a dated check prevent the scheduling mistake.
Editorial note: Researched October 5 and rechecked October 6, 2026. Method & Miles developed the decision matrix, calculated the dated examples and wrote the completed invitation. Availability windows and meeting details are hypothetical. We did not test this feature in a signed-in Calendar account. The hero is an AI-assisted editorial illustration, not a product screenshot. No sponsorship or affiliate links.