HVAC field service app: scheduling and documenting the work
What an HVAC field service app should capture, why "checked OK" kills your history, offline mode in basements, and the Québec rules that apply.
At a Glance
An HVAC field service app is only as good as the data it forces techs to enter: real readings, nameplate photos, refrigerant quantities. Set up well, it turns a stack of "checked OK" tickets into a readable history of each unit; set up badly, it just digitizes the guesswork.
Pull up the work orders you closed last week. How many contain an actual number — a pressure, a temperature, an airflow, a refrigerant charge? And how many end with “checked, running fine”? If the second pile is taller, an HVAC field service app won’t fix anything on its own. It will just make the guesswork faster to produce and easier to file.
This review treats the app the way you’d treat a test instrument: what it’s for, when it pays off, how to read what it shows you, and where it misleads. It’s not a brand shoot-out — the software changes every year; the setup principles don’t.
What is an HVAC field service app actually for?
A field service app ties together three moments that paper keeps apart: dispatch (who goes where, when, with what history), the call itself (what was measured, found and done) and the follow-up (invoice, quote, next visit). Its real value isn’t the signature on the screen. It’s the history of one specific unit, available before you’re standing in front of it.
For the tech, the difference plays out in the truck before heading up: knowing that this rooftop unit had a compressor swapped two years ago, that the last visit flagged a dirty coil, that the roof access code changed. On paper, that context sits in a filing cabinet back at the office.
What the app doesn’t do: measure anything. It keeps what you put in. It’s a logbook, not an analyzer.
When the app really pays for itself
The setup effort earns its keep in four situations:
- Multi-building portfolios. When a property manager hands you 15 or 40 addresses, routing by area — South Shore one day, Laval the next — and pulling history without stopping at the office reshapes the workday.
- Seasonal maintenance contracts. AC start-ups in spring, heating start-ups in October: the app generates recurring visits and keeps the same checklist year after year, so trends are actually comparable.
- Night emergency calls. The on-call tech arrives at a unit they’ve never seen; the history and photos from the last visit replace the phone call to the colleague who “knows the building.”
- Mandatory logs. In Québec, the halocarbon regulation requires workers to log repair, maintenance and dismantling work. A structured field for refrigerant recovered or added, entered on site, beats a sheet copied out on Friday afternoon.
On the other hand, for a one-person shop with a handful of loyal clients, a good template plus disciplined photo documentation of each job delivers most of the value for far less.
Reading the dashboard without fooling yourself
An app dashboard is like an analyzer display: it shows numbers with total confidence, right or wrong. Three readings deserve a skeptical eye.
Closed-ticket rate. A closed ticket means someone tapped “done,” not that the problem is solved. The useful number is the callback rate on the same unit within 30 days.
Time on site. It’s just the arrival and departure timestamps. A short visit can mean efficiency — or a rushed job. Never read it alone; always alongside what the ticket says.
Equipment history. The most valuable view, provided every ticket is tied to the right serial number. A unit entered twice (“RTU-2” and “North roof unit”) splits its history in two and wipes out the trends.
| What the ticket says | What you can learn from it in 3 years |
|---|---|
| ”Checked, running fine” | Nothing — there’s nothing to compare |
| Pressures, superheat, subcooling, air ΔT | A charge and fouling trend |
| Nameplate photo | Model, serial, refrigerant, build date |
| Refrigerant added, per visit | Hard numbers proving a slow leak |
| Part replaced + cause found | Wear versus a recurring defect |
Mistakes that cost real money
Confusing digitized with documented. Swapping a paper form for an identical digital one with a free-text box reproduces the “OK” tickets exactly. The setup has to make certain numeric fields mandatory depending on the job type.
Trusting offline mode you haven’t tested. Basement boiler rooms in Montréal plexes and towers, concrete mechanical rooms and some warehouse roofs have no signal. Depending on the software, offline mode ranges from read-only to full data entry with sync on reconnect. A photo that never uploads is a photo that doesn’t exist.
Overlooking language. The Office québécois de la langue française points out that workplace software should generally be available in French; English-only is allowed only when no French version exists, and training must be offered in French. For a mixed crew in Montréal it’s also about adoption: techs fill out forms better in the language they read most comfortably.
Ignoring personal information. Names and phone numbers of tenants, superintendents and property managers are personal information. Under Law 25, the business must protect them, keep a register of confidentiality incidents and complete a privacy impact assessment before that information leaves Québec — which includes hosting abroad. Our piece on cloud maintenance records digs into the hosting question.
Longueuil: three summers of “top-ups” on one unit
A shopping centre in Longueuil, six rooftop units. For three seasons, the paper tickets from unit 4’s spring start-up all read alike: “Checked, cooling well, added refrigerant.” Three different techs, none of whom had seen the other two tickets.
Moving to an app made it mandatory, on every AC start-up, to enter suction and discharge pressures, superheat, subcooling and the amount added, plus a nameplate photo. In the first summer, the imported history lined up the three top-ups side by side: about 2 kg, then 2.5 kg, then 3 kg. Not a top-up — a leak getting worse.
A targeted leak search found a brazed joint on the liquid line cracked by vibration. Repair, pressure test, a weighed-in charge per the nameplate, and an entry in the log. The following summer: nothing added. None of it took a new instrument — just three numbers kept in the same place.
Field verdict: the checklist before you sign
An HVAC field service app is a good tool if, and only if, it passes these five tests on a technician’s phone — not in a sales demo:
- Real offline mode: complete a full ticket with photos in a basement with no signal, then confirm it syncs.
- Required fields by job type: an AC start-up can’t close without pressures and superheat; a burner service, not without a combustion analysis.
- One unit, one history: a single equipment record tied to the serial number and nameplate photo.
- Exportable halocarbon log: refrigerant recovered and added, per unit, available on request.
- French and hosting: a French interface, and a straight answer from the vendor on where the data lives.
Your move this week: pull your last five AC start-up tickets and count how many include a measured superheat. That number is your baseline — before you even shortlist software.
Three readings cost a tech thirty extra seconds; for the property manager, they’re the difference between paying for a top-up every summer and paying once for a repair. It’s what Montréal Combustion builds into every preventive maintenance visit: numbers someone can still read three years from now.
Frequently Asked Questions
What is the best field service app for HVAC technicians?
Do field service apps work without cell service?
Can a Québec company use field service software that is only in English?
Do HVAC techs in Québec have to log refrigerant work?
Sources
- Charte de la langue française : mythes et réalité — Office québécois de la langue française
- Les halocarbures - Le règlement en bref — Ministère de l'Environnement du Québec
- Principaux changements aux lois sur la protection des renseignements personnels — Commission d'accès à l'information du Québec