Should a recurring meeting use fixed UTC?

Only when it must follow an absolute instant. Use a named IANA zone when the meeting should stay at a local wall-clock time.

What happens when an occurrence falls on a holiday?

Choose before expansion whether to skip it, move it to a valid workday, or retain it, and document that policy.

How do I verify an ICS file?

Inspect its recurrence and time-zone properties, import it into a test calendar, and compare ordinary, boundary, daylight-saving, and holiday occurrences.

Recurring Calendar and ICS Scheduling

Recurring Calendar and ICS Scheduling | Elysia Tools

Define the scheduling contract

Record a local start, IANA time zone, duration, attendees, recurrence rule, and explicit end condition. Decide whether the event follows a local wall-clock time or an absolute instant; this controls daylight-saving behavior.

Expand before exporting

Turn the recurrence into concrete dates and inspect month boundaries, daylight-saving transitions, and the final occurrence. Apply an explicit weekend and holiday policy, convert representative times for participants, and compare the results with busy intervals.

Verify the ICS round trip

After accepting the expanded schedule, inspect recurrence, time-zone identifier, duration, and event identity. Import the file into a test calendar and compare the rendered events, especially around time changes and exceptions.

Before you start

Have the start, duration, recurrence pattern, participants, and authoritative IANA time zone.
Collect workday rules, holiday calendars, busy intervals, and target-calendar ICS requirements.

Workflow playbook