Recurring events without the mess
A recurring event is not one event. It is a rule, plus a growing pile of exceptions, and the pile is where the trouble lives.
What most people assume
That editing a repeating event edits the repeating event.
This one, or all of them
Every edit to a repeat asks a question people answer without reading: this occurrence, or the series. Choose wrong and you either move one week or rewrite a year.
The damaging direction is choosing 'all' when you meant 'this'. It is also the default in more apps than it should be.
Endless repeats accumulate
A weekly event with no end date is still generating occurrences long after the thing stopped happening. It clutters every future week and quietly makes the calendar less trustworthy.
Give repeats an end date, even a generous one. A rule that expires is easier to renew than one that never stops.
Exceptions do not survive rewrites
Move six occurrences individually, then edit the series, and the six exceptions can be flattened back to the rule. The edits vanish and nothing warns you.
If a series needs many exceptions, it has stopped being a series.
What it looks like
What to do
- Read the this-or-all prompt every time, even when you are sure.
- Put an end date on every repeat.
- When a series needs more than a few exceptions, end it and start a new one.