Guides · 2026-08-16
Scheduling preventive maintenance starts by registering only your critical assets — not everything you own — then giving each of them a maintenance cycle, a checklist, and a named owner. The decisive step comes next: the system raises the work order automatically on its due date, rather than depending on someone remembering.
Most preventive maintenance plans do not fail because they are wrong. They fail because they stay on paper and never become work. This guide walks through the five steps that make a plan actually run.
The most common mistake is trying to schedule everything from day one, producing a plan so large the team abandons it within weeks. Start with the assets whose failure halts operations, affects safety, or costs a lot to fix urgently.
In residential and commercial buildings these are usually lifts, central HVAC units, pumps, emergency generators, fire alarm systems, and water tanks. Keep the list deliberately short — you can expand it once the first cycle is stable.
You cannot schedule maintenance for an asset that is not registered. For each critical asset, record at minimum:
This register is what turns preventive maintenance from a generic calendar into a plan attached to real assets, and it makes each asset's history available later when deciding whether to repair or replace.
One cycle does not fit all assets. Set it from three sources in priority order: the manufacturer's recommendation, then whatever the maintenance contract specifies if one exists, then your own operating reality — usage intensity and the environmental conditions at the site.
Write the cycle down per asset instead of leaving it to individual judgement, then review it after the first round: if failures keep appearing between scheduled visits, the interval is too wide.
"Maintenance done" is not information you can act on. A checklist turns the visit into specific items, each of them confirmed: what was inspected, what the reading was, and what was replaced.
Smart checklists in MRFQ let the work be documented against the required standard with evidence, which helps in two situations: reviewing contractor performance, and demonstrating compliance to a building owner or an owners association board.
This is where it is decided. A plan written in a file depends on someone opening it on the right date and acting — the first thing to slip in a busy week. When preventive maintenance is scheduled inside the system, the work order is raised on its due date and reaches its owner automatically.
The second benefit is less obvious and matters more over time: when team members or board members change, the plan survives, because it lives in the system rather than in someone's memory.
Watch these qualitative signals after the first cycle:
A growing overdue backlog signals that the plan is larger than the team's capacity, not that someone is slacking. Address it by narrowing the scheduled asset list or reviewing workload distribution — before the team abandons the plan altogether.
If your preventive maintenance plan exists on paper but is not executed on schedule, you can book a demo and see how a plan turns into work orders that raise themselves.
Start with a site walk covering only the critical assets — lifts, pumps, HVAC, safety systems — and record the location, the responsible party, and the last known service date for each. That is enough to begin scheduling; the details can be completed later.
Preventive maintenance is scheduled work carried out before a failure, to reduce its likelihood. Reactive maintenance is the response after one happens. The goal is not to eliminate reactive work, which never disappears entirely, but to shrink its share of the daily load.
Schedule them in the system as well, but link them to the responsible contractor through contractor management. That way you keep a record of what was actually delivered against what the contract specifies when renewal comes around.
Not entirely — some failures happen regardless of scheduling. The difference is that predictable failures become less frequent, and repeated failures on a specific asset become visible in its record, so you can make a repair-or-replace decision instead of treating the symptom again.