Skip to the tool

Plan a meeting across time zones

Find the overlap in two to four cities and share that minute. How the meeting planner treats working hours and daylight saving.

Updated 8 min read

Date and time comparison
On this page

A meeting across cities fails in a small number of ways. Someone converts the hour and forgets the date. Someone uses a winter offset in July. Someone schedules 9:00 their time because it is polite, and it is 11:00 p.m. for the other person. A planner does not fix politeness. It does make the arithmetic visible, including the hours that are inside everyone’s working day and the hours that only feel reasonable from one chair.

Clockbeam’s meeting planner compares two, three, or four cities. The first city is the one whose clock you set. Working hours start at 9:00–17:00 in each city, and you can change that window. The shared band is the part of the day that sits inside every city’s window at the same moment. A time field then takes one minute and shows it in every selected city. Copy meeting link sends the cities, the working hours, the date, and the time. Opening the link restores that setup on this page. It does not create a calendar event, send an invite, or start a call.

If you only need to know what time it is in those cities right now, use the world clock instead. The planner is for a minute you are proposing, on a date.

Start from the cities, not from a favorite hour

Add the cities that will actually be on the call. Two is the minimum and four is the maximum. If a fifth person is in the same zone as someone already listed, you do not need a fifth row. Zones, not headcount, are what the page compares.

The first city is the reference for the time you type. If you think in Chicago hours, put Chicago first and set the clock there. Everyone else sees the converted minute. You can still read the shared band before you pick the minute. The band is often more honest than the hour you hoped for. A overlap that only exists at 8:00 in one city and 18:00 in another is a real overlap of the default windows only if you changed the windows to include those edges. With the default 9:00–17:00, the band is the stretch that is inside the workday everywhere at once.

Change the start or end hour when a group does not work 9 to 5. A team that starts at 10:00 should not be offered a 9:15 slot just because the default window contains it. The page will believe the hours you type. It does not know the office. Working hours stay inside one local day. A shift that crosses midnight is not a separate mode. If someone’s day runs 20:00 to 04:00, this planner will not draw that shift. Say so in the invite and do not force the window into a shape the page cannot represent.

When the windows do not overlap, the page says so. That is a useful answer. It means there is no minute that is inside every city’s stated workday. You then choose, on purpose, whose evening or whose morning you are spending. The tool should not hide that choice inside a cheerful green bar.

Read the minute in every city, including the date

Set the date, then set the hour and minute in the first city. Each other city shows that same moment in local time. Read the date on each row before you copy anything into a message. A 7:00 p.m. slot in one city can be the next morning in another. People miss calls by a day more often than they miss them by an hour, because the hour was converted and the date was assumed.

Write the proposal in one sentence that includes both ends: “Tuesday 16:00 in Chicago, which is Wednesday 07:00 in Sydney.” If you only write one side, the other person converts it again and you have two chances to be wrong. The copied link is a backup. It restores the cities, the hours, the date, and the proposed time for anyone who opens it. It is still worth putting the words in the email, because not everyone will click.

The link is a configuration. It does not reserve a room and it does not know who accepted. After people agree, the calendar you actually use is where the event should live. Clockbeam does not sync to that calendar.

Daylight saving, gaps, and hours that happen twice

Local offsets move when daylight saving starts or ends, and UTC does not. NIST notes that United States time zones and daylight saving time are regulated by the Department of Transportation, and that the rules have changed in the past. IANA’s time zone database is what software, including your browser, uses to apply those rules to a date. The planner uses that data. Today’s offset on the world clock is not automatically the offset on the Tuesday after the clocks change. Set the date and read the result.

Some local times do not exist. When a region springs forward, an hour is skipped. If you ask for a minute inside that gap, the planner shows the next valid minute. It does not invent a local time the zone never had. When a region falls back, one hour happens twice. If you ask for a minute inside that repeated hour, the planner shows the earlier one. The page says so. If you needed the later occurrence, you are in the ambiguous hour and you should say which one you mean in the invitation. “1:30 a.m. the second time” is an awkward phrase and a real one. Do not schedule a meeting there if you can avoid it.

These are the same kinds of edges the alarm page handles, but the alarm asks you to confirm a skipped minute or to choose the earlier or later repeated hour before you arm it. The planner’s rule is quieter: next valid minute in a gap, earlier minute in an overlap. Read the note. Do not assume the digits you typed survived unchanged on a transition night.

Regions that do not observe daylight saving time, such as most of Arizona and Hawaii, keep their standard offset while their neighbors move. A meeting that was comfortable in January can be an hour worse in July, or an hour better. Check the date you mean. A standing weekly call is the classic place this surprise lives. Reopen the planner on a date after the change instead of copying last month’s conversion.

A planning sequence that stays short

List the cities. Put the city you think in first. Set working hours to the real windows, not the default, if the default is wrong. Look at the shared band before you fall in love with a time. Pick a minute inside the band if one exists. If none exists, pick the least bad minute and say, in the message, whose non-work hour it is.

Read every city’s local time and date. Copy the link. Paste both the sentence and the link. Ask one person in each zone to confirm the local time they see, the first time you use the page with that group. After that, the confirmation is optional, but the sentence is not.

If the meeting itself needs a visible ending once people are in the room, that is a different tool. A countdown timer can run the length of the call. It does not know the zones. The planner’s job ends when the start time is agreed.

Open the tool

Frequently asked questions

What counts as overlapping working hours?

Each city contributes its own local window. The default is 9:00 to 17:00. The overlap is the part of the day that sits inside every window at the same moment. If you change a city’s hours, the band changes.

Does the shared link start the meeting?

No. It restores the cities, working hours, date, and proposed time on this page. It does not create a calendar invite or join a call.

Why did the minute I typed change?

The local time may fall in a daylight-saving gap or in an hour that happens twice. A gap moves to the next valid minute. A repeated hour shows the earlier one, and the page says so.

How many cities can I add?

Two, three, or four. A person in a zone you already added does not need another row.

Keep reading