Proactive Care
Risk Detection
Most building failures announce themselves before they happen — a dispenser draining faster than usual, a drain smelling for the third day, traffic climbing in a wing nobody re-scoped.
Request a free assessmentThe failure was visible for three days
Walk back from almost any cleaning complaint and you find a trail. The restroom that generated the email had been running low on supplies since Monday. The lobby floor that looked bad on Thursday had taken a fortnight of construction traffic through the side entrance. The smell someone finally reported had been mentioned, in passing, twice.
In the reactive model none of that is information, because there is no mechanism that collects it. The complaint is the first data point. Everything before it happened in a building nobody was reading.
Risk detection is the mechanism that reads it.
Four kinds of signal
Drift against an area’s own baseline. Not against a target — against itself. A dispenser that normally lasts nine days and is on pace for five has told you something, even though nothing has crossed a threshold and nothing is wrong yet.
Recurrence in inspection history. The same finding, in the same area, three inspections running. Individually each is minor and gets closed. Together they are a cause that nobody has addressed, and treating them as separate incidents is how a building stays broken for a year.
Consumption anomalies. Supplies emptying far faster or slower than the area’s traffic explains. Faster usually means traffic nobody re-scoped for; slower sometimes means a dispenser that is jammed, or an area people have stopped using.
Known load ahead. Term start at a school, a season change, an event on the calendar, a floor being renovated. This is the one that requires a person to enter what they know, and it is worth the small effort — predictable spikes are the cheapest risk to get right.
Ranked by consequence, not by count
Any system that scores risk purely on likelihood will bury you in high-probability irrelevance. The dispenser in a back corridor used by four people will reliably run low, and reliably matter less than the one in the main entrance where your clients arrive.
So the ranking asks a second question: if this goes wrong, what does it cost? A medical facility’s exam room, a school restroom during term, a lobby the day of a client visit — these carry weight that a raw probability score cannot see. The weighting is set per account, with the supervisor who runs it, because the answer is different in a warehouse and a clinic.
Detection ends in an owned task
A risk that is detected and not assigned is a liability. It creates a timestamped record that the condition was known, with nothing attached showing anyone acted — which is materially worse than not having looked.
So detection terminates in exactly one place: a task in the corrective actions queue, with an owner and a deadline, or a visit scheduled through predictive cleaning. What reaches a human as an interruption is the narrow subset covered by early warnings; the rest is absorbed by the schedule without anyone’s day being broken.
What it reads from
The readings come from IoT sensors and restroom monitoring. The history comes from smart inspections and the scored checklists in digital checklists. The ranking and the task creation happen in predictive management.
How you verify it
Delivered is not the same as proven
Every service below reports into CleanVision, so the work leaves a record you can audit — not a promise you have to trust.
-
Risk is ranked by what it costs
A dispenser running low in a back corridor and one in the main lobby are the same reading and a different problem. Ranking ignores that at your expense, so ours doesn't.
-
Recurrence is treated as a finding
The same issue in the same area three times is not three incidents. It is one unresolved cause, and it escalates as one.
-
Nothing detected is left unowned
A risk that gets flagged and not assigned is worse than one never detected — it creates a record that someone knew. Every flag becomes a task with a name and a due time.
Common questions
A threshold fires when a value crosses a line — the bin is full, the dispenser is empty. That is already a failure, just an early one. Risk detection looks at the trajectory: this dispenser is draining 40% faster than its own baseline, so it will be empty before the next scheduled visit. One tells you about now, the other about the visit you haven't made yet.
It would, if everything detected were sent to a person — which is the failure mode we designed against. Most detected risk becomes a scheduled task nobody is interrupted by. Only what is both urgent and consequential becomes a notification. See early warnings for where that line sits.
Yes, through inspection history rather than readings. Recurrence patterns — the same finding in the same area across weeks — surface causes no sensor is watching, like a fixture that keeps failing or an area whose scope no longer matches how the space is used.
It is closed with that outcome recorded, and that record matters. False positives that are never marked false train nothing. Over time the ratio for each area is visible to you, which is the only way to know whether the detection is worth its noise.
Excellence isn't a promise — it's a guarantee
Request a free assessment of your facility and see what a proactive operation catches that a reactive one bills you for later.
Talk to Protex