Time zone scheduling and daylight saving

Short answer: Understand local display, organizer zones, and seasonal changes. Begin with “Set the organizer's base zone using a city-based IANA identifier.” and verify the result through the public participant path.

Before you change the setup

Identify the exact organizer, event type, public link, and time zone involved before editing anything. Save the current behavior or take a screenshot so the test has a reliable before-and-after comparison.

How to complete this task

Set the organizer's base zone using a city-based IANA identifier.Start with the intended outcome and the record that controls it.
Compare the same slot in the organizer and invitee zones.Review every related setting before saving so one rule does not mask another.
Test dates on both sides of the next daylight-saving transition.Keep private data and guest-facing information clearly separated.
Write the zone beside any time repeated outside the scheduling page.Complete the same path an external participant will use.

Verify the participant result

Run one successful case and one edge case. Confirm the public title, local time, available choices, duration, location, confirmation, calendar file, and private management path as applicable. Then check the organizer view and any email delivery record. A saved setting is not proof that the scheduling lifecycle worked.

Troubleshoot time zone scheduling

These are the failures reported most often for this specific task, with the cause that explains each one.

The invitee saw a time an hour off.

This is nearly always a daylight-saving boundary. Test a date on each side of the next transition before publishing recurring times.

Which time zone does the poll use?

The organizer's stated zone, for every viewer. Restate it in the meeting title whenever participants are in different regions.

A city abbreviation caused confusion.

Use full IANA identifiers such as Europe/Helsinki rather than CET or EST. Abbreviations are ambiguous and change with the season.

Related Meetin.gs help

Return to the Meetin.gs Help Center for the adjacent configuration guide, or send the exact event code and expected result when the documented checks do not explain the behavior.

Time zone scheduling and daylight saving acceptance checklist

Use the following evidence map while completing this specific task. It ties each action to an observable result so another person can repeat the setup or diagnose it without guessing.

1. Set the organizer's base zone using a city-based IANA identifier.

Write down the intended result, the organizer or account that owns it, and the exact event type or public link in scope. This prevents a correct change from being applied to the wrong record.

2. Compare the same slot in the organizer and invitee zones.

Inspect the related rules and dependencies before saving. Record the previous value and the new value, including the time zone, provider account, or team owner when one controls the outcome.

3. Test dates on both sides of the next daylight-saving transition.

Review what an invitee can see and what remains private. Keep only the context needed to complete the meeting task, and make the fallback understandable when information is missing.

4. Write the zone beside any time repeated outside the scheduling page.

Complete this step from a signed-out participant session. Preserve the resulting URL or event code, displayed state, message, calendar output, and any provider response needed to prove the task worked.

Evidence type	What to record
Controlling input	The account, event type, setting, public link, and time zone used in the test.
Participant result	The exact choices, context, confirmation, or error visible while signed out.
Lifecycle result	What changes after confirmation, finalization, cancellation, reschedule, or retry.
Failure boundary	The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.
Owner	The person responsible for correcting the setting, provider connection, content, or customer communication.

Evidence type

What to record

Controlling input

The account, event type, setting, public link, and time zone used in the test.

Participant result

The exact choices, context, confirmation, or error visible while signed out.

Lifecycle result

What changes after confirmation, finalization, cancellation, reschedule, or retry.

Failure boundary

The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.

Owner

The person responsible for correcting the setting, provider connection, content, or customer communication.

RELATED CAPABILITY

Customizable availability

Control working hours, booking windows, buffers, daily limits, minimum notice, and date-specific overrides. This page explains customizable availability requirements. Confirm production availability before depending on this capability.

Review scope

Time zone scheduling and daylight saving: frequently asked questions

Short answers to the questions organizers ask most about time zone scheduling.

Which time zone do invitees see?

A booking page presents times in a single stated reference, and a poll uses the organizer's stated zone. Automatic per-viewer conversion is not part of the current core, so state the zone in the meeting title when the group spans regions.

How do I avoid daylight-saving mistakes?

Use full IANA identifiers such as Europe/Helsinki rather than CET, and test a date on each side of the next transition before publishing recurring times.

Why is a meeting suddenly an hour off?

Northern and southern hemisphere transitions happen weeks apart, so a fixed offset that worked in September can break in November. Store a zone, never an offset.

What is the safest way to write a time in an email?

Include the zone every time: '14:00 Europe/Helsinki (12:00 UTC)'. Never let a bare clock time travel between regions.