What You'll Learn

• Where corrective actions fit in the measureQuick workflow between Test In and Test Out
• How to add notes, photos, and descriptions of actions taken during a service call
• How corrective actions appear in the PDF report and why they matter for customer communication
• How to link Test In findings to specific corrective actions and Test Out improvements
• Best practices for documenting warranty-related work
• How to use corrective actions to justify your work to customers and management

What You'll Need

• Device: iPhone (iOS 15+) or Android phone/tablet (Android 10+) with measureQuick installed
• App version: v3.0 or later
• Account: measureQuick Premier subscription (for Vitals Report and full reporting features)
• Context: An active project with Test In data saved, and service work completed or in progress
• Knowledge: How to save Test In and Test Out data (G11) and how to generate reports (J1)
• Time: 5 minutes to read, 2-5 minutes per service call to document actions

Why Corrective Actions Matter

A Test In shows what was wrong. A Test Out shows the system is fixed. But neither explains what you did in between. Corrective actions fill that gap. They document the specific work performed: what was adjusted, replaced, cleaned, or repaired.

This documentation serves multiple purposes:

• Customer trust. A report that shows "refrigerant charge failed" and then "refrigerant charge passed" is good. A report that shows "refrigerant charge failed, technician added 8 oz R-410A, refrigerant charge now passes" is better. The customer sees exactly what was done and why.
• Warranty protection. If a system fails again months later, your corrective action notes prove what was done, when, and by whom. This protects both your company and the customer.
• Technician accountability. Managers can review what actions were taken on each call, not just the before-and-after measurements.
• Legal and liability coverage. Documented corrective actions, backed by measurement data, demonstrate that your company followed proper diagnostic and repair procedures.

As Brandon Payne (Service Manager, Ecoplumbers) describes: "We went from an F to a B on a customer's system with very little money, and that customer has referred many customers to us." The corrective action documentation is what bridges the gap between the F and the B in the customer's mind.

Step-by-Step Guide

Step 1: Save Test In First

Before documenting corrective actions, capture the system's baseline condition by saving Test In data. This is your "before" snapshot.

1. Complete all measurements in the active test (pressures, temperatures, static pressure, electrical).
2. Wait for readings to stabilize (7-8 minutes minimum after system startup).
3. Tap Save Data at the bottom of the diagnostics screen.
4. Select Save Test In when prompted.
5. Review the subsystem pass/fail results. The failing subsystems are what your corrective actions will address.

The Test In data is now locked. Any further measurements will be compared against this baseline. As Jim Bergmann explains in the Gas Furnace Workflow video: "now I'm going to save the test in and at this point you want to review your subsystem review and we'll also grab some notes here."

Step 2: Add Notes and Descriptions

After saving Test In, add notes describing what you observed and what work you plan to perform. In the project view:

1. Navigate to the Notes section of the project (accessible from the project menu).
2. Add a text description of your findings and planned corrective actions. Be specific:
   • Good: "Refrigerant charge low. System 8 oz undercharged on R-410A. Superheat 22 degrees F (target 12-15). Adding refrigerant to bring superheat into target range."
   • Not useful: "Fixed charge."
3. Include relevant details: part numbers for replaced components, refrigerant weight added or recovered, filter size and MERV rating installed, settings changed.

Write notes as if someone else will need to understand exactly what happened six months from now. That someone might be you, a different technician on a callback, or a warranty adjuster.

Step 3: Add Photo Documentation

Photos provide visual evidence that supports your notes. measureQuick allows unlimited photo documentation per project with a Premier subscription.

Common photos to capture during corrective actions:

• Before and after: Dirty coil before cleaning vs. clean coil after. Kinked flex duct before straightening vs. after.
• Parts replaced: Old capacitor with visibly swollen top next to the new one. Removed contactor with pitted contacts.
• Nameplate/data plate: Especially for warranty claims. Photograph the equipment data plate, the part being replaced, and the replacement part label.
• Refrigerant scale: Photograph the scale showing the weight of refrigerant added or recovered.
• Wiring changes: Before and after photos of any wiring modifications.

To add photos within a project:

1. Tap the camera icon in the project or test view.
2. Take a photo or select from your camera roll.
3. Add a caption describing what the photo shows.

Photos are stored in the cloud with the project and appear in the PDF report. As Jim Bergmann notes in the Benchmarking video: "if you want to use advanced reporting features you can hit the unlock, it's gonna process this, will allow you to add your company logo to report, add in some photo documentation, do some additional things on the job site."

Photo documentation screen showing a captured photo with caption field and the list of existing project photos

Step 4: Perform the Work and Save Test Out

After completing the corrective actions:

1. Reconnect probes if disconnected during the repair.
2. Start the system and allow it to stabilize (7-8 minutes).
3. Verify all measurements are reading correctly.
4. Tap Save Data and select Save Test Out.

