One Front Door for Facilities: Corporate Campus Requests Across FM, IT and Janitorial

Ask an employee on a corporate campus what happens when something is broken and you will hear a version of the same story. They were not sure who to tell. They mentioned it to someone. They filled in a form once and never heard back. Now they mostly do not bother.

That last part is the expensive bit. A facilities operation is judged on the requests it receives, and the requests it never receives are invisible. A campus where people have stopped reporting looks quiet on a dashboard and feels shabby to everyone who works there.

The root cause is almost never the maintenance team. It is intake. We have spent years building request routing for venues, where the same problem shows up with guests instead of employees, and the fix transfers directly.

The Employee Should Not Have to Know Who Owns It

Here is the design error at the centre of most workplace request systems. They are organised around the org chart.

There is a facilities portal, an IT service desk, a cleaning email address, and possibly a security number. Each is well run. And the employee reporting a problem is required to correctly categorise it before they can report it at all.

Consider what that asks. A flickering light in a meeting room: facilities. A projector that will not connect: IT. A meeting room that was not reset after the last booking: cleaning, or possibly workplace services. A warm room: facilities, unless it is a server room, in which case both. An employee has no reason to know these boundaries and no interest in learning them.

Location Accuracy Matters More Than Category Accuracy

If you have to choose what to get right at intake, choose location.

A miscategorised request in the right room is a thirty-second reroute. A correctly categorised request in the wrong room is a technician walking three floors, finding nothing, and closing it as unable to reproduce. The second failure is far more expensive and much harder to detect afterwards.

This is why QR codes at the point of the problem work so well in workplaces. A code on a meeting room door, a printer, a kitchen or a restroom carries the location as data rather than relying on someone typing "third floor, the one near the stairs". Listo supports unlimited locations and QR codes with no per-location charge, which matters on a campus where useful granularity means hundreds of them.

One practical warning. Location naming should match how employees describe the building, not how the estate plan labels it. If everyone calls it the north kitchen and the system calls it Pantry 3.2, you have built a translation layer that will be got wrong constantly.

Requests That Span Two Teams

Every operator eventually discovers what share of real requests do not belong to exactly one team. Guidance tends to skip this, and it is where most systems fail.

What you need is the ability to add a second team to an existing request rather than closing it and raising a new one. Every time a request is retyped at a handoff, you lose the history and both teams lose confidence that the other has it.

Cleaning Has a Compliance Dimension

Janitorial requests are usually treated as the softest category, and they carry the clearest regulatory floor.

OSHA's general industry sanitation standard, 29 CFR 1910.141, requires employers to provide a minimum number of toilet facilities, keep washing facilities in sanitary condition, supply hand soap and running water, and keep all places of employment clean to the extent the nature of the work allows. OSHA's restrooms and sanitation guidance is explicit that employees must be able to use facilities when needed, without unreasonable restrictions or extended delays.

Read operationally, that is a response-time obligation rather than a policy statement. A restroom out of service for a day on a floor with no alternative is a compliance question, not a housekeeping one, and having a timestamped record of when it was reported and resolved is the difference between demonstrating compliance and asserting it.

Deskless Teams Need Mobile Capture

Facilities technicians, cleaners and security officers are deskless workers, and the same technology mismatch applies to them as to any frontline population. Emergence Capital's research found that around 80 percent of the global workforce works away from a desk, that 60 percent were unsatisfied with the technology they were given, and that over 80 percent had been issued a desktop or laptop.

The consequence in a facilities operation is specific. If work is recorded at a desk at the end of a shift, it is recorded from memory. Timestamps become approximate, detail is lost, parts used go unrecorded, and your asset history degrades into something you cannot plan from. Capture at the point of work is not a convenience feature, it is what makes the data worth having.

Planned Work and Reactive Work in One Place

Facilities teams run two streams, and separating them into different systems is a common and costly decision.

Planned work is scheduled: inspections, filter changes, testing, seasonal work. Reactive work arrives unpredictably. The reason they belong in one system is that they compete for the same technicians, and a team that cannot see both cannot make sensible trade-offs during a busy week. Planned work is also, in practice, the first thing sacrificed when reactive volume spikes, and if it lives in a separate calendar nobody notices it was skipped.

