Overview
An Assignment trigger turns a Checklist answer into work. When a User gives an answer that meets the condition you set, Mobaro creates an Assignment with details you've pre-defined — so a failed check becomes a tracked task without anyone raising it by hand.
Users must be Super Users or have the following Role to add triggers to a Checklist:
Checklists: Modify or Create
Why this matters: The gap between spotting a problem and someone owning it is where things fall through. An Assignment trigger closes that gap automatically — the moment an operator records a fault, the follow-up task already exists, assigned and prioritised, instead of relying on someone to remember to create it.
Where Assignment triggers can be used
Triggers 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, and Signature — don't support triggers, and Water Quality is handled through Water Quality Rulesets instead. The condition style depends on the type (an option match for selections, a value comparison for numeric types, a date comparison for Date); see Adding triggers to a Checklist for the full breakdown. The trigger is configured per question in the Checklist editor.
Configuring an Assignment trigger
1. Open the question's Triggers section
In the Checklist editor, select the question, scroll to the Triggers section, and click Add Trigger. Choose Assignment as the trigger type.
2. Set the condition
Define what fires the trigger — for an option question, a chosen answer (equals / does not equal); for a value question, a comparison such as above or below a threshold. The Assignment is created only when the condition is met.
3. Pre-fill the Assignment details
Set the title, description, and priority the created Assignment should carry. These become the task an operator or technician picks up.
4. Choose who it goes to
Set the assignee — a specific User or a User Group — plus any additional options such as deadline, subscribers, and Assignment Category.
Best practice: Assign to a User Group rather than an individual where you can. The task still routes correctly when someone is off shift, and you avoid editing the trigger every time staffing changes.
How it behaves during completion
Assignment triggers usually run in the background — the User completes the Checklist and the Assignment is created without interrupting them. If you don't pre-configure the assignee, the trigger can instead prompt the User to assign the task themselves at the point the condition is met.
Note: You can add more than one trigger to the same question — for example, an Assignment trigger and a Requirement trigger — each with its own condition. See Adding triggers to a Checklist for the full trigger overview.
Frequently asked questions
Q: Which questions can raise an Assignment trigger?
A: Any trigger-capable question — Select, Select Group, Smiley, Number, Temperature, Slider, Duration, or Date. The condition differs by type: a chosen option for selections, a value comparison for numeric types, a date comparison for Date.
Q: What happens if the condition isn't met?
A: Nothing — the Assignment is only created when the answer matches the condition, so you don't generate noise tasks for normal results.
Q: Can one answer create more than one Assignment?
A: Add multiple Assignment triggers to the question, each with its own condition and details, and each fires independently when its condition is met.
Q: Is the Assignment visible to the User filling out the Checklist?
A: Generally it's created in the background. If the trigger isn't pre-configured to assign automatically, it can ask the User to assign it at completion.