// Commercial refrigeration contractors · Refrigerant records
Refrigerant leak records, assembled from the tickets your technicians already wrote.
An appliance's refrigerant history sits scattered across service tickets: who added what, where and when, and whether anyone came back to test the repair. A free AI proof of concept pulls that into one draft refrigerant record for each of 20 to 30 appliances you've already serviced, with every missing amount, date or follow-up listed. Your reviewer, the compliance lead or whoever on your team knows these records best, checks each draft against the file you actually keep.
- Appliance files
- 20 to 30
- Results calculated for filing
- None
- Live records touched
- None
// The one job
From a stack of tickets to one appliance's record
A rack at a grocery store throws a low-receiver alarm. A technician finds a leak at a valve on one circuit, repairs it, adds refrigerant and closes the ticket. Someone else comes back for the follow-up test, and that lands on another ticket, perhaps under the store's general account. Later your compliance lead has to lay the whole story out in order, appliance by appliance.
For the test, AI reads copies of those tickets and your appliance list and drafts a refrigerant record for one appliance at a time: its identification and full charge, each addition and recovery with the ticket it came from, leak inspection and verification test dates, and every entry missing an amount, a date or a follow-up. The leak rate field stays blank. Nothing enters your service management system, and your reviewer sets each draft beside the record your team kept.
appliance
// What makes it hard
What one refrigerant record has to hold, and where it goes missing
Your ticket carries six items. The owner holds two more. Under 40 CFR 82.157(l)(2) and its HFC counterpart in 84.106(l), whoever services an appliance leaves the owner a record of the appliance's identity and location, the date, the parts serviced, the type of work on each part, the name of the person doing it, and the amount and type of refrigerant added. Full charge and leak rate, with the method behind it, sit on the owner's side. A ticket can be complete and the file still unfinished, so the draft shows which of the two is short.
A rack is rarely one appliance. EPA's definition makes each independent circuit in a multi-circuit system a separate appliance, so one rack can need several records, and "rack B" on a ticket may not say which. The full charge behind each record comes from the manufacturer's figure, a calculation from component sizes and piping volume, actual measurements, or an established range whose midpoint serves as the charge. That fourth route has to show the range, the midpoint and how it was set. Revisions carry their dates, and all of it stays on file until three years after the appliance is retired.
Not every test finds a location. A leak inspection record gives the date, the methods used, where each leak was and a certification that all visible and accessible parts were inspected. Standing pressure or vacuum decay tests, sight glass checks, receiver levels, pressure checks and charging charts can show a leak exists, and EPA says they must be paired with a method that locates it. Verification records add each repaired leak tested, the kind of test and its result. A ticket reading "leak checked, OK" answers almost none of that, so it comes back flagged with the entries it would need.
Some additions need a label before anyone counts them. EPA's GreenChill guidance describes a winter charge, extra refrigerant that floods the condenser to hold head pressure, and says heat recovery and gas defrost can shift a system's charge as well. A seasonal variance is refrigerant removed and put back within one consecutive 12-month period, and an owner relying on it keeps records saying so. A mothballed appliance needs the date it went down and the date refrigerant returned. The same leak rate method must run across a facility: Part 84 allows a switch only after buying a facility that used the other one, with both results on record. The draft marks each hint, does no arithmetic, and leaves the ruling to your compliance lead.
California adds to the file, and wants it at the store. Its Refrigerant Management Program has records kept at the facility for at least five years, including every refrigerant purchase invoice, each shipment for reclamation or destruction with its recipient, weight, type, date and purpose, and the measurements and assumptions behind the full charge. Annual reports ask why each reportable charge was added: leak repair, topping off, initial charge or seasonal adjustment, with the technician's ID number and certification type. In CARB's R3 tool, a wrong full charge or refrigerant type has to be corrected by CARB staff, and R3 has no report built for EPA's Section 608 rule, so the federal file has to stand on its own.
// What you send
Tickets and the appliance list your office already has
Tickets for 20 to 30 appliances
Every service ticket for each appliance across at least a year, so a repair and its follow-up both show up. Mix stores, cold storage and a food plant if you serve them, and include a circuit that kept needing refrigerant.
Your appliance list
Whatever ties a rack or circuit to its store and full charge: a spreadsheet, a startup sheet or a customer's file, along with how the charge was worked out, if you know.
The records your team kept
The refrigerant log or compliance file for those same appliances as it stood when closed, so each draft has something to be judged against. For California stores, add what was entered in R3.
NDA signed, then copies or stand-ins
Tickets name customers, stores and technicians, so the NDA is signed before any copy moves. We never log in to your service management system or R3. Records that can't leave the building get rebuilt as look-alikes with your compliance lead.
// Before it starts
Settled in writing before any ticket moves
Two decisions sit with the owner first: who judges the drafts, and what counts as a pass.
- Your reviewer
- Named by the owner, usually the compliance lead or the service manager who keeps these files
- Success criteria
- Written first, including how a missed gap counts
- Rules read against
- Part 82, Part 84 or California, as your reviewer sets for each appliance
- Leak rate
- Left blank in every draft
- Who decides
- A certified technician and your compliance lead
- Price
- A range for the live job, before it starts
- NDA
- Signed before the first ticket
// How it's judged
Each draft beside the file your team kept
| On the same 20 to 30 appliances | Your team's record | The AI draft |
|---|---|---|
| Appliance and circuit identified, with location | Filled in from your files | Filled in from your files |
| Full charge and the method behind it | Filled in from your files | Filled in from your files |
| Each addition and recovery, with amount, type and date | Filled in from your files | Filled in from your files |
| Leak inspections: date, method, each leak's location | Filled in from your files | Filled in from your files |
| Initial and follow-up verification tests: dates, type, result | Filled in from your files | Filled in from your files |
| Winter charges and mothballing marked for a person | Filled in from your files | Filled in from your files |
| Entries missing an amount, a date or a follow-up | Filled in from your files | Filled in from your files |
// After a yes
About 30 days on tickets as they close
When your reviewer says yes, new tickets feed the same draft records for about 30 days, at a fixed price you see before signing.
Your compliance lead approves each entry before it reaches a customer's file or your own. Anything that could mean a repair deadline or a report goes to a certified technician and your compliance lead.
Any further job is a separate decision with its own price, and monthly support starts once a job is live.
// What could come next
Possible next jobs, in order
- 01Next
Case and rack repair quotes
A technician's notes and photos drafted into a quote for a multi-site customer, with a person checking it before it goes out.
- 02Then
Refrigerant cylinder reconciliation
Purchases, truck stock, pounds charged and pounds recovered set side by side for each branch.
- 03After that
Automatic leak detection files
Alert dates, leak locations and each annual audit and calibration gathered for the systems that have them.
// One hard limit
Refrigerant calls stay with your people.
The proof of concept never touches your service management system or a live record. It never calculates a compliance result for filing and never decides whether a leak must be repaired or reported. Every refrigerant question belongs to a certified technician and your compliance lead. It files nothing and contacts no customer or agency, and nothing on this page is legal advice.
Priced per job. You get a range before the proof of concept and a fixed price before you sign.
What moves the range: how many appliances you keep records for, how many customers' formats they arrive in, and whether tickets are typed or handwritten.
// Questions
What compliance leads ask
Does it calculate leak rates?
Who decides whether a leak has to be repaired or reported?
Isn't the full charge the owner's job?
Our tickets just say "charged system" with no circuit. Will that work?
Does it enter anything in California's R3 tool or send EPA a report?
We service stores on R-22 and stores on R-404A. Does that matter?

Rob Eason, founder
// Book a proof of concept call
Bring one customer's tickets from last winter.
Thirty minutes with Rob about your company and role, the job you'd test and roughly how many appliances you keep records for. Keep tickets and logs with you until the NDA is signed.
- Co-owned a 60-employee financial services firm and sold his share to his partner.
- Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
- 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
- 4.3/5 from 6 Google reviews of Massmarket AI.
- Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
- Takes every proof-of-concept call himself.
