Free Tool

Schedule a Meeting Across Time Zones — Even When There Is No Overlap

Schedule a meeting across time zones by adding every participant to the planner below, checking the 24-hour overlap strip for the window with the most working-hours coverage, and — when no window covers everyone — applying one of the fallback rules on this page: rotate the inconvenient slot, or replace the meeting with an async handoff instead of forcing a live call.

Participants
#1
Proposed Meeting Time
Working Hours Window

Overlap finder highlights hours where all participants fall within this window.

Local times

ParticipantTime zoneLocal timeWorking hours
My locationEurope/MinskSun, Jul 26, 10:00In window

24-Hour Overlap Finder

Each block represents one hour of the day in the base participant's time zone. Green means all participants are within working hours. Amber means partial overlap. Neutral means no one is in their window.

00:000/1
01:000/1
02:000/1
03:000/1
04:000/1
05:000/1
06:000/1
07:000/1
08:000/1
09:001/1
10:001/1
11:001/1
12:001/1
13:001/1
14:001/1
15:001/1
16:001/1
17:001/1
18:000/1
19:000/1
20:000/1
21:000/1
22:000/1
23:000/1
All in windowPartial overlapNo overlap

Rules for Scheduling a Distributed Team

The overlap strip above tells you how much shared working time your team has. These rules cover what to do with that answer — whether it is three green hours or none at all.

Protect the overlap window you do have

If the overlap strip above shows even one or two green hours, treat that window as scarce and reserve it for meetings that genuinely need real-time discussion — decisions, planning, or anything with back-and-forth. Move status updates and one-way information out of it.

Rotate the inconvenient slot

When every option requires someone to join early or late, alternate who takes the bad slot on a fixed schedule — for example, every other week — instead of defaulting to the same region every time. Put the rotation directly on the recurring calendar invite so nobody has to renegotiate it.

Replace status meetings with an async handoff

A meeting that exists only to relay information does not need a live audience. Replace it with a short recorded update or written summary on a fixed cadence — what happened, what was decided, what is blocked — and reserve the live slot for topics that actually require discussion.

Use core hours for decisions, not updates

If your team has any shared window at all, reserve it explicitly for decisions that need every stakeholder present. Publish a short list of "core hours" so the whole team knows which slot is protected and stops scheduling status syncs into it by default.

Confirm the time zone in every invite title

Ambiguous invites ("10am call") are a common source of missed meetings across regions. Put the time zone abbreviation or a UTC reference directly in the calendar invite title, not just the body, so it survives forwarding and calendar app time zone auto-conversion mistakes.

Record and summarize the meetings people miss

For distributed teams, someone is always asleep during any given meeting. A recording with an automatic summary and action items — which is what MeetWave generates from a meeting without a bot joining the call — lets people who could not attend catch up in minutes instead of asking around for a recap.

Curious exactly how little overlap common pairs like New York and Sydney actually have? See the world clock meeting planner for the standard-hours overlap table, or the time zone meeting planner for why that overlap shifts during daylight saving transitions.

Why Use This Time Zone Converter Meeting Planner?

  • One time zone converter meeting planner for any team size or spread
  • DST-safe — uses the browser's Intl API so daylight saving changes are handled automatically
  • 24-hour overlap strip finds the widest shared working-hours window in one pass
  • Concrete fallback rules for teams with no meaningful overlap, not just a converter
  • Shareable link encodes all inputs (no personal data) so the whole team sees the same plan
  • Copy summary exports a plain-text block ready to paste into Slack, email, or a calendar invite
  • 100% private — no data is sent to any server; everything runs in your browser
  • Works for any combination of cities, teams, or countries across all IANA time zones

Frequently Asked Questions

Add every participant to a time zone planner with their IANA time zone, propose a candidate time, and check the results against each person's working hours. Then scan a full 24-hour overlap view rather than testing a handful of times by hand — the widest shared working-hours window is usually not the first time anyone suggests.

A time zone converter meeting tool converts a single proposed time into every participant's local equivalent, the same job a basic converter does for one pair. The planner on this page extends that into a full team view plus a 24-hour scan, so you get one shared window recommendation instead of manually converting each participant one at a time.

When the overlap strip shows no hour with full coverage — common for teams split across the US and Asia-Pacific — two approaches work well. First, rotate the inconvenient slot: alternate which region takes the early-morning or late-night call so the burden is shared rather than falling on the same people every time. Second, replace some live meetings with an async handoff — a recorded update, a written summary, or a shared document — so only decisions that truly need real-time discussion get a live slot at all.

Pick a fixed rotation — for example alternate weekly between a time that is morning for Region A / evening for Region B, and a time that is evening for Region A / morning for Region B. Put the rotation on the recurring calendar invite itself so nobody has to remember or renegotiate it each week, and confirm the current week's time in the invite title to avoid mix-ups.

A good async handoff replaces a status-update meeting with a short recorded video or written summary covering what happened, what was decided, and what is blocked — sent on a fixed cadence so it does not require a live audience. Tools that automatically produce a summary and action items from a recorded call, such as MeetWave, make this easier to sustain because no one has to write the update by hand after an already-long day.

Yes, completely free. Add participants, pick a time, and share the link — no account, no sign-up, and no usage limits. Everything runs in your browser.

Catch Up on Meetings You Missed

MeetWave records your Zoom, Teams, and Google Meet calls locally — then generates AI summaries and action items automatically, so teammates in a different time zone can catch up in minutes. No bot joins your call. Privacy-first, works on Windows — there is no macOS or mobile version yet.