What the Compliance Radar can and cannot show
Tom wants to know what compliance figures PTRS can produce at all, and why the screen shows so few of them. This page lists every figure, who can see it, what it is worked out from, and the five that are built and reachable from no screen. The arithmetic behind the score is on How the compliance score is calculated.
Who can see compliance figures
Site directors, regional directors, organisation administrators and super admins, for everything on this page. Nobody else. PTRS also checks that your account belongs to an organisation, refusing with "Organization context is required." if not, and, for the figures about one site, that the site is in your organisation, refusing with "Access denied to this location." if not.
The Compliance Radar page lets a read-only account in, and PTRS then refuses every figure on it. See Compliance.
Nothing here can be changed. There is no way to resolve an alert, acknowledge one, run the check on demand, or record an inspection result.
The twelve figures
| Figure | Shown by |
|---|---|
| The organisation dashboard | The gauge, the area cards, the alerts table, and three panels on the main dashboard |
| One site's rule-by-rule detail | Nothing |
| The better inspection simulation | Nothing |
| One site's credential status | Nothing |
| The score history | Nothing |
| A site's compliance PDF | Nothing |
| Documentation status | The Documentation Completeness card |
| Safety records | The Safety Records card |
| CACFP status | The CACFP Compliance card |
| The staff list | The Credential Tracker panel and the Credential Currency card |
| The incidents list | The Incident Reporting card |
| The inspection checklist | The badge under the gauge and the simulator |
What each one is worked out from
The organisation dashboard
Remembered for five minutes and forgotten by the five-minute compliance check whether or not anything changed. It reads the latest saved result per active site, then:
| Figure | How | Today |
|---|---|---|
| Overall score | The average of the latest result per site | 0, because there are no results |
| Sites | The number of active sites | Real |
| Compliant sites | Sites scoring 80 or more | 0, because a site with no result scores 0 |
| At-risk sites | Sites scoring 60 to 79 | 0 |
| Sites in violation | Sites scoring below 60 | Every active site |
| Per-site scores | Score, status and six area lines per site | Score 0, status Violation, no area lines |
| Area breakdown | Six lines, the average per area | Six lines at 0 |
| Active alerts | Up to 100 unresolved alerts, newest first | None |
A site with no result is scored 0 and called a violation. It is not told apart from a site that genuinely fails.
The page reads these figures under names PTRS does not use, so the page sees none of them. The area cards then look the six areas up under a second set of names that also matches nothing.
One site's rule-by-rule detail
The overall score, when it was last checked, six area scores, the check results and the site's unresolved alerts. With no saved result it reports a score of 0, a "last checked" time of now rather than never, six areas at 0, and six made-up check results named after the areas rather than after the eight real checks, each reading "compliance needs attention (score: 0)".
The better inspection simulation
PTRS's second simulator is the better of the two, and no screen can run it. It works out credentials live from the staff records at the site: any credential past expiry costs 20 points and any expiring within 30 days costs 5, between 0 and 100. The other five areas are read from the site's latest saved result, and each falls back to 100 when there is none. There is none, so all five are 100.
Worked out The outcome is Pass at 80 or above, Conditional at 60 or above, and Fail below that, using the screens' weight table. With credentials at their worst possible value, 0, the five other areas at 100 weigh in at exactly 80.0 (25 for ratios, 15 for documentation, 20 for safety, 10 for CACFP and 10 for incidents), which is exactly the Pass line. The simulation cannot return anything but Pass for a site with no saved result, which is every site. It can do this while listing expired credentials by name as critical findings. A Pass with critical findings is the normal case, not the exception.
One site's credential status
Per active staff member, each credential is expired, expiring soon within 30 days, or current, with the days remaining. A person is fully compliant only when nothing is expired or expiring. This is the only figure here that is correct from end to end, and no screen shows it. It counts every credential a person holds, not the four required ones check 2 looks at, so its totals would not match the Credentials area even once that area existed.
The score history
Every saved result in the organisation for the last 90 days unless told otherwise, with the site's name, newest first, with no limit. A working five-minute check across three sites would produce about 78,000 lines in 90 days. Empty today.
A site's compliance PDF
A branded page with the overall score in a colour band (green at 90 or above, amber at 70 or above, red below), an area breakdown table and an alerts table, named "Compliance-Summary", the site and the date. Two things to know before quoting it. The standing text says the score "is calculated across 6 weighted categories", which describes the design. And the percentage column divides each area's score by its weight, so an area scoring 92 with a weight of 25% prints 368.0%. That column is not a percentage of anything. With no saved result the PDF prints 0.0% overall and six areas at 0.0.
The six card feeds
| Feed | Read from | Notes |
|---|---|---|
| Documentation status | Personnel file requirements and documents | One line per requirement, total is the active staff count, complete counts verified documents. No document can ever be verified, so every line reads 0. |
| Safety records | Safety records | Nothing creates one. Always empty. |
| CACFP status | CACFP records | Real. Each shown as current, incomplete or overdue. |
| Staff list | Staff members and their credentials | Real. Active staff, by surname. Six roles are given friendly labels; any other shows as PTRS stores it. |
| Incidents list | Incidents | Real. The most recent 100. "OCCL notified" is yes only for Submitted or Acknowledged. |
| Inspection checklist | Inspection records | Nothing creates one. Always empty. |
The incidents list is read by a card that looks for statuses spelt in lower case while PTRS sends them capitalised, so the Open tile reads 0 whatever the data says.
Built and reachable from no screen
Five of the twelve figures are built and no button reaches them: one site's rule-by-rule detail, the better inspection simulation, one site's credential status, the score history, and the compliance PDF.
What that costs you:
- There is no way to export a compliance PDF from PTRS.
- There is no way to see one site's rule-by-rule detail, although the page for it is built.
- There is no way to run the better inspection simulation. The button labelled Simulate Inspection runs an animation over an unrelated, empty list.
- There is no score history, so no trend can be drawn even after the check is fixed.
Messages PTRS can give you
PTRS has three messages written for compliance, and uses none of them. The messages you actually see are "Location not found.", "Access denied to this location." and "Organization context is required." A site with no saved result is treated as scoring zero rather than as unchecked, which is why the dashboard calls every site a violation rather than unevaluated.
Settings
Two figures are settings that whoever looks after PTRS could change: the "expiring soon" window used by the credential status and the better simulator, 30 days; and the most alerts the dashboard will list, 100. Both run at their defaults everywhere. Check 2 in the score uses its own fixed 90-day window, so the score and the credential screens disagree about what "expiring soon" means by a factor of three.
Related
Checked against PTRS on 7 September 2026.