Compliance settings govern how a Schedule's Results are approved and how a Location's readiness is affected. Here's what each setting does and which Schedule types offer it.

In the Schedules and Ad Hoc Slots lists, short tags (shown in brackets in the table at the end, such as IM) show which settings are on. Continuous Schedules also have a separate Behavior section — see Continuous schedules — setup and behavior.

Allow early start lets Assignees start a planned Checklist up to 28 days before its defined start time. You can add a Message to the assignee (optional), shown to the user who opens the Checklist. An early start needs all of the following:

By default, a Calendar or Ad Hoc slot not completed in time creates a Result in Missing Results for someone to handle. Ignore missing results stops missed slots from being logged as missing.

With no compliance settings, a completed Result doesn't need validation. This setting sends every completed Result to Awaiting Validation, regardless of other settings, to be validated by the Schedule's Reviewers, a Super User, or anyone with permission to validate a Result.

Require correct GPS location checks whether the Assignee answers within the Location's pinpoint radius. Answering outside it doesn't stop them; when they finish, the Deviations screen lists the questions answered too far away, and they can add an optional explanation. Such Checklists are marked as requiring validation.

Accuracy depends on the device. Hovering over an answer's marker on a Result's map shows a confidence radius: green (high, 0–15 m), yellow (moderate, 15–50 m), red (low, over 50 m). Treat low-confidence markers with caution.

Require maximum score flags any Result scoring below the maximum (100%) as Awaiting Validation. The Checklist must use scoring; a Checklist without scoring is marked N/A and won't trigger this condition — for example, an element scoring 1 for OK and 0 for NOT OK.

Require minimum answer duration sets a minimum time, per Schedule, that a Checklist should take; any Result completed faster (e.g. under 30 minutes for a 30-minute minimum) is flagged as Awaiting Validation. Duration is the difference between the Result's Started and Answered times. The Received time isn't used; it can differ from Answered with device signal strength.

Required Competencies makes competencies a precondition for a Checklist (the bulk-change dialog calls it Require specific competencies). Two levels of control:

Require timely answer flags any Result submitted after the slot's deadline as Awaiting Validation. A Result that arrives during the grace period is still flagged.

Require validation on rule deviation flags any Result where a Water Quality reading falls outside its ruleset's acceptable range, sending it to Awaiting Validation. Only Checklists with a Water Quality Question linked to a ruleset can deviate — see Understanding validation warnings and failures. The setting only appears with Water Quality functionality, which Mobaro switches on — contact Mobaro Support.

Is critical for operation ties a Checklist's completion to a Location's readiness: Not ready for operation (red) while the condition isn't met, Ready for operation (green) once it is. Criticality doesn't require approval unless combined with a validation setting. For a single pending Checklist, the Location is Ready before the slot starts; after that it depends on the mode (see Understanding criticality settings with schedules):

Rules of thumb:

When you reschedule a Missing Result from a critical slot, the rescheduled Checklist is set to Always and starts immediately by default. Location Overview settings can also turn a Location red for any Missing Result. See Schedule criticality and Location operational status.

Enable Time Registration lets Assignees manually register the time they spent on the Checklist. Once ticked, choose Optional or Required.

Results visible to (in the Who? section, not Compliance) decides who, besides Reviewers, can view the Results from this Schedule or Ad Hoc Slot:

Can users complete a checklist before its slot starts?

Yes, if Allow early start is on. Assignees open the CALENDAR tile in the app, pick the slot's date and start it, up to 28 days early, once the previous slot for that Checklist and Location has ended. Don't use it for checks that are critical for operation.

Why does this checklist require validation, and how do I turn that off?

It usually comes from the Schedule's or Ad Hoc Slot's Compliance settings. Mark all results as requiring validation flags every Result; the others, such as Require correct GPS location or Require maximum score, flag only Results that break them. Untick the setting to stop flagging new Results.

If I turn on Ignore missing results, are completed results still saved?

Yes. Completed Results are saved as usual; only missed Checklists stop being logged in Missing Results. Don't combine it with Is critical for operation: with no Missing Result, there's nothing to approve or reschedule.

Can a Reviewer approve a result during the grace period?

Yes. A completed Result can be approved at any time, during or after its slot. Validation doesn't affect Missing Results: a Checklist goes Missing only if it isn't completed by the end of its slot, whether or not a Result has been approved.

Does changing Results visible to affect results that already exist?

Yes. The setting is checked whenever Results are viewed, so the change also applies to existing Results. The Schedule's Reviewers can still see its Results whichever option you choose.

Can I make users be at the location to fill in a checklist?

No. Require correct GPS location doesn't block anyone. Answers given outside the Location's radius are listed on the Deviations screen, and the Result is marked as requiring validation.