Lorixen.
EN

A calendar feed customers subscribe to: timetables in .ics

Short answer: If your business publishes a timetable, fixture list or events programme, such as gym classes, swimming lessons, matches or workshops, you can offer it as a calendar feed: a single URL ending in .ics that customers add to Google Calendar, Apple Calendar or Outlook once. Their calendar then checks the feed for changes, so updates and cancellations appear without anyone re-downloading anything. Build it from the same data as your website, give every event a permanent unique ID, mark cancellations rather than deleting them, and set honest expectations about how often calendars refresh.

Download versus subscribe

Many sites already offer an "Add to calendar" button for a single event, which downloads one .ics file. That is fine for a one-off booking, but it is a snapshot: if the class moves to Thursday, the customer's calendar still says Wednesday.

A subscribed feed is different. The customer adds a URL, and their calendar app fetches it again periodically. Google Calendar's help pages describe the route: under "Other calendars", choose to add a calendar from a URL, enter the address of the published calendar and click add. The feed then appears in their list alongside their own calendars, and they can hide or remove it at any time.

For a business with a changing schedule, subscription saves both sides work. Members stop asking "is Tuesday's session still on?", and you stop sending reminder emails about routine changes.

What goes into the feed

The format is iCalendar, defined in RFC 5545. A feed is a text file containing a calendar object with one VEVENT entry per event. The essentials:

  • PRODID, identifying the software that produced the calendar. RFC 5545 says it must be specified once in an iCalendar object.
  • UID for each event. The RFC defines it as the persistent, globally unique identifier for the calendar component, and requires it in each VEVENT.
  • DTSTAMP, when the entry was generated, plus DTSTART and DTEND for the event times.
  • SUMMARY for the title, with LOCATION and DESCRIPTION for the venue and details.
  • A link back to the event page on your site, so people can book or read more.

Serve the file with the text/calendar content type, which is the type RFC 5545 uses in its examples.

Get the UIDs right

The UID is what lets calendar apps recognise that an entry is the same event they saw yesterday, now with a new time or room. If your feed generates fresh IDs every time it is built, calendars may show duplicates or lose track of changes.

Use the event's database ID combined with your domain, for example "class-2817@yourdomain", and never reuse it for a different event. For changes, RFC 5545 describes a SEQUENCE number that starts at 0 when a component is created and is incremented each time the organiser makes a significant revision; increasing it when times change helps some calendar apps treat the update correctly.

Handling cancellations

When a session is cancelled, the tempting move is to delete it from the feed. Some calendars will then remove it, but others may not notice. RFC 5545 defines a STATUS property for events whose values include CANCELLED, meaning the event was cancelled. Keep cancelled events in the feed for a while with STATUS set to CANCELLED and the title updated, such as "CANCELLED: Saturday junior swim", so the change is obvious to anyone looking.

Time zones

Times are where calendar feeds most often go wrong, especially around daylight saving changes. Either publish times in UTC, which calendar apps convert to local time, or use a named time zone such as Europe/Dublin with the time zone definition included in the file. Do not publish floating local times with no zone, or customers travelling or on misconfigured devices will see sessions at the wrong hour. After each clock change, check a few events in two different calendar apps.

Refresh expectations

You do not control how often a subscriber's calendar checks your feed. RFC 7986, which extends iCalendar, defines a REFRESH-INTERVAL property that specifies a suggested minimum interval for polling the calendar data from its source. Adding it is reasonable, but treat it as a hint. Some calendar apps refresh far less often than you might like, so for same-day cancellations, still send a direct message to booked customers. Say on your site that feed changes can take some hours to appear.

Practical setup

  • One feed or several? Offer a full timetable and filtered feeds, for example per class type, location or team, so people only subscribe to what they attend.
  • Generate it from your live data, the same source as your website timetable, rather than maintaining a separate file.
  • Keep the window sensible, such as past four weeks and next three months, so files stay small.
  • Personal feeds for a member's own bookings need an unguessable URL token and a way to reset it, because anyone with the link can read it.

A worked example

Imagine a hypothetical Limerick climbing gym that published its weekly class timetable as a web page and a PDF. Every term, instructors changed slots and members turned up to the wrong session.

The gym added feeds generated from its booking system: an "all classes" feed and one per class type, each event with a permanent UID, times in the Europe/Dublin zone, and cancellations kept with STATUS set to CANCELLED. The timetable page now has "Subscribe in Google Calendar" and "Subscribe in Apple Calendar" links next to each feed, plus a note that changes may take a few hours to show. Members who subscribe see changes in their own calendars, and front-desk questions about class times have dropped.

FAQ

What is a webcal:// link?

It is the same feed URL with a different scheme, which prompts some devices to open their calendar app and subscribe directly.

Can customers edit events in the feed?

No. Subscribed calendars are read-only; changes come only from your side.

Will this work with Outlook?

Yes. Outlook can subscribe to internet calendars by URL using the same .ics feed.

If you'd like your timetable or events to update in customers' own calendars, tell us where your schedule lives today.

Sources

WhatsAppBook a call