Meeting Time Planner

About Meeting Time Planner

How It Works

Each participant's working window is projected onto a shared UTC axis, and every UTC hour is tested to see if all participants are within their local working hours at that moment. The longest contiguous run of "all available" hours becomes the best window.

Step	Action	Details
1	Add a participant	Enter a name, select a timezone, and set their working hours (default 9 AM - 5 PM)
2	Repeat for each person	Add as many participants as needed - the timeline updates live
3	Read the timeline	Each person gets a coloured bar showing their available window
4	Find the overlap	Green highlighted sections in the overlap row show when everyone is available

Worked example: A team has Alex in London (UTC+0, 9-5) and Priya in Mumbai (UTC+5:30, 9-5). Projecting both onto UTC, Alex is available 09:00-17:00 UTC, Priya is available 03:30-11:30 UTC. The intersection is 09:00-11:30 UTC - a 2.5 hour window. That becomes 9:00-11:30 AM London / 2:30-5:00 PM Mumbai. Add Jordan in New York (UTC-5, 9-5 = 14:00-22:00 UTC) and the three-way overlap shrinks to 14:00-11:30 UTC, which is empty. Either the New York start moves earlier or the Mumbai end moves later to restore overlap.

Reading the Visual Timeline

Element	What It Shows
Participant bar	A coloured horizontal bar spanning their working hours in their local time
Grey areas	Hours outside a participant's working window
Overlap row	Summary row at the bottom showing hours when all participants are available
Green highlight	Valid meeting times where every participant's window overlaps
Hour labels	24-hour markers along the top of the timeline

Common Timezone Combinations

Here are overlap windows for some common city pairs, assuming standard 9 AM - 5 PM working hours in each location:

Participants	Offset Difference	Overlap Window (UTC)	Overlap Hours
London + New York	5 hours	14:00 - 17:00	3 hours
London + San Francisco	8 hours	17:00 - 17:00	0 hours (barely possible)
New York + London + Berlin	5-6 hours	14:00 - 17:00	3 hours
London + Mumbai	5.5 hours	09:00 - 12:30	3.5 hours
London + Tokyo	9 hours	09:00 - 09:00	0 hours (requires flex)
New York + Sydney	14-16 hours	Very limited	0-1 hours (requires flex)
San Francisco + Berlin	9 hours	17:00 - 17:00	0 hours (requires flex)

When there is no overlap with standard 9-5 hours, set custom working hours for participants who are willing to take an early or late call. Even 7 AM - 4 PM for one person can open up an overlap window.

Quick City Shortcuts

One-click buttons for common cities like New York, London, Tokyo, and Sydney let you add participants without scrolling through the full timezone list. The tool uses the Intl API for timezone data, which means it automatically accounts for daylight saving time transitions.

Tips for Scheduling Across Timezones

Tip	Why It Helps
Start with the widest gap	Find the overlap between the two most distant timezones first - if that works, everyone in between will too
Rotate meeting times	If one person always takes the early/late call, rotate the time weekly to share the inconvenience
Use 30-minute meetings	Shorter meetings fit into tighter overlap windows
Set flexible working hours	Not everyone works strict 9-5; enter each person's actual availability
Check DST transitions	Clocks change on different dates in different countries - an overlap that works today might shift by an hour next week
Record meetings for absentees	When no overlap exists, async alternatives (recorded meetings, written updates) may be better than forcing bad times

DST Considerations

Daylight saving time shifts happen on different dates around the world. The US "springs forward" in March, the UK in late March, and Australia in October (southern hemisphere). For about 3-4 weeks each year, the offset between some timezone pairs changes by an hour. The tool handles this automatically using the browser's Intl API, which includes up-to-date DST transition data. If you are scheduling a recurring meeting, double-check the overlap after any DST change.

When There Is No Overlap

For teams spanning more than 10-12 hours of timezone difference (e.g. San Francisco and Tokyo), there may be no overlap during standard working hours. Options include:

Approach	How It Works
Async updates	Replace live meetings with recorded video updates or written summaries
Rotating sacrifice	Alternate who takes the early/late call each week
Split meetings	Hold two shorter meetings at different times so each group has a reasonable hour
Overlap shift	One participant starts or finishes their day 1-2 hours outside normal hours

To check the current time in multiple cities right now, the world clock shows live clocks. For calculating work hours across a week, the time card calculator tracks shifts and overtime. All calculations run in your browser with nothing sent to any server.

Why Distributed Teams Need a Planner

Distributed work is no longer the exception. As of 2026, roughly 27% of full-time employees worldwide work fully remotely and another 52% work in hybrid arrangements, according to cross-industry surveys compiled by Robert Half and Toggl. Technology, finance, and professional services lead the shift, with tech firms reporting around 67% of staff primarily working from home. When a team spans three or four timezones, finding a single slot that respects everyone's family, commute, or legal working-hours contract becomes a real constraint - not a nice-to-have. Picking the wrong time quietly pushes one person into 6 AM or 10 PM every week, and that cost is paid in attrition.

How Browsers Compute the Offset

