What You'll Learn

• What a red flag indicates: the measurement falls outside the acceptable range for that subsystem
• Which of the 19 subsystems can show a red flag and what each evaluates
• The difference between measurement-based and subjective subsystems, and why their red flags mean different things
• What to do when you see a red flag: verify, then diagnose
• How the override capability works and when to use it
• How multiple red flags can point to a single root cause (compound failures)

What You'll Need

• Device: iPhone (iOS 15+) or Android phone (Android 10+) with measureQuick installed
• Account: measureQuick account with active subscription
• Familiarity: Comfort navigating the diagnostic screen (B14) and understanding fault severity levels (I2)
• Time: 10 minutes to read; ongoing reference during field diagnostics

Red Means Fail

A red flag on the measureQuick diagnostic screen means a measurement or subsystem has failed - the reading falls outside the acceptable range for the equipment, conditions, and configuration in the system profile. It is not a suggestion or a warning. It is a determination that something is outside the design envelope.

Yellow flags indicate marginal readings that may or may not require action. Red flags indicate conditions that should be investigated and, in most cases, corrected. The distinction matters for customer communication: a yellow flag is "worth watching," while a red flag is "this needs attention."

Diagnostic screen showing multiple red flag faults including dirty condenser, overcharged refrigerant, and liquid line restriction

Subsystems That Can Show Red

measureQuick evaluates system performance through 19 pass/fail subsystems. Each can produce a green (pass), yellow (warning), or red (fail) result. The subsystems divide into two categories based on how the evaluation is performed.

Measurement-Based Subsystems

These subsystems evaluate live instrument data against calculated target ranges. When a probe reading exceeds the acceptable threshold, the subsystem fails.

Each of these subsystems relies on probe data. The pass/fail determination is objective: the measurement either falls within the target zone or it does not. Failure rates from these subsystems reflect real field conditions.

Subjective Subsystems

Four subsystems are based on visual inspection rather than instrument measurement:

These subsystems appear on the diagnostic screen, but measureQuick cannot measure them with instruments. The app defaults to a conservative position, prompting the technician to review and confirm. The override rate for subjective subsystems is approximately 95%, meaning technicians change the app's default result nearly every time.

A red flag on a subjective subsystem means the technician has not yet confirmed the visual inspection, or has confirmed that the condition is poor. It does not carry the same diagnostic weight as a red flag from a measurement-based subsystem. When reporting failure rates across a fleet, subjective subsystems should be reported separately to avoid skewing the numbers.

What to Do When You See a Red Flag

A red flag is not the end of the diagnostic process. It is the beginning. Follow this sequence:

1. Verify Probe Placement

Before diagnosing a fault, confirm that the probes are correctly placed and reading accurately. A suction line temperature probe that has slipped off the pipe will give a false reading. An outdoor temperature probe in direct sunlight will skew every condenser-side calculation.

Common probe issues that cause false red flags:

• Temperature probe not insulated against ambient air
• Pressure probe not fully seated on the service port
• Clamp-on ammeter around multiple conductors instead of a single wire
• Outdoor probe reading condenser discharge air instead of true ambient

2. Check the System Profile

The target zones that define pass/fail are calculated from the system profile (SEER rating, metering device type, refrigerant type, tonnage). If the profile is wrong, the targets are wrong, and the red flag may not reflect a real fault. Verify the profile against the equipment data plates.

3. Wait for Stabilization

Readings during the first 5-7 minutes after startup will often show red and then settle into green as the system reaches steady state. If you see red flags immediately after turning the system on, give it time. If the red flags persist after 7-8 minutes of continuous operation, they are real.

4. Diagnose the Root Cause

Once you have confirmed accurate probes, correct profile, and stable readings, the red flag represents a real condition. Use the measurement values, the relationships between subsystems, and your field experience to identify the cause. measureQuick's mQ Assist (I4) can provide AI-driven guidance that considers multiple measurements together.

Measurement detail view showing current value, design target, ideal range, and ABOVE Ideal deviation indicator

Overriding a Red Flag

Technicians can override any subsystem's pass/fail result. When you override a red flag to green, the system records the change:

• pf_{subsystem}_override = 1 indicates the technician changed the result
• The headline failure rate in reports and analytics reflects the post-override result, not the app's original determination

