Ask a property manager what tenants complain about and you get a list shaped by whoever shouted most recently. Ask the request log and you get a different list, in a different order, and the two rarely agree. The gap between them is where most tenant satisfaction work goes wrong: buildings fix the loudest thing instead of the most common one.

What follows is the pattern that shows up across commercial office buildings when you sort by volume instead of by volume of voice. It comes out of request logs, not a survey, and the shape holds from building to building.

1. Temperature, and it is not close

Too hot, too cold, hot in the morning and cold by three. In almost every office building, thermal comfort generates more requests than everything else combined, and it is the category most likely to be reported repeatedly by the same person because the underlying condition never fully resolves.

The operational trap is treating each report as a new incident. The fifth complaint from the same suite in a month is one unresolved problem, with a person who has now decided the building does not listen, and the difference between those two readings is whether your system can see that history at a glance.

2. Restrooms

Cleanliness, supplies, a fixture that runs. Individually trivial, collectively the second largest category, and the one with the shortest fuse: nobody submits a polite ticket about a restroom. They report it once, and if it is still like that at lunchtime they tell their office manager, who tells you in a different tone.

Restroom issues are also the clearest argument for scheduled rounds. A porter walking a set route four times a day catches most of this before anyone reports it, which converts a complaint category into an invisible one.

3. Access and badges

A new hire whose badge does not work. A contractor who cannot get to the mechanical room. A tenant administrator who has emailed twice about a departure. These are administrative instead of physical, which is why they get triaged below a leak and why they annoy people disproportionately: the person waiting knows nothing needs to be fixed, only that someone has to press a button.

The complaints that damage a tenant relationship are rarely the expensive ones. They are the ones where nothing was broken and nothing happened anyway.

4. Cleaning quality in the suite

Bins not emptied, vacuuming missed, glass left marked. This category is unusual because the tenant is often reporting on a vendor you manage but do not supervise directly, and because the evidence disappears overnight. Without a log, month three of a declining cleaning contract feels like the tenant becoming fussy instead of the vendor slipping.

5. Lifts

Wait times more than faults. A lift out of service is an incident everyone understands; a lift bank that is slow at 8:50 is a grievance that never quite becomes a ticket and comes up in every renewal conversation instead.

6. Noise and construction

Almost entirely a notice problem instead of a noise problem. Tenants tolerate a fit-out on the floor above if they were told, and they escalate to the landlord's asset manager if they were not. This is the cheapest category on the list to fix, because the fix is a broadcast message sent two days earlier.

7. Parking and visitors

The nine o'clock arrival with nowhere to park, the reserved stall someone else is in, the guest who could not get through the lobby. Low volume, high emotional weight, because the tenant was trying to impress someone at the time.

What is missing from the list

Two things you would expect near the top and rarely find there.

Security incidents are far down the volume list in most office buildings, which surprises people who have just sat through a security vendor's pitch. They matter enormously per event and almost never in aggregate, and a programme built around them will misallocate attention for years.

Amenities barely register as complaints at all. Tenants do not file tickets about a conference room they could not book; they simply stop trying and mention it eleven months later when someone asks why they are looking at another building. Amenity dissatisfaction is invisible in a request log by its nature, which is exactly why utilisation data matters more there than complaint data.

What the ranking is telling you

Two things, and neither is about the categories.

First, most of the list is recurring instead of novel. Buildings that measure repeat rate by suite, instead of total volume, find a small number of locations generating a disproportionate share of everything, and fixing those is a capital conversation instead of a service one.

Second, satisfaction tracks acknowledgement more closely than it tracks resolution time. A tenant told "we have it, the engineer is on four, expect it after lunch" is calm. The same tenant with the same wait and no message is composing an email to their broker. That is not a platitude; it is why closure notification is the single highest-return switch in most buildings.

The survey trap

Annual tenant satisfaction surveys are useful for benchmarking and almost useless for operations, because they arrive months after the events that shaped the answers and they average away the thing you need: which suite, which floor, which week.

The request log is the continuous version of the survey, and it is already in your building. It has no response bias, no recall error and no seasonal timing problem. What it lacks is anyone reading it as a whole, which takes twenty minutes a month and almost nobody does.

What to do with this on Monday

Sort last quarter by category and by suite. Two lists, ten minutes. The second one is the interesting one.
Find the repeat reporters. Anyone who has raised the same category three times has an unresolved condition and a forming opinion.
Check acknowledgement time separately from closure time. They have different causes and only one of them is free to fix.
Turn on closure notifications. If they are off because someone worried about noise, turn them on for a month and count the "any update?" emails before and after.
Send notice before disruption, not during. Fit-outs, water shutdowns, fire tests, lift maintenance. Two days is enough.

One caution on acting from a ranked list. Volume tells you where the work is, not where the risk is. A category with four reports a year can still be the one that produces an incident, and thermal comfort at the top of the list does not mean the sprinkler valve inspection can wait. Read the ranking as an operations plan, not a risk register, and keep the two conversations separate.

Where BuildingHub fits

Requests, repeat rate by suite and acknowledgement time all come out of the work order records in Operations Hub, and broadcast notices go to the tenants a disruption affects instead of the whole building. Rounds and inspections run in the same place, which is how the restroom category stops being a category. Related: the work order that closes on time.

What tenants complain about, ranked