Overview
Every water quality reading is checked against the sub-rule's minimum and maximum. When a value falls outside that range, Mobaro flags it as a deviation — but what happens next depends on how you've set up triggers and Schedule compliance. This article covers the possible outcomes so you can choose the right level of accountability for each parameter.
🚀 Early Access: Water Quality is an early-access feature — expect changes and new features as the module evolves.
Why this matters: A flagged reading is only useful if the right thing happens next. Matching each outcome to the parameter — a gentle warning for minor values, a forced Assignment or validation hold for safety-critical ones — keeps staff moving while making sure nothing important slips through unreviewed.
What happens with an out-of-range reading
Outcome | What it does |
Validation warning | Staff see a high or low warning when entering a value outside the range. They can still submit, unless another setting prevents it. Always present once a ruleset is linked. |
Assignment via trigger | A deviation automatically creates an Assignment for corrective action — for example requiring a comment or photo. Configure a trigger for this. |
Validation required | Any Result containing a deviation is held for approval before it counts as complete. Enable Require validation on rule deviation in Schedule compliance settings. |
Recorded only | With no trigger and validation off, the out-of-range value is simply recorded — visible in reporting, but with no Assignment or hold. |
Heads-up: Require validation on rule deviation changes your workflow significantly. Before enabling it, make sure the activated Schedule has reviewers set up and that they're ready to handle the validation queue.
Trigger vs. validation requirement
These are easy to confuse but do different jobs. A trigger creates an Assignment so someone takes corrective action in the field. A validation requirement holds the whole Result so a manager or approver confirms it before it's complete. You can use either, both, or neither per parameter and Schedule.
Best practices
Decide which parameters need triggers for corrective action versus those that only need a warning.
Use Require validation on rule deviation deliberately — it adds accountability but can slow processing if deviations are frequent.
Train staff to respond to warnings appropriately, even when no Assignment is created.
Frequently asked questions
Q: Can staff ignore a validation warning?
A: Yes, unless a trigger creates an Assignment or the Schedule requires validation on deviation.
Q: What's the difference between a trigger and a validation requirement?
A: A trigger creates an Assignment for corrective action; a validation requirement holds the Result for a manager or approver to confirm.
Q: Do out-of-range results still appear in dashboards and exports?
A: Yes. All values are recorded and included in reporting, regardless of the outcome.