Core workflows

Refrigerant compliance

ChillOps treats refrigerant records as part of the job — captured at close, tied to the equipment passport, and audit-ready instead of reconstructed from paper tickets.

What gets logged

  • Refrigerant type (for example R-410A, R-454B, R-32).
  • Quantity added or recovered, by weight.
  • Reason for the change — service, retrofit, recovery, disposal.
  • Leak context and repair disposition when applicable.
  • The specific equipment the event belongs to.
  • The technician who performed the work.

When it gets logged

Refrigerant logging happens at job close, as part of the same workflow the technician uses to record parts, labor, and notes. It is not a separate paperwork pass at the end of the week.

How records are organized

Every refrigerant event in ChillOps is tied to a specific equipment record, not just a job. Pull up any unit and you see its full refrigerant history — every add, every recovery, every leak event — across its lifetime in your system.

What this produces

  • A per-unit refrigerant log suitable for EPA-style audit review.
  • A per-technician record of refrigerant handling.
  • A shop-wide view of refrigerant added and recovered over any date range.

What ChillOps does not do

ChillOps structures the operational record. It does not replace EPA Section 608 technician certification, does not file reports on your behalf, and does not substitute for legal counsel on regulatory obligations. If your shop has specific regulatory questions, work with your compliance advisor — ChillOps keeps the underlying data clean so those conversations are easier.

Refrigerant compliance | ChillOps Docs