Check the health of a location's sampling plan

This article explains how managers can check the health of a Location's sampling and scheduling plan before an inspection. It describes the four types of health checks performed on a Location's plan, what their findings mean, and how to act on them.

Note

Required role: Manager

Understanding the Four Plan Health Checks

Four checks run on a Location's plan to ensure the sampling and schedule remain valid. Each open finding names the check that raised it in the Check row.

Rotation-pool Check

This check verifies that the sampling points a rule draws from still exist, are linked, and qualify. It reports if the pool is empty, if a point committed to the current cycle has been deleted, or if a point no longer qualifies. Qualification issues can occur if a point has moved to another Location, is no longer marked as a sampling point, is unlinked from the system the rule rotates over, is outside the rooms or activities the rule covers, or holds a network position that excludes it from the rotating selection.

Coverage Check

This check ensures the sample size still covers the point pool within the set coverage period. It flags windows that cannot be completed as configured, the last cycle containing points left uncovered, or a period restarting at the next scheduling event.

New-points Check

This check reports any points that have joined a pool after the plan was fixed.

Schedule-consistency Check

This check confirms that rule settings, planned job windows, and week-grid anchors still match their compliance rules. It flags invalid sampling settings, jobs scheduled outside the Location's week grid, or anchors left on by unused activities.

Interpreting the Why Row in Findings

The Why row appears only on findings related to a point the current cycle had committed to. It clarifies whether a point was deleted or remains intact but no longer pickable, listing reasons such as:

• The point was moved to another Location
• The point is no longer marked as a sampling point
• The point is unlinked from the system the rule rotates over
• The point is not in a room the rule draws from
• The point lacks the activity that initially brought it into scope
• The point's network position excludes it from the rotating selection
• The point is eligible yet absent from the pool

Running a Plan Health Check

The plan health check runs automatically overnight for each Location, approximately at 02:00 in the Location's local time zone. It checks any Location whose plan has changed since the previous run and ensures every Location is checked at least once weekly. Locations without a time zone set run the check on UTC time instead.

You can also run a check on demand to confirm fixes immediately:

1. Open Locations and select the Location.
2. Go to the Rotation plan tab.
3. Click Check now in the Plan health header.

During the check, the line below the button shows Checking…. Once complete, the findings refresh. If the check fails to start or stops midway, you will see an error message.

Note: Running a plan health check on demand requires the scheduling role. Anyone with access to the tab can read findings, but only users with scheduling permissions can start a check.

Viewing Plan Health Findings

To review plan health findings for a Location:

1. Open Locations and select the desired Location.
2. Go to the Rotation plan tab.
3. See the Plan health card listing open findings sorted by severity (High, Medium, Low).

Each finding displays:

• The Check that raised it
• What it Applies to
• The specific Point involved (if applicable)
• The Why explanation (for points committed to the running cycle)
• When it was First detected
• Any suggested remedy

A badge by the page heading shows the count of open findings in the worst severity colour. If no findings are open, it shows No plan issues found. If the Location has never been checked, the card line reads This location has not been checked yet.

Even Locations without a rotation plan can raise findings because schedule-consistency checks cover every compliance rule.

Notifications for High-Severity Findings Left Open

High-severity findings left open without action for seven days trigger notifications automatically, by default, to all users with the Owner, Admin, or Manager role and Location access. Notifications include:

• The Location name
• The number of findings that have been open a week without action
• How long the oldest finding has been open
• Details for each finding
• A direct link to the Rotation plan tab

This alert is sent once per finding and only on organisation working days, at the start of the Location's local working day (including weekends if weekend service applies). Medium and Low severity findings do not escalate.

Users can disable these notifications in the Notifications tab of My Settings, but muting the shared preference also silences compliance status change notifications.

Note that Inspectors, Engineers, Viewers, and Managers without access to the Location are never notified.

Summary

By understanding the four plan health checks and how to interpret their findings, managers can verify whether their Location's sampling and scheduling plans are sound before inspections. They can run checks on demand or rely on the overnight automatic process and receive escalation notifications for serious issues left unresolved.