What You'll Learn

• What manufacturers typically require for warranty claims
• How measureQuick test reports satisfy those requirements
• How to document initial commissioning at installation for warranty protection
• How to document the failure when a warranty issue arises
• What to include in a warranty submission package
• Common warranty scenarios where mQ data strengthens your case

What You'll Need

• Account: measureQuick Premier Services subscription
• App version: measureQuick v3.5 or later
• Prerequisite knowledge: Safety compliance documentation (L15) and saving test-in/test-out data (G11)
• Recommended: A standard process for running mQ diagnostics on every new installation

Why Documentation Decides Warranty Outcomes

Warranty claims fail for one reason more than any other: insufficient documentation. The equipment failed, the contractor knows it was not their fault, but they cannot prove it. The manufacturer asks for commissioning records, and the contractor has a handwritten note on an invoice or nothing at all.

measureQuick changes this dynamic. Every test you run generates a timestamped record with equipment identification, measurement data across 19 subsystems, pass/fail evaluations, and a PDF report. When a warranty claim requires proof that the system was installed and commissioned correctly, that record is already in the cloud.

The key is running the test at installation - not after the failure. A warranty claim backed by commissioning data from day one is fundamentally stronger than one assembled after the fact.

What Manufacturers Require

Warranty requirements vary by manufacturer, but most ask for the same core documentation:

Some manufacturers also require photos of the data plate, the installation, or specific components. measureQuick's photo documentation feature attaches these directly to the project record.

Documenting the Initial Commissioning

The most important step for warranty protection happens at installation, not when something breaks.

What to Capture at Install (Test-In)

Run a full mQ diagnostic as your test-in on every new installation:

1. Profile the equipment using AI System Profiler or manual entry. Capture condenser, air handler, and evaporator make, model, and serial number.
2. Connect all available probes. For cooling systems, aim for 9+ physical probe channels: supply/return temperatures, suction/liquid line, outdoor ambient, static pressure, and refrigerant pressures.
3. Run the diagnostic. Let measurements stabilize and capture steady-state readings.
4. Document pass/fail results across all applicable subsystems: refrigerant charge, airflow, static pressure, temperature split, venting (if applicable).
5. Attach photos of the data plate, the installation, and the thermostat settings.
6. Save the project with the test-in workflow phase marked.
7. Generate a PDF report (Pro Report or Vitals Report) and store a copy in the customer's file.

This creates a baseline record proving the system was operating within manufacturer specifications at installation.

Test-in report showing passing subsystems on a new installation

Documenting the Failure

When a warranty issue arises, run another mQ diagnostic before contacting the manufacturer.

What to Capture at the Service Call (Test-In)

1. Open the existing project for that equipment (search by address or serial number).
2. Run a new test-in on the current service call. This documents the system's current state, including the failure.
3. Capture the specific failure in the mQ measurements. If the compressor is not running, the data will show it. If refrigerant charge is incorrect despite no evidence of a leak, the readings will reflect that.
4. Attach photos of the failed component, any visible damage, and the equipment data plate.
5. Save and generate a report.

You now have two records: the commissioning data showing the system was installed correctly, and the service call data showing what failed. The contrast between the two tells the story.

Building the Warranty Submission Package

When you submit a warranty claim, include:

1. Commissioning report (PDF) - the test-in from installation day, showing all subsystems passing and measurements within spec
2. Service call report (PDF) - the test-in from the day the failure was discovered, showing the specific problem
3. Project summary - equipment make, model, serial number, installation date, and service history
4. Equipment serial and model - confirmed by mQ's equipment profile, not transcribed from memory
5. Photo documentation - data plates, installation photos, and photos of the failed component

All of this is available from the cloud dashboard. You do not need to reconstruct it from memory or dig through paper files.

Cloud portal project list showing project history with type, customer, site, technician, and status

Common Warranty Scenarios

Compressor Failure with Documented Proper Charge

A compressor fails 18 months after installation. The manufacturer's first question: was the charge correct at installation? Without documentation, this becomes a he-said dispute. With an mQ commissioning report showing subcooling and superheat within target ranges on day one, you have timestamped proof the charge was set to spec. The claim shifts from "prove you did not overcharge it" to "the compressor failed despite proper installation."

Heat Exchanger Crack with Documented Proper Venting

A cracked heat exchanger surfaces during a maintenance visit. The manufacturer may question whether improper venting caused excessive thermal stress. Your mQ commissioning report includes venting subsystem results, static pressure measurements, and combustion analysis data. If venting passed at installation, you have evidence the failure was not caused by installation error.

Refrigerant Leak on a New System

A system loses charge within the first year. The manufacturer wants to know if the charge was correct initially or if the system was undercharged from the start. Your installation test-in shows the exact superheat and subcooling readings at commissioning, proving the charge was correct. The current service call shows the charge deficit. The manufacturer can see the leak developed after proper commissioning.

TXV or Metering Device Failure

Metering device issues can be difficult to distinguish from installation errors. An mQ report showing proper subcooling at installation, followed by abnormal subcooling at the service call with no other changes to the system, points clearly to a component failure rather than an installation problem.

Tips & Common Issues

What if I did not run mQ at the original installation?

You can still use mQ to document the current failure, but your claim will be weaker without commissioning data. Going forward, make it standard practice to run a full diagnostic on every new installation. The 15-20 minutes it takes at install can save hours of warranty dispute later.

Do manufacturers accept mQ reports directly?

Most manufacturers accept PDF documentation that includes the data they need. mQ reports contain equipment identification, timestamped measurements, and pass/fail evaluations. Some manufacturers have specific claim forms; attach the mQ report as supporting documentation alongside their required paperwork.

How long does mQ store project data?

Premier accounts include permanent cloud storage. Your commissioning data from three years ago is still accessible. This is important for warranty claims, which can arise years after installation depending on the manufacturer's coverage period.

Should I share the full report or just excerpts?

Submit the full PDF report. It contains equipment identification, measurement data, and pass/fail results in a professional format. Cherry-picking data points can raise questions about what you left out. The full report demonstrates thoroughness.

Related Articles

Prerequisite articles:

• Safety Compliance Documentation - using mQ for compliance and liability protection
• Save Test In/Test Out - saving diagnostic snapshots at each workflow phase

Related in the same domain:

• Customer Education with Data - using reports in customer conversations
• Quality Metrics & KPIs - tracking quality to prevent warranty issues
• Reading Diagnostic Results - understanding what mQ measurements mean

Need Help?

If you get stuck or this article does not answer your question:

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