Meeting Time Planner
Pick several locations and see when local times align for a call — including daylight-saving rules.
By Aryan Khan, Founder & Editor · Updated October 2026
For example, 9:00 a.m. in New York is 2:00 p.m. in London and 7:30 p.m. in Mumbai — a workable three-continent slot that survives most of the year, and the planner shows you the weeks when it does not.
How to use Meeting Time Planner
Somebody's midnight is hiding in your recurring invite. Find it before they do:
The Meeting Time Planner lines up several locations' local clocks for a candidate time so you can see when a call actually works for everyone. Add the cities, pick a time, and compare everyone's clock — daylight-saving rules included, since changeover weeks are where recurring meetings die.
- 1Add participant cities or zones.
- 2Pick a candidate UTC or local time.
- 3Compare everyone’s local clock.
What people use Meeting Time Planner for
1. Standing team calls
Set the recurring slot from the overlap, not from headquarters' convenience — and recheck it at the DST changeovers with the Daylight Saving Checker.
2. Family video calls
Three generations, three continents: the planner finds the kind hour — awake for the kids, not midnight for the grandparents.
3. Client and vendor calls
Proposing a time inside everyone's workday is basic courtesy made visible. Send the planner's result as the receipt.
4. Event and stream timing
A launch at 9:00 New York is 14:00 London and 19:30 Mumbai — prime time or dead air, depending on the audience you wanted.
Worked examples
9:00 New York (winter, EST) = 14:00 UTC = 14:00 London, 15:00 Berlin, 19:30 Mumbai. In summer New York's 9:00 becomes 13:00 UTC and London stays 14:00 (BST) — the slot survives, which is why it is a classic.
Add Sydney and the same slot lands at 1:00 a.m. (winter, AEDT next day). No single hour flatters four continents — rotate the pain or split the meeting; the planner makes the cost explicit instead of surprising.
One moment, five clocks
A winter weekday, 9:00 a.m. New York rendered everywhere — computed with standard-time offsets; the planner applies each city's live rules.
| City | Local time | Zone state |
|---|---|---|
| New York | 9:00 a.m. | EST (UTC-5) |
| London | 2:00 p.m. | GMT (UTC+0) |
| Berlin | 3:00 p.m. | CET (UTC+1) |
| Mumbai | 7:30 p.m. | IST (UTC+5:30) |
| Sydney | 1:00 a.m. next day | AEDT (UTC+11) |
Half-hour offsets (Mumbai) and date-line flips (Sydney) are why planners exist. DST weeks shift some rows by an hour — the planner's rules account for the date you pick.
Overlap beats guesswork across time zones
Remote teams waste meetings when someone joins at 11 p.m. by accident. A meeting planner converts one candidate moment into everyone’s local clock using real timezone boundaries, not fixed UTC offsets that ignore daylight saving.
Start from the person with the hardest constraints, then widen. If no humane overlap exists, the honest output is ‘split the session’ — better than a matrix of exhausted attendees.
How to interpret the result
The most common errors come from using a correct result to answer the wrong geographic question. Keep these points in mind for Meeting Time Planner:
- Check accuracy before trusting a GPS-derived answer: indoors, browser positioning can be off by blocks, which flips counties near borders. Zoom the map and nudge the pin by hand when the stakes are real — the tools here let every GPS result be corrected with a click.
- Prefer clicking the map over typing when you can: a placed pin is unambiguous, while a mistyped address can silently resolve to the wrong Springfield. When you must type, include the country for common town names and drop apartment numbers if the street fails — geocoders match best on street + city.
Limits & appropriate use
Every location stack has a competence boundary, and naming it is part of being trustworthy. OpenStreetMap's administrative coverage is excellent where mappers are active and thinner in rapidly changing or sparsely mapped regions; brand-new developments can lag, and disputed zones follow the community's de-facto consensus rather than arbitrating sovereignty. Postal layers add a second boundary: ZIPs and postcodes are delivery-routing systems, not geography, so PO boxes and carrier routes can legitimately disagree with the map. Indoor positioning adds a third: a browser fix can be a block off, which matters precisely at the borders where people ask these questions.
None of this makes the tools unsafe to use; it makes them safe to use *knowingly*. The design response is transparency: fields stay separate so layers never blur, empty answers are shown as empty rather than guessed, accuracy context travels with GPS results, and every page names its sources. For questions where the cost of being wrong is high — a property line, a legal filing, a medical dispatch — the escalation is always the same: licensed surveys, official registers and emergency services own those answers, and a good free tool points at the door instead of pretending to be it.
- Legal boundaries and property lines → licensed surveyor / county recorder.
- Mailing validity → the postal service's own address tools.
- Life-safety dispatch → official emergency services, never a map lookup.
Data & methodology
Participant coordinates are resolved to timezones locally; current browser timezone rules are used to find whole UTC hours within 09:00–17:00 local today. This is not a date-selectable scheduler.
For source details, licences and model limitations, see Data Sources and Methodology.
Key terms worth knowing
- Postal vs administrative city
- Mailing city follows postal routes; legal city follows municipal boundaries — they can differ.
- Accuracy radius
- The device-reported uncertainty of a GPS/network position, in metres.
Editorial guidance: MapBench explains the method and limitations so the tool can be used as a transparent reference, not as a black-box answer. For legal boundaries, safety-critical routing, surveying, engineering, regulated decisions or official statistics, verify the result with the responsible authority or a qualified professional.
Category: Location. Results are intended for everyday analysis and planning unless a page explicitly states otherwise.
Method, assumptions & limits
- This tool’s method
- Participant coordinates are resolved to timezones locally; current browser timezone rules are used to find whole UTC hours within 09:00–17:00 local today. This is not a date-selectable scheduler.
- Before relying on the answer
- Check the selected pin before reading the returned place or boundary label. Address labels, administrative areas and postal geography can disagree.
- What the result cannot establish
- For official jurisdiction or mailing decisions, confirm the result with the responsible local authority or postal service.
Coverage: Worldwide. Search, basemap and external data requests may use third-party services; browser-based does not mean every operation is offline. Read the source and licence notes, calculation methodology and privacy policy. If a result looks inconsistent, report a correction with the inputs and mode used.
Frequently asked questions
Clear answers about the calculation, accuracy and appropriate use.
DST included?
Yes — IANA timezone rules including daylight saving where applicable.
How many cities?
Add the places you need; results show local times side by side.
Can I use the tool without sharing my precise location?
Yes. Search a place, paste coordinates or click the map where supported. Browser location is optional.
Why might a boundary or place name look different elsewhere?
Administrative, postal and map datasets can use different boundaries, names and update cycles. Verify official decisions with the responsible authority.
Does MapBench store my browser location?
Public tools do not require an account. Location is used to produce the requested result; see the privacy and data-source pages for details.
Is DST included?
Yes — the planner applies each location's daylight-saving rules for the date, which is exactly the feature spreadsheets lack and changeover weeks punish.
How many cities can I add?
Several — enough for a genuinely global team. Beyond six or so, the overlap usually vanishes and the tool's honest answer is to rotate times or split the call.
What counts as a workable hour?
Your call — the planner shows clocks, you judge lives. A common courtesy band is 8 a.m. to 7 p.m. local; the table makes breaches visible.
Recurring meeting across a changeover?
The slot can shift for a few weeks between regions' change dates. Recheck in March and October — a calendar habit worth more than the tool.
Half-hour zones?
Handled exactly — Mumbai's :30 is arithmetic the planner does natively.
Can it send the invitation?
No — it finds the time. Your calendar sends the invite; paste the local times for each city into it as the courtesy receipt.
Related tools and resources
Rules behind it: the Daylight Saving Checker; overlap math: the Working Hours Overlap Calculator; conversions: the Timezone Converter.
More free tools
Sources, methodology & editorial trust
- ✓ Browser-first processing where supported
- ✓ External sources are documented
- ✓ No account required for public tools
- ✓ Review data sources
Calculations are documented with their assumptions, limitations and source context rather than presented as unexplained answers.
Reviewed and maintained by Aryan Khan, Founder & Editor of MapBench.
Part of our time zones hub
Meeting Time Planner sits in the time zones cluster, alongside 16 other tools that answer neighbouring questions with different methods or datasets.
You may also need
When this answer is only part of the job, these clusters cover the next step.
Read the guide behind this tool
How to Find the Time Zone for Any Coordinates — Why a longitude is not a time zone, how the tz database resolves an offset for a coordinate, and how daylight saving changes the answer twice a year.