Meeting Planner

The meeting planner finds hours when two cities both fall inside a typical 9:00 AM–5:00 PM work band on a date you choose. Pick city A, city B, and the meeting day; the tool walks the UTC timeline and lists overlapping local hours so you can propose a call that is reasonable on both sides. It complements live boards on the world clock when you are planning a future slot rather than reading the current hour in each city.

Planner versus live world clock

The world clock shows what time it is right now in each city. This page searches forward on a specific calendar date for mutual daytime overlap. Use event time when you already have one timestamp and need it translated into another city. Broader city search lives on the time zone converter hub from time tools.

Planning on the actual meeting date matters because daylight saving offsets can differ from last month’s offsets. Re-run the planner if your first choice date falls on a holiday in either city—local closures are not modeled, but human schedules still are.

How to read the overlap list

Select two cities and a date, then calculate. Results show local hours where both zones land between 9:00 and 17:00. Each line pairs city A and city B readings for the same UTC instant. Prefer slots that avoid very early mornings and very late evenings for both parties when you can.

If no comfortable overlap appears, rotate who takes the inconvenient hour, shorten the agenda, or switch to asynchronous updates. Three or more zones often require pairwise planning or picking one anchor city and converting outward with event time.

Daylight saving and travel

Spring-forward nights skip a local hour; fall-back nights repeat one. Meetings near those transitions deserve a second check with the daylight saving time page. Travelers should plan in the city where they will physically be on the meeting date, not their hometown zone.

Half-day holidays and Sunday–Thursday workweeks in some countries are not modeled here. Adjust manually when local norms differ from a Monday–Friday assumption.

Worked example: New York and Berlin

A sync is needed next Tuesday between New York and Berlin. The planner may show late morning Eastern aligning with late afternoon Central European Time. You propose 11:00 AM Eastern / 5:00 PM CET, confirm with both sides, and send a calendar invite with those zone labels—not only a screenshot of overlap.

A hiring panel spans San Francisco and Singapore where overlap is thin. They rotate who takes the early or late slot across 2026 interview weeks and record decisions in writing for candidates who could not attend at a humane hour.

Inclusive scheduling habits

Rotate inconvenient slots across a quarter so one region is not always disadvantaged. Keep meetings shorter when overlap is awkward. Share an agenda early so scarce shared time is used well. Document outcomes for people who could not join live at a humane hour in their zone.

Before the call, open the world clock for a last-second sanity check if someone’s travel plans changed overnight.

After you pick a slot

Send a calendar invite immediately with zone-aware start times, dial-in or video link, and one sentence stating the zone assumption. Optionally attach a countdown link for high-stakes sessions. Reconfirm twenty-four hours ahead if DST or travel could shift someone’s local reading. Include the meeting title so invitees recognize the hold in crowded calendars.

If invitees decline because of hours, rerun the planner on an alternate date rather than forcing the same painful slot. A slightly delayed meeting with full attendance beats a poorly timed call that loses half the room to time-zone fatigue.

Prep time and follow-ups

Use the timer or Pomodoro timer to bound prep before international calls. Afterward, log billable duration with the hours calculator if you tracked clock-in and clock-out times.

Date-side scheduling—next weekday, deadlines, business days—lives on the date tools hub. Mark confirmed meetings on the 2026 yearly calendar when a printable overview helps the team.

Vendor demos and customer success

SaaS teams scheduling QBRs across continents run the planner before proposing three candidate slots in email. Customer success managers note which region took the early hour and rotate next quarter. Shorten default meeting length when overlap is only one or two hours wide for the chosen date.

Before the live session, open the world clock to confirm nobody's travel plans shifted their local zone overnight. Note the confirmed slot in your team channel so late joiners see the same time without reopening the planner.

Family and community calls

Holiday video calls spanning US and European relatives benefit from the same overlap scan used in business. Grandparents overseas may prefer late afternoon their time; younger households may cap calls before bedtime. The planner surfaces compromise hours without mental offset math or guesswork about daylight saving.

Understanding the nine-to-five model

Results assume a nine AM to five PM work band in each city on the selected date. Teams with shifted cores—ten AM to six PM, for example—should mentally adjust candidates rather than treating the list as exhaustive for every organization. Public-sector crews on four-tens schedules may need to scan adjacent hours manually when the overlap window is narrow.

After you confirm a slot, set a countdown to meeting start for speakers in multiple zones so everyone joins the bridge on time. Recruiters scheduling panels across 2026 hiring seasons should save the chosen slot in writing before time zones shift at the next DST boundary.

Related tools

Stay on time tools for clocks, stopwatch, and timers. Convert single instants on event time. Scan live times on the world clock before you send the invite. Log call duration afterward on the hours calculator when you tracked start and end clock times during the meeting itself.