Overview
An Ad Hoc Slot is a Mobaro Schedule type that runs on demand rather than on a fixed recurrence. It is created explicitly — by a manager, by a triggering event, or by rescheduling a missed or invalidated Result — and carries its own scheduled time and deviation window, just like a Calendar slot.
The one thing to know: Ad Hoc Slots combine the time-accountability of a Calendar slot with the flexibility of being created on demand. They have the widest range of compliance and deviation options of any Schedule type.
What an Ad Hoc Slot is
An Ad Hoc Slot is a one-time, scheduled occurrence of a Checklist. Unlike a Calendar schedule (which creates slots on a fixed recurrence) or a Continuous schedule (which has no slots at all), an Ad Hoc Slot is created explicitly whenever the work needs to happen.
Once created, an Ad Hoc Slot behaves much like a Calendar slot — it has a scheduled time, a deviation window, and produces a missed-slot signal if it goes unrun. The difference is that it exists because someone or something specifically created it, not because the calendar said so.
When to use an Ad Hoc Slot
Ad Hoc Slots are the right choice when:
The task is triggered by a specific event — an incident, a weather change, a guest complaint, a sensor alarm.
The task is scheduled but not recurring — a one-time deep inspection, a contractor visit, a pre-event walkthrough.
Timing accountability matters, but the schedule is too irregular to fit a Calendar pattern.
A compliance rule requires a time-bounded record but not a fixed cadence.
How Ad Hoc Slots are created
Ad Hoc Slots can be created in several ways:
Manually — through the Mobaro Backend, typically in response to a specific situation.
Automatically from a Checklist answer — for example, a "Found damage" answer on a pre-opening inspection could auto-create an Ad Hoc Slot for follow-up inspection.
From a Reschedule — missed results that are rescheduled would create an Ad Hoc Slot.
Setting up an Ad Hoc-capable Schedule
To create a Schedule that supports Ad Hoc Slots:
1. Go to Schedules > Ad Hoc Slots
Navigate to Schedules and select Ad Hoc Slots.
2. Click Create
Use the Create button to begin a new Ad Hoc Schedule.
3. Choose the Checklist
Pick the Checklist that will run when a slot is created.
4. Define the default activation window
This window is applied to new slots. Individual slots can override it at creation.
5. Scope the Schedule
Apply to Locations, Assets, and Users or User Groups.
6. Configure compliance and deviation options
Set required Certifications, trigger source audit, and any other applicable settings (see the next section).
7. Save the Schedule
The Schedule is now available to receive Ad Hoc Slot creations.
Compliance and deviation options
Ad Hoc Slots offer the widest range of compliance and deviation options of any Schedule type. This is because Ad Hoc Slots often carry the most operational weight — they exist because something specific triggered them, which typically means the stakes are higher.
Options typically available:
Per-slot Grace Period window — in addition to the Schedule default, individual slots can override the window when created.
Required Certifications — restrict which operators can run the Checklist.
Trigger source audit — record what created the slot (manual, Checklist answer, Assignment, Handover Note, operator-initiated).
For the complete list of compliance options by Schedule type, see the Schedule compliance reference.
Common patterns
Pattern: incident-triggered re-inspection
When a ride has a guest report or an e-stop event, the incident system auto-creates an Ad Hoc Slot for a "Post-incident ride inspection" Checklist.
Pattern: weather-triggered inspection
When lightning within a configured radius triggers an operational hold, an Ad Hoc Slot is created for each affected outdoor Asset requiring a "Post-weather reopen inspection" before operations resume.
Pattern: manager-created one-off audit
An area manager creates an Ad Hoc Slot for a specific Asset ("Detailed brake inspection — East Coaster") scheduled for the following morning at 6am, with a 2-hour deviation window. The slot is visible to all qualified operators in that area.
Pattern: contractor verification
When an external contractor completes work on a ride, an Ad Hoc Slot is created for a "Contractor work verification" Checklist, requiring a senior technician to run it before the ride returns to service.
Frequently asked questions
Q: Can an Ad Hoc Slot be rescheduled after creation?
A: Yes. Managers with the right permission can adjust the scheduled time and deviation window of an existing Ad Hoc Slot before it has been run.
Q: How is an Ad Hoc Slot different from an Assignment?
A: An Assignment is a task — it represents work to be done. An Ad Hoc Slot is a scheduled Checklist run — it represents a time-bounded record of a Checklist being completed.
Q: Do Ad Hoc Slots show up in compliance reporting?
A: Yes. They are captured in the Gallery, counted in Dashboards, and available in reporting just like any other Schedule type's Results.