CSV / timezone / calendar
Turn a timezone CSV into ICS and a change list. Use the explicit offset on each schedule row to normalize it to UTC, then review the source CSV, ICS, and changes from the previous version in your browser. Nothing is registered with an external calendar.
Check current and previous CSV Fixed input: id,title,start_local,end_local,offset. Use YYYY-MM-DDTHH:mm and an explicit offset such as +09:00.
Synthetic fixture Three rows cover multiple offsets and a date boundary. In the previous version, event-002 changes and event-004 is removed.
id,title,start_local,end_local,offset
event-001,Tokyo handoff,2026-10-01T09:00,2026-10-01T10:00,+09:00
event-002,New York review,2026-09-30T20:00,2026-09-30T21:30,-04:00
event-003,London follow-up,2026-10-02T23:30,2026-10-03T00:15,+01:00 Output boundary ICS is saved as UTC events. The source CSV is the current input version. The change list contains added, removed, and changed IDs. No external calendar write, invite, or sync occurs. Open the existing workday planner
About timezones This guide does not infer region names automatically. For daylight-saving rules or organization-specific calendars, verify the explicit offset and the resulting output before use.