CALCULATE WITH CONFIDENCE

Dates & Time · Time zones & global coordination

World Meeting Planner

Find shared meeting windows across multiple named zones using each participant's local working interval, meeting length, search date, and configurable step.

Dates & Time · Time zones & global coordination

Enter the date and time scenario

Private in-browser workflow · no account, upload, location tracking, or saved schedule
Participants

Add one structured row per item. Use short non-identifying labels; rows remain only in this browser tab.

Enter the calendar, clock, named-zone, workweek, and closure assumptions that actually govern the task. A named IANA zone models offset transitions; a fixed abbreviation such as CST is intentionally not accepted. Nothing entered here is added to a URL, analytics event, account, or saved schedule.

Date and time result

—

Enter valid values to see the result.

Your entries are calculated in this browser and are not submitted to 365CALCS.COM.

Quick guide

How to use this calculator

  1. Choose the exact calendar, clock, recurrence, time-zone, working-day, or endpoint convention before entering values.
  2. Add one structured row for each participant, interval, stage, closure, target, or period that belongs in the scenario.
  3. Check the component ledger before using the headline result: it exposes skipped dates, offsets, transitions, overlaps, stage boundaries, and the convention driving the answer.

Calculation method

Explicit date and time workflow

Candidate UTC instants are retained only when the complete meeting interval lies inside every participant's local availability window.

The calculator keeps civil dates, elapsed durations, local clock readings, UTC instants, work calendars, and recurring rules distinct rather than silently treating them as interchangeable.

Worked example

Worked example

A 60-minute meeting is feasible only where all entered local windows overlap after date-aware zone conversion.

Candidate UTC instants are retained only when the complete meeting interval lies inside every participant's local availability window.

Supported inputs

Precision and limits

Calendar and time-zone conventions

Gregorian dates and IANA named zones are modeled explicitly. Holiday, school, legal, payroll, contractual, and operating calendars are never inferred from a country name.

DST and civil-time limits

Repeated or nonexistent local clock readings are identified where they matter. Future government time-zone changes cannot be predicted beyond the time-zone data available to the runtime.

Planning support, not authority

Results organize entered assumptions. They do not determine legal notice, payroll compliance, staffing safety, entitlement, service credits, travel feasibility, or institutional policy.

Calculator-specific boundary

Availability rows describe recurring local windows for the searched dates. Personal calendars, holidays, breaks, travel, and organizational policy are not inferred.

Continue calculating

Related calculators