Highlights
- See each participant's current time in analog + digital cards.
- Find overlapping working-hour slots with top suggestions.
- Use a reference time zone and date to keep everyone aligned.
- Share settings via URL or export/import JSON for full data.
How to use
- Add participants and set their time zones and working hours.
- Pick a reference time zone and the meeting date.
- Adjust duration, step, and range, then compute suggestions.
- Copy a share URL or export/import JSON to save the plan.
Quick answer: find the best meeting time in 3 decisions
- Set fairness first: choose a reference zone and keep work-hour windows realistic for each participant.
- Set constraints next: pick duration, search range, and step size before computing suggestions.
- Pick from overlap quality: choose top slots where everyone is inside working hours, then share the URL with the team.
If no slot appears, widen the range (for example 07:00-22:00), reduce duration, or split attendees into two sessions.
Common scenarios
- US-EU weekly sync: 30-45 min duration, 15-min step, compare London/Berlin/New York cards first.
- APAC-EU handoff: shorter windows (15-30 min) usually produce better overlap quality.
- Large cross-region team: test two candidate dates and share both URLs so participants can choose.
See also
- World Clock Board for live city time checks before locking a slot.
- Time Zone Converter for one-to-one date-time conversion.
- 12/24 Time Format Converter when sharing schedules with mixed format preferences.
Time Zone Meeting Planner
Find meeting times based on participants' time zones and working hours.
Reference date is interpreted in the reference time zone.
DST boundaries may shift times slightly in rare cases.
Settings stay in this browser and are not sent anywhere.
How to use this tool effectively
This guide helps you use Time Zone Meeting Planner in a repeatable way: define a baseline, change one variable at a time, and interpret outputs with explicit assumptions before you share or act on results.
How it works
The page applies deterministic logic to your inputs and shows rounded output for readability. Treat it as a comparison workflow: run one baseline case, adjust a single parameter, and measure both absolute and percentage deltas. If a result seems off, verify units, time basis, and sign conventions before drawing conclusions. This approach keeps your analysis reproducible across teammates and sessions.
When to use
Use this page when you need a fast estimate, a classroom check, or a practical what-if comparison. It works best for planning and prioritization steps where you need direction and magnitude quickly before investing in deeper modeling, manual spreadsheets, or formal external review.
Common mistakes to avoid
- Changing multiple parameters at once, which hides the true cause of output movement.
- Mixing units (percent vs decimal, monthly vs yearly, gross vs net) across scenarios.
- Comparing with another tool without aligning defaults, constants, and rounding rules.
- Using rounded display values as exact downstream inputs without re-checking precision.
Interpretation and worked example
Run a baseline scenario and keep that result visible. Next, modify one assumption to reflect your realistic alternative and compare direction plus size of change. If the direction matches your domain expectation and the size is plausible, your setup is usually coherent. If not, check hidden defaults, boundary conditions, and interpretation notes before deciding which scenario to adopt.
See also
FAQ
How is the reference date interpreted?
It follows the calendar date in the reference time zone, not your local date.
What does the share URL include?
Share URLs include settings and up to six participants. Use JSON export/import for full data.
What should I do first on this page?
Start with the minimum required inputs or the first action shown near the primary button. Keep optional settings at defaults for a baseline run, then change one setting at a time so you can explain what caused each output change.
Why does this page differ from another tool?
Different pages often use different defaults, units, rounding rules, or assumptions. Align those settings before comparing outputs. If differences remain, compare each intermediate step rather than only the final number.
How reliable are the displayed values?
Values are computed in the browser and rounded for display. They are good for planning and educational checks, but for regulated or high-stakes decisions you should validate assumptions with official guidance or professional review.