DEV Community

Cover image for Why Your JavaScript Meeting Scheduler Breaks During Daylight Saving Time
ToolZenhub
ToolZenhub

Posted on

Why Your JavaScript Meeting Scheduler Breaks During Daylight Saving Time

A meeting works perfectly for months.

Your team in India joins at 7:30 PM. Your colleague in New York joins at 10:00 AM. Everyone is happy.

Then daylight saving time changes.

Suddenly, somebody joins an hour late.

Nobody changed the meeting invitation. Nobody deliberately modified the schedule.

So what happened?

The problem is often an incorrect assumption about time zones.

Let's understand how these bugs happen in JavaScript and how to design more reliable meeting scheduling.

1. The hidden problem with UTC offsets

Imagine your application schedules a meeting between India and New York.

You know:

  • India uses UTC+05:30.
  • New York sometimes uses UTC-04:00.
  • New York also uses UTC-05:00.

The crucial word is sometimes.

India doesn't currently observe daylight saving time.

New York does.

On October 28, 2026:

New York: 10:00 AM EDT
India:    7:30 PM IST
Enter fullscreen mode Exit fullscreen mode

But on November 18, 2026:

New York: 10:00 AM EST
India:    8:30 PM IST
Enter fullscreen mode Exit fullscreen mode

The New York meeting stays at 10:00 AM local time.

The corresponding time in India changes by one hour.

This happens because New York changes its UTC offset.

A scheduling application that assumes New York is always UTC-04:00 will eventually produce the wrong result.

2. A UTC offset is not a time zone

Consider these values:

UTC+05:30
UTC-04:00
UTC-05:00
Enter fullscreen mode Exit fullscreen mode

They describe offsets from UTC.

They do not fully describe a location's historical and future time-zone rules.

Now consider:

Asia/Kolkata
America/New_York
Europe/London
Enter fullscreen mode Exit fullscreen mode

These are IANA time-zone identifiers.

They allow applications to apply the appropriate time-zone rules for a particular date.

For example:

const date = new Date(
  "2026-11-18T15:00:00Z"
);

const result = new Intl.DateTimeFormat(
  "en-US",
  {
    timeZone: "America/New_York",
    hour: "2-digit",
    minute: "2-digit",
    hour12: true
  }
).format(date);

console.log(result);
Enter fullscreen mode Exit fullscreen mode

Output:

10:00 AM
Enter fullscreen mode Exit fullscreen mode

The date matters.

If you use the same time zone for a summer date, its UTC offset may be different.

Practical rule

For a real location, prefer an IANA time-zone identifier over a permanently hardcoded offset.

3. The JavaScript Date constructor can be misleading

Consider:

const meeting = new Date(
  "2026-11-18T10:00:00"
);
Enter fullscreen mode Exit fullscreen mode

What instant does this represent?

For a date-time string with no UTC offset, JavaScript interprets it using the runtime's local time zone.

A developer running the application in India may get a different instant from someone running the same code in New York.

That makes this dangerous for globally shared meeting schedules.

Compare it with:

const meeting = new Date(
  "2026-11-18T15:00:00Z"
);
Enter fullscreen mode Exit fullscreen mode

The Z explicitly indicates UTC.

This identifies an unambiguous instant.

You can then display the same instant in different time zones.

function displayTime(date, timeZone) {
  return new Intl.DateTimeFormat(
    "en-US",
    {
      timeZone,
      dateStyle: "medium",
      timeStyle: "short"
    }
  ).format(date);
}

const meeting = new Date(
  "2026-11-18T15:00:00Z"
);

console.log(
  displayTime(meeting, "America/New_York")
);

console.log(
  displayTime(meeting, "Asia/Kolkata")
);
Enter fullscreen mode Exit fullscreen mode

The results correspond to:

New York: Nov 18, 2026, 10:00 AM
Kolkata:  Nov 18, 2026, 8:30 PM
Enter fullscreen mode Exit fullscreen mode

The underlying instant remains identical.

4. What happens when a local time does not exist?

Daylight saving time creates a more surprising problem.

In New York, clocks move forward on March 8, 2026.

The clock jumps from:

01:59:59 AM
Enter fullscreen mode Exit fullscreen mode

to:

03:00:00 AM
Enter fullscreen mode Exit fullscreen mode

That means this local time doesn't exist:

2026-03-08 02:30 AM
America/New_York
Enter fullscreen mode Exit fullscreen mode

If someone enters this time into a scheduling form, what should your application do?

Possible business policies include:

  • Reject the invalid time.
  • Ask the user to choose a valid time.
  • Offer nearby valid times.
  • Apply an explicitly documented adjustment policy.

What you shouldn't do is silently assume that the entered time represents a valid instant.

