Recheck the date, then carry the instant into a calendar
Named zones and fixed UTC events solve different parts of the task.
Choose a named zone
A name such as America/New_York identifies a rule set. A fixed offset such as “UTC−5” does not describe every date in a place that changes clocks. OverlapAtlas uses your browser's time-zone data for the selected date; it does not fetch a live rule service.
Missing and repeated wall-clock hours
Clock changes can skip or repeat local times. Candidates are generated from real UTC instants, so the repeated hour can appear twice with different offsets. The local table includes the offset to distinguish them. Meeting duration is elapsed time, which may differ from subtracting the two displayed wall-clock hours on a clock-change day.
A single event, not an invitation
The downloaded ICS file contains one UTC DTSTART and DTEND. It does not connect to your calendar, add attendees, send invitations or create a repeating meeting. Importing it is your choice. A calendar app will display the same instant in its configured zone.
The CSV is a selected-time report. JSON preserves editable people and settings. Files are created locally and may contain the names you entered; review them before sharing. No automatic save exists. Close or refresh the tab and an unsaved plan is lost.
Keep the source of truth clear
Availability here means inside manually entered windows, not “free in someone's calendar.” Browser time-zone data may change, and distant future rules can change politically. Recheck the chosen date and confirm important meetings with participants. For technical background, see Intl.DateTimeFormat and the iCalendar specification.