A maintenance contract can say “preventative” on the cover page and still function reactively in practice. The tell is usually in what actually triggers a technician showing up: if a visit only happens after something is reported broken, the schedule is preventative in name only, no matter what the contract calls it or how the proposal was worded when it was signed.
The difference is in what triggers a visit, not what the contract is titled
The simplest way to tell the two apart is to ask a single question: does anything happen on a visit where nothing is currently broken? A genuinely preventative program is built around a fixed interval — monthly, quarterly, or annual depending on the system — where inspection happens on schedule regardless of whether a complaint has come in. Filters get checked before airflow suffers, not after occupants start noticing. Belts, bearings, and seals get inspected on a cadence, not when a unit starts making an unusual noise. The entire value of the program lives in catching the version of a problem that hasn’t cost anyone anything yet — the filter that’s getting dirty, not the filter that’s already caused a comfort complaint.
A reactive program dressed up in preventative language looks almost identical on paper. It might even use the same words — “scheduled visits,” “regular inspection” — but the actual trigger for a technician arriving is still a work order, not a calendar. Facility managers often don’t discover which kind of program they’re actually running until something fails that a real PM schedule would have caught months earlier.
Why the gap matters more than it looks like it should
The cost of reactive maintenance rarely shows up as a single dramatic failure. It shows up as a slow accumulation of small deferred items that eventually convert into emergency repair calls — a filter that goes unchanged for eighteen months because nobody was tracking it, a belt that finally snaps instead of being replaced during a routine check, a seal that fails after months of gradual wear nobody was watching for. Each of these, caught early, is a minor line item. Caught late, they’re often a multiple of that cost, plus the disruption of an unplanned outage.
There’s also a budgeting dimension that gets overlooked. A facility running genuinely preventative maintenance has predictable costs — the same inspection, the same interval, the same expected consumables, year over year. A facility running reactive maintenance dressed up as preventative has unpredictable costs that spike unexpectedly, which makes annual budgeting an exercise in guessing rather than planning.
What real documentation looks like, and why it’s not optional
The other piece that separates real PM from paperwork PM is documentation that actually holds up over time, not just per visit. A single completion report is useful in isolation. A year of consistent completion reports — same format, same level of detail, attached to the same asset over time — becomes something a facility manager can actually use: a real maintenance history that shows patterns, not just a folder of disconnected paperwork. Our technology platform is built around making that history usable rather than just archived somewhere it never gets reviewed again.
This matters most in exactly the moments documentation gets asked for unexpectedly — an insurance claim, an audit, a dispute with a landlord or tenant over whether a system was properly maintained. A facility manager who can produce eighteen months of consistent, dated, photo-verified inspection records is in an entirely different position than one who has to explain that records exist “somewhere” across several vendors’ individual systems.
How to tell which kind of program you’re actually being offered
If you’re evaluating a PM proposal and can’t tell which kind you’re being offered, the simplest test is the same question from above, asked directly: what happens on a visit where nothing is wrong? A real preventative program still performs the inspection, documents that everything checked out, and moves on to the next scheduled item. A reactive program dressed up as preventative usually doesn’t have a good answer for that question, because it was never actually designed to generate a visit with nothing to report.
It’s also worth asking who owns the schedule itself. If the facility team is the one tracking when something is “due” and has to initiate the request, that’s closer to a reactive relationship with a preventative label attached. In a genuinely preventative arrangement, the vendor owns the calendar and the facility team simply receives the documentation afterward.
For a broader look at how Services structures inspection cadence across multiple trades at once, or for help evaluating a specific PM proposal you’ve already received, see Facility Advisory — this is exactly the kind of vendor-language question worth a second read before signing.
