An open paper planner with a pencil and a few dates circled on a wooden desk

Store the rule, not fifty copies

It is tempting to type a weekly event into a calendar fifty-two times. It works on the day, and it fails the first time the meeting time changes: every copy has to be found and edited, and one is always missed.

A better habit is to store one event with one recurrence rule and let the calendar expand it into dates when it is shown. Edit the rule and every future date follows. The same idea sits behind the RRULE property of the iCalendar format, which the ICS guide explains.

Recurring event examples: the four patterns most groups need

Nearly every recurring event in a club, venue or parish calendar fits one of a few shapes.

  • Every day or every few days, for example a daily opening time during a festival.
  • Every week on one or more weekdays, for example every Tuesday evening.
  • Every month on a date, for example the 15th, or on a weekday position, for example the second Thursday or the last Friday.
  • Every year on a date, for example an annual open day.

The difference between a date and a weekday position matters more than it looks. The 15th falls on a different weekday each month, while the second Thursday always falls on a Thursday and moves between the 8th and the 14th.

RRULE examples: how the rules look in iCalendar

The iCalendar standard writes these patterns as short rules. Reading them helps even if you never type one by hand, because many calendar tools show the same options in a form.

PatternRule textMeaning
Every TuesdayFREQ=WEEKLY
BYDAY=TUOne date per week, on Tuesday
Second Thursday of the monthFREQ=MONTHLY
BYDAY=2THOne date per month, the second Thursday
Last Friday of the monthFREQ=MONTHLY
BYDAY=-1FRCounted from the end of the month
The 15th of each monthFREQ=MONTHLY
BYMONTHDAY=15Same date, changing weekday

The fifth Friday problem

Some weekday positions do not exist every month. A fifth Friday appears only in months that have five of them, so a rule that says fifth Friday silently skips most of the year. If people mean the last Friday, write the last Friday.

The same care applies to the 31st. A monthly rule on the 31st has no date in months with 30 days or fewer. Decide what your calendar does there and say it in the event description, or pick a weekday-based rule instead.

Editing one date: this event, this and following, or all events

Real groups skip holidays and move rooms. A good calendar lets an editor change one date in a series without touching the rest. Two cases cover almost everything.

  • Cancelled date: the series stays, one date is removed or marked as cancelled, so people who saw it earlier can see what happened.
  • Moved date: the series stays, one date gets a new time or place, and the original slot disappears.

In iCalendar the first case is an exception date and the second is an override of a single occurrence. Tools label this differently, but most offer the same three choices when you edit: this event only, this and all following events, or all events.

End dates and open series

Every series needs an end condition, even if it is far away: an end date, a count, or an explicit open-ended flag that someone reviews. An open series that nobody owns is how a calendar ends up promising a Tuesday meeting for a group that stopped meeting years ago. The guide to keeping an event calendar updated covers the review habit.

Time zones and daylight saving time

A weekly 19:00 meeting should stay at 19:00 on the wall clock when the clocks change. That works when the event is stored with a named time zone such as Europe/London. It breaks when the time is stored as a fixed UTC offset or as UTC only, because after the clock change the same stored time shows an hour earlier or later on local clocks.

For events in one place, store the local time and the place's time zone name. For online events with an international audience, show the time zone name next to the time and, if you can, a second local time.

A short checklist

  1. Write the rule in words first, then pick the matching option.
  2. Decide how many months ahead the calendar expands the series.
  3. Set an end condition or an owner who reviews the series.
  4. Use exceptions for single changes instead of editing copies.
  5. Store a time zone name, not only an offset.