Time Zone Meeting Planner: Avoid Daylight Saving Time Mistakes

Time zone mistakes usually happen because people use fixed offsets like UTC+8 instead of real city-based time zones.

Offsets are useful for a moment in time. Meeting planning needs rules, and those rules can change with daylight saving time.

Use Cities, Not Just Offsets

Prefer time zones like:

• America/New_York
• Europe/London
• Asia/Shanghai
• Asia/Tokyo
• Australia/Sydney

These IANA time zone names carry local daylight saving rules. A fixed offset such as UTC-5 does not tell you whether New York is currently on standard time or daylight time.

Check the Date

The same cities can have different offsets depending on the month. A meeting that works in January may shift by one hour in March or November.

Always convert the exact date and time, not just the current offset.

Share the Source Time

When inviting a distributed team, write:

Tuesday, 10:00 AM America/New_York
London: 3:00 PM
Singapore: 11:00 PM

One source time plus converted attendee times reduces ambiguity.

Daylight Saving Time Is the Trap

Daylight saving transitions do not happen on the same date everywhere. The United States, Europe, Australia, and parts of South America may shift clocks in different weeks, while places such as Singapore, China, and Japan do not use daylight saving time.

That means a recurring meeting can change for some attendees even if the organizer never edits the calendar invite. A meeting that is comfortable for New York and London in February may become awkward for one side after March transitions.

Meeting Checklist

Before sending an invite across regions, check:

| Check | Why it matters | | ------------------ | ----------------------------------------------- | | Exact date | Offsets can change by month. | | City time zone | America/New_York is safer than UTC-5. | | Attendee local day | A late evening meeting can become the next day. | | Recurring schedule | DST can shift future instances. |

For one-off meetings, include the converted local times in the message body. For recurring meetings, check at least one future date after the next daylight saving transition.

Quick Answer

For cross-time-zone meetings, choose the meeting date, use IANA city time zones, convert for each attendee, and double-check daylight saving changes. Avoid planning with fixed UTC offsets alone.

Useful reference:

• MDN: Intl.DateTimeFormat