Building Systems and Components: House-as-a-System Defect Recognition
The technical domain tests whether you can recognize defects across roofs, structure, exterior, electrical, heating, cooling, plumbing, insulation and interiors. It rewards house-as-a-system thinking and safety prioritization rather than memorized code numbers. Exam scenarios usually give you a visible clue and ask for the significance, the likely interaction, or the correct recommendation.
Think in interacting systems
Water, air, heat, vapour and structure move together. A roof leak may appear as attic staining, ceiling damage or exterior efflorescence. A bathroom fan discharging into the attic links moisture, insulation performance and mould risk. Combustion appliances, exhaust fans and duct leakage interact through house depressurization. Report what you observe and the plausible mechanism, not a definitive cause you cannot prove.
High-yield Canadian items
- Electrical: knob-and-tube, aluminum branch wiring, bootleg grounds, missing bonding, overloaded panels, double-tapped breakers.
- Plumbing: Poly-B, galvanized supply piping, lead service lines, TPR valve and discharge termination, cross-connections.
- Heating: draft-hood spillage and backdrafting, high-efficiency PVC venting and condensate handling, cracked heat exchangers suspected from flame or CO clues.
- Building envelope: roof flashings, ice damming, attic ventilation, siding and wall flashing, deck ledger attachment and flashing, foundation cracks, window wells and grading.
Worked example
A mid-efficiency furnace in a basement has a draft hood. With the dryer and a bathroom fan running, a smoke pencil at the hood shows spillage into the room. Report spillage/backdrafting under combined exhaust conditions and recommend evaluation by an HVAC technician, including venting and combustion air. The reasoning is depressurization and flue performance; you are not diagnosing a cracked heat exchanger or citing a code clause, you are reporting an observed safety condition and its implication.
Traps that cost marks
Naming a cause beyond the evidence. Calling a system safe because you saw no defect. Missing interacting conditions such as a new high-efficiency furnace with poor condensate drainage or a finished basement hiding structural clues. Relying on code numbers you cannot verify; describe the performance concern instead.
Key points
- Use house-as-a-system reasoning: moisture, air, heat and structure interact.
- Prioritize electrical, combustion, structural and fall hazards in your reporting.
- Report observed conditions and plausible mechanisms, not unproven diagnoses.
- Know common Canadian defect patterns: aluminum wiring, Poly-B, backdrafting, deck ledgers and ice damming.
- Recommend specialist evaluation when the evidence exceeds your scope.