EPA Refrigerant Log Generator

An EPA refrigerant log is a documented service record that captures the specific details of a refrigerant addition event — the type of refrigerant, the quantity added, the full system charge, the technician information, and the calculated annualized leak rate. Under EPA regulations, every time refrigerant is added to a covered appliance, the owner or operator must document the event in a retrievable service record. As of January 1, 2026, coverage extends to appliances containing 15 lbs or more of HFC refrigerant under EPA's AIM Act HFC Management Rule (40 CFR Part 84); the traditional 50 lb threshold under Section 608 (40 CFR Part 82 Subpart F) continues to apply for non-HFC refrigerants such as R-22.

The log is not just an internal record-keeping convenience. It is a legal document. EPA inspectors treat the absence of a log as evidence that the work was not done to code — regardless of what actually happened. A contractor who performs a compliant service call but doesn't write it up is, from a regulatory standpoint, in the same position as a contractor who never did the work at all.

Refrigerant logs also serve as the primary evidence during enforcement actions. When the EPA investigates a potential violation, they compare refrigerant purchase records against service logs to identify quantities of refrigerant that are unaccounted for. If you purchased 50 lbs in a quarter and only logged 20 lbs to service calls, that gap demands an explanation.

Section 608 of the Clean Air Act is the federal statute governing refrigerant handling. The EPA implements it through 40 CFR Part 82 Subpart F, which specifies exactly what records must be maintained for every covered appliance. Here is what the regulation actually requires:

Civil penalties for Section 608 violations can reach $59,114 per day per violation. In practice, most enforcement actions stem from recordkeeping failures rather than actual refrigerant releases — because inspectors can only verify compliance through records.

The recordkeeping obligation sits with the appliance owner or operator, not the contractor. But in practice, the contractor is almost always the one generating the records at the time of service — which means the contractor's paperwork is what the owner presents during an inspection. If the contractor's records are incomplete, the owner has no defense.

At minimum, contractors should maintain:

• 1.A service log for every job involving a covered appliance, including jobs where no refrigerant was added.
• 2.Cylinder purchase and tracking records — quantity purchased, supplier, and which jobs the refrigerant was consumed on.
• 3.Leak rate calculations for every refrigerant addition event on covered appliances.
• 4.Any repair orders, work orders, or follow-up documentation for systems that exceeded the applicable threshold.
• 5.Copies of technician EPA 608 certifications for all personnel who purchase or handle regulated refrigerants.

Many contractors also maintain equipment files — a folder (physical or digital) for each covered appliance containing the complete service history, nameplate specifications, and any repair documentation. This is especially valuable for large accounts with multiple covered systems, where an audit requires producing records for each piece of equipment separately.

The EPA mandates a minimum retention period of three years from the date of the service event. Records must be available for inspection upon an EPA request — meaning they must be retrievable, not archived at an offsite storage facility with a two-week retrieval window.

Three years is a regulatory floor, not a recommended target. The Clean Air Act's statute of limitations for civil violations is five years in most circumstances. If you are a contractor who works on the same accounts year over year, consider retaining records for the life of the equipment. The cost of additional storage is negligible compared to the cost of a violation you cannot defend because the records are gone.

For systems with a history of threshold exceedances or unresolved repair orders, retain records indefinitely while the equipment remains in service. In an enforcement scenario, those records become the evidence that you responded to compliance events appropriately.

Most compliance failures are not caused by intentional violations — they are caused by sloppy paperwork practices that made sense in a paper-log world but don't hold up when an inspector looks closely. Here are the mistakes that appear most often in enforcement actions:

1. Logging zero-charge top-offs without documentation. Any refrigerant addition to a covered appliance is a recordable event, even if it's one pound. "It was just a pound, not worth logging" is not a defense.
2. Using current fill instead of nameplate charge. If a technician arrives and a 100-pound system is holding 70 pounds, the denominator in the leak rate formula is 100 — not 70. The EPA formula is based on design capacity, not current inventory.
3. Reconstructing records after an audit notice. Backdated or retroactively created records are a criminal risk, not a compliance fix. Inspectors are experienced at identifying records created after the fact. If records are missing, disclose it — don't fabricate.
4. Treating multi-circuit systems as a single appliance. A supermarket rack system with multiple independent refrigerant circuits may constitute multiple "appliances" under EPA definitions. Each must be tracked separately.
5. Not documenting leak location when threshold is exceeded. When a system's leak rate exceeds the applicable threshold, the record should note the leak location found (or that no leak was found despite investigation), repairs performed, and the follow-up schedule. An exceeded threshold with no documented response is a compounded violation.
6. Counting business days instead of calendar days. The leak rate formula uses 365 calendar days per year, and "days since last addition" must also be calendar days — weekends, holidays, and shut-down periods all count.

EPA compliance inspections for Section 608 violations typically begin with a records request. Inspectors ask for refrigerant purchase records and cross-reference them against service logs to identify discrepancies. Here is what they are looking for:

Paper logs have been the industry standard since refrigerant regulations were first enacted. Most contractors know how to fill them out — but paper logs have structural failure modes that become liability in an audit:

Physical degradation. A service log that has been folded in a work truck for three years, exposed to refrigerant spills, or stored in a leaking file cabinet may be partially or fully illegible. An inspector who cannot read the date or the technician's name treats the record as if it doesn't exist.

Inconsistent formatting. When every technician uses their own format for paper logs, the record set lacks coherence. Inspectors looking for specific data fields — particularly the leak rate calculation — may not find them because one technician records leak rate and another does not.

No linkage between purchase records and service records. Paper invoices and paper service logs are two separate documents that are rarely cross-referenced until an inspector requests them simultaneously. The reconciliation gaps that result are one of the most common enforcement triggers.

No alerts for threshold exceedances. A paper log does not tell you when a system is approaching a threshold. The technician who filled in the calculation might have missed that 23% exceeds the 20% commercial threshold. By the time the next technician arrives, the 30-day repair window has passed.

Digital logs — including structured PDFs generated at the time of service — eliminate most of these failure modes. They are legible, consistent, searchable, and can be stored off-device in a form that survives equipment loss.

The contractors who have the cleanest audit outcomes are not necessarily the ones with the fewest compliance events — they are the ones whose records tell a coherent story. Here is what that looks like in practice:

• →Log every service call, including calls where no refrigerant was added. A "no charge added" entry creates a timeline gap that shows normal operation, not a missing record.
• →Calculate leak rate at the time of service, not retroactively. Record the calculation in the log, not in a separate spreadsheet that exists in one place.
• →Note the leak location found, or document that a thorough leak check was performed and no leak was located. "System low, charged to spec" is insufficient.
• →Keep a cylinder log that matches purchases to jobs. Each cylinder should have a running balance — weight at purchase, weight after each use, and the job to which each use was charged.
• →Store service records both on-site (at the customer location or in the service vehicle) and in a central, retrievable system. On-site records satisfy the immediate availability requirement; central records protect against loss.
• →Review records for threshold exceedances on a schedule, not just when a technician flags them. A slow leak that incrementally crosses the threshold across multiple service calls should trigger a repair review even if no single addition event exceeded the limit.