Recurring events
A weekly meeting is not fifty copies of a meeting. In ManageCal it is one event with a rule, so changing one week, skipping one, or moving every future week is a single edit, and nothing is left behind to tidy up.
Every repeat is set from the event itself. Choose how often, how many units apart, and when it stops.
| Repeats | Options |
|---|---|
| Daily | Every day, or every 2, 3 … days |
| Weekly | On the weekdays you pick, every week or every few weeks |
| Monthly | On the same date, every month or every few months |
| Yearly | On the same date each year |
| Ends | Never, after a number of times, or on a date |
Open any occurrence and choose whether the change is for This Event or Every Event in the Series. A change to one occurrence is kept on its own: rename it, move it, put it in another room, and the rest of the series carries on as before. Skip This One removes a single week and leaves the others.
A changed occurrence starts from its own date and time, not the series’ first one. Renaming the fourth week of a meeting leaves it in the fourth week.
Repeats are worked out in the event’s own time zone, in local time, and only then turned into exact moments. A weekly nine o’clock meeting in Berlin is at nine before the clocks change and at nine after, rather than drifting to eight or ten because a fixed number of hours was added.
Every calendar has its own time zone, so offices in different countries each keep their local times.
Clocks go back on 25 October. The meeting does not move.
Open any occurrence and it says whether it repeats. One that was changed on its own is marked Changed, so nobody mistakes a one-off move for the new pattern, and the next person to edit the series can see that week was deliberate.
A series created with a rule more complex than the editor’s own patterns is kept exactly as it was written and shown as a custom rule. It can be replaced with a simple one, but it is never rewritten without anyone asking.
A club that runs until the end of term ends on that date. A course of ten sessions ends after ten. The series stops by itself, and past occurrences stay on the calendar as a record of what happened.
On a sub-calendar that refuses double bookings, a repeating event is checked against every other booking for its whole length, or across the coming year if it never ends. A clash in its twelfth week is refused when the series is created.
Yes. Open it and choose This Event. The change is kept on that occurrence alone, and the rest of the series is untouched.
Not from the editor, which repeats monthly on the same date. A series created with a more complex rule is kept exactly as written and shown as a custom rule.
They stay as they are. A changed or skipped occurrence is its own record, so an edit to the series does not overwrite it.
Yes. They keep their local time through the change, because each occurrence is worked out in the event’s time zone before it is turned into an exact time.
Yes. Open it, choose Every Event in the Series, and set it to end on that date. The occurrences before it stay on the calendar as they were.
Yes. Tick All Day and set the repeat as for any other event: a weekly all-day event, a yearly anniversary.
Set up your sub-calendars, decide who sees what, and start scheduling.