A robust scheduler should clearly communicate that the requested local time doesn't exist.

5. What happens when a local time occurs twice?

The opposite problem happens when clocks move backward.

In New York, daylight saving time ends on November 1, 2026.

Consider:

2026-11-01 01:30 AM
America/New_York
Enter fullscreen mode Exit fullscreen mode

This local time occurs twice.

The first occurrence represents:

2026-11-01T05:30:00Z
Enter fullscreen mode Exit fullscreen mode

The second represents:

2026-11-01T06:30:00Z
Enter fullscreen mode Exit fullscreen mode

Both display as 1:30 AM in New York.

But they are different instants, separated by one hour.

If your application stores only:

{
  "date": "2026-11-01",
  "time": "01:30",
  "timeZone": "America/New_York"
}
Enter fullscreen mode Exit fullscreen mode

It has not identified a unique instant.

Your scheduler needs a policy for choosing between the two occurrences.

For an important appointment, asking the user is often better than guessing.

6. Converting an instant safely with JavaScript

For an existing, unambiguous timestamp, JavaScript provides a useful built-in tool:

Intl.DateTimeFormat.

Here's a reusable function:

function formatInTimeZone(
  isoTimestamp,
  timeZone
) {
  const date = new Date(isoTimestamp);

  if (Number.isNaN(date.getTime())) {
    throw new Error("Invalid timestamp");
  }

  const formatter = new Intl.DateTimeFormat(
    "en-US",
    {
      timeZone,
      year: "numeric",
      month: "short",
      day: "2-digit",
      hour: "2-digit",
      minute: "2-digit",
      hour12: false,
      hourCycle: "h23"
    }
  );

  return formatter.format(date);
}

const meeting = "2026-11-18T15:00:00Z";

console.log(
  formatInTimeZone(
    meeting,
    "America/New_York"
  )
);

console.log(
  formatInTimeZone(
    meeting,
    "Asia/Kolkata"
  )
);
Enter fullscreen mode Exit fullscreen mode

This function converts an already known instant into a local display.

It does not solve the reverse problem of interpreting an ambiguous local time.

That distinction is important.

Two different scheduling operations

Operation A: Instant to local time

2026-11-18T15:00:00Z
      ↓
10:00 AM in New York
Enter fullscreen mode Exit fullscreen mode

Operation B: Local time to instant

November 1, 2026
1:30 AM in New York
      ↓
Which occurrence?
Enter fullscreen mode Exit fullscreen mode

Operation B requires time-zone rules and an explicit ambiguity policy.

7. A practical way to plan international meetings

Suppose you're coordinating a meeting involving:

  • Hyderabad, India
  • London, United Kingdom
  • New York, United States

You need to identify a time that works reasonably well for everyone.

The challenge isn't merely converting one time.

You also need to consider each person's preferred working hours.

For example:

India:    9:00 AM – 9:00 PM
London:   9:00 AM – 6:00 PM
New York: 9:00 AM – 6:00 PM
Enter fullscreen mode Exit fullscreen mode

These are illustrative preferences, not universal working hours.

A meeting planner needs to determine whether the participants' available windows overlap.

And it needs to do so for the actual meeting date, because offsets can change throughout the year.

This is where a dedicated meeting-time planner can reduce repetitive calculations.

8. Demonstrating a browser-based time-zone planner

I maintain ToolZenHub, which provides practical browser-based utilities.

Its Time Zone Converter & Meeting Planner is available here:

https://toolzenhub.in/tools/time-zone-converter/

Let's use it for our example.

Step 1: Select the meeting date

Choose:

18 November 2026
Enter fullscreen mode Exit fullscreen mode

Step 2: Select the source time zone

Search for:

America/New_York
Enter fullscreen mode Exit fullscreen mode

Enter:

10:00 AM
Enter fullscreen mode Exit fullscreen mode

Step 3: Add other time zones

Add:

Asia/Kolkata
Europe/London
Enter fullscreen mode Exit fullscreen mode

The tool supports the source time zone plus up to five additional zones.

Step 4: Review the conversions

For this example, the corresponding times are:

New York: 10:00 AM
London:   3:00 PM
India:    8:30 PM
Enter fullscreen mode Exit fullscreen mode

All three represent the same instant.

Step 5: Find a better meeting time

Open:

Find a time that works for everyone

Set each location's preferred hours.

Choose a meeting length.

The tool evaluates candidate start times in 15-minute steps within the source time zone's selected calendar day.

It then identifies times that fall within everyone's preferred hours.

This reduces the need to manually compare multiple calendars or calculate offset differences.

Step 6: Share the conversion

The tool's page URL preserves the selected date, time and time zones.

