Dashboard

Tom Bradley opens PTRS every morning before the first family arrives at Claymont, and this is the screen he lands on. Seventeen panels, pulled together from twelve different parts of PTRS, meant to answer four questions in one glance: is any room out of ratio, is anything about to expire, did anything happen overnight, and how many children are we expecting. This page is for Tom, and for anyone who reads this screen first thing.

This screen has no address of its own

There is no separate home-screen address; it is simply the page you land on the moment you sign in. Every signed-in account sees it, and it applies no check of its own before showing you a panel. A guardian who types the address directly is not sent anywhere else, and instead sees a screen of panels that each quietly fail behind the scenes.

What the dashboard is for

Instead of opening four separate screens every morning, one screen answers: is a room out of ratio right now, is a credential or a licence about to lapse, did anything happen while nobody was watching, and how many children are expected today. That is the whole idea, and most of the panels genuinely do this.

Who uses it

Who can do this

• Front-line staff
• Site director
• Regional director
• Organisation admin
• Super admin

There is no check on this screen at all. Any signed-in account reaches it, including a guardian or a read-only account, for whom every panel behind it quietly fails and shows its own empty state.

Because the screen pulls together twelve modules, what you actually see depends on which of their own rules you satisfy:

Panel group	Rule behind it	Who it admits
Ratio banner, headline tiles, site overview, activity feed, attendance trend, expected vs actual	The shared dashboard rule	Staff and above
Compliance by location, compliance trend	The reporting rule	A site director, a regional director, an organisation administrator or a super admin
Recent incidents, incident trend, OCCL deadlines	The incident-submission rule	Staff, a site director, an organisation administrator or a super admin
Credential timeline, staff readiness, urgent actions	The Staff module's own rule	Staff and above
CACFP meal service	The CACFP module's own rule	Staff and above
Expiring licences	The Centers module's own rule	A site director, an organisation administrator or a super admin

A staff member therefore sees the two compliance panels in their error state; a regional director sees the three incident panels in theirs.

A day in the life

Tom glances at the ratio banner first, because that is the one panel built to tell him the truth even when it cannot check: if the figure cannot be read, it says so in words rather than staying quiet. He trusts it over the smaller ratio number lower on the screen, because the two use different rules and can disagree about the very same room.

He scans the ratio banner, checks the count of things about to expire, glances at the incident panel, and moves on with his morning. What he does not realise is that three of those panels, the alerts count, the critical incidents count and the OCCL deadline panel, are built to warn him and are currently unable to, because of one small mismatch each between the word PTRS sends and the word the panel is looking for.

What has been built

Screen	What it is	What it can do today
The home screen	Seventeen panels in four visual groups	Shows live figures from twelve modules; four of the seventeen never turn from calm to alarmed no matter what happens

What stays your job

• Trust the ratio violation banner over the smaller ratio figure lower on the screen. They can disagree about the same room, and the banner is the one using the actual rule for that room's age group.
• Do not trust a grey compliance badge to mean "compliant". A site in violation is shown in the exact same grey as a healthy one, with the word itself still printed and correct.
• Check the actual incident list rather than the Critical Incidents count or the OCCL Deadlines panel. Both currently read zero and empty respectively, no matter what is actually open.
• Do not read the attendance trend chart or its small sparkline as a measurement of anything. Nothing currently fills in the table it reads from.

What happens on its own

Nothing on this screen runs on a timer of its own; none of PTRS's background jobs belong to this module. Three things still happen without being asked for:

• Two of the nine figures this screen owns refresh automatically every thirty seconds: the ratio snapshot and today's attendance.
• A live event from elsewhere in PTRS, a check-in, a compliance evaluation, or an OCCL deadline warning, refreshes the whole screen's figures at once rather than just the one that changed.
• A loading skeleton is shown for exactly eight tenths of a second, whether or not the real figures have actually arrived yet. On a slow connection you may see empty panels rather than a loading state.

The last of PTRS's six live-update connections

This screen's own live-update connection is the last of six across the whole product, and the first one where a message actually sent is also a message something is listening for. Any signed-in account can open it, of any role, and on connecting it is placed into a group for each site it can reach.

Six different sources can send an update over this connection. Three of them work as intended: a check-in or check-out, a compliance evaluation, and regulation loading progress. Two of the six are never actually sent by anything, so subscribing to them does nothing. One more is sent and nothing is listening for it.

One thing about this connection is worth knowing regardless of your role: most of what is sent over it goes to every connected person on the entire installation, not just the group for the site it concerns. The site grouping exists and is mostly unused, so an update naming a site, a headcount, a ratio or a compliance score can reach every signed-in account on every organisation sharing this installation.

What it connects to

Module	The connection
Attendance	Four of this screen's own figures are attendance reads, and the child detail panel opened from the Attendance screen is the only place that reads this screen's own member list. See Attendance
Compliance	Two panels read the compliance summary, and the colour behind each site's badge does not match what that summary sends. See Compliance
Incidents	Three panels read incident figures, and all three compare against wording the incident records do not actually use. See Incidents
Staff	Three panels read credentials, background checks, training and onboarding. See Staff
CACFP	One panel reads today's meal claim and allergy alerts. See CACFP
Centers	The expiring-licences panel is a Centers screen shown here. See Centers
AI Assistant	The regulation-loading progress bar rides on this screen's own live-update connection. See AI Assistant
Notifications	Half of the activity feed is meant to show guardian notifications, and none has ever been sent. See Notifications

Not yet available

Filtering the whole screen by site

Every one of this screen's own figures can be asked for one site at a time, and nothing on the screen actually asks for one; changing the site selector only changes which remembered copy of the whole organisation's figures you are looking at. Five panels work around this by filtering what they were given after the fact; the activity feed and the attendance trend chart do not, and both were already working from a list capped well below the whole organisation to begin with.

An attendance trend, or any historical attendance figure on this screen

The chart and the small sparkline both read from a table meant to be filled in overnight, and nothing in PTRS currently writes to it. Both render empty. This is the same table the AI Assistant reads from seven times and Analytics reads from eight; see How PII is protected for that side, and Analytics for the reporting side.

A guardian notification in the activity feed

Half of the feed is meant to show entries like a guardian being notified or a no-show alert going out. PTRS has never sent a notification of any kind by any means, so this half of the feed can never actually show anything.

Three finished panels with no page showing them

Three panels are fully built and not shown anywhere: a streak-leaders panel duplicating what the child detail drawer already reads, a meal-program panel that duplicates one already shown, and a program-snapshot panel.

A working expected-vs-actual figure at a site with no program schedules

This panel's logic is correct, and what it is given can be wrong. When a site has no program schedules to build an expected list from, it falls back to counting every active member in the whole organisation as expected today, with no arrival window to measure against, so nobody is ever marked absent and the figure reads as a large expected count against a suspiciously clean zero absences.

A child's site or attendance streak inside the drawer opened from this screen

The drawer opened from the Attendance screen expects two pieces of information this screen's own member list does not actually send. Its site line is blank, its peer comparison ends up comparing against the whole organisation instead of one site, and its Check Out control cannot find the session it needs to close.

Where to go next

• What each of the seventeen panels reads, and what to trust it for → What each panel on the home screen shows
• Who can reach each figure, and its live-update connection → Who can do what on the dashboard
• A panel is wrong or empty → Dashboard troubleshooting