Smart washroom management: how IoT improves facility operations

Washrooms are one of the most visible parts of any building and one of the hardest to manage well. In an airport terminal, a shopping centre or a large office, usage changes by the hour. A washroom near a busy gate can go from fine to unacceptable in twenty minutes, while one at the end of a corridor stays untouched all morning. Fixed cleaning schedules cannot keep up, and the people who notice first are your visitors.

We have built and operate a smart washroom platform for a large international airport. This article shares what we learned: which sensors make sense, how the system is built, and what changes for facility teams.

The problem with fixed rounds

Traditional washroom cleaning follows a schedule: every 30 or 60 minutes someone walks a route, cleans, refills and signs a sheet on the door. That approach has three weaknesses:

1. Wasted effort: staff clean washrooms that do not need it.
2. Slow response: problems between rounds stay unnoticed until a visitor complains.
3. No real data: signatures on a sheet do not prove quality, and they do not help with planning.

Demand-based cleaning turns this around: sensors measure what is happening, software decides what needs attention, and staff are sent where they are needed.

Which sensors are worth it

Not every sensor adds value. In our experience these four cover most needs:

• People counters (footfall): count entries without identifying anyone. Usage is the best predictor of when cleaning is needed.
• Odour and air-quality sensors: detect ammonia and other indicators, as well as CO₂, humidity and temperature, so ventilation problems become visible too.
• Occupancy sensors: show whether cubicles or rooms are in use, useful for queues and accessible toilets.
• Consumable sensors: soap, paper and hand-towel levels, so refills happen before they run out.

Feedback buttons ("How clean is this washroom?") are a good complement because they capture the visitor's perspective.

The architecture: from sensor to smartphone

A reliable system has four layers.

1. Devices and the edge

Sensors communicate via protocols such as MQTT or LoRaWAN with a local gateway or an edge PC on site. The edge device collects all messages and forwards them to the cloud. The important detail: it must survive network outages. In our airport installation, the edge service buffers up to 3 GB of messages on disk when the uplink fails and replays them with exponential back-off when it comes back. Delayed messages are flagged so the dashboard never confuses old data with live data.

2. Cloud ingestion and API

Messages arrive in a cloud IoT hub and are processed by an API service. In our case that is a NestJS API with MongoDB, which normalises sensor data, applies thresholds per washroom, creates tasks and stores history for reporting.

3. Dashboards

The live operations dashboard shows every washroom on one screen, colour-coded by health, so a supervisor sees at a glance where attention is needed. A drill-down shows the individual washroom and each sensor. A separate portal gives management and the client reports on usage, response times and service levels.

4. The staff app

Cleaning staff receive tasks on a mobile app with push notifications: which washroom, what the issue is, how urgent it is. They check in on arrival, confirm completion with a photo and escalate problems such as broken fittings. The app has to work with gloves on, in noisy environments and with patchy connectivity, so large buttons and offline awareness matter.

What changes for the facility team

• Faster response: issues are detected when they happen, not at the next round.
• Better use of staff: cleaners go where they are needed, which matters when staff are hard to hire.
• Fewer complaints: problems are fixed before visitors notice.
• Data for planning: usage patterns show which washrooms need more capacity and when.
• Proof of service: reports based on sensor data and check-ins replace paper sign-off sheets.

We are currently collecting the metrics from our airport deployment to publish concrete before-and-after figures.

Privacy and works councils

People counters count; they do not identify. Cameras do not belong in washrooms, and a good system does not need them. Staff data from the app (who cleaned what, when) can be personal data, so define its purpose and retention clearly and involve the works council early. We document every data flow for these discussions.

How to start

1. Pick a pilot zone with high usage and known complaints.
2. Define success together: response time, complaints, staff hours, consumable costs.
3. Install sensors and an edge device, connect them to the dashboard and app.
4. Run for six to ten weeks, tune thresholds and processes.
5. Roll out to further zones and sites based on the results.

One platform for the whole building

Washrooms are often the first step. The same infrastructure (edge devices, API, dashboards and staff app) can manage visitors, parking and workspaces. That is the idea behind Smart DigiBuild, the modular platform we develop for Four Corners Technology (4CT), where washroom operations are one module among several.

Frequently asked questions

Do we need new sensors if we already have some?

Not necessarily. Many existing sensors can be integrated if they offer MQTT, HTTP or another documented interface. We usually start by connecting what is there and add sensors only where data is missing.

How many sensors does a washroom need?

A people counter at the entrance is the minimum. An odour or air-quality sensor adds the most value after that. Consumable sensors pay off in high-traffic locations where running out of soap or paper causes complaints.

How do cleaning staff accept the system?

Involve them early. The app must save them time, not add paperwork. When staff see that they walk fewer unnecessary routes and get fewer complaints, acceptance usually follows quickly.

Can the data feed into our CAFM system?

Yes. Tasks, incidents and reports can be exchanged with common CAFM and ticketing systems through APIs or webhooks, so the washroom system does not become another island.

Key figures to track

A good system makes service measurable. These figures are worth tracking from day one:

• Response time: minutes from an alert (high usage, odour, empty dispenser) to a staff check-in.
• Alerts per washroom and hour: shows where capacity or cleaning frequency should change.
• Task completion rate: how many tasks are closed with photo proof within the target time.
• Complaints and feedback scores: before and after the pilot.
• Consumable usage: helps optimise orders and storage.

Agree on the baseline before the pilot starts, otherwise improvements are hard to prove.

Conclusion

Smart washroom management replaces fixed rounds with demand-based service: sensors measure, software prioritises and staff act. The technology is proven; success depends on reliable edge infrastructure, clear dashboards, an app staff actually like using and a well-run pilot. If your facility team is ready to move from clipboards to data, we would be glad to show you the system in action.

Plan your facility platform