Overview
A Calendar schedule is a Mobaro Schedule type that runs at fixed, recurring times — for example, every day at 8am, every Monday morning, or on the first of the month. Each occurrence is a specific slot with a scheduled time, and compliance is tracked against that slot.
The one thing to know: Calendar schedules produce a time-bounded record — "this Checklist was run at 7:52am for the 8am pre-opening slot." That specific time accountability is what Continuous schedules don't offer.
What a Calendar schedule is
A Calendar schedule creates a series of scheduled slots over time. Each slot has a start time, a deviation window, and a specific Checklist associated with it. The slot is expected to be completed within its window; if it is not, the Schedule records a missed slot.
Calendar schedules are the right choice when the timing of the task is part of the record. Pre-opening inspections, shift-change audits, and end-of-day reconciliations all fit naturally here.
Recurrence patterns
Calendar schedules support several recurrence patterns:
Daily — every operating day at a given time.
Weekly — on specific days of the week at a given time (for example, Mondays and Thursdays at 9am).
Specific dates — on a list of pre-selected dates.
Every N days — for tasks that recur on a fixed interval regardless of the calendar.
When to use a Calendar schedule
Calendar schedules work well when:
A task must happen at a specific time of day or week.
Compliance requires proof the task ran within a window.
Missing the task should be visible — for example, as a missed slot on a Dashboard.
You want to track deviation (how far off the scheduled time the actual run happened).
Setting up a Calendar schedule
To create a Calendar schedule:
1. Go to Schedules
Open the Schedules module in the Mobaro Backend.
2. Click Create schedule
Use the Create schedule button to begin a new Schedule.
3. Select Calendar as the Schedule type
Pick Calendar from the Schedule type options.
4. Choose the Checklist
Pick the Checklist this Schedule will run.
5. Scope the Schedule
Apply to Locations, Assets, or User Groups as needed.
6. Configure compliance and deviation options
Set late-run handling, missed-slot behavior, Assignment requirements, and reminders (see the next section).
7. Save the Schedule
Now that you have the configuration saved, you can now allow the time slots.
8. Configure the recurrence pattern
Set the cadence by using patterns — daily, weekly, specific dates, or every N days. Or inherit a master calendar to pickup time slots automatically (recommended).
Compliance and deviation options
Calendar schedules have more compliance options than Continuous schedules but fewer than Ad Hoc Slots. Because each slot has a scheduled time, Mobaro can track:
Deviation window — how long after the scheduled time the slot can still be completed (for example, 30 minutes after the slot ends).
Late-run handling — whether runs completed after the deviation window still count, flag as late, or fail entirely.
Missed-slot behavior — what happens when a slot's window passes without completion (flag, notify, auto-create follow-up Assignment).
Assignment requirements — Certification or Role required to run the Checklist.
Reminder behavior — push notifications to eligible operators as the window opens or closes.
For the complete list of compliance options by Schedule type, see the Schedule compliance reference.
Missed slots and late runs
Important: Missed slots are the core signal a Calendar schedule produces. If you configure the Schedule so that missed slots are ignored (no notification, no Dashboard surface, no escalation), you lose the main benefit of using a Calendar type in the first place.
When a Calendar slot's deviation window passes without a completed run, Mobaro marks it as missed. Depending on configuration, the missed slot may:
Surface on a Dashboard for manager review.
Create a Missed Result to be actioned by a manager.
Count against a compliance metric visible in reporting.
Late runs — completed after the scheduled time but before the deviation window closes — are typically allowed and recorded with the actual timestamp. The difference between the scheduled time and the actual run is the deviation.
Common patterns
Pattern: daily pre-opening inspection
Every operating day at 8am, a "Ride pre-opening inspection" Calendar schedule creates a slot. Operators have a 30-minute deviation window (7:45–8:30). Missed slots trigger a Notification to the area manager and generate a follow-up Assignment.
Pattern: weekly deep-clean audit
Every Monday at 6am, a "Weekly deep-clean audit" Calendar schedule runs for each F&B location. The deviation window is wide (until 10am) because the audit is substantial and timing flexibility matters.
Pattern: monthly compliance check
On the first of every month, a "Monthly fire-safety compliance check" Calendar schedule runs. The task is required to be completed within 48 hours; after that, the slot is missed and escalates to the safety director.
Related
Schedules overview — comparison of Continuous, Calendar, and Ad Hoc.
Continuous schedules — setup and behavior.
Ad Hoc Slots — setup and behavior.
Schedule compliance reference — full list of compliance options.
Notification Rules — for missed-slot alerts.
Frequently asked questions
Q: What happens if the park is closed on a recurrence day?
A: Calendar schedules respect the operating calendar you configure. If a day is marked as closed, no slot is created for that date.
Q: Can I skip a specific day of a recurring Calendar schedule?
A: Yes. Individual slots can be marked as skipped in advance — for example, for a planned park closure or a special event that replaces the usual routine.
Q: What happens if the deviation window overlaps the next slot?
A: Avoid this — configure deviation windows that end before the next slot begins. If they do overlap, a single run is counted toward the slot with the closest scheduled time.
Q: Do Calendar schedules support multi-occurrence days (twice a day, three times a day)?
A: Yes. Create one Calendar schedule per recurrence time for the clearest setup, or use multiple start times on a single Schedule if your configuration supports it.