Listo supports scheduled recurring task requests alongside routed reactive ones, which means planned work generates itself into the same queue rather than depending on somebody opening a spreadsheet.

Closing the Loop With the Person Who Reported It

The most under-built part of workplace request systems is the message back. Most send an automated acknowledgement, resolve the issue, and never tell the reporter anything again.

That single gap explains most of the decline in reporting rates. From the employee's side, a request they never heard about again is indistinguishable from one that was ignored. They have no way to know the light was fixed the following Tuesday, because they were in a different meeting room by then.

Three notifications do almost all the work. An acknowledgement that names the team, so the reporter knows it reached a human. A resolution message that says what was done, briefly. And, where relevant, a message explaining why something will not be fixed soon, which is far better received than silence. Employees are considerably more tolerant of a six-week wait for a part than of not knowing.

There is a second-order benefit worth naming. A resolution message reaching the person who reported it is your cheapest quality check. If the light is still flickering, they will say so immediately, which is how you catch premature closures without auditing anything.

Contractors, Vendors and the Boundary Problem

On most campuses a meaningful share of the work is delivered by third parties: cleaning contractors, HVAC specialists, lift engineers, security providers. Each usually arrives with its own system and its own reporting.

The boundary is where records go to die. A request is raised internally, passed to a contractor by email or phone, completed on site, and the internal record is closed by someone who was not there and does not know what was done. Six months later nobody can say whether the same fault has recurred three times or once.

Two workable approaches. Bring contractor supervisors in as users of your intake system, which is usually a commercial conversation rather than a technical barrier, and means the completion note is written by whoever did the work. Or keep the internal request open until an internal person verifies and closes it with a note of what the contractor did and what was replaced.

Whichever you choose, insist on one thing in the contract: a shared definition of response time and a monthly review of the same numbers. Agreements written around visit frequency and headcount measure inputs. Agreements written around acknowledge and resolve times measure what the building actually experiences.

What to Measure

1. Time to acknowledge - Reported to accepted by a named person. This is what the employee experiences and the strongest driver of whether they report again.
2. Time to resolve - Accepted to closed. Read separately, because a fast acknowledge with a slow resolve is a parts or contractor problem rather than a routing one.
3. Reopen rate - Requests closed and raised again for the same issue. A rising reopen rate usually means closure targets are being met by closing things prematurely.
4. Requests per location, rolling quarter - Ranked. This is how you find the room, floor or asset that needs a capital fix rather than a fifth visit.
5. Reporting rate by team or floor - Areas that report almost nothing are rarely problem-free. They have usually given up.

Hybrid Working Changed the Demand Pattern

One change worth accounting for explicitly: on most campuses demand is no longer evenly spread across the week. Tuesday to Thursday now carry a disproportionate share of occupancy, and request volume follows.

That has practical consequences for how facilities work is staffed and scheduled. Planned work belongs on the quiet days, where it does not compete with reactive volume and does not disturb anyone. Reactive capacity needs to be weighted toward the busy middle of the week rather than spread evenly. And consumable restocking cadence set from a pre-hybrid pattern will consistently run short on the peak days and waste effort on the others.

Requests per location by day of week is the report that shows you this, and it is usually the first genuinely surprising output of a new intake system. Most estates teams find that their assumptions about which floors are busy are a year or two out of date.

A Realistic First Phase

Do not attempt a campus-wide deployment as a first step. The pattern that works is narrower.

Pick one building or one floor. Put QR codes on meeting rooms, kitchens and restrooms, which between them generate most workplace requests. Route to three teams: facilities, IT and cleaning. Publish acknowledge and resolve times to the people in that building, monthly.

Two things usually happen in the first month, and both are useful. Request volume goes up sharply, which is not a new problem appearing but an existing one becoming visible. And the distribution across teams is not what anyone predicted, which tells you where to put capacity.

From there the extension that matters most is usually the second team on a request, because by then you will have a list of the cross-boundary issues that kept circulating. Listo is used in enterprise environments specifically to connect facilities management, IT and janitorial services in one routing layer, and the mechanics are covered on our platform page and in our enterprise overview.