Overview
A Requirement trigger forces extra input when an answer meets your condition. Give a flagged answer and the User must add a comment, a photo, or both before they can continue — so the evidence behind an exception is captured in the moment, not chased down later.
Users must be Super Users or have the following Role to add triggers to a Checklist:
Checklists: Modify or Create
Why this matters: "Failed — see notes" with no notes is the bane of any inspection record. A Requirement trigger makes the evidence mandatory exactly when it's relevant: report a defect and you can't move on until you've photographed it or described it. The Result that lands is self-explanatory and audit-ready.
Where Requirement triggers can be used
Requirement 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, 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 a Requirement trigger
1. Add the trigger to the question
In the Checklist editor, select the question, open the Triggers section, click Add Trigger, and choose Requirement.
2. Set the condition
Choose which answer requires the extra input — a chosen option for an option question, or a value comparison for a value question. The requirement only applies when the condition is met.
3. Choose what's required
Set the validation requirement: a comment, a photo, or both. The User can't complete the Checklist past that answer until they've provided it.
Best practice: Require a photo on the answers where a picture removes ambiguity — damage, leaks, wear — and a comment where context matters more than an image. Requiring both on every exception can slow operators down, so target it where the evidence genuinely earns its place.
How it behaves during completion
Unlike Assignment and Ad Hoc Slot triggers, a Requirement trigger is visible to the User during completion. When the condition is met, Mobaro prompts for the comment or photo and blocks progress until it's supplied, so the requirement can't be skipped.
Note: You can combine triggers on one question — for example, a Requirement trigger to capture a photo and an Assignment trigger to raise the follow-up task, both on the same failing answer. See Adding triggers to a Checklist.
Frequently asked questions
Q: Can I require both a comment and a photo?
A: Yes. Choose comment, photo, or both when configuring the trigger.
Q: Can the User skip the requirement?
A: No. When the condition is met, the comment or photo is mandatory before the Checklist can be completed past that answer.
Q: Which questions support Requirement triggers?
A: Any trigger-capable question — Select, Select Group, Smiley, Number, Temperature, Slider, Duration, or Date.
Q: How is this different from the Checklist's general "allow comments" or "allow image attachment" settings?
A: Those make comments and images optional across the Checklist. A Requirement trigger makes them mandatory for specific answers that meet the condition.