Cities carried over
Seattle ↔ Dublin ↔ Bengaluru ↔ Singapore ↔ Sydney
Time zone scheduling
Use this preset when reliability, support, and engineering leaders need a live incident bridge without hiding which region is paying the sleep-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
Tue, Jun 2, 07:00
Score 57/100Not recommendedWhy this window: Seattle is night at 00:00
Disadvantaged: Seattle · Night · 00:00
Inside work hours
3/5
Inconvenient cities
2
Burden
high team burden
3 of 5 cities are inside 09:00–18:00. 2 cityies carries inconvenience, including 1 severe night/weekend conflict.
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.
Seattle
GMT-7
Dublin
GMT+1
Bengaluru
GMT+5:30
Singapore
GMT+8
Sydney
GMT+10
4-week recurring fairness
Seattle carries the highest accumulated burden (120 pts / 4 conflicts). Sydney carries the lightest burden.
Total burden
160
Occurrences
4
Accumulated by city
DST / offset watch
No UTC offset changes detected in the next 8 weeks for the selected cities.
Week 1
SeattleGMT-7 · 00:00
DublinGMT+1 · 08:00
BengaluruGMT+5:30 · 12:30
SingaporeGMT+8 · 15:00
SydneyGMT+10 · 17:00
Week 2
SeattleGMT-7 · 00:00
DublinGMT+1 · 08:00
BengaluruGMT+5:30 · 12:30
SingaporeGMT+8 · 15:00
SydneyGMT+10 · 17:00
Week 3
SeattleGMT-7 · 00:00
DublinGMT+1 · 08:00
BengaluruGMT+5:30 · 12:30
SingaporeGMT+8 · 15:00
SydneyGMT+10 · 17:00
Week 4
SeattleGMT-7 · 00:00
DublinGMT+1 · 08:00
BengaluruGMT+5:30 · 12:30
SingaporeGMT+8 · 15:00
SydneyGMT+10 · 17:00
Burden rotation plan
This option keeps the heaviest city at 92 pts over 4 weeks, 28 pts less concentrated than the fixed weekly time.
Fixed max
120
Rotated max
92
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
Seattle ↔ Dublin ↔ Bengaluru ↔ Singapore ↔ Sydney
Selected instant
Mon, Jun 1, 2026 23:00
America/Los_Angeles
Best next window
Tue, Jun 2, 07:00 · Not recommended · Score 57
Why this window: Seattle is night at 00:00
Share link
/meeting?at=2026-06-02T06%3A00%3A00.000Z&tz=America%2FLos_Angeles&cities=seattle%2Cdublin%2Cbangalore%2Csingapore%2Csydney
Next full overlap
No full overlap in 48h
Current fit
56/100
Not recommended · high team burden
Seattle is night at 23:00
Best candidate windows
09:00–18:00 local workday · weekends flaggedTue, Jun 2, 07:00
Not recommended · high team burden · 3/5 in work hours
Seattle is night at 00:00
Disadvantaged: Seattle
Tue, Jun 2, 07:30
Not recommended · high team burden · 3/5 in work hours
Seattle is night at 00:30
Disadvantaged: Seattle
Wed, Jun 3, 07:00
Not recommended · high team burden · 3/5 in work hours
Seattle is night at 00:00
Disadvantaged: Seattle
Selected cities
America/Los_Angeles
Mon, Jun 1, 2026 23:00
UTC offset
GMT-7
Day relation
base city
Local date
Mon, Jun 1, 2026
Europe/Dublin
Tue, Jun 2, 2026 07:00
UTC offset
GMT+1
Day relation
next day
Local date
Tue, Jun 2, 2026
Asia/Kolkata
Tue, Jun 2, 2026 11:30
UTC offset
GMT+5:30
Day relation
next day
Local date
Tue, Jun 2, 2026
Asia/Singapore
Tue, Jun 2, 2026 14:00
UTC offset
GMT+8
Day relation
next day
Local date
Tue, Jun 2, 2026
Australia/Sydney
Tue, Jun 2, 2026 16:00
UTC offset
GMT+10
Day relation
next day
Local date
Tue, Jun 2, 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.
01
Models a realistic follow-the-sun incident response chain.
02
Highlights severe local-time burden before a recurring bridge is created.
03
Turns the chosen incident window into a shareable decision memo and invite.
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.