Override is a designed part of the workflow. measureQuick provides the initial assessment; the technician confirms or adjusts based on professional judgment and field context. Valid reasons to override include:

• The system is still stabilizing and you know the reading will settle
• You have additional context the app does not (e.g., the homeowner just opened all the windows, temporarily affecting return air temperature)
• The reading is barely across the threshold and other correlated measurements are solidly green

Override is not intended to hide real failures. A technician who overrides every red flag is not using the tool as designed. The test-in/test-out workflow depends on honest documentation of the system's condition before and after service.

Multiple Red Flags: Compound Failures vs Single Root Cause

When you see more than one red flag, resist the urge to treat each as a separate problem. Multiple failures frequently share a single root cause.

Example: Low Refrigerant Charge

A system that is 15% undercharged may show red flags on:

• Superheat (too high, evaporator is starved)
• Subcooling (too low, not enough liquid in the condenser)
• Capacity (system cannot deliver rated BTUs)
• Temperature split (supply air is not as cold as expected)
• Discharge temperature (compressor runs hot due to high superheat)

Five red flags, one root cause. Correcting the charge will resolve all five. Chasing each red flag individually - without recognizing the pattern - wastes time and can lead to unnecessary parts replacement.

Example: Severe Airflow Restriction

A system with a blocked return duct or collapsed flex may show red flags on:

• Air distribution (TESP exceeds threshold)
• Temperature split (excessively cold supply air due to low airflow across the coil)
• Superheat (low, because the evaporator is absorbing less heat than designed)
• Capacity (reduced because less air is being conditioned)

Again, multiple red flags with a single fix. Clear the obstruction, restore proper airflow, and the refrigerant-side readings normalize.

How to Identify Shared Root Causes

Look for patterns:

• Are the failing subsystems all on the same side of the system (condenser-side vs evaporator-side)?
• Do the directions of deviation make physical sense together (e.g., high superheat + low subcooling both point to low charge)?
• Does correcting one condition logically resolve the others?

measureQuick's fault aggregation helps here. The system-level summary considers relationships between measurements rather than evaluating each in isolation. If the app identifies a system-wide issue, it will often point to the most likely root cause.

Tips & Common Issues

I see a red flag but the system seems to be working fine

"Working" and "operating within design parameters" are not the same thing. A system can cool the house while operating with a significant charge deficit, excessive static pressure, or voltage imbalance. The red flag is telling you the system is working harder than it should, wearing out faster, or consuming more energy than necessary. The homeowner may not notice a problem today, but the equipment is degrading.

Should I override a red flag before making a repair?

No. Save the test-in with the red flag intact. Perform the repair. Run a test-out. The comparison between the two tests is the strongest documentation of the work you performed. If you override the test-in, the before/after comparison loses its value.

A subjective subsystem is showing red and I did not inspect it yet

Tap the subsystem, perform the visual inspection, and set the result based on what you observe. If the condensate drain is clear and flowing, override to pass. If the outdoor unit coil is dirty and obstructed, leave it as fail and note the condition.

The same subsystem keeps failing across multiple systems

If you see the same red flag consistently, check your process. A recurring superheat failure across different systems might indicate a probe calibration issue, a consistent profiling error, or a real regional trend (e.g., systems in your area are commonly undercharged). Compare your results with other technicians in your company to determine whether it is a measurement issue or a pattern.

Related Articles

Prerequisites (complete these first):

• Understanding Diagnostic Screens - Navigating the interface where red flags appear
• Fault Types: Minor vs Major - How fault severity levels work, including the flag color system

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

• mQ Assist (AI Diagnostics) - AI-driven guidance for diagnosing root causes behind red flags
• Vitals Score Interpretation - How red flags affect the 0-100 system health score
• Component Pressure Drops - Diagnosing specific airflow-related red flags

Related in the same domain:

• Electrical Diagnostics - Detailed coverage of electrical subsystem red flags
• Target Zones - How the acceptable ranges that define red vs green are calculated

Need Help?

If you have questions about what a specific red flag means or how to respond:

• Check the Related Articles section above
• Contact measureQuick support: support@measurequick.com
• Schedule a training session with the measureQuick training team