When people think about BNQ 3009-500, they think about the report. That's reasonable — the report is the deliverable, it's what the requester receives, and it's what shows off the quality of your work. But a surprising amount of what the standard requires happens around the report — specifically, what you have to keep on file behind the scenes. And this is where most inspectors have a blind spot.
Here's what the standard expects when it comes to objective evidence and the inspection file, and why the way you archive your work matters more than it looks.
What counts as objective evidence
The standard (article 7.1) defines objective evidence (preuve objective) as a factual element or piece of data gathered at the time of inspection to demonstrate either the presence of an apparent defect, deficiency indicator, or risk — or the absence of those things, or the truthfulness of an observation.
The examples the standard gives include photographs, handwritten notes, recordings, results from a measurement taken with a common instrument, emails, sketches.
Two things worth pulling out of that definition:
-
Objective evidence can demonstrate an absence. It's not just about documenting what you found — it's also about documenting what you didn't find. If a requester later claims you missed a sign of moisture at the base of a basement wall, your photo of that same wall, taken that day, is your strongest defense.
-
The evidence exists at the moment you gather it — not at the moment you decide whether to put it in the report. The two steps are distinct.
The obligation to gather evidence
Article 7.1.1 is explicit: the inspector has to gather objective evidence of every apparent defect, deficiency indicator, or risk detected during the inspection. And the inspector also has to gather evidence to demonstrate, where applicable, the absence of those things when their absence is detectable.
In other words: every observation, positive or negative, has to be backed by concrete evidence. That's not a best practice — it's a requirement.
Meaningful data
The standard also introduces the concept of meaningful data (données complémentaires) in article 7.2.2: precise facts or elements obtained using common instruments to objectively validate what the inspector detected during the close examination.
Example: you spot staining that suggests possible moisture. You pull out your moisture meter and get a reading. That reading is meaningful data. It reinforces the objective evidence you already had (the photo of the staining).
Technical detail worth remembering: if your instrument requires calibration per the manufacturer, you have to be able to demonstrate that it was calibrated. That's an explicit requirement of article 7.2.2.
The inspection file (chapter 10)
This is the chapter a lot of inspectors haven't read carefully. Article 10 requires the inspector to keep a file for every job, and it spells out exactly what that file has to contain:
- All correspondence exchanged with the requester, including any written authorization to release the report to a third party
- A copy of the service contract(s)
- A copy of any contract for supplementary services, plus the report covering those services
- All objective evidence gathered at the time of inspection (handwritten notes, photographs, recordings, sketches), whether or not they were used in preparing the report
- A copy of the report delivered to the requester
- A copy of every document obtained in connection with the inspection
The key sentence is the fourth one. All objective evidence. Even the pieces that didn't make it into the final report.
What that means in concrete terms
Run through a practical scenario. You're inspecting a Category 1 residential building. On site, you take 180 photos. When you sit down to write, 40 of them end up in the report delivered to the requester — the ones that document the apparent defects, deficiency indicators, and risks you identified. What about the other 140? They were there for reference, to document the inspection as a whole, or to establish the absence of a problem in a given area.
Under the standard, all 180 photos have to be kept in the file. Not just the 40 that appear in the report. It's not a suggestion — it's an article 10 requirement.
Same thing for the handwritten field notes, the quick sketches you tapped out on your tablet, the 15-second video you shot to document a noise in the plumbing. All of it is objective evidence, and all of it has to stay in the file.
Why this matters
Three reasons this requirement isn't just paperwork:
1. Your defense if something gets contested
If a requester later accuses you of missing a problem, your file is your strongest defense. The 140 photos you didn't put in the report can become the 140 pieces that show what you actually observed that day — and what wasn't visible.
2. It makes you a better inspector
An inspector who knows every photo is going to be kept subtly changes how they work. They document more carefully, more systematically, and build up a reference base that makes their inspections more reliable over time.
3. The requirement is formal
Starting October 1, 2027, with REIBH in full effect, a certified inspector who can't show they kept the file chapter 10 requires is in non-compliance. Independently of how good the final report is.
The problem with manual workflows
In a manual workflow, archiving objective evidence is exactly the kind of task reality catches up with. A few common scenarios:
- Photos sit on your phone until it's full, then you transfer them in bulk to a folder on your computer, with no clear link back to the requester's file
- Handwritten notes on a job-site pad end up in a pile that, six months later, is impossible to tie to a specific inspection
- Photos that didn't make it into the report get deleted at the end of the job to save storage space
None of those situations comply with article 10. And most inspectors who work that way don't even know it.
What good software changes
With software designed around the standard, the chapter 10 requirement becomes a non-issue — because it's handled automatically:
- Every photo you take is linked to the requester's file at the moment of capture, with a timestamp
- Photos that didn't make it into the final report stay archived in the file, searchable
- Notes, annotations, and sketches created in the editor are kept in the same place
- Signed service contracts are automatically filed with the project, along with their signing date
- Correspondence with the requester, authorizations, received documents — everything stays accessible within a few clicks
The result: if something gets contested two years later, you're not digging through three hard drives and four email inboxes. The file is right there, complete, the way the standard expects.
Axiom³ and chapter 10
The Axiom³ report editor automatically archives every piece of objective evidence to the project file:
- Photos taken from the app (whether or not they end up in the report)
- Annotations and sketches created in the editor
- Digitally signed service contracts
- Reports delivered to the requester through the client portal
- Documents received from the requester
Nothing to manage by hand. The file is complete, timestamped, and searchable.
Try Axiom³ for free — 10 inspections, no credit card required.