---
name: tbt-event-list-to-calendar-file
description: "Specify time zones and event boundaries, then inspect actual import results for Turn a permitted event list into a calendar file with AI. Use permitted source material; this kit does not authorise external actions."
---

# Turn a permitted event list into a calendar file with AI

Specify time zones and event boundaries, then inspect actual import results.

Use the supplied source as authority. Check the account supports the actual file or image operation before attempting it.

## Task instruction

Create an iCalendar .ics file from the attached permitted event table.
Use the supplied named time zones and dates, not my device's assumed zone.
Ask about missing or ambiguous dates before generating an event.
Give each event a stable unique UID and preserve it when revising that event.
For each row, show the source start/end, the encoded start/end and whether
it is timed or all-day. Escape text correctly and use valid .ics line endings.
Do not add attendees, organisers, reminders or invitations unless supplied.
Return the actual file and the mapping table.

## Source boundaries

- 12 Nov 2026, 13:00–14:00 London
- 13 Nov all-day
- All-day end is 14 Nov exclusive

## Review and correction

Check the actual .ics and then a permitted test import separately. This sample has not been imported into a real calendar account.

Event [source ID] covers [last included date]. Its all-day DTEND must be
the following date, because the end is exclusive. Correct that field,
retain the event UID and all other source facts, and return a fresh file
plus a concise list of changes. Do not silently revise other events.

Use references/practice-source.json for the labelled example. The practice HTML is a local teaching tool; it does not call an AI service. Apply this method to the user's supplied facts rather than copying fictional example values. Do not infer approval or permission to publish.