Time Zone Meeting Overlap Calculator

Remote meetings fail quietly when the clock math is treated as a fixed offset problem. A time that looks normal for one office can land before breakfast, after a school pickup, or on a local weekend for another. The problem is not only that cities sit in different time zones. The harder part is that the relationship between those zones can change by date as daylight-saving rules begin, end, or change by law.

Good overlap planning starts with a few terms that sound similar but behave differently:

Time zone

A location-based rule set such as America/New_York or Asia/Singapore. It can include historic and future offset changes.

UTC offset

The clock difference from Coordinated Universal Time at one moment, such as UTC+08:00. It may not stay the same all year.

Work window

The local start and end time a person is willing to meet, such as 09:00 to 17:00.

A useful meeting start must fit the whole meeting, not just the opening minute. A 60 minute call starting at 16:30 does not fit a 09:00 to 17:00 work window because it ends at 17:30. That end-time check matters for workshops, handoffs, interviews, and customer calls that run longer than a short sync.

Abbreviations are a common scheduling trap. EST can mean a North American standard-time label, an Australian eastern label in some contexts, or simply a shorthand someone typed without checking the date. IANA names are longer, but they identify the civil-time rules needed for date-aware conversion.

Real teams also need a fairness policy. A strict shared window treats every participant's workday as a hard boundary. A fallback window admits that a high-priority meeting may sometimes ask someone to join early or late, then makes the tradeoff visible instead of hiding it behind one convenient clock time.

• Date changes the answer. Daylight-saving transitions can move the overlap by an hour even when every local workday stays the same.
• Duration changes the answer. A 30 minute overlap does not support a 90 minute workshop.
• Local weekends matter. Friday afternoon in one place may already be Saturday somewhere east of it.
• Weighted planning needs review. Giving one participant more weight can improve a critical attendee's fit while making another person's local time worse.

Time-zone overlap is only the scheduling math. It does not know holidays, leave, travel, meeting rooms, school runs, religious observances, or the local etiquette of asking someone to meet outside normal hours. Treat the overlap as a shortlist, then confirm the human calendar before sending the invite.

How to Use This Tool:

Start with a realistic roster, choose the date and meeting length, then compare strict work-hour overlap with fallback options.

1. Choose a Team preset for a common corridor or select Custom roster when you want to paste your own participants.
2. Enter the Participant roster with one person or location per line. Use Name | Time zone | HH:MM | HH:MM | weight; the weight is optional and defaults to 1. At least two valid participant lines are required.
3. Use IANA names such as America/Los_Angeles, Europe/Berlin, or Asia/Kolkata. If a line uses an unsupported abbreviation, the validation message names the line to fix.
4. Set Planning date and Reference timezone. The results are sorted and labeled first in the reference zone, with UTC and participant-local times shown beside it.
5. Choose Meeting length, Scan window, and Recommendation mode. Use Strict work-hours only for hard boundaries, Strict first, then fallback for normal planning, or Least-pain ranking when a compromise is acceptable.
6. Open Advanced when you need finer control over Candidate step, Edge-hours buffer, Workday rule, Minimum fallback score, and calendar labels.
7. Read Best Windows first, then check Participant Impact before copying a table, downloading an invite, opening Google Calendar, or saving the JSON report.

Interpreting Results:

Best Windows ranks candidate starts in the reference timezone and UTC. A row marked as full work-hour overlap means every participant stays within the local work window for the entire meeting. A fallback row means the start passed the current score filter, but at least one participant is in edge hours or outside the normal window.

Participant Impact is the confidence check. Look at each participant's local meeting time, work window, fit label, and local note. A high weighted score does not guarantee that every person has a good time, especially when one attendee has a larger weight.

