THE PLANNING GUIDE
Same meeting.
Different local times.
Scheduling between Asia and Europe often means a late afternoon for one person and a morning for another. Start with the team’s actual availability and a specific date. A fixed time difference is not enough when daylight saving time changes.
1. Choose your reference city
The first city sets the date and start times you see in the results. Add up to five cities. The current clocks below the planner show today’s time; they are separate from the date you are planning.
2. Enter each person’s workday
The default is 09:00–18:00, Monday to Friday. Change each city’s hours in 30-minute steps, or include weekends for that city. Work hours must finish after they start on the same local day. An end of 24:00 means midnight at the end of that day.
Each city has one continuous work interval. This first version does not model lunch breaks, overnight shifts, holidays or calendar events. Use the hours as a starting point, then ask participants to confirm.
3. Pick the date and the full meeting length
Choose a 30- or 60-minute meeting. The planner checks 15-minute start intervals across the reference city’s chosen day. A result is shown only if the entire meeting fits all cities’ entered work hours and local weekday settings.
On 15 July 2026, with both cities set to 09:00–18:00, their shared hour is 17:00–18:00 in Seoul and 09:00–10:00 in London. A 30-minute meeting can start at 17:00, 17:15 or 17:30 in Seoul.
On 15 January 2026, the same workdays only touch at 18:00 in Seoul / 09:00 in London. No full meeting fits: London’s workday begins just as Seoul’s ends. The planner therefore shows no shared working hours.
4. Send a date as well as a time
Select a candidate, then copy its share link or meeting details. The details list each city’s local date, weekday, start and end time, and UTC offset. A link includes the date, cities, hours, length and selected meeting time. It is a snapshot: later edits are not synced.
The link contains no name, email or meeting agenda, but anyone who receives it can read the included availability. A shared setup does not overwrite the recipient’s saved setup.
If you already have a proposed time
Open “Already have a time? Convert it” and enter the reference city’s local time on the selected date. Converted times are shown even if they are outside work hours, with an explicit label. This is conversion, not a recommendation.
When clocks move forward, some local times do not exist. We ask you to choose another time. When clocks move back, some times happen twice. We show both UTC offsets and ask you to choose the first or second occurrence.
When there are no shared hours
First check the date, weekend switches and all work intervals. Try 30 minutes instead of 60. If there is still no overlap, agree on adjusted availability, split the discussion into separate calls, or handle it asynchronously. Do not assume an out-of-hours suggestion is acceptable to everyone.
What to know about time zone rules
We use your browser’s IANA time zone data for the selected date, rather than a fixed country offset. Supported dates are 2000–2100. Governments can change time rules; keep your browser updated and recheck future meetings after an announced rule change. This planner does not promise that today’s browser data predicts every future change.
Plan a meeting ↗