Modern browsers use the IANA Time Zone Database (also called the tz database or tzdata) to resolve named zones like Europe/London or Asia/Tokyo into a UTC offset for any given instant. The database is the authoritative source used by operating systems, programming languages, and cloud platforms, and ships a new release several times a year when governments change their DST rules. The tool exposes this via Intl.DateTimeFormat, which means the offsets shown reflect the user's machine at the current date - including whatever DST transitions are active today. If a country abolishes DST mid-year, the browser picks up the change once the OS tzdata is updated.

What Are the Best Overlap Windows for Common Team Maps?

Most distributed teams fall into one of a few predictable shapes. Knowing the typical overlap ahead of time saves a lot of guesswork when hiring into a new region.

Team Shape	Typical Overlap (9-5 each)	Practical Notes
US East + Western Europe	2-3 hours (afternoon US / late afternoon EU)	Most forgiving intercontinental map
US West + Western Europe	0-1 hours (needs flex)	One side starts early or stays late
Western Europe + India	3-4 hours (afternoon EU / afternoon IN)	Comfortable working middle
Western Europe + East Asia	0-1 hours	EU afternoon vs JP evening
US West + East Asia	1-2 hours (AM US / AM next day JP)	Date-line flip makes this confusing
India + East Asia	4-5 hours	Closest thing to a "normal" pairing
US + Australia East	0 hours standard	Practically requires async or flex

For the trickiest pairings (US West plus Tokyo, London plus Sydney), the healthy answer is usually async-first: keep live meetings rare and make written updates the default. The time zone converter is useful when you only need a single point-in-time check instead of a full overlap calculation.

How DST Gaps Break Recurring Meetings

For a few weeks each year, the offset between two regions changes because one country has switched to DST and the other has not. The classic cases are the US-UK gap in March (US springs forward about two weeks before the UK) and the US-Australia gap in October and November (Australia springs forward, then the US falls back). During these gap weeks, a "fixed" meeting time on the organiser's calendar will drift by an hour on every participant's clock. Calendar apps handle this correctly for zone-anchored events but not for floating ones. When setting up a recurring meeting for a global team, always anchor the event to a named timezone (usually the organiser's), not to a bare time string. Re-run the overlap check after each DST boundary to confirm the window has not shifted outside someone's working hours.

Timezone Quirks That Trip Teams Up

• Half-hour and quarter-hour offsets: India (UTC+5:30), Iran (UTC+3:30), Newfoundland (UTC-3:30), Nepal (UTC+5:45), the Chatham Islands (UTC+12:45). Tools that round to whole hours misreport these by 30 or 45 minutes.
• Countries with one zone spanning huge longitudes: China uses Asia/Shanghai nationwide despite covering five geographical zones. India likewise uses a single zone. Early or late meetings look very different depending on which city the person is in.
• Arizona, Hawaii, and most of Saskatchewan do not observe DST. The offset from the US East Coast changes by an hour twice a year relative to these regions.
• Southern hemisphere DST is inverted: Australia and New Zealand spring forward in September-October and fall back in April. European and North American DST is roughly opposite.
• The International Date Line: A meeting on Monday morning in San Francisco is already Tuesday morning in Sydney. Tools that display only the time without the date cause chronic confusion.

Common Mistakes to Avoid

• Assuming GMT and UTC are the same on calendars. GMT is a civil time zone the UK sits in during winter; it shifts to BST in summer. UTC is a fixed reference that never moves. If a calendar invite says "10 AM GMT" in July, whoever sent it likely meant BST.
• Using city names loosely. "9 AM New York" is fine; "9 AM Eastern" is ambiguous about EST vs EDT. Use an IANA zone name (America/New_York) in technical settings and let the software resolve DST.
• Letting one person always take the bad hour. Rotate the sacrifice. If a weekly all-hands is 7 AM for Tokyo one week, move it to 7 AM for London the next.
• Forgetting Fridays in Muslim-majority countries and Sundays in parts of the Middle East. Working weeks are not uniform. Some teams treat Friday afternoon as off and work Sunday morning.
• Not checking the date. "Tuesday 10 AM" in London is "Tuesday 7 PM" in Sydney, but "Monday 10 PM" Pacific is "Tuesday 4 PM" Sydney. Always send invites in the recipient's local date/time.

Async-First When Overlap Is Impossible

If the best contiguous window is zero hours, stop trying to force a meeting and redesign the rhythm. Common patterns: Loom-style recorded video updates swapped every 24 hours, a written shared doc that each timezone appends to during their day, a 15-minute "handover" only at the boundary between two overlapping regions, or split meetings where the organiser attends both so context survives. Teams that lean into async this way report fewer calendar conflicts and more written institutional knowledge - the meetings you do hold become higher quality because they are rarer.

Sources

• IANA - Time Zone Database
• MDN - Intl.DateTimeFormat
• Robert Half - Remote Work Statistics and Trends
• GOV.UK - When Do the Clocks Change
• NIST - Daylight Saving Time
• Wikipedia - List of tz Database Time Zones