MyCalcBuddy

Meeting Scheduler Calculator

Find overlapping availability across different time zones for scheduling meetings.

Participants

Available Meeting Times (5 slots found)

14:00 UTC
Person 1: 9:00 AM
Person 2: 2:00 PM
14:30 UTC
Person 1: 9:30 AM
Person 2: 2:30 PM
15:00 UTC
Person 1: 10:00 AM
Person 2: 3:00 PM
15:30 UTC
Person 1: 10:30 AM
Person 2: 3:30 PM
16:00 UTC
Person 1: 11:00 AM
Person 2: 4:00 PM

What Is the Meeting Scheduler Calculator?

The Meeting Scheduler Calculator finds the best time windows for a meeting when participants are in different time zones with different availability windows. You specify each participant's timezone offset, their working hours (local start and end times), and the required meeting duration — the calculator identifies all time slots where everyone is simultaneously available.

Scheduling across time zones is one of the most common logistical challenges in global business. A slot that is 9 AM for someone in London might be 4 AM for someone in Los Angeles or 10 PM for someone in Tokyo. Without a systematic approach, overlapping availability across multiple time zones requires tedious manual conversion for every candidate slot.

This calculator converts all participant availability windows to UTC as a common reference, then identifies the intersection — the time slots where all availability ranges overlap simultaneously. Results are displayed in each participant's local time for instant readability.

Finding Overlapping Availability

All participant availability windows are converted to UTC minutes, then the intersection of all windows is found.

Availability Overlap in UTC

utcStart = localStart − timezoneOffset×60; utcEnd = localEnd − timezoneOffset×60; overlapStart = max(all utcStarts); overlapEnd = min(all utcEnds)

Where:

  • localStart/localEnd= Participant's available window in their local time (minutes from midnight)
  • timezoneOffset= UTC offset in hours (e.g., −5 for EST, +5.5 for IST)
  • utcStart/utcEnd= Availability window converted to UTC minutes
  • overlapStart= max(all utcStarts) — earliest time everyone is available in UTC
  • overlapEnd= min(all utcEnds) — latest time everyone is still available in UTC
  • validSlot= overlapEnd − overlapStart >= meetingDuration — if true, the overlap accommodates the meeting

Common Time Zone Overlap Challenges

Locations Time Difference Best Overlap Window
New York + London5h (EST/EDT)9 AM–1 PM NY / 2 PM–6 PM London
London + Mumbai5.5h9 AM–11:30 AM London / 2:30 PM–5 PM Mumbai
New York + Tokyo14h7 AM–8 AM NY / 8 PM–9 PM Tokyo (very narrow)
NY + London + MumbaiMultiple9 AM–11 AM NY / 2 PM–4 PM London / 7:30 PM–9:30 PM Mumbai

How to Use This Calculator

  1. Add Participants: For each participant, enter their name, UTC timezone offset (e.g., −5 for EST, +1 for CET), and their available start and end times in their local time.
  2. Set Meeting Duration: Enter how long the meeting needs to be in minutes (e.g., 60 for one hour).
  3. View Results: The calculator shows all valid meeting windows, displayed in each participant's local time for easy reference.
  4. Add/Remove Participants: Use the + and − buttons to adjust the participant list. A minimum of 2 participants is required.

Real-World Applications

Global software teams with engineers distributed across the US, Europe, and Asia use meeting schedulers for daily standups, sprint reviews, and stakeholder meetings. Finding a recurring slot that works across 10+ time zones often requires accepting that someone will attend outside normal hours — the calculator makes the tradeoff visible so teams can make informed choices.

International sales teams scheduling calls with prospects in different regions need a quick way to find the next available window without manually doing time zone math. The calculator shows the local time for each participant so the sales rep can propose the slot in a way that makes sense to each party.

Academic conference organizers planning virtual sessions for globally distributed attendees use scheduling tools to determine when the largest proportion of the target audience will be available. Regional session times can be set to maximize attendance from each geographic market.

Worked Examples

New York and London Teams

Problem:

Find a 60-minute window for New York (UTC−5, 9 AM–5 PM) and London (UTC+0, 9 AM–5 PM).

Solution Steps:

  1. 1New York availability in UTC: 9 AM + 5h = 14:00 to 5 PM + 5h = 22:00
  2. 2London availability in UTC: 9 AM + 0h = 09:00 to 5 PM + 0h = 17:00
  3. 3Overlap: max(14:00, 09:00) = 14:00 to min(22:00, 17:00) = 17:00
  4. 4Overlap duration = 3 hours > 60 minutes → valid
  5. 5Meeting window: 14:00–17:00 UTC = 9 AM–12 PM NY = 2 PM–5 PM London

Result:

Valid 3-hour overlap: 9 AM–12 PM New York (2 PM–5 PM London). Best slot: 10 AM–11 AM New York (3 PM–4 PM London).

Three-Continent Meeting

Problem:

