Educational note / Recurring schedules

What does
“every month” mean?

A repeating schedule is a rule for finding future occasions, not simply a copied date.

The calendar is part of the meaning

“Every month” sounds precise until the starting date is the thirty-first. Some months do not contain that date. A product description must distinguish between repeating on a numbered day and repeating on the last day of a month.

A calendar pattern also differs from a fixed elapsed interval. Thirty days after one event will not always fall on the same date in the following month. Choosing one interpretation changes the occasions that a schedule produces.

Time introduces another distinction. A reminder tied to nine o’clock in a named time zone follows local clock rules. A reminder tied to a fixed instant has a different meaning when viewed elsewhere. Clock changes can complicate local times, so the schedule’s time-zone policy matters.

Hypothetical example / A monthly reminder

Write the exception into the description

Imagine a fictional personal reminder created on January 31. Its owner wants a prompt at the end of each month. Describing it as “repeat on day 31” would leave February unresolved and could express the wrong intention.

Intended pattern
The last calendar day of each month.
Time basis
Nine o’clock in the owner’s selected time zone.
Editing scope
Changing one occurrence leaves later occurrences unchanged.

Those are choices for this hypothetical tool, not universal calendar behavior. Another product could use a different policy. A preview of upcoming dates could help the owner check the interpretation before relying on it.

Questions to keep

  • Does the pattern follow calendar dates or elapsed time?
  • What happens when the requested date does not exist?
  • Does an edit affect one occasion or the remaining series?

A skipped occasion and a rescheduled occasion are different events. Moving a single reminder to another day should not silently redefine the whole series unless that is the intended behavior. Likewise, an end date needs a clear meaning: is the final day included?

Calendar exchange formats address these distinctions in detail. The IETF’s iCalendar specification and errata provide technical background. This note introduces product questions rather than a complete implementation of that standard.