Skip to content

Time zone scheduling

Team presets

Start from common remote-team patterns, then tune cities and date.

09:00–18:00 local workday · weekends flagged

Decision command center

From timezone conversion to a defensible meeting decision: recommended slot, tradeoff, poll, memo, calendar handoff.

RecommendAlignRotateCommit

01 · Recommend

Score every candidate by overlap, local work hours, and visible burden.

02 · Explain

Show who pays the cost before the poll starts.

03 · Mitigate

Check DST and rotate recurring burden instead of repeating pain.

04 · Commit

Copy the poll, memo, or calendar invite with the rationale intact.

Best fair window

Thu, May 28, 11:00

Score 88/100Recommended

Why this window: New York City is starting soon at 07:00

Disadvantaged: New York City · Starting soon · 07:00

Inside work hours

1/2

Inconvenient cities

1

Burden

low team burden

1 of 2 cities are inside 09:00–18:00. 1 city carries inconvenience.

Decision packet

Copy a decision-ready packet: poll language to align the team, memo language to record the call, and a calendar handoff that preserves the fairness rationale.

CommitCalendar inviteFairness note included
Create calendar invite

Fairness timeline

Work hours, off-hours, and the chosen instant for every city.

Work hoursOff hours

Kalaburagi

GMT+5:30

0918
Work hours16:30

New York City

GMT-4

0918
Starting soon07:00

4-week recurring fairness

Who carries the recurring burden?

New York City carries the highest accumulated burden (40 pts / 4 conflicts). Kalaburagi carries the lightest burden.

Total burden

40

Occurrences

4

WeekDecision reasonScore
W1Thu, May 28, 2026 · New York City is starting soon at 07:0088/100
W2Thu, Jun 4, 2026 · New York City is starting soon at 07:0088/100
W3Thu, Jun 11, 2026 · New York City is starting soon at 07:0088/100
W4Thu, Jun 18, 2026 · New York City is starting soon at 07:0088/100

Accumulated by city

Kalaburagi0 pts · 0x
New York City40 pts · 4x

DST / offset watch

No UTC offset changes detected in the next 8 weeks for the selected cities.

Stable offsets

Week 1

KalaburagiGMT+5:30 · 16:30

New York CityGMT-4 · 07:00

Week 2

KalaburagiGMT+5:30 · 16:30

New York CityGMT-4 · 07:00

Week 3

KalaburagiGMT+5:30 · 16:30

New York CityGMT-4 · 07:00

Week 4

KalaburagiGMT+5:30 · 16:30

New York CityGMT-4 · 07:00

Burden rotation plan

Rotate the pain instead of repeating it

This option keeps the heaviest city at 30 pts over 4 weeks, 10 pts less concentrated than the fixed weekly time.

Fixed max

40

Rotated max

30

WeekRotated slotScore
W1Thu, May 28, 2026 16:30 · New York City is starting soon at 07:0088/100
W2Thu, Jun 4, 2026 18:30 · Kalaburagi is evening at 18:3082/100
W3Thu, Jun 11, 2026 16:30 · New York City is starting soon at 07:0088/100
W4Thu, Jun 18, 2026 16:30 · New York City is starting soon at 07:0088/100

Rotated burden by city

Kalaburagi16 pts · 1x
New York City30 pts · 3x

Use this when a fixed weekly slot keeps making the same office pay the night or early-morning cost.

Build rotation-aware invite

Send this fairness context into Calendar Link Builder so the invite note explains the recurring tradeoff.

Build recurring-aware invite
Selected citiesLocal timeWork hours
KalaburagiThu, May 28, 2026 16:30Work hours
New York CityThu, May 28, 2026 07:00Starting soon

Ready from compare

Ready from compare

This planner keeps the compared cities and fixed instant together, then turns them into a scored meeting window and a calendar invite.

Cities carried over

Kalaburagi ↔ New York City

Selected instant

Thu, May 28, 2026 02:30

Asia/Kolkata

Best next window

Thu, May 28, 11:00 · Recommended · Score 88

Why this window: New York City is starting soon at 07:00

Share link

/meeting?at=2026-05-27T21%3A00%3A00.000Z&cities=kalaburagi%2Cnew-york

Create calendar invite

Next full overlap

