Building maintenance covers everything from changing a filter to replacing a roof, and treating it as one activity is why it is so hard to budget. It divides cleanly into three kinds of work with different rhythms and different owners, and a plan that separates them is far easier to defend than one that lists tasks in the order somebody thought of them.
The three kinds of work
Planned rounds are the recurring, predictable work: filters, belts, lamps, drains, inspections. Reactive repair is what breaks, which you can forecast in aggregate but never per item. And statutory or insurer-driven checks are non-negotiable and dated, whatever else is happening. Building maintenance and repair is usually used to mean the first two together. Keeping the third visible and separate is what stops it being squeezed when the budget tightens.
What building maintenance software has to handle
A building is a set of assets in locations, and location matters more here than in a plant: the same asset type recurs on every floor, and a technician needs to know which one. Building maintenance software and the building maintenance management system are the same category, and the thing to test is whether the location hierarchy is real, site, building, floor, room, or a text field. That single choice decides whether the system is usable at two hundred assets.
Budgeting the part you cannot schedule
Planned work can be costed precisely. Reactive cannot be costed per item and can be costed in aggregate, if you have kept records long enough to see the pattern. That is the practical argument for logging small reactive jobs that feel too minor to record: after a year they are the only evidence for what next year's reactive budget should be. Sites that log only planned work end up defending a reactive budget with nothing but assertion.
Questions people ask about building maintenance management system
What is building maintenance?
The work of keeping a building and its systems serviceable: planned recurring rounds, reactive repair when something breaks, and the dated statutory or insurer-driven checks that happen regardless.
What should building maintenance software handle first?
A real location hierarchy, site, building, floor, room. The same asset type recurs on every floor, and if location is just a text field the system stops being usable at a couple of hundred assets.
How do you budget reactive repair?
In aggregate, from your own history. That is the reason to log small reactive jobs that feel too minor to record: after a year they are the only evidence for next year's figure.