Overview
Compliance settings streamline the approval process for Schedules and provide a high-level overview of conditions that may not have been met with submitted Results. With compliance settings, you can automate approvals and quickly identify any discrepancies, ensuring smoother operations and adherence to regulations.
Users must be Super Users, be listed as an Owner on a Schedule, or have the following Roles to manage a Schedule's compliance settings:
Schedules: Create or Modify
Compliance Settings
As previously mentioned, compliance settings aim to automate approval processes. However, to optimize their effectiveness for your needs, it's crucial to grasp their significance and how they integrate with factors such as a Location's readiness and other scheduling settings.
Allow early start
The Allow early start (AES) feature empowers Assignees to start a planned Checklist up to 28 days before the defined start date, pending the fulfillment of certain conditions.
Allow early start Preconditions
For an Assignee to begin a planned Checklist early, all of the following conditions must be met:
The Schedule must be enabled for Allow early start.
Any previously scheduled slots must both be completed and past their defined end time.
For example, if today's slot was completed and scheduled from 7am to 7pm, the Assignee will be able to start the next scheduled slot starting from 7:01pm.
The next scheduled slot must fall within the next 28 days.
The Assignee must utilize the Calendar tile on the mobile app and select the date of the next scheduled slot.
Warning: It is not recommended to utilize Allow early start for checks deemed Critical for operation or Schedules that necessitate completion of a Checklist within the defined start and end times.
Ignore missing results
By default, if a Calendar or Ad Hoc Schedule has a slot that was not completed within the defined time, the Result will filter into the Missing Results section to be further mitigated by an authorized User.
There may be occasions that you do not wish for incomplete Results to be logged in the system, such as when testing a Schedule or a non-critical Checklist. In these cases, the Ignore missing results (IM) setting may be good to use.
Enabling Ignore missing results will simply have any Result that is missed, not be logged as missing.
Warning: It is not recommended to utilized Ignore missing results on Schedules that are considered Critical for operation as there will be no log of non-completed Results nor will you have the ability to approve or reschedule these Results.
Requires validation
The Requires validation (RV) compliance setting allows you to move into a multi-level approval process for your Checklist program. By default, a Schedule setup with no compliance settings will be automatically 
Preapproved by the system as there are no conditions setup to otherwise place a Result into an 
Awaiting Validation state.
Toggling on Requires validation automatically placed a completed Result immediately into the Awaiting Validation state to be validated by the Schedule's listed Reviewers, a Super User, or User who has permission to validate a Result.
Note: Requires validation does not need to be used in conjunction with other compliance settings if you only want the need to validate a Result based on other conditions; Requires validation will place all submitted Results for the Schedule into the Awaiting Validation state regardless of other compliance settings.
Requires correct GPS location
When configuring a geographic location for the Locations on your account, you have the ability to tap into the Requires correct GPS location (GPS) compliance setting.
Enabling this setting will utilize the Location's set pinpoint and radius to determine if a User is answering within the allotted space. Assignees outside the intended radius will be presented with a warning prior to going into a Checklist letting them know they are too far away from the set radius. The system will allow the Assignee to enter the Checklist if they are outside the set radius and will offer them a prompt to offer any reasoning.
Note: Please note that the accuracy of GPS locations depends on the quality of the Assignee's device. When looking at the 
Maps view on Results, the system displays a colorized radius around each pinpoint, these correlate to how confident the system is based on the placement of each pinpoint:
Green: High confidence (0-15 meters / 0-49 feet)
Yellow: Moderate confidence (15-50 meters / 49-164 feet)
Red: Low confidence (Over 50 meters / +164 feet)
Due to factors such as device quality, connectivity, and other variables beyond the system's control, some GPS markers may be less accurate. Please use caution when interpreting these markers.
Requires maximum score
Configuring a Schedule with the Require maximum score (SBM) setting will move any Result with a calculated score under 100% as Awaiting Validation.
Note: A Checklist must be setup with scoring in order to utilize Requires maximum score. A Checklist without scoring will be marked with a score of N/A and will not trigger a failure of the Require maximum score condition.
For example, an element in your Checklist may use a score of 1 for OK and a score of 0 for NOT OK:
Requires minimum answer duration
When using the Requires minimum answer duration (MD) setting, you are able to define, per Schedule, a minimum time a User should take to complete each Checklist listed on a Schedule.
For example, if I set up a Schedule with a minimum duration of 30 minutes, that system will place any Result from this Schedule that is completed under 30 minutes as Awaiting Validation.
Note: The system measures the time of completion based on the difference between the Started and Answered times recorded on a Result. The Received time is not factored into the calculation. While the Received time typically aligns with the Answered time, it may differ due to variations in the device's signal strength.
Requires specific competencies
Competencies can be utilized as a precondition to enter and complete a Checklist by utilizing the Requires specific competencies (RC) setting. Enabling this setting offers two levels of control:
Permit Assignees without active Certifications for the required Competencies to complete the Checklist but mark the completed Result as
Awaiting Validation.Restrict access to only listed Assignees with active Certifications for the required Competencies.
Tip: When opting for allowing Assignees without active Certifications for the required Competencies to complete the Checklist, the system will prompt the Assignee to provide a reason for doing so. The provided reason will be accessible on the completed Result.
Requires timely answers
To ensure a Checklist is completed within the originally scheduled start and end times, you can enable the Requires timely answers (DUE) setting. Results submitted after the defined end time with be marked as Awaiting Validation.
Note: The defined start and end time does not include the grace period; a Result that comes in between the defined end time and grace period will still be marked as Awaiting Validation.
Critical for operation
The Critical for operation (CFO) setting is designed to streamline operational readiness assessments for your Locations. When enabled for a Checklist, CFO allows you to indicate the criticality of the scheduled Checklist for the operational status of a Location.
When a Checklist is marked as Critical for operation, it means that its completion directly impacts the readiness status of the associated Location. Here's a breakdown of the available CFO subcategories:
Always: The Location's readiness status is affected as long as the Schedule slot is active, keeping the Location in the Not ready for operation state (colorized red) until the Checklist is completed with all preconditions met.
When overdue: The Location remains in the Ready for operation state (colorized green) until the checklist becomes overdue (by the definition of a grace period). Once overdue, the Location status changes to Not ready for operation until the Checklist is completed.
When missing: The Location remains in the Ready for operation state (colorized green) until the Checklist Result goes Missing. Once the Result is Missing, the Location status changes to Not ready for operation until the Missing Result is either approved or rescheduled.
Ready for operation example
To illustrate the Location's Ready for operation status with the different Critical for operation subcategories, consider the chart below. It demonstrates the Location's Ready for operation status under the following conditions:
One Schedule is configured with one Checklist for each CFO setting.
The Checklist in this example is pending completion (not submitted).
No other conditions are affecting the Location's status, keeping it in a Not Ready for Operation state.
| Prior to Slot Start | Slot Started | Slot Ended/ Grace Period Started | Grace Period Ended |
Always |
|
|
|
|
When overdue |
|
|
|
|
When missing |
|
|
|
|
No status
Not ready
ReadyWhen to use the different CFO subcategories
Choosing the appropriate CFO subcategory is crucial for ensuring operational efficiency and minimizing the need for Schedule adjustments. While each organization's setup is unique, selecting the right subcategory can significantly impact operational workflows.
Below, we provide examples of different checklist types along with a 
Best practice or 
NR (Not recommend) indicator:
| Always | When overdue | When missing |
Daily, pre-opening maintenance Checklist |
|
|
|
Weekly lubrication Checklist |
|
|
|
Weekly, non-critical painting Checklist |
|
|
|
Warning: When setting up CFO subcategories, please use discretion and consider your organization's specific requirements. While our examples offer guidance, it's essential to tailor your choices accordingly. Remember, each organization is unique, so ensure that your selections align with your operational needs and practices.
Compliance Settings Availability
Compliance settings can be individually toggled on to Calendar, Continuous, and Ad Hoc Schedules. The following are the current compliance settings and their availability on each Schedule type:
| Calendar | Continuous | Ad Hoc |
Allow early start (AES) |
|
|
|
Ignore missing results (IM) |
|
|
|
Requires validation (RV) |
|
|
|
Requires correct GPS location (GPS) |
|
|
|
Requires maximum score (SBM) |
|
|
|
Requires minimum answer duration (MD) |
|
|
|
Requires specific competencies (RC) |
|
|
|
Requires timely answers (DUE) |
|
|
|
Critical for operation (CFO) |
|
|
|
