Time zone guides

Find a 30-minute meeting time across three studio schedules

·

A meeting start is useful only when its full duration fits the intended working windows. Compare the continuous overlap first, then choose a start on a practical scheduling grid.

Meeting Time Zone Planner

Find the studios' common working window

Load the example and select Find meeting times. The search covers November 2, 2026 UTC. New York enters 09:00–17:00, London 13:00–18:00 and Delhi 18:00–22:00 in their local zones.

The continuous common window runs from 14:00 to 16:30 UTC. With a 30-minute meeting and 30-minute step, five starts fit everyone. Another five starts fit a majority.

IANA Time Zone Database practice for civil-time offsets

Read the first match in each local clock

The first start for everyone is 14:00 UTC. The local start table shows 09:00 in New York, 14:00 in London and 19:30 in Delhi.

Check the UTC timeline at 16:00 and 17:00. Three people can attend the full 30-minute slot at 16:00. Two can attend at 17:00. Use the local dates and zone identifiers when sharing the chosen time.

IANA Time Zone Database practice for civil-time offsets

Account for an overnight work window

Set a participant's work times to 22:00 and 02:00. The window ends on the following local date. Use local weekdays only to include windows starting on Monday through Friday in each participant's zone.

If a local clock jumps past a boundary time, the planner lists the skipped work window. Export the meeting report to keep the search dates, common windows and matching UTC starts.

IANA Time Zone Database practice for civil-time offsets

Common questions

Does the hour grid replace the slot list?

The grid reports meetings that start on each UTC hour. Preview matching starts and the export include all matching starts on your configured slot grid.

What changes if I request a longer meeting?

The common working window stays the same. Fewer start times may fit the full longer duration.

Sources

Put it into practice.

Related guides