Restroom Monitoring

The complaint you never hear is the expensive one

Almost nobody complains about a restroom. They form an opinion about the building, tell a colleague, and leave. The facilities team hears about a fraction of what people experience — usually the fraction that had already escalated.

That silence is the reason restrooms damage reputations so efficiently. The feedback loop that would let you fix the problem doesn’t exist, so the first signal arrives as a review, a tenant conversation, or a contract not renewed.

Two layers: conditions and reactions

Sensors measure what is objectively happening — occupancy, supply levels, odor, leaks — continuously. That’s covered in detail under IoT & sensors.

A locked tablet captures what people actually felt, at the moment they felt it. One tap on a face: bad, neutral, excellent. No app, no account, no form. The whole interaction is under two seconds, which is the only reason anyone completes it.

The two layers answer different questions, and they need each other. Sensors know the room has taken 200 visits and the soap is low; they don’t know whether that adds up to a bad experience. Ratings know people are unhappy; they don’t know why. Together they usually do.

The device is locked, and the sensors are deaf

This is the part worth reading closely, because a screen in a restroom deserves scrutiny.

Cameras and microphones on the tablet are fully disabled — not unused, disabled. The device is locked to the feedback function: users cannot change configuration, open a browser or reach anything else. It is designed for one purpose and physically constrained to it.

We take the position that a capability which exists can eventually be switched on by someone with a different priority, so the right answer for a restroom is a device that cannot do the thing in the first place.

From tap to dispatch

A negative rating raises an alert to the assigned team with the location attached. Not a data point for a monthly chart — an alert, with a response window defined by your service level and the escalation described under smart alerts.

Single taps are read in context rather than acted on individually. One negative rating during a quiet hour is noise; three within ten minutes, with the occupancy sensor confirming traffic, is a room that needs someone now.

What accumulates

Every rating and reading builds history per location — not per building. Restrooms in the same building diverge, and an average across them hides exactly the one that is failing.

Over weeks, that history is what lets the frequency be set from real use rather than from a timetable, and it feeds the account’s client feedback score and its certification. The people using the room end up with a vote in whether the account passes.