How to integrate cleaning, maintenance, reception, access control and landscaping

Consider some common situations. Reception gets a complaint about a leak and does not know whom to pass it on to. The landscaping crew prunes trees at the same time the cleaning team is washing the sidewalk. Access control lets a vendor in without notifying maintenance.

None of these problems is the fault of a specific team. They arise at the boundaries between services that do not talk to each other, and they are precisely the hardest to solve when each contract has a different person in charge. For the people who use the building, it hardly matters which company is responsible for what: what they notice is that the problem took a long time to fix.

The first step toward integration is having a single entry point for requests and incidents. It can be a ticketing system, an app or a well-organized service desk, as long as every request goes through it.

With a single channel, each request is logged, routed to the right team and tracked through to completion. The manager gains a complete view of what is happening in the building, and users no longer have to guess whom to ask for help.

1. To work, the channel needs simple rules

   Who can open tickets, how to classify urgency and how quickly each type of request should be answered.

Each service needs to see the others' schedules. A few arrangements prevent many of the conflicts:

• Preventive maintenance scheduled so it does not coincide with heavy cleaning of the same area.
• Post-construction cleaning built into the schedule of any repair or renovation.
• Pruning, mowing and fertilizing on days and at times communicated in advance to cleaning and access control.
• Access control and reception informed ahead of time about vendors, deliveries and scheduled services.
• Areas closed off for maintenance marked with signage and communicated to all teams.

A short, regular meeting among the leads of each service, with the week's or month's calendar on the table, is often enough to resolve many of these overlaps.

Receptionists, doormen and access control staff are in constant contact with the building and with the people moving through it. They are often the first to notice a burned-out light bulb, a leak or a restroom out of paper.

Training these teams to log and route incidents through the single channel turns access control and reception into sensors for the operation. All they need is to know what to look for and where to report it. The same goes for the cleaning team, which walks through every area daily and can flag maintenance problems early on.

Integrating does not mean everyone does everything. On the contrary, it requires clearly defining who is responsible for each task that sits on the line between services. Some examples that often cause confusion:

• Who cleans gutters, outdoor drains and grease traps?
• Who picks up branches and leaves after pruning?
• Who replaces light bulbs and who cleans the light fixtures?
• Who opens and closes technical rooms for other teams?

A responsibility matrix, even a simple one, keeps these tasks from going unowned. Ideally, it should be part of the contract or an operational appendix and be reviewed whenever a service is added or removed.

With a single channel and aligned routines, it becomes possible to monitor the operation as a whole: request response time by type of service, recurring incidents by area and adherence to each service's schedules.

This integrated view reveals connections that would otherwise go unnoticed, such as a rise in cleaning complaints caused by a water seepage problem that has not yet been fixed. It is the view a manager needs to act on causes, not just on symptoms. If it would help to talk about how to organize this in your building, the Milclean team is available.