Here's a question that should take ten seconds to answer: how much refrigerant went into the chiller on Building C this year? If you can pull that number without opening a drawer, good for you. Most shops can't.
The amount lives wherever the tech wrote it down. A line on a work order, a note buried in a phone, a figure he remembers for about a week. Add that up across a dozen units and a dozen trucks over twelve months, and the honest answer is that nobody knows the total until somebody is forced to find out.
Usually that somebody is you, the week an EPA letter shows up or a unit starts eating R-410A and you need to prove what you put in and when. The information existed every single time a tech topped off a system. It just never landed anywhere you could actually use it.
What the record actually has to show
EPA Section 608 is the federal rule that governs how refrigerant gets handled, and it expects a real paper trail on commercial equipment. For any unit with a full charge of 50 pounds or more (the full charge is the amount of refrigerant it holds when it's running right), you're on the hook to record the service that touches that charge.
Every time a tech adds or recovers refrigerant, the record needs to tie together a handful of facts:
- The unit, pinned down well enough that nobody confuses it with the rooftop sitting next to it: location, make, model, and serial.
- The refrigerant type, like R-410A or R-22, because you can't blend two types onto one record.
- Pounds added and pounds recovered, kept as two separate numbers, never a single net figure.
- Cylinder or lot numbers for what came off the truck, so the gas stays traceable.
- The date, the tech, and the reason: a top-off, a repair, or a recovery before a changeout.
Leave one of those out and what you have is a story, not a record. An auditor can't use it, and neither can you when you're trying to figure out which unit is quietly bleeding money every August.
Why the scribbled work order lets you down
A work order is built to get a job billed, not to track one unit across years. The refrigerant line gets written to justify the charge on that invoice, then the paper goes in a folder and the number dies there. Nothing adds it to last spring's top-off on the same machine.
Leak rate is the math that makes this matter. Over a year, you compare how much refrigerant you had to add back against the unit's full charge, and that percentage tells you whether the thing is leaking faster than the EPA allows. Once the annualized rate crosses the limit set for that equipment type, a clock starts on a required leak inspection and repair.
You cannot run that math honestly from notes scattered across twelve months and three techs. So the calculation gets skipped until an audit or a big loss forces it, and then you're reconstructing a year of service from memory and smudged carbon copies. That's a bad week, and it's avoidable.
Capture it off the tech's phone, at the job
The good part is that the hard data already exists at the moment it's created. Your tech weighs the cylinder before and after, reads the scale, and knows exactly what he put in and pulled out. The only thing broken is the handoff between his hand on the scale and your file on that unit.
You can close that gap with a short capture step on the phone he's already holding. The tech reports four or five things at the job, by typing them, snapping a photo of the scale readout, or saying them into a voice note. Software then reads that report, pulls the numbers into the right fields, and files them against the correct unit automatically. In plain terms, that's the AI part: it structures loose input and routes it, so no one keys it in later.
- Tech picks the unit from the ones tied to that address, so the record lands on the right machine, not just the right building.
- He enters or speaks the pounds added and the pounds recovered, and the cylinder number for the gas he used.
- He notes the reason in a few words, and he's done, usually in under a minute before he's back on the Loop.
- The system stamps the date and tech, slots it into that unit's running history, and keeps a live total for the year.
Filed this way, the annual leak-rate math isn't a year-end scramble. It's a number you can read any day you want it, and the full 608 record is already sitting where an auditor would ask to see it.
What this can and can't do for you
Be clear about the limits before you buy into it. Software can't weigh the cylinder for the tech, and it can't know whether the pounds he reported are the pounds that actually moved. If he eyeballs it or fat-fingers a number, the record will be wrong and tidy, which is its own kind of trap. The scale and the tech's honesty are still the foundation, same as always.
It also can't guess which unit got the work. Somebody has to identify the machine, so your equipment list for each site needs to be real and current, or the filing has nothing to file against.
Where it earns its keep is everything after the number is spoken. Good software catches a missing cylinder number before the tech leaves, keeps the add-and-recover totals straight per unit, and flags you when a machine's yearly adds are creeping toward the threshold, instead of letting you find out at renewal. It handles the sorting and the arithmetic so the compliance part is boring, which is exactly what you want it to be.
Worth doing this week
You don't need a big project to get most of this benefit. Start small and make the capture automatic before you worry about reports.
- Pull the records on your three largest commercial units, the 50-pound-and-up machines, and see whether you can actually total this year's refrigerant. Where you can't, you've found your real exposure.
- Write down the five fields you want off every refrigerant job, and have your techs report exactly those, the same way, starting Monday.
- Make sure each service address has a clean equipment list so a report has a unit to attach to.
- Set one running total per unit and glance at it monthly, so a leaker shows up in spring, not at audit time.
If wiring the phone-to-file piece together sounds like more than you want to sort out alone, that's the kind of setup we build for Houston shops. Either way, the goal is simple: the record is done when the tech drives off, not the week the EPA asks.