What HVAC contractor software should measure

What to take away

General guidance on selecting and using systems. No vendor is recommended or criticized, and any security requirement should be confirmed with the relevant guidance rather than assumed.

The seven data objects

Write these down before looking at any system.

Customer and site. Not the same thing. One customer can have several sites and one site can change hands. Systems that conflate them produce history attached to the wrong place.

Equipment. Make, model, serial, install date, warranty position, and where it sits on the site. This is the object most systems handle worst and the one this trade most needs.

Job. The visit or the project, with what was found, what was done, hours consumed, parts issued, and the readings taken.

Quote and scope. Including exclusions, allowances and the version the customer accepted.

Agreement. Recurring maintenance, its visit schedule, and whether the visits actually happened.

Parts and stock. What is on each vehicle, what was consumed, and what has to be reordered.

People and permissions. Who is qualified for what, and when each certification expires.

The seventh matters more here than in most trades, because dispatch decisions depend on it. What each level may do unsupervised comes from the ladder in the hiring and training guide, and the expiry dates come from the layers in the licensing and compliance guide.

What a system has to produce

Judge candidates on outputs, not on features.

A job record reconstructable years later with readings and photographs, plus a commissioning record in the form your work requires. An invoice raised the day the technician leaves, and a history by equipment so the second visit knows about the first.

A stock position by vehicle, and a record of who did what with their qualification at the time. And exports you own, in a format you can read without the vendor.

The last one is a purchasing rule rather than a feature request. Ask how you get your data out before you put any of it in.

Evaluating without being sold to

The honest method is a trial on real jobs, with tests you wrote before the demonstration rather than after it. Write the tests from the seven objects and from the outputs above, and score every candidate on the same ones.

Two rules that save money. Run the trial during a normal week rather than a quiet one, and have the technicians use it rather than the owner. A system that is pleasant in an office and unusable on a phone in an attic will be abandoned in the field, quietly, and you will find out from the missing records.

The records the regulated work generates

Some of what a system holds is not yours to design. It is required by the work.

Refrigerant handling generates recovery and handling records under a federal program, described at the EPA Section 608 technician certification pages. Ask, before choosing a system, whether it can hold those records in a form you could produce on request, and whether they stay attached to the job and the technician.

Permits and inspections generate their own trail: what was applied for, when, what the inspector said, and what changed as a result. Warranty positions generate another: registration completed, terms, and the evidence that the installation met what the manufacturer required.

None of these is a marketing feature and few systems present them well. Ask about them specifically, because reconstructing them from photographs and memory two years later is exactly the situation you are trying to avoid.

Two systems, one truth

Most firms end up with more than one tool, and that is fine as long as one of them is authoritative for each object.

Where this goes wrong is quiet duplication: a spreadsheet of agreements alongside the system's own, or a technician's notes that never reach the job record. Duplication does not announce itself. It appears the day two people give a customer different answers.

Security arrives with the software

The moment you hold customer addresses, photographs of their homes and payment details, you have obligations that do not depend on your size.

Practical starting points published for small organizations include the NIST small business cybersecurity quick start guides and the material for small and medium businesses from the Cybersecurity and Infrastructure Security Agency.

The last one matters in this trade because photographs of customers' properties end up on personal devices by default.

The numbers worth watching

Not many. Six, defined once and left alone.

First visit close points to stocking, so use the equipment and setup guide. Return visits point to quality standards, so use the service quality guide for owners.

Quote acceptance points to the document and the number, so use the pricing and profit guide. Referral share points to how the business presents itself and how the last job went, covered in the marketing and growth guide.

Definitions are the whole game

A measure whose definition drifts is worse than no measure, because people act on it anyway.

Write down, for each number: exactly what counts, exactly what does not, where the data comes from, and who reviews it. Then leave the definitions alone for at least a year. Comparing this quarter to last quarter is only meaningful if both were counted the same way.

The financial records underneath all of this should meet the standard described in the IRS guidance on records that clearly show income and expenses, and job records deserve the same discipline even though nobody audits them.

What software will not fix

Three things, and they are the three most often bought against.

It will not make technicians record hours honestly. That is a management habit, and every number above depends on it.

It will not fix a scope document that does not name exclusions. It will simply reproduce the confusion faster.

And it will not tell you what your work costs. It will tell you what you recorded, which is only useful if what you recorded was true.

Common questions

Do I need field service software as a one-person business?

Not necessarily, but you need the seven objects to exist somewhere connected. Many firms start with simple tools and move when the reconstruction of a job takes longer than the job did.

Should accounting and job management be one system?

They need to agree, which is not the same as being one product. What matters is that a job's costs and its invoice reconcile without anyone retyping anything.

How long should a trial run?

Long enough to include a busy week, a complicated job and a month end. A quiet fortnight teaches you nothing about a system.

What if the technicians resist it?

Find out why before deciding it is resistance. Usually the objection is specific and correct: too many taps, unusable in the sun, or a form that does not match the work.