Time Zone Meeting Scheduler

Visually find the "Golden Hours" for globally distributed teams.

Struggling to find a time to meet with a globally distributed team? Add your participants below, and we'll map out a 24-hour day to find the Golden Hours where everyone is awake and in standard business hours (8 AM - 6 PM).

Participants

Alice (Host)
America/New York
Bob
Europe/London
Charlie
Asia/Tokyo
Timeline
0:00
utc
1:00
utc
2:00
utc
3:00
utc
4:00
utc
5:00
utc
6:00
utc
7:00
utc
8:00
utc
9:00
utc
10:00
utc
11:00
utc
12:00
utc
13:00
utc
14:00
utc
15:00
utc
16:00
utc
17:00
utc
18:00
utc
19:00
utc
20:00
utc
21:00
utc
22:00
utc
23:00
utc
Alice (Host)
New York
8:00PM
9:00PM
10:00PM
11:00PM
12:00AM
1:00AM
2:00AM
3:00AM
4:00AM
5:00AM
6:00AM
7:00AM
8:00AM
9:00AM
10:00AM
11:00AM
12:00PM
1:00PM
2:00PM
3:00PM
4:00PM
5:00PM
6:00PM
7:00PM
Bob
London
1:00AM
Sat
2:00AM
Sat
3:00AM
Sat
4:00AM
Sat
5:00AM
6:00AM
7:00AM
8:00AM
9:00AM
10:00AM
11:00AM
12:00PM
1:00PM
2:00PM
3:00PM
4:00PM
5:00PM
6:00PM
7:00PM
8:00PM
9:00PM
10:00PM
11:00PM
12:00AM
Sun
Charlie
Tokyo
9:00AM
Sat
10:00AM
Sat
11:00AM
Sat
12:00PM
Sat
1:00PM
2:00PM
3:00PM
4:00PM
5:00PM
6:00PM
7:00PM
8:00PM
9:00PM
10:00PM
11:00PM
12:00AM
Sun
1:00AM
Sun
2:00AM
Sun
3:00AM
Sun
4:00AM
Sun
5:00AM
Sun
6:00AM
Sun
7:00AM
Sun
8:00AM
Sun
Golden Hour (Everyone awake)
Fair (<1 person outside hrs)
Business Hrs (8am-6pm)

How to Use

1

Add all participants with their time zones

Select each team member's IANA timezone from the dropdown and add them to the scheduling grid.

2

Review the 24-hour timeline visualization

See color-coded blocks showing each participant's business hours, off-hours, and sleep windows across the full day.

3

Identify the Golden Hours overlap

Find the time columns where all participants show green business-hours blocks simultaneously.

4

Choose the best or least-bad meeting time

If no perfect overlap exists, select the window that minimizes off-hours burden across the team.

What are Golden Hours?

Golden hours are the time slots during the 24-hour day where all participants across different global timezones are awake during standard business hours (typically 8AM to 6PM local time).

Real-World Examples & Use Cases

Distributed Engineering Team Standups

Software teams spread across multiple continents need a daily standup time that works for everyone. A team with members in San Francisco (UTC-8), London (UTC+0), and Bangalore (UTC+5:30) has only a narrow window where all three are in business hours simultaneously. San Francisco 8 AM = London 4 PM = Bangalore 9:30 PM. The meeting scheduler visualizes this overlap immediately, showing that either San Francisco needs an early standup or Bangalore participates in the evening — helping the team make a fair, informed decision.

International Client Calls and Sales

Account managers and sales teams working with clients in different regions need to schedule calls without forcing clients to join at unreasonable hours. Knowing that a New York–Tokyo call inherently requires someone to be outside business hours, the scheduler identifies the least-bad options: Tokyo 8 AM = New York 7 PM, or New York 8 AM = Tokyo 10 PM. This helps account managers offer clients slots that are inconvenient for themselves rather than the client, improving satisfaction and professionalism.

Remote Work Policy and Scheduling Guidelines

HR teams and managers building remote work policies need to understand the timezone landscape of their teams. If a company has staff from Los Angeles to Warsaw, the scheduler reveals the realistic overlap window and whether a 'core hours' policy (e.g., all staff available 10 AM–2 PM in a reference timezone) is feasible. It also helps set expectations: teams spanning 12+ time zones like US West Coast and Southeast Asia face near-zero mutual business hours and require asynchronous-first communication policies.

