Overview
An Ad Hoc Slot trigger spins up a follow-up Checklist on demand. When a User gives an answer that meets your condition, Mobaro creates an Ad Hoc Slot — a one-off scheduled occurrence of a Checklist — so a finding in one inspection automatically queues the deeper check it warrants.
Users must be Super Users or have the following Role to add triggers to a Checklist:
Checklists: Modify or Create
Why this matters: Some answers shouldn't just create a task — they should trigger a whole second procedure. A failed quick check might need a full diagnostic Checklist run by a technician. An Ad Hoc Slot trigger launches that second Checklist automatically, with its own compliance tracking, instead of hoping someone schedules it.
How this differs from an Assignment trigger
Both react to an answer, but they produce different things. An Assignment is a task to be done; an Ad Hoc Slot is a Checklist to be completed, with its own deadline and compliance options. Reach for an Ad Hoc Slot trigger when the follow-up is itself a structured set of checks rather than a single action.
Where Ad Hoc Slot triggers can be used
Like all triggers, these attach to question types whose answer can be evaluated against a condition: Select, Select Group, Smiley, Number, Temperature, Slider, Duration, and Date. Free-form and capture types (Text, Email, Photo, Signature) don't support triggers, and Water Quality is handled through rulesets. The condition style depends on the type — see Adding triggers to a Checklist.
Configuring an Ad Hoc Slot trigger
1. Add the trigger to the question
In the Checklist editor, select the question, open the Triggers section, click Add Trigger, and choose Ad Hoc Slot.
2. Set the condition
Choose what fires the trigger — a chosen option for an option question, or a value comparison for a value question. The Slot is created only when the condition is met.
3. Configure the Slot details
Set which Checklist the Slot runs, its assignees, and its deadline. This is the follow-up procedure that will be queued.
4. Set validation options
Enable the compliance settings the Slot should carry — the same kinds of validation options available on an Ad Hoc Slot Schedule.
Best practice: Point the Slot at a purpose-built follow-up Checklist (for example, a detailed diagnostic) rather than re-running the same Checklist. The trigger then escalates from a quick check to a thorough one in a single step.
How it behaves during completion
Ad Hoc Slot triggers are processed after the Checklist is submitted, so they don't interrupt the User completing the current Checklist. The new Slot appears for its assignees once the triggering Checklist is done.
Note: For how Ad Hoc Slots behave once created — completion, deadlines, and compliance — see Ad Hoc Slots — setup and behavior.
Frequently asked questions
Q: When should I use an Ad Hoc Slot trigger instead of an Assignment trigger?
A: Use an Ad Hoc Slot when the follow-up is a Checklist to complete; use an Assignment when it's a single task to action.
Q: Which questions can fire it?
A: Any trigger-capable question — Select, Select Group, Smiley, Number, Temperature, Slider, Duration, or Date.
Q: Does the Slot appear immediately while the User is still in the Checklist?
A: No. It's processed after the triggering Checklist is submitted or saved, so it doesn't interrupt the current workflow.
Q: Can I require validation on the created Slot?
A: Yes. The trigger exposes the Slot's compliance and validation options so the follow-up can carry its own sign-off requirements.