Cities carried over
Minsk ↔ Singapore
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.
Global product teamSF · London · Bangalore · SydneyUS ↔ Asia launch callSan Francisco · Tokyo · SingaporeAPAC ↔ Europe standupSingapore · Bangalore · London · BerlinUS ↔ Europe team syncSan Francisco · New York · London · BerlinCalifornia ↔ India standupSan Francisco · Los Angeles · Bangalore · DelhiNew York ↔ London client callNew York · LondonTokyo ↔ San Francisco product reviewTokyo · San Francisco · SeattleSingapore ↔ London team meetingSingapore · London · BerlinAustralia ↔ US team callSydney · Melbourne · San Francisco · New YorkRemote engineering standupSF · Austin · London · Berlin · BangaloreCustomer success global callNew York · London · Singapore · SydneyWebinar time zone plannerLos Angeles · New York · London · SingaporeRecurring global team meetingSeattle · London · Bangalore · Singapore · Sydney
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, 07:30
Score 98/100RecommendedWhy this window: Every city is inside weekday work hours.
all in work hours
Inside work hours
2/2
Inconvenient cities
0
Burden
low team burden
2 of 2 cities are inside 09:00–18:00. No city is pushed into off-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.
Fairness timeline
Work hours, off-hours, and the chosen instant for every city.
Work hoursOff hours
Minsk
GMT+3
0918
Work hours10:30
Singapore
GMT+8
0918
Work hours15:30
4-week recurring fairness
Who carries the recurring burden?
Minsk carries the highest accumulated burden (0 pts / 0 conflicts). Singapore carries the lightest burden.
Total burden
0
Occurrences
4
WeekDecision reasonScore
W1Thu, May 28, 2026 · Every city is inside weekday work hours.98/100
W2Thu, Jun 4, 2026 · Every city is inside weekday work hours.98/100
W3Thu, Jun 11, 2026 · Every city is inside weekday work hours.98/100
W4Thu, Jun 18, 2026 · Every city is inside weekday work hours.98/100
Accumulated by city
Minsk0 pts · 0x
Singapore0 pts · 0x
DST / offset watch
No UTC offset changes detected in the next 8 weeks for the selected cities.
Week 1
MinskGMT+3 · 10:30
SingaporeGMT+8 · 15:30
Week 2
MinskGMT+3 · 10:30
SingaporeGMT+8 · 15:30
Week 3
MinskGMT+3 · 10:30
SingaporeGMT+8 · 15:30
Week 4
MinskGMT+3 · 10:30
SingaporeGMT+8 · 15:30
Burden rotation plan
Rotate the pain instead of repeating it
No better rotation was found than the fixed weekly time: the heaviest city still reaches 0 pts over 4 weeks. Use the fixed best window unless the team wants to alternate for etiquette.
Fixed max
0
Rotated max
0
WeekRotated slotScore
W1Thu, May 28, 2026 10:30 · Every city is inside weekday work hours.98/100
W2Thu, Jun 4, 2026 10:30 · Every city is inside weekday work hours.98/100
W3Thu, Jun 11, 2026 10:30 · Every city is inside weekday work hours.98/100
W4Thu, Jun 18, 2026 10:30 · Every city is inside weekday work hours.98/100
Rotated burden by city
Minsk0 pts · 0x
Singapore0 pts · 0x
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 inviteSelected citiesLocal timeWork hours
MinskThu, May 28, 2026 10:30Work hours
SingaporeThu, May 28, 2026 15:30Work hours
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.
Selected instant
Thu, May 28, 2026 00:00
Europe/Minsk
Best next window
Thu, May 28, 07:30 · Recommended · Score 98
Why this window: Every city is inside weekday work hours.
Share link
/meeting?at=2026-05-27T21%3A00%3A00.000Z&tz=Europe%2FMinsk&cities=minsk%2Csingapore
Next full overlap
from May 28, 06:00 AM
Current fit
40/100
Not recommended · high team burden
Minsk is night at 00:00
Best candidate windows
09:00–18:00 local workday · weekends flaggedThu, May 28, 07:30
Recommended · all in work hours
Every city is inside weekday work hours.
all in work hours
Thu, May 28, 09:30
Recommended · all in work hours
Every city is inside weekday work hours.
all in work hours
Fri, May 29, 07:30
Recommended · all in work hours
Every city is inside weekday work hours.
all in work hours
Selected cities
Minsk
Europe/Minsk
Thu, May 28, 2026 00:00
UTC offset
GMT+3
Day relation
base city
Local date
Thu, May 28, 2026
Singapore
Asia/Singapore
Thu, May 28, 2026 05:00
UTC offset
GMT+8
Day relation
same day
Local date
Thu, May 28, 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 Europe/Minsk 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. 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.