Recurrences and exceptions in Nebulas Calendar: an operational playbook

01

What a growing company gains

A company adding staff and locations can schedule repeated appointments without recreating the same record every time. Nebulas Calendar links daily, weekly, monthly or yearly recurrences to working hours, slots and multiple calendars, keeping operational load consistent across day, week, month and agenda views.

02

The workflow for setting up a series

Steps

1. Create the event by choosing the calendar of the operator or resource involved.
2. Choose the cadence: daily, weekly, monthly or yearly.
3. Apply custom rules and review the preview of the generated series.
4. Check availability with daily indicators and overlap checks.
5. Confirm the series, which stays linked to clients, products, notes and status.

03

What you need before starting

Prerequisites

• Calendars configured for the operators and resources involved in the series.
• Working hours and slots already set up on the relevant calendars.
• Client and participant records that can be linked to the event.
• Notification channels enabled, if you want to send reminders.

04

Hypothetical example: a studio with weekly classes

Scenario: a studio schedules a weekly class with the same operator. One week the room changes time for a single day. With the weekly recurrence set up, an exception is created for that single occurrence, choosing the edit scope for that occurrence only: the series stays unchanged for the other dates, while that event receives an updated time, notes and status.

05

Controls worth monitoring

• Overlap checks that flag conflicts before confirmation.
• Availability reports to check the load across multiple calendars.
• History and audit trail to reconstruct changes to series and exceptions.
• Text search and filters for calendars, records and status.

06

How Nebulas Calendar handles this

Nebulas Calendar distinguishes a single occurrence from the series through dedicated edit scopes, which let you act on the single event or on the series. Preview and custom rules show the effect of the chosen cadence before saving, while search, filters, availability reports and audit trails let you find and reconstruct every subsequent change.

07

Practical steps to fix an exception

Steps

1. Find the occurrence to change using search or calendar filters.
2. Open the event and choose the edit scope for the single occurrence.
3. Revise the time, notes or status for that date only.
4. Check for overlaps before confirming the change.
5. Verify in the history that the change is correctly tracked.

08

Next step

Before launching a new recurring series, define calendars, working hours and notification channels, then use the preview to check how occurrences and any exceptions will behave.