Compliance Score

The Compliance Score on the Home dashboard is one number for the whole workspace. This page is what is behind it: every domain's score, and every obligation costing points, ranked by how much each one costs, each a link to the record. Open it from See what's behind this score under the score on the Home dashboard. It is available to every role that can see reports.

How the score is calculated

Every dated obligation the workspace carries earns credit against its due date:

State	Credit
Done	full
more than two weeks out	full
due within two weeks, in progress	85%
due within two weeks, not started	60%
due within a week, in progress	60%
due within a week, not started	30%
overdue	none

Training renewals use a thirty-day band instead of two weeks, because renewing a certification means finding and booking a class.

The obligations come from every part of the workspace, not only permits and tasks:

Domain	What counts
Permits	each permit's renewal date, and its expiry when that is a separate date
Tasks	permit tasks, incident tasks, one-off tasks, and each occurrence of a recurring task
Incidents	CAPA actions on open incidents
Regulatory reporting	OSHA 8-hour and 24-hour, NRC (15 minutes) and state agency report deadlines on flagged incidents
Training	each person's required courses: a renewal is due when the completion expires, and a course never taken is overdue now
Chemical inventory	an SDS review is due three years after the revision on file; a chemical with no SDS date is overdue now
Audit binders	required binder items with a review date

Each domain is averaged on its own, then the domains present are combined by weight, equally by default. That way a large domain cannot hide a small one: four hundred current training renewals do not bury one overdue permit. A domain with nothing dated is left out rather than counted as perfect, and a workspace with nothing dated at all shows No Data Yet rather than 0%.

The cap

A regulatory report that is past its window and not recorded as sent caps the score at 59%, which reads red whatever the target is. A missed fatality report is the most serious compliance failure the product can record, and it is not allowed to be one small deduction among many. The page names the report and the incident. The cap lifts the moment the report is recorded as sent, or the incident is closed.

Reading the page

• The number and its target, with the same chip the Home card shows, and the cap if one applies.
• By domain — each domain's score, weight, how many obligations were counted, how many are overdue and how many are at risk.
• What to address first — every obligation costing points, most costly first. The points beside each one are what it is taking off the score above, so fixing the top of the list moves the number most. Each row begins with the plant it belongs to — or All plants where it belongs to no single one and counts for every plant — so the same obligation at two sites reads as two pieces of work. Each row opens its record: the permit, incident, task or chemical, or the Training Matrix or Audit Readiness page.

Items in sections your role cannot open are counted in the score but not listed, and the page says how many were held back. The plant filter applies here as it does on the Home dashboard.

On a phone

The By domain and System Health tables become labelled cards below 760 pixels wide, one card per row, so no column is hidden and nothing has to be scrolled sideways. See Getting Started.

System Health

The second number on the Home dashboard, and the second section of this page. Where the Compliance Score asks whether dated obligations are being met, System Health asks how the site is doing on the things a date does not capture. Seven components, each scored on its own from 0 to 100, combined by weight:

Component	Weight	What it measures
Open incidents	30	the load of open incidents, by priority. An incident costs more the longer it stays open: a critical incident open for three months costs four times a fresh one. Closing it is what makes the cost fade, over the following thirty days.
Regulatory reporting	15	OSHA report deadlines in the last twelve months. Any report past its window and not recorded as sent costs half the component.
Deadline performance	20	the Compliance Score itself, counted once
Training currency	15	the share of required courses that are current; a completion expiring within thirty days earns half
Hazard communication	10	the share of chemicals with an SDS revised in the last three years
EPA: quarters in non-compliance	5	from the EPA's ECHO record of the site: twelve and a half points off per quarter, so eight quarters is zero
EPA: enforcement actions	5	twenty-five points off per enforcement action in the last three years

A component with no data is left out and the rest share its weight: a site with no chemicals is not marked down for hazard communication, and one with no EPA link is not marked down for the regulator's silence. Such a component still has a row, and its score reads "— no data" so the blank is explained rather than left to guess at. Every plant's health badge is the same calculation over that plant's own records.

The bands — Critical below 40, Good from 70 — are the workspace's. An administrator can move them in Admin Settings → System Health Bands, and the chip, the dial and every plant badge follow the same pair.

By plant

Below System Health, every plant is listed with its own Compliance Score and System Health: the same two calculations over that plant's records. Items that belong to no plant count for every plant. Each plant links to Plant Manager.

Weights

Each domain's share of the Compliance Score is a weight, equal by default. An administrator can change them in Admin Settings → Compliance Domain Weights: a domain with a weight of 0 stops moving the number but is still scored and still listed, so nothing disappears. The By domain table on this page shows the weight in force beside each domain's score.