Building maintenance management software sells to two buyers with opposite problems, and the mismatch is why so many implementations feel heavy. A facilities management company needs contracts, SLAs, client reporting and billing. An organisation maintaining the building it occupies needs a plant register, a statutory inspection list, a schedule it can staff, and a way for colleagues to report faults in ten seconds. This page is written for the second, and specifically about how small the useful register actually is.
The useful register is a few dozen items, not a few hundred
Boilers, chillers, air handling, pumps, lifts, generators, fire systems, water systems. That list carries nearly all the cost and nearly all the risk in most buildings. Registers that run to hundreds of rows are usually counting rooms, doors and light fittings, which adds volume and no schedule.
Statutory items belong in the same register with a flag
Lift inspections, pressure systems, fire alarms, emergency lighting. Intervals set externally, evidence retained, completion that should not be casually adjusted. One register with flags beats two lists, because two lists drift and the audit finds the gap between them.
Reporting has to be usable by people who are not maintenance
A QR code by the door, three fields, a photograph. Anything heavier and faults arrive by email and live in an inbox. This single design choice decides whether the fault stream in the system reflects the building or a fraction of it.
The schedule is costed the same way as any other
Assets times tasks times hours against the technicians you have. On the worked example this site publishes, 66 hours a month and $3,168 at a $48 loaded rate. Buildings are not exempt from the arithmetic that makes a schedule staffable rather than aspirational.
Questions people ask about building maintenance management software
Is this CAFM?
No. CAFM and IWMS manage space, occupancy, moves and services across an estate. This manages equipment in a building and what it needs.
Should we track cleaning contracts here?
Usually not. Contract management is a different job with different data, and mixing it in makes the maintenance register noisier without improving either.
What about multiple buildings?
One register with a site field works to a point. Past a few sites with separate teams and separate budgets, you are into the consolidation problem that EAM exists for.