01
Preloads San Francisco, Tokyo, and Singapore for common launch coordination.
Time zone scheduling
Use this preset for launch, incident, and go-to-market calls split between the US West Coast and Asia. The planner shows whether the burden is acceptable or needs rotation.
01
Preloads San Francisco, Tokyo, and Singapore for common launch coordination.
02
Flags when the US or Asia side is pushed into night or early morning.
03
Creates a shareable planner state before you finalize the invite.
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, 00:00
Score 86/100RecommendedWhy this window: Singapore is starting soon at 08:00
Disadvantaged: Singapore · Starting soon · 08:00
Inside work hours
2/3
Inconvenient cities
1
Burden
low team burden
2 of 3 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.
Fairness timeline
Work hours, off-hours, and the chosen instant for every city.
San Francisco
GMT-7
Tokyo
GMT+9
Singapore
GMT+8
4-week recurring fairness
Singapore carries the highest accumulated burden (40 pts / 4 conflicts). Tokyo carries the lightest burden.
Total burden
40
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 · 17:00
TokyoGMT+9 · 09:00
SingaporeGMT+8 · 08:00
Week 2
San FranciscoGMT-7 · 17:00
TokyoGMT+9 · 09:00
SingaporeGMT+8 · 08:00
Week 3
San FranciscoGMT-7 · 17:00
TokyoGMT+9 · 09:00
SingaporeGMT+8 · 08:00
Week 4
San FranciscoGMT-7 · 17:00
TokyoGMT+9 · 09:00
SingaporeGMT+8 · 08:00
Burden rotation plan
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
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 ↔ Tokyo ↔ Singapore
Selected instant
Wed, May 27, 2026 12:00
America/Los_Angeles
Best next window
Thu, May 28, 00:00 · Recommended · Score 86
Why this window: Singapore is starting soon at 08:00
Share link
/meeting?at=2026-05-27T19%3A00%3A00.000Z&tz=America%2FLos_Angeles&cities=san-francisco%2Ctokyo%2Csingapore
Next full overlap
No full overlap in 48h
Current fit
39/100
Not recommended · high team burden
Tokyo is night at 04:00
Best candidate windows
09:00–18:00 local workday · weekends flaggedThu, May 28, 00:00
Recommended · low team burden · 2/3 in work hours
Singapore is starting soon at 08:00
Disadvantaged: Singapore
Thu, May 28, 00:30
Recommended · low team burden · 2/3 in work hours
Singapore is starting soon at 08:30
Disadvantaged: Singapore
Fri, May 29, 00:00
Recommended · low team burden · 2/3 in work hours
Singapore is starting soon at 08:00
Disadvantaged: Singapore
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
Asia/Tokyo
Thu, May 28, 2026 04:00
UTC offset
GMT+9
Day relation
next day
Local date
Thu, May 28, 2026
Asia/Singapore
Thu, May 28, 2026 03:00
UTC offset
GMT+8
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.