One of the most commonly misunderstood pieces of BNQ 3009-500 is the distinction it draws between three types of findings. A lot of inspection reports — including reports written by experienced inspectors — treat all three categories as one long list of "problems found." That's not what the standard asks for.
Here's why the three categories exist, how to tell them apart, and how to document each one correctly in a compliant report.
Three categories, three different treatments
Articles 8.1, 8.2, and 8.3 of the standard define three possible inspection results. Each one has its own documentation requirements in the report. Collapsing them isn't just a vocabulary slip — it changes what the standard expects of you.
Here's the core difference:
| Category | Nature | Certainty level |
|---|---|---|
| Apparent defect | Confirmed problem | High — the inspector saw and confirmed it |
| Deficiency indicator | A sign suggesting a problem | Uncertain — the inspector couldn't confirm |
| Risk to safety or physical integrity | Potential source of danger | Variable — possible or confirmed |
1. The apparent defect (article 8.1)
Definition
The standard defines an apparent defect (vice apparent) as a problem detectable by the building inspector at the time of inspection. The key word is detectable: the inspector saw the problem, can document it directly with objective evidence, and can confirm that it exists.
What the standard requires in the report
For every apparent defect detected, article 8.1 requires the inspector to:
- Describe the defect from the objective evidence gathered and, where applicable, from meaningful data or information contained in documents obtained from the requester
- Describe the defect's impact on the state of the building parts covered by the inspection
- State the risks of leaving it uncorrected
- Recommend that the requester, depending on the nature or significance of the defect, obtain additional information or commission a technical expertise before making a decision about the transaction
A concrete example
Active step cracks in the brick cladding above a door. The inspector sees the cracks, photographs them, measures their width with calipers, confirms it's an apparent defect. In the report: precise description, annotated photo, impact on the envelope, risks of leaving it alone, and a recommendation to commission a technical expertise from a structural engineer.
2. The deficiency indicator (article 8.2)
Definition
The standard's definition of this one is important to read carefully: a deficiency indicator (indice de déficience) is a detectable sign, or combination of detectable signs, at the time of the inspection that does not let the inspector confirm the existence of a problem.
The nuance is crucial. The inspector sees something that might indicate a problem — but can't confirm it. Either because a component isn't accessible, or because the sign alone isn't conclusive, or because confirmation would require a technical expertise that falls outside a building inspection's scope.
What the standard requires in the report
For every deficiency indicator, article 8.2 requires the inspector to:
- Describe the sign or combination of signs that led them to identify the indicator, including whether the indicator relates to a component, appliance, or system reaching the end of its useful life
- Formulate and objectively justify a recommendation about each indicator
- If a technical expertise is recommended, specify what it's expected to explain or verify, guide the requester on the qualifications of the person to commission it, and state the risks of ignoring the recommendation
A concrete example
Efflorescence staining on a basement foundation wall in an area where the adjacent wall is finished and not accessible. The inspector sees the staining, photographs it, takes a moisture reading with their moisture meter (meaningful data), but can't confirm the extent of the problem behind the finished wall. That's a deficiency indicator — not an apparent defect. In the report: description of the signs, note that part of the wall wasn't accessible, recommendation for a more in-depth expertise before the transaction, with a note on the qualifications of the specialist to consult.
3. The safety or physical integrity risk (article 8.3)
Definition
The standard defines this kind of risk as a potential source of danger identifiable by the inspector, which could result in illness, damage to the residential building or its contents, or harm to the environment.
This category is separate from the other two because the liability stakes are higher. An inspector who fails to clearly flag a safety risk is exposed differently from one who missed a cosmetic defect.
What the standard requires in the report
For every risk detected, article 8.3 requires the inspector to:
- Describe the risk from the objective evidence gathered
- Establish the risk's impact on the state of the building parts covered by the inspection
- Formulate a recommendation to eliminate it
- State the risks of ignoring the recommendation
The standard adds an important detail: the inspector should lean on an existing requirement from a standard, code, or regulation when formulating the elimination recommendation, where one applies. In other words, when you can point to a codified requirement (Construction Code, National Building Code, municipal regulation), do it.
A concrete example
A kitchen outlet next to a sink with no ground fault circuit interrupter (GFCI). The inspector spots it, photographs it. That's a safety risk: risk of electrocution. In the report: description of the risk, impact (risk to occupants), recommendation to replace the outlet with a GFCI outlet, and explicit mention that the requirement comes from the Construction Code. Depending on context, the inspector might also note that the replacement cost is worth factoring in before the decision, or suggest the requester plan to do the replacement after closing.
Why the distinction matters
For report clarity
A report that blends defects, indicators, and risks into one section gets unreadable fast. The requester can't tell what's confirmed, what's possible, and what's dangerous. And the priorities get muddy.
For your professional liability
Each category carries different treatment requirements. If you handle a deficiency indicator as an apparent defect, you're asserting a certainty you don't have — and you're exposed. If you handle an apparent defect as a deficiency indicator, you're under-communicating the severity — and you're exposed the other way. Precision protects you.
For third-party readability
Notaries, brokers, buyers, insurers — everyone who reads your report after the requester needs to see the three categories clearly. That's what lets them make informed decisions without having to call you for clarification.
How good software helps you keep the distinction straight
A report editor designed around the standard should:
- Force you to place each finding in the right category as you enter it
- Surface the required fields specific to each category (impact, recommendation, risks of inaction for apparent defects; description of signs, justified recommendation for indicators; impact, elimination recommendation, and reference to an applicable code for risks)
- Structure the final report so the three sections are distinct and clearly labeled for the requester
- Block publication of an incomplete finding — like an apparent defect without a risks-of-inaction statement
That's exactly how Axiom³ is structured. The editor walks you through the specific requirements of each category, and the final report cleanly reflects the distinction the standard asks for.
Try Axiom³ for free — 10 inspections, no credit card.