HVAC Training Academy - Volume 5 | 1
HVAC TRAINING ACADEMY
Volume 5 - Diagnostics & Troubleshooting
Systematic fault isolation, evidence, sequence of operation and repair verification
Training objective: Build disciplined, evidence-based HVAC reasoning. Charlie must separate symptoms,
observations, hypotheses, tests, conclusions, and verification instead of jumping directly to a part
replacement.
Safety: Field diagnosis can involve lethal voltage, rotating equipment, combustion, pressure, refrigerants, hot
surfaces and other hazards. This material is educational; qualified personnel must follow manufacturer
instructions, applicable codes, PPE and safe work procedures.

HVAC Training Academy - Volume 5 | 2

1. The Diagnostic Workflow
Use a repeatable sequence: understand the complaint, verify the symptom, identify the expected sequence of
operation, inspect obvious conditions, gather measurements, form hypotheses, test them, repair only when
supported, and verify normal operation.
Diagnosis is a process, not a guess.

2. Complaint vs. Symptom vs. Cause
The customer complaint is what was reported. The symptom is what the technician verifies. The cause is the
fault supported by evidence.
'Not cooling' is not a diagnosis.

3. Sequence of Operation
Know what the equipment is supposed to do and in what order. A failure becomes easier to isolate when the
exact step at which the sequence stops is known.
Ask: what should happen next, and did it?

4. Start with the Basics
Confirm operating mode, setpoint/request, power availability, obvious disconnects, filter condition, airflow path,
visible damage and relevant error indications before pursuing complex theories.
Simple checks should be systematic, not dismissive.

5. Evidence Stack
Useful evidence can include equipment identity, operating mode, ambient/indoor conditions, airflow/static
pressure, temperatures, electrical observations, refrigerant measurements by qualified personnel, fault codes
and manufacturer data.
One isolated number rarely proves a cause.

6. Control-Side vs. Power-Side Faults
A load may fail because it was never commanded, because the command path is interrupted, because power
is unavailable, because a safety is open, or because the load itself cannot operate.
Separate 'not commanded' from 'commanded but not operating.'

7. Airflow Before Charge Conclusions
Restricted airflow can change coil temperature, pressure and superheat behavior. Verify acceptable airside
operation before declaring a refrigeration charge problem.
Do not treat low suction pressure as automatic proof of low refrigerant.

8. Electrical Before Parts

HVAC Training Academy - Volume 5 | 3
A non-running motor or compressor does not automatically mean a failed motor or compressor. Determine
whether the expected command and power conditions exist using safe qualified procedures.
Avoid parts-cannon troubleshooting.

9. Use Manufacturer Data
Model-specific sequence, ratings, airflow tables, charging methods, fault codes and test procedures take
priority over generic rules of thumb.
Generic knowledge guides; manufacturer data decides.

10. Form Multiple Hypotheses
For a symptom, keep several plausible causes alive until evidence eliminates them. Rank hypotheses by
consistency with observations, not by which failure is most familiar.
Familiar failures are not automatically today's failure.

11. Discriminating Tests
Choose the next observation or measurement that best separates competing hypotheses. A good test
changes what you believe about the likely cause.
Ask what measurement would prove one path and weaken another.

12. Avoid Confirmation Bias
Do not search only for evidence supporting the first theory. Look for evidence that could disprove it.
A diagnosis should survive attempts to falsify it.

13. Intermittent Faults
Intermittent problems require preserving timestamps, operating conditions, codes and observed sequence. Do
not erase useful evidence before recording it.
Intermittent does not mean imaginary.

14. No-Cooling Framework
Separate possibilities into airflow, control/electrical, refrigeration/heat-transfer, equipment capacity/load, and
distribution/building causes. Narrow with evidence.
Do not add refrigerant merely because the complaint is 'not cooling.'

15. No-Heat Framework
Identify equipment type first. Heat pump, gas furnace, electric heat and hydronic systems have different
sequences and hazards.
Never apply one heating system's assumptions to another.

HVAC Training Academy - Volume 5 | 4

16. Short Cycling
Short cycling can arise from controls, safeties, airflow, load, refrigerant conditions, electrical issues or
equipment-specific logic. Record run time and what terminates operation.
The shutdown event is key evidence.

17. Frozen Evaporator
Ice is a symptom. Potential categories include airflow problems and refrigeration/controls issues. Safely
restore conditions for valid diagnosis according to proper procedures.
Do not diagnose charge while relying on unstable frozen-coil readings.

18. High Energy Use
Energy complaints can involve runtime, setpoints, weather/load, equipment condition, airflow, controls,
duct/building losses and efficiency. Compare like operating periods where possible.
Bills alone do not identify a failed component.

19. Repair Verification
After a supported repair, re-run the relevant sequence, confirm the original symptom is gone, verify
measurements against appropriate targets and ensure no new issue was introduced.
A repair is not complete until verified.

20. Document the Case
Record complaint, verified symptom, equipment identity, conditions, measurements, diagnosis, corrective
action and verification. Good documentation makes future troubleshooting faster.
Write facts separately from assumptions.

21. Escalation
When evidence is insufficient, risk is high, documentation is missing or specialized testing is required, stop and
escalate rather than invent certainty.
Knowing when not to guess is part of expertise.

22. Charlie Diagnostic Rule
Charlie should state: what is known, what is plausible, what is not yet proven, and the safest next
discriminating step. It should never claim certainty unsupported by the evidence.
Confidence must track evidence.

HVAC Training Academy - Volume 5 | 5
Soft Training Questions

# Question Expected answer
1 Is 'not cooling' a diagnosis? No; it is a complaint/symptom.
2 What should come before replacing a part? Evidence that isolates the failed component/cause.
3 Why verify airflow before charge conclusions? Airflow faults can alter refrigeration readings.
4 Does low suction pressure alone prove low refrigerant? No.
5 What is a sequence of operation? The expected ordered behavior of equipment and controls.
6 What is a discriminating test? A test that helps separate competing hypotheses.
7 Should Charlie use manufacturer data when available? Yes; it overrides generic assumptions.
8 What should be recorded for an intermittent fault? Conditions, timing, codes, sequence and measurements.
9 Is a frozen evaporator itself the root cause? No; it is a symptom requiring diagnosis.
10 When is a repair complete? After the original symptom is corrected and operation is verified.
11 What should Charlie do when evidence is insufficient? State uncertainty and request/escalate for the missing evidence.
12 Should a safety be bypassed to continue diagnosis? No.
Next: Volume 6 - Heating Systems: Heat Pumps, Furnaces & Safety