That lets you share the conversion with other participants.

It does not create calendar invitations or book meetings automatically.

9. What about daylight-saving ambiguity?

A useful scheduling tool should handle unusual local times explicitly.

ToolZenHub's converter distinguishes two important cases.

Nonexistent local time

For a skipped hour during a spring transition, it explains that the requested time does not exist and shows nearby valid times.

Ambiguous local time

For a repeated hour during an autumn transition, it displays both possible instants and asks which one you mean.

This is better than quietly choosing one and potentially scheduling a meeting an hour away from what the user intended.

These cases are easy to miss during manual conversion.

They are also worth including in automated tests for any scheduling application.

10. How to test DST behavior in an application

Suppose you're testing a meeting scheduler.

Don't test only ordinary dates.

Include time-zone boundaries and unusual transitions.

A useful test matrix might look like this:

Scenario What to verify
Normal winter date Correct standard-time offset
Normal summer date Correct daylight-time offset
Spring skipped time Invalid time handled explicitly
Autumn repeated time Ambiguity handled explicitly
India to New York Half-hour offset respected
Multiple locations Same instant shown consistently
Invalid time-zone identifier Clear validation error
Scheduled event near midnight Calendar date converted correctly

For example, you can verify two different instants within the repeated hour:

const first = new Date(
  "2026-11-01T05:30:00Z"
);

const second = new Date(
  "2026-11-01T06:30:00Z"
);

const formatter = new Intl.DateTimeFormat(
  "en-US",
  {
    timeZone: "America/New_York",
    hour: "2-digit",
    minute: "2-digit",
    hour12: false
  }
);

console.log(formatter.format(first));
console.log(formatter.format(second));
Enter fullscreen mode Exit fullscreen mode

Both display:

01:30
01:30
Enter fullscreen mode Exit fullscreen mode

This demonstrates why displaying only the local clock time is insufficient.

To distinguish the instants, include the appropriate UTC offset or zone abbreviation.

For automated tests, use a runtime with up-to-date time-zone data.

11. Common implementation mistakes

Here are some mistakes worth avoiding.

Hardcoding offsets

// Unsafe as a general New York conversion
const newYorkOffset = -4;
Enter fullscreen mode Exit fullscreen mode

New York's offset changes during the year.

Use time-zone rules instead.

Mixing local time with UTC

new Date("2026-11-18T10:00:00");
Enter fullscreen mode Exit fullscreen mode

Without an offset, this represents local time in the executing environment.

Do not assume it means UTC.

Using abbreviations as unique identifiers

IST
CST
BST
Enter fullscreen mode Exit fullscreen mode

These abbreviations can be ambiguous.

Prefer identifiers such as:

Asia/Kolkata
America/Chicago
Europe/London
Enter fullscreen mode Exit fullscreen mode

Assuming every offset is a whole hour

India uses a half-hour offset.

Other locations have offsets that include 30 or 45 minutes.

Do not build time-zone logic that assumes whole-hour differences.

Assuming a calendar day is always 24 hours

During daylight-saving transitions, a local calendar day can contain a different number of elapsed hours.

That matters when calculating durations.

12. A checklist for reliable meeting scheduling

Before building or testing an international scheduler, ask:

  1. Are you using IANA time-zone identifiers?
  2. Does every scheduled instant have an unambiguous representation?
  3. Do local times require DST disambiguation?
  4. Are nonexistent local times rejected or handled explicitly?
  5. Are repeated local times handled according to a clear policy?
  6. Are UTC offsets calculated for the actual date?
  7. Are half-hour and 45-minute offsets supported?
  8. Are time-zone conversion and meeting availability treated as separate problems?
  9. Are results tested near date boundaries and DST transitions?
  10. Can users clearly understand the final meeting time in their own zone?

Final thoughts

International scheduling problems often start with a simple assumption:

"New York is always a fixed number of hours behind India."

It isn't.

A reliable application needs to understand dates, time zones, daylight-saving rules, and ambiguous local times.

For developers, Date and Intl.DateTimeFormat can help display known instants correctly.

For interpreting complex local times, a scheduling system needs additional time-zone-aware logic and explicit policies.

And when you simply need to coordinate a meeting across several locations, a browser-based planner can reduce repetitive conversion work.

I maintain the following free tool for this purpose:

https://toolzenhub.in/tools/time-zone-converter/

It can help compare multiple time zones, explain daylight-saving edge cases and identify overlapping meeting hours.

The objective is straightforward: spend less time calculating time differences and more time coordinating the work that matters.


References

Disclosure: I maintain ToolZenHub, the website referenced in this article. This draft was generated with AI assistance and requires technical and editorial review before publication.

Top comments (0)