The question comes up constantly in Quebec inspector forums: what should a BNQ 3009-500-compliant inspection report actually look like? Templates floating around online are too generic, pulled from U.S. contexts, or built around a checklist — when the standard explicitly rules that format out. Here's a system-by-system breakdown with concrete sample excerpts, to show what a compliant report actually contains.
The standard's central principle: descriptive text, not a checklist
Article 9.1 of BNQ 3009-500 is explicit: "A list of items checked off on a form does not constitute an inspection report." The report must be a descriptive text, written in simple, explicit, unambiguous language. It cannot contain general or imprecise statements.
In practice:
- ❌ "Roof: fair condition."
- ✅ "Asphalt-shingle roof installed approximately in 2015. Observations: missing granules on the south slope, two lifted shingles near the chimney, slightly deformed back flashing. These observations constitute deficiency indicators (article 8.2); we recommend an expert review by a certified roofer before the transaction."
Descriptive, component-by-component structure is non-negotiable. Tools built around a checklist don't meet this requirement structurally.
The 10 essential information items (article 9.2)
Every compliant report opens with an identification block that must contain ten mandatory items. Missing any one makes the report non-compliant:
- Requester's name and contact info (the client who ordered the inspection)
- Inspector's name and contact info and, if applicable, their practice
- Inspector's RBQ certificate number (starting October 1, 2027)
- Service contract signing date
- Date the inspection was performed on site
- Date the report was issued
- Full address of the inspected building
- Weather conditions at the time of inspection
- People present during the inspection (seller, broker, requester, etc.)
- A statement that the report was prepared in accordance with BNQ 3009-500
In a compliant structured editor, these items are entered once at the start of the mandate and flow automatically into the final report.
The 8 systems of chapter 12
Chapter 12 of the standard breaks the inspection into eight major sections. Each must appear in the report, even briefly, even to confirm no finding was made in that section:
- Structural components (foundations, framing, load-bearing walls)
- Exterior architectural components (cladding, roof, windows, doors)
- Plumbing installation
- Electrical installation
- Heating, ventilation, and air conditioning systems (HVAC)
- Interior architectural components
- Attics, crawl spaces, and thermal insulation
- Security systems
For each system, the standard defines a scope (what the inspector must examine) and a non-exhaustive list of expected results — sample apparent defects, deficiency indicators, and risks to look for. A compliant report follows this breakdown and explicitly flags any section with no findings.
The three types of findings and how to write each one
The technical core of the standard sits in articles 8.1, 8.2, and 8.3, which separate findings into three categories. We've written a dedicated guide on the difference between apparent defect, deficiency indicator, and safety risk — here's how each shows up in a report.
Example of an apparent defect (article 8.1)
An apparent defect is a problem the inspector can detect and confirm at the time of inspection. The write-up must include: a description based on objective evidence, impact on the building, and a recommendation.
System 1 — Structural components — Foundations
During inspection of the visible concrete foundation from the basement, we observed a through-wall vertical crack approximately 1.2 m high on the west wall, accompanied by moisture staining and a deposit of white salts (efflorescence) at its base.
Type of finding: apparent defect (article 8.1).
Impact: active water infiltration into the foundation wall, potentially linked to a perimeter drainage issue or freeze-thaw cycling. Moisture can lead to progressive degradation of the concrete, indoor air-quality problems (mold), and loss of basement thermal performance.
Recommendation: an expert review by a structural engineer or a waterproofing contractor is required before the transaction, including an assessment of the French drain and the water-table level.
Example of a deficiency indicator (article 8.2)
A deficiency indicator is a sign — or a combination of signs — that doesn't let the inspector confirm a problem, but suggests one may exist. The write-up must include: description of the signs, and an objective, justified recommendation.
System 2 — Exterior architectural components — Roof
The asphalt-shingle roof shows uneven discolouration on the south slope and an area of approximately 2 m² where granules appear absent. Gutters and downspouts were not accessible during the inspection.
Type of finding: deficiency indicator (article 8.2).
Justification: these signs do not allow us to confirm the roof's integrity or remaining service life, but they suggest advanced aging. The precise installation date could not be confirmed from the documents available.
Recommendation: an expert review by a certified roofer, with safe roof access, is recommended before the transaction to assess remaining service life.
Example of a safety risk (article 8.3)
A risk is a potential source of danger to occupants, the building, or the environment. Because liability stakes are higher, the standard handles this category separately. The write-up must include: description, impact, and a recommendation for elimination, referencing an existing standard, code, or regulation.
System 8 — Security systems — Alarms
We noted the absence of carbon-monoxide detectors in the basement, which houses a natural-gas furnace. Two smoke detectors were found — one on the main floor, one on the upper floor — but both were past service life (manufacture dates 2009 and 2011).
Type of finding: safety risk (article 8.3).
Impact: undetected carbon monoxide in a basement with a combustion appliance presents a serious poisoning risk. Smoke detectors have a useful life of 10 years; those observed should be replaced.
Normative reference: National Building Code of Canada, Division B, Section 9.10.19 — smoke detectors; CAN/CSA 6.19 — carbon monoxide detectors.
Recommendation: immediate installation of a CO detector in the basement and replacement of both smoke detectors with recent photoelectric models using long-life batteries.
Specific signs to flag (article 7.2.3)
Article 7.2.3 requires the inspector to pay particular attention to specific signs, which must be explicitly mentioned in the report when detected:
- Rodents, insects, or other pests that could damage building components
- Ochre deposits (an issue in certain regions of Quebec)
- Pyrite or pyrrhotite in concrete
- Mold or fungi
- Asbestos, particularly in buildings renovated before 1990
For asbestos, the standard is explicit: the inspector must inform the requester of the possibility of a risk as long as technical expertise has not confirmed its absence, and must outline the precautions to take in the meantime.
The inspection file (chapter 10): beyond the delivered report
An often-overlooked aspect: the standard requires keeping a complete file for every mandate. That file must contain, among other things, all objective evidence gathered during the inspection — whether or not it ends up in the final report. Handwritten notes, photographs, recordings, sketches: all of it.
In a manual workflow, this requirement is hard to honour — photos that didn't make the cut tend to get lost. In a tool that archives automatically, it's a non-issue.
Report delivery (article 9.1)
The report must be delivered within the window set in the service contract. Electronic delivery requires the requester's explicit authorization (to comply with Quebec's Act to establish a legal framework for information technology). Otherwise, a paper copy must be provided.
In practice, a secure client portal with explicit consent to electronic delivery covers this requirement — which is what Axiom³ does by default.
What sets an Axiom³ report apart
The Axiom³ report editor was built around this structure from day one:
- 8 pre-organized systems — you can't skip a section by accident.
- Explicit finding-type selection (apparent defect / deficiency indicator / risk) with the required fields for each.
- Inline photo annotation tied to the system in question, with automatic archiving to the file.
- Identification block filled in once at mandate start.
- Client-portal delivery with time-stamped electronic consent.
- Structured PDF export ready to deliver.
Try Axiom³ for free — 10 inspections, no credit card.
Common questions
Can I write a BNQ 3009-500 report in a Word template?
Technically yes, but hard to keep rigorous. Word templates drift toward checklists, and maintaining the structure manually as the standard evolves is a growing burden. For occasional practice, it can hold; for full-time practice, a structured editor is safer from a compliance standpoint.
Does BNQ 3009-500 provide an official template?
The standard defines the required structure and content, but does not provide an official Word or PDF template. Each compliant software tool implements that structure in its own way.
How long is a typical report?
Between 35 and 80 pages, depending on building size and number of findings. A short report on a new condo may run 25 pages; a report on an older triplex can exceed 100. Length is not a compliance criterion — structural completeness is.
Where can I download BNQ 3009-500?
The standard is free to download from the Bureau de normalisation du Québec website.
Sources & references
- BNQ 3009-500 standard — Residential Building — Inspection Practices in a Real Estate Transaction Context (free download): bnq.qc.ca
- REIBH (chapter B-1.1, r. 3.1): LégisQuébec
- National Building Code of Canada: National Research Council of Canada
- Act to establish a legal framework for information technology: LégisQuébec
Last verified: April 22, 2026.