How to Schedule a Multi-City Web Meeting (Free Online Planner)

schedulingtoolsmulti-timezone

Scheduling a one-on-one across two time zones is annoying. A multi-city web meeting — three cities, four team members, five time zones — is a different category of problem.

The core problem: nobody agrees on “morning”

When you write “let’s meet Thursday morning,” you’ve said nothing useful to a distributed team. 9am in Berlin is 3am in San Francisco. The only shared reference point is UTC, and nobody thinks in UTC naturally.

The solution is a visual overlap map: plot every participant’s work day on the same 24-hour axis and find the intersection.

Step 1: Collect all locations

Before touching a scheduling tool, write down every city (or timezone) that needs to attend. Group people by timezone — three teammates in Berlin count as one timezone entry.

Example roster:

Alice & Bob → San Francisco (America/Los_Angeles)
Chen → Austin (America/Chicago)
Priya → Bangalore (Asia/Kolkata)
Lars → Stockholm (Europe/Stockholm)

Step 2: Load them into a visual planner

Open meetwhen and add each timezone. Switch to Find view to see the overlap scoring. The tool marks each hour as:

Work (green) — within a standard 9–5 window
Morning/Evening (yellow/orange) — adjacent hours some people keep
Night (dark) — outside reasonable availability

Hours where all timezones show green or yellow are your candidates.

For the example above — San Francisco, Austin, Bangalore, Stockholm — the overlap is tight. The best window is typically 8–9am Central (Austin) which lands at:

6–7am Pacific (San Francisco) — early but doable
3–4pm CET (Stockholm) — mid-afternoon
7:30–8:30pm IST (Bangalore) — end of evening

Step 3: Propose two or three slots, not one

Never send a single proposed time to a multi-city group. Send two or three options from your overlap window. Let each participant vote. Tools like meetwhen let you share a URL that shows any recipient the times in their own timezone — paste that URL into your poll or invite description.

If you don’t yet know your overlap window and need to collect availability first, Align lets each participant mark their open windows across a date range. The results heatmap shows which slots work for the most people, so you’re proposing from real data rather than guessing.

Step 4: For tight or no overlap, rotate the burden

Some city combinations have zero clean overlap. San Francisco ↔ Singapore is a classic: the best available slot still puts someone at 6am or 10pm.

When that’s the case:

Acknowledge it explicitly — don’t pretend a 6am call is convenient.
Rotate who takes the bad slot each week. Keep a shared log.
Consider async alternatives (recorded update + written Q&A) for lower-urgency meetings.

Step 5: Encode the time in the invite

The most common scheduling failure is writing times like “3pm EST” in a calendar invite. EST and EDT are different things, and your team spans people who know that and people who don’t.

Use your calendar’s timezone field (every major calendar supports it), or paste a meetwhen share link so each recipient sees their local time. Ambiguity is what causes people to show up an hour late.

Quick-reference: city pairs worth bookmarking

If you run recurring multi-city meetings, bookmark the meetwhen comparison page for your specific cities:

Each page opens the tool pre-loaded with those two cities so you can jump straight to the overlap view.