• Overlap Heatmap shows the first scanned reference date by hour. Green marks work-hour fit, yellow marks edge-hour fit, and gray marks off-hours or no overlap.
• Calendar Invite uses the current best-ranked slot. Confirm the participant table before copying the summary, copying ICS text, downloading the .ics file, or opening Google Calendar.
• No qualifying window means the current mode and minimum fallback score removed every candidate. Try a shorter meeting, wider scan window, larger edge-hours buffer, or lower fallback score.
• The first 10 nonblank participant lines are evaluated. Split larger groups into smaller planning runs when more people need review.

Technical Details:

Meeting overlap is an interval problem on a UTC timeline. Each candidate start begins as a date and minute in the reference timezone, then maps to a UTC start. The meeting end is the UTC start plus the selected duration. That same UTC interval is converted into each participant's local time zone so the local workday rule, start time, end time, and daylight-saving offset are evaluated for the actual date.

The calculation uses the participant's local start date for weekday checks. If a work window crosses midnight, such as 22:00 to 06:00, the local end is treated as the next day for interval comparison. This keeps overnight support shifts and late handoff windows from being rejected simply because the clock wraps past 24:00.

Formula Core

For one participant, early and late minutes measure how much of the meeting falls outside the local work window:

A participant inside the work window scores 100. An edge-hours participant starts below that and loses score as the meeting moves farther outside the window. A normal workday candidate outside the edge buffer can still receive a lower score, while a local weekend scores 0 under the Monday to Friday rule.

If New York and London both score 100 but Singapore scores 0, and all weights are 1, the weighted score is 66.7. If Singapore has weight 2, the same local times score 50 because that participant carries twice as much influence in the average.

Ranking depends on the selected mode. Strict work-hours only returns only rows where every participant is strict. Strict first, then fallback returns strict rows when any exist, otherwise it uses rows meeting the minimum fallback score. Least-pain ranking ranks rows meeting the fallback score directly. Ties sort by strictness, higher score, lower worst local pain, then earlier UTC start.

Accuracy Notes:

The result is a planning aid, not a live calendar availability check. Accuracy depends on current time-zone data, the date you choose, and the local work windows you enter.

• Governments can change time-zone boundaries, UTC offsets, and daylight-saving rules, so very future-looking schedules should be rechecked closer to the meeting date.
• The calculator does not read personal calendars, room bookings, holidays, leave, travel time, or local office closure rules.
• Opening Google Calendar sends the event title, time, location, and details to Google Calendar. Copying or downloading the ICS text keeps the decision in your own handoff flow until you import or share it.

Worked Examples:

Americas and Europe sales call

With San Francisco set to 08:00-17:00, New York to 09:00-17:30, Berlin to 09:00-18:00, a 60 minute meeting, 30 minute candidate step, and a June 2, 2026 planning date, Best Windows can return an 11:00 New York start as a full work-hour overlap. Participant Impact shows 08:00 in San Francisco, 11:00 in New York, and 17:00 in Berlin, all scoring 100.

US, Europe, and Asia compromise

A New York, London, and Singapore roster may have no strict 60 minute overlap on the same date. With fallback scoring allowed, Best Windows may surface a 05:00 New York start with a 66.7 score because London and Singapore are inside work hours while New York is 240 minutes before work. That is a usable warning, not an endorsement to schedule it without checking the New York attendee.

Long Pacific workshop near the edge

For Bengaluru, Singapore, and Sydney, a 180 minute session can fit Singapore and Sydney but begin 30 minutes before Bengaluru's 10:00 workday. With a 60 minute edge buffer, Participant Impact labels Bengaluru as Edge hours and the best row can still score above 90. Reducing the edge buffer to 0 would remove that compromise from strict consideration.

Validation failure from an abbreviation

A roster line like Berlin client | CET | 09:00 | 18:00 | 1 fails because CET is not a supported IANA location name. Change it to Europe/Berlin, then check Best Windows again.

FAQ:

References:

• IANA Time Zone Database, Internet Assigned Numbers Authority.
• Intl.DateTimeFormat() constructor, MDN Web Docs.
• RFC 5545: iCalendar, RFC Editor, September 2009.