EPA Section 608 Refrigerant Addition Log
Track every refrigerant addition to a covered appliance with a per-service log that captures the equipment, reason, quantity, technician certification, and compliance attestation in one place.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Facilities Management · Commercial Hvac · Refrigeration Services · Property Management · Healthcare Facilities
Overview
This template is a per-appliance refrigerant addition log for service events where refrigerant is added to a covered system. It captures the appliance identity, location, asset tag, service date, service ticket number, reason for the addition, refrigerant type, quantity added, and the technician’s certification details, followed by a completion attestation.
Use it when you need a structured record for EPA Section 608-related refrigerant additions and want each entry tied to one piece of equipment. It is especially useful for HVAC contractors, facility teams, and maintenance departments that need a clean audit trail across multiple sites or assets. The form works well as a companion to a work order, CMMS record, or service ticket because it preserves the service context without forcing users to search through free-form notes.
Do not use this template as a general maintenance checklist or for service events that do not involve refrigerant addition. It is also not the right place to collect unrelated employee data, broad asset history, or unnecessary PII. Keep the fields focused on the minimum necessary information, use conditional logic for “other” reasons or refrigerant types, and make sure the technician certification and signature are completed before filing the record.
Standards & compliance context
- This template supports EPA Section 608 recordkeeping by capturing refrigerant additions, appliance identity, and technician certification details in a structured format.
- The form follows data minimization by focusing on the minimum necessary fields needed for the service record and avoiding unrelated personal data.
- If your workflow includes technician signatures or review steps, keep an audit trail so edits and approvals remain traceable.
- Use clear required-versus-optional labeling and accessible field labels to support WCAG 2.1 AA usability for public-facing or shared intake forms.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Appliance Identification
This section ties the record to one specific piece of equipment so the addition can be traced back to the correct asset and location.
-
Appliance / System Name
Enter the equipment name or identifier used in your maintenance records.
-
Equipment Location
Enter the building, site, or area where the appliance is located.
-
Asset Tag / Equipment ID
Optional internal identifier if your organization uses asset tags.
- Appliance Type
Service Event Details
This section explains when the addition happened and why it was needed, which is essential for understanding the service context.
-
Date of Refrigerant Addition
Select the date the refrigerant was added.
-
Service Ticket / Work Order Number
Optional reference number for linking this entry to your maintenance system.
- Reason for Refrigerant Addition
-
Other Reason Details
Provide a brief explanation when ‘Other’ is selected.
Refrigerant Added
This section captures the substance and amount added, using structured fields that reduce ambiguity in the record.
-
Refrigerant Type
Select the refrigerant added to the appliance.
-
Other Refrigerant
Enter the refrigerant designation if it is not listed above.
-
Quantity Added (lbs)
Enter the amount of refrigerant added in pounds.
-
Quantity Added (oz)
Optional ounces field if your team records quantities in smaller units.
Technician Certification
This section documents who performed the work and confirms that the technician’s certification details are on file.
-
Technician Name
Enter the technician performing the service.
- Certification Type
-
Technician Certification Number
Enter the EPA Section 608 certification number exactly as issued.
-
Technician Signature
Optional signature for internal verification, if your process requires it.
Compliance Attestation
This section confirms the record is complete and ready to be filed, creating a final checkpoint before storage or review.
- I confirm this refrigerant addition record is complete and accurate to the best of my knowledge.
-
Compliance Notes
Optional notes for leak checks, repairs, or other compliance-related context.
How to use this template
- 1. Set up the form with your required appliance identifiers, service fields, refrigerant fields, and technician certification fields, and mark only the truly mandatory fields as required.
- 2. Preload or connect asset data where possible so the technician can select the appliance name, location, and asset tag instead of typing them from scratch.
- 3. Have the technician complete the service event details immediately after the refrigerant addition, including the reason for the addition and any “other” details when the preset options do not apply.
- 4. Record the refrigerant type and quantity using the correct units, then verify that the certification type, certification number, and signature match the person who performed the work.
- 5. Review the compliance attestation for completeness, route the record to the compliance owner or supervisor if needed, and store the final submission in an audit trail tied to the appliance and service ticket.
Best practices
- Use a date picker for the service date so the record is consistent and easy to sort.
- Keep refrigerant quantity in one primary unit and make the alternate unit optional only if your workflow needs it.
- Use conditional logic for the reason for addition so “other reason details” appears only when needed.
- Require the technician certification number and signature before the form can be submitted.
- Tie each entry to a single appliance and asset tag to avoid mixing records across equipment.
- Add a clear post-submit message that explains who reviews the record and where it is stored.
- Avoid collecting extra PII that is not needed for compliance or service tracking.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this template used for?
This template records refrigerant additions for a specific appliance after service, including the equipment identity, service date, reason for the addition, refrigerant type, quantity added, and technician certification details. It is designed for recordkeeping tied to EPA Section 608 requirements and helps create a consistent audit trail. Use it when you need a per-appliance log rather than a general service note.
Which appliances should be logged here?
Use it for appliances that fall under the applicable EPA recordkeeping threshold and for service events where refrigerant is added. The appliance identification section is meant to tie the entry to one unit, asset tag, and location so the record is easy to retrieve later. If the equipment is not covered or the event does not involve refrigerant addition, this template may not be the right fit.
How often should this form be completed?
Complete one log entry each time refrigerant is added during a service event. Do not wait until the end of the week or month, because service details and quantities are easier to capture accurately at the time of work. A per-event record also reduces missing fields and supports a cleaner audit trail.
Who should fill out and sign the log?
The technician who performed or supervised the refrigerant addition should complete the service details and certification fields, then sign the attestation. A supervisor or compliance reviewer can verify completeness, but the certification number and signature should come from the qualified technician. If your workflow separates data entry from sign-off, keep that handoff visible in your process.
What are the most common mistakes with this template?
Common issues include leaving the appliance identification vague, entering the refrigerant quantity in the wrong unit, or using free text where a structured field would be clearer. Another frequent problem is skipping the reason for addition or failing to document the technician certification number. Those gaps make the record harder to defend during review.
Can this template be customized for our maintenance workflow?
Yes. You can add conditional logic for common reasons for addition, prefill asset tags from your CMMS, or include a service ticket lookup field if your team uses one. Keep the form focused on the minimum necessary data needed for compliance and internal tracking, and avoid adding unrelated fields that create friction.
How does this template fit with other systems?
This log can sit alongside a work order system, CMMS, or compliance archive as the record of the refrigerant addition itself. Many teams connect it to service tickets so the ticket number and appliance record stay aligned. If you export records, keep the original submission and any edits in an audit trail.
What should we do after the form is submitted?
After submission, route the record to the compliance owner or maintenance supervisor for review, then store it where it can be retrieved by appliance, date, or ticket number. If the entry is incomplete, send it back for correction before it is filed. A clear post-submit step helps prevent missing certification details or inconsistent quantities.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
Support remote teams with the right tech, people, and plan—boost access, collaboration, and productivity with a unified platform.
-
Generative AI boosts workplace productivity, upskilling, and knowledge sharing—helping enterprises work smarter and unlock measurable gains.
-
See how frontline managers replace group texts and spreadsheets with connected scheduling, certifications, and attendance tools for a smoother shift cycle.
-
Discover 4 proven keys to successful project management and team collaboration — from transparent goal-setting to real-time communication and workflow...
Ready to use this template?
Get started with MangoApps and use EPA Section 608 Refrigerant Addition Log with your team — pricing built for small business.