Conference and Webinar Global Scheduling

Event organizers hosting live webinars, online conferences, and virtual workshops for global audiences need to choose time slots that maximize attendance. The meeting scheduler shows which time slots reach the most participants in their business hours. A single 60-minute webinar slot inevitably disadvantages some regions — the tool helps organizers decide whether to run two sessions (morning Americas/Europe and morning Asia-Pacific) or identify a single compromise slot that works reasonably well across target regions.

How It Works

Golden Hours Calculation Logic: Core algorithm: 1. Convert each participant's timezone offset to UTC at the current date (accounting for DST using IANA timezone database) 2. For each hour H from 0 to 23 (UTC): a. Convert H to each participant's local hour: localHour = (H + tzOffsetHours + 24) % 24 b. Check if localHour falls within business hours: isBusiness = 8 <= localHour <= 18 (configurable) isSleep = 23 >= localHour >= 7 (overnight sleep window) 3. Golden Hour = UTC hour where ALL participants have isBusiness=true 4. Acceptable Hour = UTC hour where isSleep=false for ALL participants Timezone offset considerations: - Offsets are not always whole hours: India (UTC+5:30), Nepal (UTC+5:45), parts of Australia (UTC+9:30), Iran (UTC+3:30) - DST shifts occur on different dates in different countries (US/Canada spring-forward and fall-back dates differ from EU dates) - IANA timezone database (via Intl.DateTimeFormat API in browsers) provides the correct offset for any timezone at any date Antipodal timezone example (near-zero overlap): New York (UTC-5) and Tokyo (UTC+9) are 14 hours apart NY 8AM (business) = Tokyo 10PM (sleep) ❌ Tokyo 9AM (business) = NY 7PM (evening, acceptable?) ✓ minimal overlap

Frequently Asked Questions

What exactly are 'Golden Hours' for meetings?
Golden hours are the time windows during the 24-hour day when all meeting participants are simultaneously within their standard business hours (typically 8 AM to 6 PM local time). During golden hours, everyone joining the meeting is in their normal workday — no one is asked to attend before breakfast or after dinner. For teams with close timezones (e.g., all in Europe or all in North America), golden hours are usually plentiful. For teams spanning 10+ time zone difference, golden hours may not exist at all.
What do I do when there are no Golden Hours?
When no time slot puts all participants in business hours simultaneously, look for 'acceptable hours' — windows where everyone is at least awake, even if outside normal business hours. The next-best approach is rotating meeting inconvenience: alternate who gets the awkward time slot so no single person always bears the off-hours burden. For recurring meetings, some teams split into regional syncs and use async updates (recorded video, written summaries) to bridge the gap rather than forcing a poorly-timed global meeting.
How does the scheduler handle Daylight Saving Time?
The scheduler uses IANA timezone names (like America/New_York or Europe/London) rather than fixed UTC offsets like UTC-5. IANA timezones encode the full history of DST transitions for each region, so the calculated offsets automatically adjust when DST changes occur. This matters because the US and Europe change their clocks on different dates — meaning the offset between New York and London is 5 hours in winter but only 4 hours for a few weeks each spring and fall when the transitions don't align.
Why is scheduling between the US West Coast and Asia so difficult?
Los Angeles (UTC-8 in winter) and many Asian cities have offsets making them nearly 180 degrees apart on the 24-hour clock. Tokyo (UTC+9) is 17 hours ahead of LA. Singapore (UTC+8) is 16 hours ahead. When it's 9 AM Monday in Singapore (business hours), it's 5 PM Sunday in LA (weekend). The single viable window is Tokyo/Singapore early morning (around 8-9 AM) = LA late afternoon (around 4-5 PM the previous day). Many cross-Pacific teams accept that one side will always be outside core business hours.
What is the difference between a timezone offset and a timezone name?
A timezone offset (like UTC+5:30) is a fixed number representing how far ahead or behind UTC a clock is set right now. A timezone name (like Asia/Kolkata or America/Chicago) is a geographic identifier that maps to the correct UTC offset at any given date and time, including DST transitions. Always use timezone names for scheduling tools — an offset of UTC-5 is correct for New York in winter but wrong in summer (when New York becomes UTC-4). Using timezone names ensures DST is handled automatically and correctly.

Related Tools

Explore other tools in this category.

Looking for something else?