Skip to content
Digital Tool Space

International Meeting Planner

Planning

Compare working hours for up to eight participants, rank fair meeting times and download a calendar file.

Time zonesMeeting schedulerDSTRemote teamsWorld clock

Plan a meeting across timezones

Preparing the planner in your browser…

How it works

The planner works from real instants rather than from a single offset. It walks a 15-minute grid across the selected dates, converts each candidate into every participant's local date and clock time using the IANA timezone database, and then decides whether that moment sits inside each person's working hours. Because the conversion happens for the date in question, a meeting that crosses a daylight-saving change is treated correctly instead of an hour out. Local wall times that never happened, such as the hour skipped when clocks go forward, are left out of the results rather than silently moved.

How the planner chooses a time

Each participant has a city, an IANA timezone, working hours and working days. The organizer sets the dates and the meeting length. The planner evaluates every 15-minute start time across those dates and keeps the ones that work for the group. A slot is ideal when every participant is inside their own working hours, workable when it overlaps a break or uses declared flexibility, and a compromise when somebody would be outside working hours. The result is a ranked list of actual instants, not a grid of offsets that has to be interpreted by hand.

Fairness, not just overlap

The fairest slot is not always the one with the most people in working hours. A time that puts one person at 03:00 is usually worse than a time that asks three people to accept a short break overlap. The ranking therefore looks first at the worst individual penalty, then at the total penalty across the group, then at how many people are outside working hours, and finally at the earlier start time. That ordering protects the person carrying the heaviest burden. Compromises are always calculated separately, so a group can see the least-bad alternative.

Daylight saving and unusual offsets

Offsets are not stored as fixed numbers. The planner reads the timezone rules that apply on the selected date, which matters around daylight-saving changes and in zones that use half-hour or quarter-hour offsets. A city such as Kathmandu can be 5 hours 45 minutes ahead of UTC, while Adelaide changes at a different moment from London. If clocks jump forward, a local time such as 02:30 may not exist on that date; the planner skips that candidate instead of pretending it occurred. When clocks fall back and a local time occurs twice, the earlier occurrence is used.

Sharing and calendar files

The planner runs in your browser. It does not create an account, store the group on a server or send an invitation. A shared plan is encoded after the # in the URL, which browsers keep on the device and do not include in the request to the site. The calendar download is a standard .ics file containing the chosen start and end in UTC, so it imports into common calendar apps. Review the event in your own calendar before sending it to anyone, and check the participant list against the final local times shown on screen.

Examples

London, Berlin and New York

Input
  • Participants:London, Berlin, New York
  • Working hours:09:00–17:00 local
  • Duration:30 minutes
Output
A late-afternoon London slot that is still inside Berlin's day and mid-morning in New York.

No shared morning window

Input
  • Participants:London, Tokyo, Los Angeles
  • Working hours:09:00–17:00 local
  • Duration:45 minutes
Output
No ideal overlap; the planner ranks the least disruptive outside-hours compromise.

Kathmandu's quarter-hour offset

Input
  • Participants:London, Kathmandu
  • Working hours:09:00–17:00 local
  • Duration:30 minutes
Output
Local times line up to the quarter hour, without rounding Kathmandu to a whole-hour offset.

Frequently Asked Questions

It uses the IANA timezone rules for the selected date rather than a fixed UTC offset. When clocks change, the local time is converted for that specific day, so the meeting does not drift by an hour. Local times that do not exist because the clocks go forward are skipped.

Each participant has their own start and end time, working days and optional break. A slot is ideal only when it sits wholly inside that person's working hours and outside their break. A declared flexibility window can make a slightly early or late slot workable instead of a compromise.

The planner minimises the worst individual penalty first, then the total penalty for the group, then the number of people outside working hours, and finally chooses the earlier start. This avoids a result that is technically balanced but places an unreasonable burden on one person.

Not every timezone is a whole number of hours from UTC. India is UTC+05:30, Nepal is UTC+05:45, and Adelaide is UTC+09:30 or UTC+10:30 depending on the season. The planner reads the actual offset for the selected date instead of assuming whole hours.

Up to eight. Each participant can have a different city, timezone, working day pattern, break and flexibility allowance. The organizer's timezone is used for the date range.

No. The calendar download creates an .ics file for you to review and add to your own calendar. The planner does not send email, create a shared event or book anything on anyone's behalf.

In the link's hash fragment after the #. That part stays in the browser and is not sent to the server in the request. Anyone with the full link can read the participant names and settings, so share it only with people who should see them.

The selected dates, meeting length or working-hour patterns may leave no common moment. Try widening the date range, shortening the meeting, or adjusting participant working hours and working days to inspect the least-bad compromise.

Yes. It is free to use and calculations run in your browser. The form does not upload the participant list or dates to a server, and there is no account or tracking requirement to use it.

Related Tools