Selected cities
London · Dubai · Mumbai · Singapore
The preset URL passes the city list and base timezone into the interactive planner.
Time zone scheduling
Start with London · Dubai · Mumbai · Singapore, then choose a fair live meeting window, check DST risk, and hand the decision into a calendar-safe invite without losing city context.
Preset operating brief
This landing page stays canonical for search. The action link carries the working planner state, then the tool scores the meeting, prepares the team poll, and builds the rotation-aware calendar handoff.
Selected cities
London · Dubai · Mumbai · Singapore
The preset URL passes the city list and base timezone into the interactive planner.
Decision output
Fair score, poll text, and memo
Use the first-screen recommendation to explain the tradeoff before the team votes.
Calendar handoff
DST-safe, rotation-aware invite
The planner carries named time zones, DST notes, and recurring burden context into the calendar builder.
Scenario playbook
Use this preset as a searchable operating playbook before opening the live planner: define the approval rule, name the scheduling risk, and keep the final calendar handoff tied to the same city set.
Approval rule
The planner ranks London · Dubai · Mumbai · Singapore by fair score. Treat sleep, family, customer, legal, and immovable onsite constraints as blockers; preference alone should move to the next candidate, not restart the process.
Risk to check
Re-check the offset watch before sending a recurring invite. If the same city keeps carrying early, late, night, or weekend cost, use the rotation plan instead of a fixed weekly slot.
Handoff checklist
Share the planner URL with source=meeting-london-dubai-mumbai-singapore, copy the decision memo for the record, then create the invite with named IANA time zones so Google Calendar, Outlook, and ICS files stay aligned.
Time zone scheduling
Find the best meeting time across time zones in seconds.
+1 more city included in scoring, recommendations, and calendar handoff
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⌄Why not the next best option?
Use this when a fixed weekly slot keeps making the same office pay the night or early-morning cost.
01
Preloads London · Dubai · Mumbai · Singapore into the live meeting planner so the city set stays consistent from search result to calendar handoff.
02
Ranks candidate windows by fair score, visible inconvenience, local work hours, and recurring burden instead of one headquarters timezone.
03
Keeps the final poll, memo, and calendar invite tied to named IANA time zones so DST changes do not silently drift the meeting.
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.