Refrigerant does not get used up
It is worth saying plainly, because a surprising amount of field practice implies otherwise: a sealed refrigeration circuit does not consume refrigerant. A system that is low has lost it. Topping up without finding out where it went is not maintenance, it is deferral, and it is deferral with an environmental cost attached.
Regulators in a growing number of jurisdictions take precisely this view, which is why top-up without leak investigation is increasingly restricted and why the record of what was added is the thing that gets examined.
What the record has to contain
Specific requirements differ by jurisdiction, but the useful content is consistent, and it is per system rather than per visit.
- The system: make, model, serial number, location, refrigerant type and nominal charge.
- Every charge: how much, when, by whom, and why it was needed.
- Every recovery: how much was taken out, when, and where it went.
- Leak checks: when, by what method, and the result, including the negative ones. A record showing checks that found nothing is evidence of diligence.
- Leaks found: where, what was done, and the verification check afterwards.
- The technician, and the certification they held at the time.
Per system, for the life of the system
This is the part that defeats job-based filing. The question asked in an inspection, or by a client's compliance team, is about a particular machine across years: how much has gone into this circuit since it was installed?
Answering that from job sheets means reading every job sheet for the site and hoping nothing was missed. Answering it from an asset record takes seconds. The difference only appears when somebody asks, and by then it is too late to reorganise.
The pattern a good record reveals
There is a commercial benefit beyond compliance. A system that has taken refrigerant three times in two years is telling you something, and the record makes it visible where individual visits do not.
That is the conversation to have with the customer: not 'it needs gas again' but 'this circuit has lost its charge three times, here are the dates, and the economic answer is to find the leak properly or replace the unit'. With the history in front of them, customers usually agree. Without it, you are asking them to take your word for it.
Leak checking is a scheduled obligation, not an event
Several regimes require periodic leak checking at intervals determined by the size of the charge, with larger systems checked more often and sometimes required to carry automatic leak detection. The interval is a legal minimum rather than a recommendation, and missing one is a finding regardless of whether a leak existed.
That makes leak checks a scheduling problem as much as a technical one. They have to be generated, assigned and completed on time, and the record has to show the date. A company relying on somebody remembering which systems are due will eventually miss one, and will discover it during an inspection rather than beforehand.
What recovery records are for
Recovered refrigerant has to go somewhere, and the chain from the system to the cylinder to the reclaimer is what demonstrates it was not simply vented. Record how much came out, which cylinder it went into, and where that cylinder went.
As the phase-down tightens and virgin supply becomes scarcer, reclaimed refrigerant also becomes commercially valuable rather than merely a disposal obligation. Companies with disciplined recovery practice are better placed than those treating it as a chore, and the records are what turn recovered volume into something you can actually trade.
Make it part of the job, not a separate form
A refrigerant log kept in a separate book, filled in at the end of the week, will be incomplete, and the gaps will be exactly where the pressure was highest.
Capturing it as part of completing the job, against the unit, is the only version that stays accurate. It also means it is attached to the readings and the photographs from the same visit, which is what makes the whole record credible rather than merely present.