I switched several client sites from fixed, time-based cleaning rosters to demand-based services using simple occupancy sensors. The results were lower costs, better-targeted cleaning, and happier occupiers — but it takes a clear plan to avoid confusion and compliance pitfalls. Below I share a step‑by‑step approach you can follow to convert your office cleaning schedule to an occupancy‑driven model using straightforward, off‑the‑shelf sensors and practical processes.
Why go demand‑based?
Before diving into steps, let me explain the upside from my experience. A demand‑based model:
Those benefits are real, but only if the implementation is clear to cleaning teams and building users.
Choose the right sensors
Not all sensors are equal. For most offices I recommend simple, privacy‑friendly occupancy detectors rather than cameras. Good options include passive infrared (PIR) motion sensors, door‑counting sensors, and low‑accuracy CO2 or sound sensors as proxies for occupancy. Brands I’ve used successfully: EnOcean PIR devices for low‑power installs, and Xiaomi/Aqara motion sensors for pilot projects where cost matters. For door counting, look at Flowscape or Countbox units.
Criteria I use when selecting sensors:
Map your spaces and objectives
Next I map the building and set objectives. Ask: which areas should be demand‑driven and which stay on a fixed schedule for compliance or service level reasons? Typical demand‑driven candidates:
Keep bathrooms, clinical rooms, and food prep compliant with regulatory cleaning frequencies — they usually remain scheduled. I draw a simple floor plan and mark sensor locations and intended cleaning triggers.
Define cleaning triggers and service levels
You need clear rules so cleaners and clients trust the system. My typical trigger setup:
Define service levels in plain language for staff: e.g., "Level A — Quick tidy and wipe hotspots; Level B — Full vacuum & bins; Level C — Deep clean." Map each trigger to a level and estimated time.
Design the sensor network and install
Installation needn’t be invasive. I follow these practical steps:
During installation, I keep a short log: sensor ID, location, install date, and initial test results. This makes troubleshooting faster later.
Set up data flow and dashboard
Raw sensor data is useless unless it drives clear actions. You need a simple aggregation layer (could be an off‑the‑shelf IoT dashboard, a facility management platform, or even a spreadsheet for pilots). I recommend platforms that can:
If you don’t have a CAFM, you can start with low‑cost automation: use IFTTT or Node‑RED to convert sensor events into emails or push notifications to supervisors and cleaners’ phones.
Pilot and calibrate
Always pilot in one or two zones for 4–8 weeks. In pilot I focus on:
Use a simple log to note mismatches and tune rules. Expect a few iterations before you’re confident.
Train teams and communicate with occupiers
This is where projects succeed or fail. I run short training sessions for cleaning teams covering:
Communicate with building occupants via email and signage: explain why schedules are changing, how to report missed cleans, and reassure them on privacy (no cameras, no personal data). I provide a one‑page FAQ for facilities managers and a poster for shared spaces.
Measure performance and report ROI
Track key metrics for 3 months post‑rollout:
I build a simple table to compare pre/post metrics. Example:
| Metric | Before | After (3 months) |
|---|---|---|
| Cleaning hours/week | 120 | 92 |
| Consumables cost/month | £1,800 | £1,250 |
| Occupant satisfaction | 72% | 86% |
Typical payback on sensor hardware vs labour savings is 3–12 months depending on site size and labour rates.
Maintain and scale
Operational discipline keeps the system honest:
When scaling across multiple buildings, standardise sensor models, naming conventions, and trigger rules where possible to reduce operational complexity.
Privacy, compliance & pitfalls to avoid
Key safeguards I enforce on every project:
Common pitfalls: relying on a single sensor for a large space, failing to train staff, and not communicating changes to occupants. Each of those undermines trust in the system.
Switching to demand‑based cleaning is a practical, measurable way to improve efficiency and service — but it’s an operational change, not just a technology install. If you plan the mapping, triggers, pilot, training and maintenance upfront, you’ll get sustainable results that both reduce costs and deliver cleaner, healthier workplaces when people need them most.
