An appointment series that changes without breaking: the rule leadership must set for recurrences and exceptions

01

The hidden cost of an ungoverned appointment series

Whoever decides how an appointment series repeats and how exceptions are handled also decides how many manual corrections the team will absorb when a date changes. Nebulas Calendar distinguishes the single occurrence from the series, so an exception applies to a specific date without altering the rules of the others, limiting chain corrections between those who plan and those who execute.

02

How to set up a recurrence without leaving room for improvisation

Steps

1. Choose the recurrence frequency: daily, weekly, monthly, or annual.
2. Configure custom rules and the edit scope before publishing the series.
3. Manage exceptions on the single occurrence without altering the full series.
4. Check the preview to assess the effect before confirming.
5. Enable notifications linked to event data to inform the parties involved.

03

What to have ready before activating a recurring series

Prerequisites

• Calendars configured for the operators or resources involved in the series.
• Working hours and slots defined for the activity to be repeated.
• A company role responsible for deciding the edit scopes.

04

Hypothetical example: an exception that must not spread to the series

Hypothetical example: a company schedules a monthly department meeting with a supplier. For a month when the room is unavailable, the team applies an exception only to that occurrence, leaving the series unchanged for the following months. The preview shows the effect of the change, and the overlap checks flag any conflicts before confirmation.

05

What to check before confirming a change to the series

• Series preview before confirmation to verify the impact of changes.
• Distinct edit scopes for a single occurrence and the full series.
• Overlap checks that flag conflicts before confirmation.
• History and audit to reconstruct changes to recurrences and exceptions.

06

How Nebulas Calendar separates the occurrence and the exception from the series

Nebulas Calendar manages daily, weekly, monthly, and annual recurrences with custom rules, preview, and edit scopes that separate the single occurrence from the series. Text search, filters by calendars, records and status, availability reports, and audit make it possible to find every event and reconstruct exceptions introduced over time, keeping the schedule readable even as it changes.

07

Operating path for introducing a controlled exception

Steps

1. Assign a calendar for each operator or resource involved.
2. Create the recurrence choosing frequency and custom rules.
3. Open the preview to check occurrences and conflicts.
4. Apply the exception choosing the scope for the single occurrence.
5. Verify the changes introduced through audit and history.

08

The decision to make now

Before introducing new recurring series, establish who in the company can decide the scope of a change: single occurrence or entire series. This rule, made traceable by preview, custom rules, and audit, is what keeps every exception from turning into manual correction work.