A refrigerant repair is not complete when the system starts cooling again. It is complete when the technician can show what was found, what was repaired, how the circuit was tested, and what refrigerant was recovered or added. Knowing how to document refrigerant repairs protects the technician, gives the next service call a usable history, and helps the company meet applicable recordkeeping requirements.
A good repair record should allow another technician to understand the job without calling the original tech. That is the practical standard. If the notes only say “fixed leak, added refrigerant,” the useful diagnostic information is already gone.
Start the Record Before the Repair
Document the equipment and the customer complaint before connecting gauges or opening the refrigerant circuit. This creates a baseline and keeps the final notes from becoming a memory exercise at the end of a long day.
Identify the equipment by manufacturer, model number, serial number, unit location, and system type. For split systems, make it clear which indoor and outdoor sections belong together. On larger equipment, identify the circuit number if the unit has multiple circuits.
Then record the reported issue and the condition you observed. “Not cooling” is the customer complaint. “Suction pressure low, evaporator coil partially iced, and electronic detector indicated a leak at the outdoor liquid-line service valve core” is the technician’s finding. Both belong in the record, but they serve different purposes.
Capture operating conditions that affect diagnosis. Outdoor temperature, indoor return-air temperature, supply-air temperature, thermostat call, blower operation, and initial pressures may all matter. You do not need to fill the ticket with random readings. Record the readings that support your diagnosis and the repair decision.
What a Refrigerant Repair Record Needs
The strongest records follow the actual sequence of work: diagnose, recover if needed, repair, test, evacuate, charge, and verify operation. That sequence helps prevent missed details and makes the notes easier to review later.
At a minimum, document these items:
- Equipment identification and refrigerant type
- Customer complaint and the observed condition
- Leak location, leak-detection method, and repair performed
- Refrigerant recovered, refrigerant added, and source of any charge used
- Pressure test and evacuation results, including the vacuum level and hold result when applicable
- Final operating readings and confirmation that the system was returned to service
For many residential service calls, the record can be concise. For equipment subject to federal, state, local, customer, or facility-specific requirements, the record may need more detail. The job ticket is not a substitute for knowing the rules that apply to that equipment, refrigerant, and customer location.
Record the Leak, Not Just the Charge
The most valuable line in a refrigerant repair note is usually the leak description. “Leak repaired” does not tell anyone where the problem was, why it occurred, or whether similar failures may happen again.
Write the component and location in plain field language. For example: “Confirmed leak at Schrader core on liquid service port using electronic leak detector and bubble solution. Replaced core and cap.” Or: “Found rubbed-through suction line at cabinet entry. Isolated line, brazed damaged section, added abrasion protection, and secured tubing.”
Also state the method used to confirm the leak. Electronic detector, bubble solution, ultrasonic detection, nitrogen pressure test, visual oil residue, or another accepted method may be relevant. If the leak was difficult to find, note the conditions that affected testing, such as wind, wet coil surfaces, or inaccessible piping.
This level of detail turns one repair into useful team knowledge. It can also reveal patterns, such as repeated valve-core failures, vibration damage, corroded coils, or recurring leaks at a particular installation point.
Document Recovery and Refrigerant Added
Refrigerant numbers should be specific and separated by activity. Do not write “used 4 pounds” when the job involved recovery, repair, and recharge. The person reviewing the record needs to know what came out, what went in, and why.
Record the refrigerant type and amount recovered. If refrigerant was stored for reclamation, reuse, or disposal under your company process, identify the cylinder or recovery container when your procedure requires it. If the system was not opened and no recovery was required, say so rather than leaving the field blank.
For refrigerant added, record the type, amount, and charging method. A useful note might read: “Added 2.4 lb of R-410A by weighed charge after evacuation. Final charge adjusted using manufacturer charging procedure at 78°F outdoor ambient.” This is much more useful than “charged unit.”
Be careful with estimates. If the amount is calculated rather than weighed, identify it as an estimate and explain why. Weighed recovery and charging records are generally easier to defend, troubleshoot from, and reconcile with inventory than rough cylinder-level guesses.
Show That the Repair Was Tested
A repair that passes a quick glance is not the same as a verified repair. The documentation should show the tests performed after the repair and their results.
When the refrigerant circuit was opened, record the pressure-test medium and test pressure according to the equipment and your company procedures. Note whether the pressure held and for how long. If you repaired a small leak without opening the entire system, document the post-repair leak check performed at the repair point and any other areas tested.
If evacuation was required, record the final vacuum level and the result of the standing-vacuum or decay test. The exact target and hold time can depend on the equipment, moisture exposure, system size, manufacturer instructions, and company standards. The point is not to copy a generic micron number onto every ticket. The point is to record the actual result and verify that it met the procedure used.
Finish with functional verification. Include the final pressures or temperatures that mattered, temperature split where relevant, compressor and fan operation, and any remaining conditions discussed with the customer. If the system could not be fully verified because of weather, load conditions, a failed accessory, or a separate electrical issue, state that clearly.
Make Notes Useful for the Next Technician
Clear documentation is a problem-solving tool, not office paperwork. The next technician may be responding to a callback, a seasonal maintenance visit, or a completely different failure. Good notes keep that person from repeating leak searches, guessing at prior charge adjustments, or assuming a component was replaced when it was only tested.
Use complete sentences for findings and abbreviations only when everyone on the team understands them. “Unit low” can mean low voltage, low airflow, low refrigerant, or low capacity. “Low suction pressure due to restricted indoor airflow from impacted filter and iced evaporator” is clear.
Photos can help when the system allows them, especially for corroded coils, tubing rub-outs, inaccessible leak locations, damaged insulation, or nameplates. A photo should support the written record, not replace it. Label it by unit and component so it remains useful later.
For teams, consistent note fields matter more than elaborate forms. A shared repair structure makes it easier to search past issues and compare similar equipment. HVAC Assist Pro can support this practical approach by keeping diagnostic instructions, equipment information, and technician discussion available from one field-ready workspace.
How to Document Refrigerant Repairs When the Job Is Incomplete
Not every refrigerant call ends with a repair. A customer may decline a coil replacement, a part may be unavailable, the leak may be inaccessible, or a system may have multiple issues that require a return visit. In those cases, document what was confirmed, what was recommended, and the system status when you left.
Avoid wording that suggests a permanent repair when only a temporary measure was performed. If refrigerant was added to restore limited operation while awaiting a repair decision, say that directly. Note the known leak location if identified, the amount added, the recommendation provided, and any operating limitations or risks explained to the customer.
This is also where accurate timestamps and technician identification matter. A complete record should show who performed the work and when the system was evaluated. For regulated equipment or customers with formal maintenance programs, follow the retention process and documentation format required by the applicable rules and contract.
The best refrigerant repair note answers one simple question: if this equipment fails again tomorrow, what does the next technician need to know before starting? Build every record around that question. It takes a few extra minutes at the job, but it saves time, protects the repair, and gives your team better information when they need it.
