Why are some weeks weird in March or November?

Daylight-saving start/end dates differ across regions. US DST starts on the second Sunday of March; EU on the last Sunday of March. For roughly three weeks each spring, US-to-EU offsets shift by an hour from their usual values. The widget computes offsets at the chosen date, so it gets these transitions right.

Can I save a configuration?

Not yet. The widget is stateless; refresh and you lose the zones. Bookmark the URL and the widget will load defaults each time — if you need persistent multi-zone scheduling, a calendar app like Cal.com or Calendly handles that better.

What about half-hour zones like India (UTC+5:30)?

Fully supported. The grid shows hours in each zone; India will display the same hour your local clock does even though the offset is non-integer.

Why does the grid show a different date in some cells?

When a cell crosses midnight in a zone, it's technically a different calendar date there. Hover the cell to see the full timestamp.

Are working hours configurable?

Currently fixed at 09:00-17:00 — the conventional 8-hour office day. The most-requested zones in distributed teams use that window. If you need different working hours (early-bird, late-shift), use our time zone converter for individual time conversions.

Meeting Planner

Pick the cities. The grid paints the overlap. No spreadsheet required.

The grid below shows the next 24 hours, hour by hour, across every zone you add. Each zone’s working hours (09:00-17:00) are highlighted; the cells where everyzone is in working hours simultaneously are painted green. That’s your scheduling window. The widget uses the browser’s IANA timezone database, so daylight-saving transitions are handled automatically — including the three-week period each spring when US and EU DST schedules don’t align.

Reference date

Add zone

Working hours: 09:00-17:00 in each zone. Common overlap shown in green.

Zone	00	01	02	03	04	05	06	07	08	09	10	11	12	13	14	15	16	17	18	19	20	21	22	23
Los Angeles	00	01	02	03	04	05	06	07	08	09	10	11	12	13	14	15	16	17	18	19	20	21	22	23
New York	03	04	05	06	07	08	09	10	11	12	13	14	15	16	17	18	19	20	21	22	23	00	01	02
London	08	09	10	11	12	13	14	15	16	17	18	19	20	21	22	23	00	01	02	03	04	05	06	07
Mumbai / Delhi	12	13	14	15	16	17	18	19	20	21	22	23	00	01	02	03	04	05	06	07	08	09	10	11

working hours in that zone overlap window (all zones working)

How to use

Pick a reference date
Defaults to today. Change it to a future date to handle a DST transition or a long-weekend-affected week.
Add zones
Up to 6 zones (the default 4 cover most distributed-team configs: LA, NYC, London, Mumbai). Add or remove from the dropdown.
Read the green column
Green cells are the overlap window. Cyan cells are working hours in that specific zone. Greyed cells are out-of-hours for everyone or nearly everyone.

Common team-shape overlaps

Team shape	Overlap	Notes
SF + NYC	11am-5pm PT / 2pm-8pm ET	6h overlap; ample
SF + London	8am-9am PT / 4pm-5pm BST	1h. SF mornings, London end-of-day.
SF + Berlin	None during standard hours	SF 8am = Berlin 5pm.
NYC + London + Berlin	9-11am ET / 2-4pm BST / 3-5pm CEST	2h. Classic transatlantic.
London + Mumbai	9am-1pm BST / 1:30-5:30pm IST	4h. Most generous Eurasian pair.
SF + Sydney	None during standard hours	SF 3pm = Sydney 8am next day.

Frequently asked questions

Why are some weeks weird in March or November?: Daylight-saving start/end dates differ across regions. US DST starts on the second Sunday of March; EU on the last Sunday of March. For roughly three weeks each spring, US-to-EU offsets shift by an hour from their usual values. The widget computes offsets at the chosen date, so it gets these transitions right.
Can I save a configuration?: Not yet. The widget is stateless; refresh and you lose the zones. Bookmark the URL and the widget will load defaults each time — if you need persistent multi-zone scheduling, a calendar app like Cal.com or Calendly handles that better.
What about half-hour zones like India (UTC+5:30)?: Fully supported. The grid shows hours in each zone; India will display the same hour your local clock does even though the offset is non-integer.
Why does the grid show a different date in some cells?: When a cell crosses midnight in a zone, it's technically a different calendar date there. Hover the cell to see the full timestamp.
Are working hours configurable?: Currently fixed at 09:00-17:00 — the conventional 8-hour office day. The most-requested zones in distributed teams use that window. If you need different working hours (early-bird, late-shift), use our time zone converter for individual time conversions.

About

Why 09:00-17:00

The 8-hour workday is the global default for office-style remote work. Some teams (creative agencies, ops) shift it; others (early-bird startups) start earlier. The widget uses 09:00-17:00 because that's where the maximum overlap is for most cross-zone team configurations. If your zone's effective working hours are different, treat the 'working hour' shading as a baseline and adjust mentally.

When the overlap is empty

Pacific time and Australian Eastern time overlap by zero hours during standard working hours. The fix isn't a meeting time — it's an async-first workflow: written status updates, recorded video summaries, shared documents with comments. Reserve synchronous time for genuinely-collaborative work (decisions, design reviews) and even then, expect one side to be at the edge of their work window.