The planner converts each location's available hours on the selected date to the same timeline, then finds the intervals included in every location's availability. Only the shared intersections are highlighted as possible meeting windows.
IANA time zones apply the offset rules for the selected date, so a location may show daylight saving time on one date and standard time on another. This avoids treating a city as if it always had one fixed UTC offset.
Set a separate start and end time for each location to reflect different schedules. The share link carries the selected date, time, zones, and availability, so another person can open the same planning view and review the proposed window.
Common questions and answers about this topic.
Yes. The planner applies each IANA time zone's rules for that date. A city can therefore have a different UTC offset in summer and winter, and its local time is recalculated when you change the date.
Yes. Set the available start and end time separately for every time zone. The overlap result updates to include only the intervals that fit all selected schedules.
Try another date, widen one or more availability ranges, or remove a time zone that is not required for this meeting. No overlap simply means that the current settings do not share one interval across every selected location.
The URL includes the selected date, selected time, IANA time zones, and each location's availability. If someone opens a link with missing or invalid values, the planner ignores the shared settings and keeps its current safe settings.
An IANA zone such as America/New_York carries date-based time rules, including daylight saving time changes. A fixed offset such as UTC-5 cannot describe every date correctly when a region changes between daylight saving time and standard time.
No. It compares time zones and creates a shareable planning URL, but it does not write to a calendar. After agreeing on a time, add the event to your calendar separately.