San Francisco (UTC−8, 9–5), New York (UTC−5, 9–5), London (UTC+0, 9–5): find a 30-minute window.

Solution Steps:

  1. 1SF in UTC: 17:00–01:00 (+1 day); NY in UTC: 14:00–22:00; London in UTC: 09:00–17:00
  2. 2Overlap start: max(17:00, 14:00, 09:00) = 17:00
  3. 3Overlap end: min(01:00+, 22:00, 17:00) = 17:00
  4. 4Overlap = 0 minutes → no valid slot during standard hours
  5. 5Solution: Extend SF end time or London start time; or NY participant attends before 9 AM local

Result:

No overlap exists during standard working hours for all three offices. Consider 4:45 PM London / 4:45 PM NY / 8:45 AM SF (before SF standard hours).

Two-Hour Sprint Review

Problem:

London (UTC+0) and Singapore (UTC+8) need a 2-hour sprint review during 9 AM–5 PM each.

Solution Steps:

  1. 1London UTC: 09:00–17:00; Singapore UTC: 01:00–09:00
  2. 2Overlap: max(09:00, 01:00) = 09:00 to min(17:00, 09:00) = 09:00
  3. 3Overlap = 0 minutes at single point → no valid 2-hour window
  4. 4London 9 AM = Singapore 5 PM (just ending); no overlap during both standard hours
  5. 5Options: London ends at 6 PM (extends overlap) or Singapore starts at 8 AM (extends overlap)

Result:

No overlap in standard hours. With Singapore starting at 8 AM: 9 AM London / 5 PM Singapore (1-hour window at boundary). For 2-hour meeting, London must shift to 8–10 AM or Singapore must shift to 4–6 PM.

Tips & Best Practices

  • ✓Add 'buffer' to participants' available windows — a meeting filling an entire availability window leaves no time for breaks or transitions.
  • ✓When no overlap exists, try expanding availability to 8 AM start or 6 PM end for one region to create a workable window.
  • ✓Rotate recurring meeting times quarterly so no single team always meets outside their preferred hours.
  • ✓For very large time zone differences (>10 hours), consider making meetings biweekly and alternating who takes the inconvenient slot.
  • ✓Include travel time context: if a participant is traveling internationally, their effective timezone changes — update their offset accordingly.
  • ✓For 3+ continent meetings, aim for overlap at the edges of workday (8-10 AM or 4-6 PM) rather than requiring everyone to be mid-day simultaneously.

Related Calculators

Time Zone Converter

Convert times between any two time zones

UTC Converter

Convert between UTC and local time zones

Frequently Asked Questions

The UTC offset is the number of hours your local timezone is ahead of (+) or behind (−) Coordinated Universal Time. For example, Eastern Standard Time is UTC−5 (5 hours behind UTC), so you enter −5. India Standard Time is UTC+5.5, so you enter 5.5. If you observe daylight saving time, use your current offset — EST (winter) is −5 but EDT (summer) is −4.
When two locations are more than 9–10 hours apart in time zones, their standard 9 AM–5 PM working hours do not overlap at all. For example, when it's 9 AM in New York, it's 10 PM in Tokyo — Tokyo's workday ended 5 hours ago. In these situations, you either need someone to meet outside their standard hours, or use async collaboration tools (recorded video, shared documents) instead of real-time meetings.
The 'least painful' time for global teams often requires compromise. Common approaches: (1) Rotate meeting times so no single region always sacrifices convenience; (2) Find a 'least bad' time that is early morning for one group and late afternoon for another; (3) Limit real-time meetings to highest-priority decisions and use async channels for routine updates. Tools like Calendly, Doodle, and World Time Buddy help visualize team availability across time zones.
Enter the offset as a decimal: UTC+5:30 = 5.5, UTC+5:45 (Nepal) = 5.75, UTC+9:30 (Central Australia) = 9.5. The calculator converts these correctly by multiplying the offset in hours by 60 to get the total minute offset, allowing accurate conversion of Indian, Nepalese, and Australian half-hour timezone availability windows.
Use the offset that is currently in effect for each participant's location at the time of the meeting. For example, a London participant would use UTC+0 (GMT) in winter but UTC+1 (BST) in summer. A New York participant would use UTC−5 (EST) in winter but UTC−4 (EDT) in summer. If the meeting is being planned far in advance, note that DST transitions can change the overlap window — verify the offsets closer to the meeting date.

Sources & References

Last updated: 2026-06-06

💡

Help us improve!

How would you rate the Meeting Scheduler Calculator?

<>

Editorial Note

MyCalcBuddy Editorial Team

This page is maintained as an educational calculator reference.

Source

Formula Source: Standard Mathematical References

by Various

UpdatedLast reviewed: May 2026
CheckedFormula checks are based on standard references and internal QA review.

Privacy choices

MyCalcBuddy uses necessary storage for the site to work. Optional analytics, notifications, and future advertising features stay off unless you allow them.