Time zone scheduling
Time Zone Meeting Planner
Find fair meeting windows across cities, catch DST mistakes, and create calendar-safe invites without making the same teammate pay the early/late-hours cost every week.
Decision command center
RecommendScore every candidate by overlap, local work hours, and visible burden.
ExplainShow who pays the cost before the poll starts.
MitigateCheck DST and rotate recurring burden instead of repeating pain.
CommitCopy the poll, memo, or calendar invite with the rationale intact.
Decision command center · Recommend · Explain · Mitigate · Commit
🛡 Recommended
13:30
Nice
12:30
London
Score
100
Every city is inside weekday work hours.
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.
▣ Single meeting invite⌄▣ Build recurring-aware invite⌄24hWork hours
Work hoursAcceptableOff hoursNight
Meeting pain
Nice
☺Low
all in work hours
London
☺Low
all in work hours
Best candidate windows
UseRunner-up check
Why not the next best option?
Chosen · Thu, Jun 11, 2026 · 100/100
Not chosen · Fri, Jun 12, 2026 · 100/100 · Same score, lower tie-break; Every city is inside weekday work hours.
Burden rotation plan
Use this when a fixed weekly slot keeps making the same office pay the night or early-morning cost.
‹
›
!The fixed best window remains the cleanest recurring plan; no rotation lowered the maximum city burden below 0 points.
DST / offset watchStable offsetsNo UTC offset changes detected in the next 8 weeks for the selected cities.Nice GMT+2 · London GMT+1Nice GMT+2 · London GMT+1Nice GMT+2 · London GMT+1Nice GMT+2 · London GMT+1
4-week recurring fairness
◉ Nice
0%
Low
◉ London
0%
Low
Why this wins: highest scored fair window; alternatives are recorded below so the decision is explainable, not just a timezone conversion.
✓2 of 2 cities are inside 09:00–18:00. No city is pushed into off-hours.
✓Every city is inside weekday work hours.
✓No UTC offset changes detected in the next 8 weeks for the selected cities.
✓Rotation option: 4-week plan lowers max city burden by 0 pts (0 → 0).
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. Choose citiesAdd every participant city or IANA time zone and set the real meeting date.
- 2. Compare fair scoreCheck which candidate windows balance normal working hours across the group.
- 3. Spot outside hoursSee who would be early, late, or on the wrong day before you confirm the time.
- 4. Copy or shareShare a prefilled planner link so teammates can review the same DST-aware view.
- 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.