HVAC preventive maintenance software is bought to end a specific situation: a list of rooftop units and air handlers on a spreadsheet, quarterly intervals somebody keeps in their head, and no reliable answer to when a given unit was last touched. Judged against that, most of the feature list is decoration. Four jobs decide whether the product removes the spreadsheet or joins it, and each one is testable in a trial with your own unit list rather than a demo dataset.
Job one: the unit list, with the interval on the unit
The asset is the thing that carries the interval, not the calendar. A rooftop unit on a quarterly filter change and an annual coil clean is two intervals on one asset, and a product that models only a single schedule per asset forces the second into a note. Ask to see one unit with two different intervals before you look at anything else, because everything downstream inherits that answer.
Job two: due is derived, never typed
The next visit should move by the interval when the last one completes. That single behaviour is the difference between software and a shared calendar: it means a visit done two weeks late shifts the following one, and nobody has to remember to update anything. If due dates are typed in, the plan is a spreadsheet with a login and it will go stale in exactly the same way.
Jobs three and four: the checklist, and what it leaves behind
The visit runs a list of checks, and what matters afterwards is that the answers filed themselves against the unit. Who did it, on what date, what failed, what was deferred. Filed on the asset rather than in a folder by month, because every question anybody asks later starts with the unit. A product that produces a PDF and nothing queryable has automated the paperwork and left the record where it was.
Questions people ask about hvac preventive maintenance software
Do we need HVAC-specific software or will general maintenance software do?
General software handles it if it models intervals per asset and lets a visit carry a checklist. What HVAC-specific products usually add is a starting checklist per equipment type, which saves an afternoon of setup rather than changing what the product can do.
Should the software decide the service intervals?
No. The interval comes from the manufacturer, the duty the unit is under and your own competent person. Software holds the interval you set and makes the due date follow from it; a product that proposes intervals is guessing about your equipment.
What about units under a contractor's maintenance agreement?
Keep them on the same list. The interval is the contractor's visit rather than your own labour, but the questions are identical: when is it due, was it done, what did they find. A separate list for contracted units is how sites lose track of half their plant.