01
Preloads Pacific Time and India Standard Time cities used by many engineering teams.
Time zone scheduling
Start with a common California and India engineering standup corridor, then compare whether the meeting should favor Pacific morning, India evening, or a rotating compromise.
01
Preloads Pacific Time and India Standard Time cities used by many engineering teams.
02
Shows when India is pushed too late or California is pushed too early.
03
Supports recurring fairness when the same side keeps paying the inconvenience cost.
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.
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, 03:30
Score 64/100AcceptableWhy this window: San Francisco is evening at 20:30
Disadvantaged: San Francisco · Evening · 20:30
Inside work hours
2/4
Inconvenient cities
2
Burden
moderate team burden
2 of 4 cities are inside 09:00–18:00. 2 cityies 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.
Fairness timeline
Work hours, off-hours, and the chosen instant for every city.
San Francisco
GMT-7
Los Angeles
GMT-7
Bengaluru
GMT+5:30
New Delhi
GMT+5:30
4-week recurring fairness
Los Angeles carries the highest accumulated burden (64 pts / 4 conflicts). New Delhi carries the lightest burden.
Total burden
128
Occurrences
4
Accumulated by city
DST / offset watch
No UTC offset changes detected in the next 8 weeks for the selected cities.
Week 1
San FranciscoGMT-7 · 20:30
Los AngelesGMT-7 · 20:30
BengaluruGMT+5:30 · 09:00
New DelhiGMT+5:30 · 09:00
Week 2
San FranciscoGMT-7 · 20:30
Los AngelesGMT-7 · 20:30
BengaluruGMT+5:30 · 09:00
New DelhiGMT+5:30 · 09:00
Week 3
San FranciscoGMT-7 · 20:30
Los AngelesGMT-7 · 20:30
BengaluruGMT+5:30 · 09:00
New DelhiGMT+5:30 · 09:00
Week 4
San FranciscoGMT-7 · 20:30
Los AngelesGMT-7 · 20:30
BengaluruGMT+5:30 · 09:00
New DelhiGMT+5:30 · 09:00
Burden rotation plan
This option keeps the heaviest city at 48 pts over 4 weeks, 16 pts less concentrated than the fixed weekly time.
Fixed max
64
Rotated max
48
Rotated burden by city
Use this when a fixed weekly slot keeps making the same office pay the night or early-morning cost.
Send this fairness context into Calendar Link Builder so the invite note explains the recurring tradeoff.
Build recurring-aware inviteReady 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
San Francisco ↔ Los Angeles ↔ Bengaluru ↔ New Delhi
Selected instant
Wed, May 27, 2026 12:00
America/Los_Angeles
Best next window
Thu, May 28, 03:30 · Acceptable · Score 64
Why this window: San Francisco is evening at 20:30
Share link
/meeting?at=2026-05-27T19%3A00%3A00.000Z&tz=America%2FLos_Angeles&cities=san-francisco%2Clos-angeles%2Cbangalore%2Cdelhi
Next full overlap
No full overlap in 48h
Current fit
38/100
Not recommended · high team burden
Bengaluru is night at 00:30
Best candidate windows
09:00–18:00 local workday · weekends flaggedThu, May 28, 03:30
Acceptable · moderate team burden · 2/4 in work hours
San Francisco is evening at 20:30
Disadvantaged: San Francisco
Thu, May 28, 04:00
Acceptable · moderate team burden · 2/4 in work hours
San Francisco is evening at 21:00
Disadvantaged: San Francisco
Thu, May 28, 04:30
Acceptable · moderate team burden · 2/4 in work hours
San Francisco is evening at 21:30
Disadvantaged: San Francisco
Selected cities
America/Los_Angeles
Wed, May 27, 2026 12:00
UTC offset
GMT-7
Day relation
base city
Local date
Wed, May 27, 2026
America/Los_Angeles
Wed, May 27, 2026 12:00
UTC offset
GMT-7
Day relation
same day
Local date
Wed, May 27, 2026
Asia/Kolkata
Thu, May 28, 2026 00:30
UTC offset
GMT+5:30
Day relation
next day
Local date
Thu, May 28, 2026
Asia/Kolkata
Thu, May 28, 2026 00:30
UTC offset
GMT+5:30
Day relation
next day
Local date
Thu, May 28, 2026
Calendar-safe handoff
Need a checklist before inviting the team? Read the timezone meeting planning guide for overlap windows, shared calendar links, and daylight-saving-safe scheduling.
The calendar handoff uses America/Los_Angeles 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.
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.
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.
Scheduling FAQ
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.
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.
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.
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.
Yes. The planner accepts cities, time zone, and date query parameters for prefilled planning while the canonical page remains the clean /meeting URL.
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.