Overview
An Ad Hoc Slot (often written "adhoc" or called an ad hoc checklist) is a single, one-off slot for one or more Checklists. It isn't part of a Schedule and doesn't repeat: it has its own start, deadline and optional grace period, its own targets and people, and its own compliance settings. It can be created manually, by a Checklist trigger, by rescheduling a Missing Result, or through the Public API.
At a glance |
|
Who can do this | Super Users or a Role with Schedules › Create. To edit or delete a slot: Schedules › Modify, or the user who created it. |
Where | Schedules › Ad Hoc Slots › Create |
Works on | Backend (web), Public API; Assignees complete the Checklists in the Mobile app |
Availability | All organizations. Asset targets need Scheduling functionality for assets; Require validation on rule deviation needs Water Quality functionality. Public API access is enabled per organization by Mobaro — ask your CSM. |
💡 Why this matters: Ad Hoc Slots combine the time-accountability of a Calendar slot with the flexibility of being created on demand. They offer the same compliance options as a Calendar Schedule — set per slot.
What an Ad Hoc Slot is
An Ad Hoc Slot is a one-time, scheduled occurrence of one or more Checklists. Unlike a Calendar schedule (which creates slots from Patterns, Specifics and Calendars) 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 start, a deadline and an optional grace period, and produces a Missing Result if a Checklist isn't completed by the time it ends (unless Ignore missing results is on). In the Ad Hoc Slots list, each slot shows as Future, Started or In Grace Period.
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, or a particular answer on another Checklist.
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 four ways:
How | What happens |
Manually | Someone creates the slot in Schedules › Ad Hoc Slots — see the steps below. |
From a Checklist answer | An Ad Hoc Slot Trigger on a Checklist question creates a slot when a submitted answer meets the trigger's condition. The slot's Checklists, Assignees, timing and compliance settings come from the trigger. See Ad Hoc Slot triggers in Checklists. |
From a reschedule | Rescheduling a Missing Result creates an Ad Hoc Slot for that Checklist and target. See Approving or rescheduling missed Results. |
Through the Public API | Your own systems — for example an incident or weather system — can create, update and delete Ad Hoc Slots with the Mobaro Public API. See Getting started with the Mobaro API. |
ℹ️ Note: Mobaro records where each slot came from automatically — you don't set it. In the Ad Hoc Slots list, an icon marks slots that are a Reschedule of a Missing Result or were created From Result by a Checklist trigger.
Create an Ad Hoc Slot
1. Go to Schedules › Ad Hoc Slots
Navigate to Schedules and select Ad Hoc Slots.
2. Click Create
Click Create to open the Configure Ad Hoc Slot dialog.
3. Set the times in General
Set the slot's start and deadline. Optionally tick Allow grace period and set the End of grace period, add Reminders (each must fall between the slot's start and end), and enter an External ID.
4. Choose Checklists in What?
Choose the Checklists the slot makes available. At least one is required.
5. Choose targets in Where?
Choose the targets — Locations or Location Groups (with any exclusions), or Assets if your organization has Scheduling functionality for assets. A target is required.
6. Add people in Who?
Add Assignees (required), Reviewers and Owners, and choose Results visible to. You can also tick Notify assignees when scheduled checklist(s) becomes available and add a Message to the assignee (optional), which is shown to the user who opens the Checklist.
⚠️ Heads-up: If you don't add any Reviewers, only Super Users will be able to validate Results and handle Missing Results from this slot.
7. Set Compliance
Choose the compliance settings (see the next section).
8. Save
Click Save. The slot appears in the Ad Hoc Slots list and becomes available to its Assignees at its start time.
Ad Hoc Slot compliance options
Each Ad Hoc Slot has its own Compliance section, with the same options as a Calendar Schedule:
Allow early start (up to 28 days before the start) and Ignore missing results.
Mark all results as requiring validation, Require correct GPS location, Require timely answer, Require maximum score and Require minimum answer duration.
Require validation on rule deviation — only shown when your organization has Water Quality functionality.
Is critical for operation — Always, When overdue or When missing, set for this slot only.
Enable Time Registration — Optional or Required.
Required Competencies, optionally with Restrict access based on required competencies — use this to limit who can run the Checklist.
For what each option does, see Schedule compliance settings. To change settings on many slots at once, select them in the Ad Hoc Slots list and use Bulk Change Compliance Settings, Bulk Change Start/Due/End Date, Bulk Change Assignees/Reviewers/Owners or Bulk Change Result Visibility.
Edit or delete an Ad Hoc Slot
You can edit an Ad Hoc Slot until it ends. Once it has started, its start time is locked; once its grace period has begun, its deadline is locked.
After a slot has ended, it can no longer be edited, and archived slots can't be deleted.
A slot created by rescheduling a Missing Result keeps its Checklist and target — they can't be changed. Deleting that slot rejects the reschedule of the Missing Result.
Common Ad Hoc Slot patterns
Incident-triggered re-inspection — when an operator records an incident on a Checklist, an Ad Hoc Slot Trigger on that answer creates an Ad Hoc Slot for a "Post-incident ride inspection" Checklist. If the incident is logged in another system, that system can create the slot through the Public API instead — Mobaro doesn't create Ad Hoc Slots from e-stops or other external events on its own.
Weather-triggered inspection — when lightning causes an operational hold, a supervisor — or a weather system integrated through the Public API — creates an Ad Hoc Slot for each affected outdoor Asset, requiring a "Post-weather reopen inspection" before operations resume. Set Is critical for operation to Always so the Location shows as not ready until the inspection is done.
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 grace period. The slot is available to the Assignees the manager picks.
Contractor verification — when an external contractor completes work on a ride, an Ad Hoc Slot is created for a "Contractor work verification" Checklist. Required Competencies with Restrict access based on required competencies blocks users without the senior-technician competency from starting it.
Related articles
Choosing a Schedule type — comparison of Calendar, Continuous, and Ad Hoc.
How to use Ad Hoc Slots — step-by-step guide.
Schedule compliance settings — full list of compliance options.
Frequently asked questions
What is an ad hoc slot, and when should I use one?
It's a one-off, time-bound slot for one or more Checklists, with its own targets, people and compliance settings. Use it for work that doesn't fit a weekly Pattern. It's created manually, by a Checklist trigger, by rescheduling a Missing Result, or through the Public API.
How do I create an ad hoc slot automatically when a checklist is completed?
Add an Ad Hoc Slot Trigger to a question in that Checklist. When a submitted answer meets its condition, a slot is created with the Checklists, Assignees and timing set on the trigger. See Ad Hoc Slot triggers in Checklists.
Can an ad hoc slot stop a ride from opening?
Yes, if its own Is critical for operation is ticked. Even when it isn't, a missed slot turns the Location red by default once it ends, until the Missing Result is handled, because Red if one or more checklists are missing is on by default.
Why can a user validate scheduled results but not ad hoc ones?
Reviewers are set on each Ad Hoc Slot; being a Reviewer of a Schedule doesn't cover it. Add the user, or their User Group, to the slot's Reviewers. A slot created by a reschedule uses the original Schedule's Reviewers unless you change them.
A partly completed ad hoc checklist disappeared. Where did it go?
When the slot ended, the unfinished Checklist became a Missing Result. Reschedule it from Missing Results: by default, the partly completed Result moves to the new slot so Assignees can finish it. See Approving or rescheduling missed Results.