The Test Out data is your "after" snapshot. measureQuick will compare it against the Test In data, showing which subsystems improved, which stayed the same, and whether any new issues appeared.

Jim Bergmann describes this workflow: "make it perform, and we're going to test out the same exact way we test it in." The Test Out uses identical measurement methodology to ensure the comparison is valid.

Step 5: Generate the Report

With Test In, corrective actions (notes and photos), and Test Out all captured:

1. Tap Generate Reports from the project menu.
2. Select the report type:
   • Vitals Report (Premier) - includes Vitals Score comparison, letter grade, color-coded consumer format
   • Pro Report (Premier) - detailed technical report with full measurement data
   • Classic Report (Basic) - standard report with measurements and pass/fail
3. The report will include your Test In data, Test Out data, notes, and photos in a structured format.

The corrective actions appear in the report between the Test In and Test Out sections, giving the customer a complete narrative: here is what was wrong, here is what we did, and here is the proof it worked.

PDF report page showing Test In/Test Out comparison with corrective action notes and photos between them

Step 6: Use Corrective Actions for Warranty Documentation

For warranty-related work, thorough corrective action documentation is essential:

1. Document the failure mode. Record the Test In data showing the specific failure. Screenshot or note the exact measurements that are outside acceptable range.
2. Document the diagnosis. In notes, explain what component failed and why you believe the failure occurred (manufacturing defect, installation error, normal wear, etc.).
3. Document the replacement. Note the part number removed, the part number installed, the serial number of any replacement equipment, and the date.
4. Document the result. Test Out data proves the replacement resolved the issue.
5. Photograph everything. Failed part, new part, data plates, wiring, and the final readings on screen.

This documentation package - diagnostic data, notes, photos, and test results - satisfies most manufacturer warranty claim requirements and protects your company if the claim is challenged.

Video Walkthrough

• YouTube: (4:00). Covers project workflow including saving data, generating reports, syncing to cloud. Jim Bergmann: "the most important step right here is you want to save the data down at the bottom."

• YouTube: (1,576 views, 1:38). Quick walkthrough of saving test data and generating the report that includes corrective action documentation

• YouTube: (31:40). Demonstrates the full Test In to report generation workflow. Shows saving Test In, reviewing subsystems, and generating the report with all documentation

• YouTube: (4,365 views, 12:44). Walks through the Vitals Report and how corrective actions and Test In/Test Out comparisons appear in the customer-facing document

Tips & Common Issues

How detailed should my notes be?

Write enough that a different technician visiting the same system six months later can understand exactly what was done. Include: what you found, what you did, what parts you used (with quantities), and what the result was. If you added refrigerant, note the exact weight. If you changed a setting, note the old value and the new value.

I forgot to save Test In before starting repairs

If you have already made changes to the system, the current readings do not reflect the original condition. You have two options:

• If the changes are reversible (e.g., you adjusted a charge but have not changed a part), restore the original condition, save Test In, then make the corrections again and save Test Out.
• If the changes are not reversible, save the current readings as Test In (noting in your project notes that corrections were already in progress). The report will not show the full before-and-after, but you will still have documentation of the final system condition.

Photos are not appearing in the report

Verify that your photos are associated with the correct project. Photos taken outside the project context (using the phone's native camera app) will not be linked to the measureQuick project. Always use the camera function within the measureQuick app or attach photos through the project's photo documentation feature.

Corrective actions for "no problem found" visits

Even when you do not find an issue, document it. Save Test In showing all subsystems passing, add a note that the system was evaluated and found to be operating within design parameters, and generate a report. This documentation is valuable if the customer later claims the system was not working properly on the date of your visit.

Using corrective actions for technician coaching

Managers reviewing technician projects can evaluate not just the before-and-after measurements but the quality of the corrective action documentation. Is the technician explaining their reasoning? Are photos included? Are notes specific enough? This is a direct indicator of field process quality that goes beyond pass/fail scores.

Chad Simpson (Owner, Simpson Salute) reduced callbacks from 4% to under 2% after requiring measurement-based documentation on every call. Consistent corrective action documentation was a key part of that process change.

Reference Material

Download: Sample Pro Report (PDF)

Related Articles

Prerequisites (complete these first):

• Save Test In / Save Test Out - How to capture the before-and-after measurement snapshots
• Report Generation - How to generate the PDF report that includes corrective actions

Follow-up articles (next steps after this one):

• Report Sharing & Email - How to send the completed report to the customer
• HVAC Vitals Score - Understanding the score improvement your corrective actions produced
• Cloud Sync & Backup - Ensuring your corrective action data is safely stored

Related in the same domain:

• Searching & Filtering Projects - Finding past projects to review corrective action history
• Benchmarking Data - How corrective action quality affects company-level metrics

Need Help?

If you have questions about documenting corrective actions or how they appear in reports:

• Check the Related Articles section above
• Contact measureQuick support: support@measurequick.com