How can occupancy data improve cleaning schedules?

On a Friday in a hybrid office, a cleaning team may spend the evening wiping desks nobody sat at, while on Tuesday the washrooms on the busiest floor fall behind by mid-morning. Occupancy data fixes that mismatch by showing which spaces were actually used, how heavily and when. Cleaning effort can then follow demand: busy washrooms serviced more often, unused meeting rooms and desks skipped, and staff sent where they are needed.

The aim is better service where it matters and less effort where it does not, which is not the same as an automatic cost reduction. Making it work means keeping a fixed baseline for hygiene-critical and statutory tasks, moving only suitable spaces to demand-based cleaning, using aggregated data that does not track individuals, and changing the cleaning contract so that the new way of working is paid for and measured.

Same tasks, different trigger

A traditional cleaning specification lists tasks and frequencies: every desk wiped daily, every meeting room cleaned twice a day, washrooms checked hourly. Where use varies from day to day, that guarantees cleaning empty rooms while busy areas fall behind. Demand-based cleaning keeps the task list but changes what sets it off. Work happens when usage passes an agreed threshold, at agreed intervals for spaces in use, and at a reduced or minimum frequency for those that are not.

Counters, sensors and bookings

A simple count combined with a booking feed is often enough for a first phase. Each extra data source adds cost and complexity, so add one only when a gap appears.

What must be cleaned regardless

Demand-based cleaning should never mean that a space goes uncleaned because a sensor reported it unused. A fixed baseline stays in place for hygiene-critical areas such as kitchens, washrooms and clinical or food-preparation spaces, at frequencies set by the operator's risk assessment and the applicable rules. It also covers statutory or contractual tasks that must happen at set intervals, and periodic deep cleaning that does not depend on recent use. Any space whose sensor has failed or whose data is missing should fall back to the baseline, never to "no cleaning required".

Privacy, for occupants and for cleaners

Occupancy data can become personal data if it identifies, or can be linked to, individuals; desk sensors in an office with assigned seating are the obvious case. In the EU, the GDPR's principles of purpose limitation and data minimisation point towards collecting only what the cleaning purpose needs, which usually means counts and used-or-unused status by space, not identities. The purpose, retention period and who can see the data should be agreed with your data protection adviser. It also helps to explain the system to occupants: people accept a washroom counter far more readily than an unexplained sensor under their desk.

The same care applies to the cleaning staff. Task apps that record completion times can slide into monitoring individual performance. Decide in advance what is recorded, why and how it will be used, and involve the cleaning contractor and its staff in that decision.

Questions for whoever owns the cleaning contract

Cleaning contracts are commonly priced on fixed frequencies and hours, and a demand-based service sits awkwardly on that basis. How the commercial model should change is a matter for the client's FM procurement lead or adviser, but the data design throws up questions they will need to answer before the system goes live:

• Will the contract drop the rota and specify outputs, such as standards of cleanliness and response times? If so, how will those outputs be measured?
• Is a fixed baseline team, with a variable element driven by measured use, a better fit than a single fixed price?
• What response is expected when a usage trigger fires, for instance how soon after a washroom reaches its visit threshold must it be serviced?
• How will the contractor receive tasks (usually through a mobile app or the facilities management system), how is completion recorded, and how is quality checked independently, through periodic inspections or occupant feedback?

The occupancy data, the triggers and the integration can be designed to support any of those answers, but they cannot settle them.

Better service first, savings second

What you can reasonably expect is better-targeted effort and faster response in busy areas. Whether total cleaning cost falls depends on the contract model, on how much of the old rota was spent on unused space, and on whether released hours are removed or redeployed. Reducing hours is a commercial decision between owner and contractor, and the business case should keep it separate from improvements in service quality. Certification schemes have started to take notice, too: WiredScore's SmartScore scorecard for hotels lists cleaning orchestration under operational excellence. That shows market interest; it does not prove every building will benefit.