No full overlap in 48h

Current fit

68/100

Acceptable · moderate team burden

Kalaburagi is night at 02:30

Best candidate windows

09:00–18:00 local workday · weekends flagged

Thu, May 28, 11:00

Recommended · low team burden · 1/2 in work hours

Score 88

New York City is starting soon at 07:00

Disadvantaged: New York City

New York City · Starting soon · 07:00
Create calendar invite

Thu, May 28, 11:30

Recommended · low team burden · 1/2 in work hours

Score 88

New York City is starting soon at 07:30

Disadvantaged: New York City

New York City · Starting soon · 07:30
Create calendar invite

Thu, May 28, 12:00

Recommended · low team burden · 1/2 in work hours

Score 88

New York City is starting soon at 08:00

Disadvantaged: New York City

New York City · Starting soon · 08:00
Create calendar invite

Selected cities

Kalaburagi

Asia/Kolkata

Night

Thu, May 28, 2026 02:30

UTC offset

GMT+5:30

Day relation

base city

Local date

Thu, May 28, 2026

New York City

America/New_York

Work hours

Wed, May 27, 2026 17:00

UTC offset

GMT-4

Day relation

previous day

Local date

Wed, May 27, 2026

Calendar-safe handoff

Planning guide

Need a checklist before inviting the team? Read the timezone meeting planning guide for overlap windows, shared calendar links, and daylight-saving-safe scheduling.

Base timezone

The calendar handoff uses Asia/Kolkata as the base timezone. Keep the IANA zone with the invite so daylight saving changes are recalculated by the calendar, not guessed from a fixed offset.

Invite memo

Copy the meeting text before sending links. It gives attendees the local-time audit trail, offset labels, and work-hour warnings behind the selected instant.

Recurring meetings

For repeats, create the recurrence in your calendar with the same timezone and re-open this planner around DST boundaries to confirm the burden has not shifted unfairly.

Why teams switch

Not a timezone converter. A fair meeting decision engine.

Converters show clocks. Meeting Planner chooses the best window, explains who pays the inconvenience, rotates the burden over time, and hands off a calendar-safe invite.

Fairness + rotation + handoff

1. Fair decision

Pick the window that hurts the group least.

Compare candidate scores, see who falls outside working hours, and stop optimizing for only one office.

2. Recurring fairness

Rotate the pain instead of repeating it.

Plan a 4-week burden rotation so the same city does not keep paying the early-morning or late-night cost.

3. Actionable handoff

Turn the answer into something people can send.

Copy a team poll, share a prefilled link, or build a calendar-safe invite with named time zones and the checked date.

Quick answer

How to plan a fair, calendar-safe meeting across time zones

  1. 1. Choose citiesAdd every participant city or IANA time zone and set the real meeting date.
  2. 2. Compare fair scoreCheck which candidate windows balance normal working hours across the group.
  3. 3. Spot outside hoursSee who would be early, late, or on the wrong day before you confirm the time.
  4. 4. Copy or shareShare a prefilled planner link so teammates can review the same DST-aware view.
  5. 5. Create calendar inviteUse named time zones and the checked date to create a calendar-safe invite.

Scheduling FAQ

Time-zone meeting planner FAQ

How do I find a fair meeting time across time zones?

Choose the cities or IANA time zones, compare the fair score for candidate windows, then pick a time that keeps the burden away from the same participant every week.

What does the fair score show?

The fair score summarizes how well a proposed window fits local working hours across all selected cities, so you can quickly spot balanced times instead of optimizing for only one office.

How can I see who is outside working hours?

After selecting cities and a meeting date, review each local time row to identify participants who would be before or after normal working hours before you copy or send the invite.

Why do DST changes break recurring meetings?

Daylight saving time can change UTC offsets on different dates in different countries. Keep calendar invites tied to real IANA time zones, not fixed offsets, and re-check the meeting date.

Can I share a prefilled meeting planner link?

Yes. The planner accepts cities, time zone, and date query parameters for prefilled planning while the canonical page remains the clean /meeting URL.

How do I create a calendar-safe invite?

Copy the selected meeting details after checking the date, city list, and DST-aware local times, then create the calendar invite with named time zones so Google Calendar, Outlook, and ICS files do not drift.