Inspection Program Audit: Auditing Your Own Program

An inspection program audit asks a different question from an inspection. An inspection asks "what condition is this building in?" An audit asks "is our program producing anything true, and is anybody acting on it?" You can run flawless inspections for two years inside a program that changes nothing.

The property inspection checklist defines what the program is supposed to do. The audit tests whether it does it.

Most programs are never audited, because the person who would audit them is the person who built them. That is why it needs a fixed date, a written test and a short list of pass-or-fail questions rather than a general feeling that things are going fine.

Key takeaways

• The audit tests the program, not the building. Condition belongs in inspections; coverage, consistency and closure belong here.
• Four tests: coverage, consistency, closure, and use. Failing any one of them makes the other three largely decorative.
• Closing rate, not finding count, is the single most diagnostic number.
• Sample the records, do not trust the summary. Pull five inspections and compare them against what the schedule says should exist.
• Audit annually in writing, and at any change of staff, system or vendor. Informal audits never happen.
• Findings from an audit are program changes, not building repairs. Different output, different owner.

What an inspection program audit is not

Three things get mistaken for an inspection program audit.

A condition inspection is a walk that records asset condition. Useful, not an audit.

A vendor quality audit examines whether a contractor delivered against a scope. It uses inspection evidence but asks a contractual question — covered under auditing the service you are paying for.

A compliance check confirms that inspections happened because a rule required them. It is the weakest form, because a program can be fully compliant and completely inert — a distinction that also applies to how you store the records, covered in inspection records and retention.

The program audit sits above all three, asking whether the system that produces inspections, records and closures works.

The four tests

Every program audit reduces to four questions. Score each honestly and the picture appears.

Test 1: Coverage

Did we inspect what the schedule says we inspect? Pull the inspection calendar for the last twelve months and the actual records. Count the gaps.

• Inspections scheduled versus completed, by month and by area.
• Areas in the schedule with no record at all.
• Areas marked "not inspected" with no reason given.
• Areas excluded from the schedule entirely, and whether that exclusion is deliberate.

A program that covers only the areas people complain about fails this test regardless of how good the individual inspections are.

Test 2: Consistency

Would two inspectors describe the same condition the same way? This is the test most programs never run, and the one that decides whether the data means anything. Pick three findings from different inspections and check whether each has a defined severity, a specific location and a photograph. Then pick one area inspected twice by different people and compare. Divergence is normal; unexplained divergence is a calibration problem. Also check whether the checklist and scale changed mid-year, because a format change silently resets every trend.

Test 3: Closure

Did findings get resolved, and can you prove it? This is where most programs fail.

• Percentage of findings closed within their assigned window.
• Findings open past their due date, and by how long.
• Findings closed without evidence: no photograph, no note, no date.
• Findings that recur across cycles under different identifiers, meaning nobody noticed they were the same problem.

CCOHS guidance on effective workplace inspections recommends carrying unfinished items from the previous report onto the next one with their original identifiers, and noting the completion status of each corrective action. Without stable identifiers, recurrence is invisible.

Test 4: Use

Did anything change because of this program? The hardest test. Look for evidence outside the inspection file:

• Budget requests or capital plans that cite inspection findings.
• Work orders traceable to inspection items.
• Vendor conversations that used inspection records.
• Changes to the checklist itself, driven by what inspections kept finding.

A program that passes tests one to three and fails this one is an expensive filing system.

The audit checklist

Run the audit as a scored exercise with a named auditor, a date and a written result. Twelve questions are enough.

Keep the pass conditions simple and quantitative where possible. "Looks fine" is not an audit result.

Common failure patterns the audit reveals

Five patterns account for most of what an audit finds.

The binder that grows and is never read. Records are complete and nothing has ever been retrieved. Coverage passes, use fails.

The all-green run. Every inspection scores well for a long stretch. Usually the checklist or the scoring has drifted.

The recurrence carousel. The same three defects appear every cycle under new identifiers, are repaired cosmetically, and return. Closure looks fine on paper; root cause is never addressed.

The unilateral program. One person holds the knowledge, so coverage collapses on their first week of leave. Deciding who should inspect a building is program design, not an administrative detail.

The calendar that survives and the standard that does not. Inspections happen on time but the checklist, scale and format changed twice, so nothing is comparable.

How often to audit, and who should do it

Audit annually, and again after any material change. Material change means a new inspector, a building added to the portfolio, a change of inspection tool, a new contractor, or a change to the checklist or scoring scale. Each resets the conditions the program was built around.

On who: CCOHS distinguishes internal audits performed by qualified staff to verify that the inspection program is effective from external audits performed by accredited auditors or requested by insurers. An internal audit checks whether the program does what it says; an external audit checks whether what it says is good enough.

For a single building or a small portfolio, an internal audit against a written checklist is sufficient and should take half a day. Where the program owner is not the program operator, bring in someone from another site. Independence matters more than seniority.

Not regulatory advice. Requirements for inspection records, workplace inspections and health and safety committees vary by province and by ownership structure. Confirm what your building must produce and retain with your provincial regulator and follow the owner's own procedures.

What to do with the findings

An audit that produces a report and no changes has become the thing it was meant to test. Convert each finding into one of four actions:

1. A program change — a new checklist section, a revised scale, a changed cadence.
2. A resourcing decision — more time, a second inspector, a better tool.
3. A training action — calibration, checklist use, photo standards.
4. An escalation — a condition issue the program cannot resolve and the owner must fund.

Set a date for the next audit before closing this one, and check the previous audit's actions first. A program that fails the same audit test two years running has a management problem, not an inspection problem.

Scope discipline

An audit reads records and inspects the system. It does not re-assess the building.

Scope note: Structural, electrical, mechanical, hazardous materials and fire system assessment are outside a property manager's remit. Where an audit surfaces a technical observation, refer it to a qualified professional rather than rating it.

Frequently asked questions

What is an inspection program audit?

A structured review of the inspection system rather than of the building. It tests whether scheduled inspections happened, whether different people record condition the same way, whether findings close with evidence, and whether anything changed as a result. The output is program changes, not repairs.

How often should I audit my inspection program?

Annually as a minimum, and again after any material change: a new inspector, a building added to the portfolio, a change of inspection tool, a new contractor, or a change to the checklist or scale.

What is the most important thing to check?

The closure rate. Whether findings are resolved within their assigned window, with evidence, is the most diagnostic measure of whether the program functions.

Can I audit my own program?

You can, and for a small portfolio a written internal audit is usually sufficient. The risk is that the program's designer is the least likely to see its weaknesses, so where possible have someone from another site run it.

How do I know if my inspection scores are real?

Compare two inspections of the same area by different inspectors and look for unexplained divergence. An unbroken run of high scores usually indicates the checklist or the scoring has drifted, not that the building has become flawless.

Audit the program, then run it better

An inspection program that has never been tested is a set of assumptions. The audit turns it into a system with a known coverage rate, a known closure rate and a record of what changed.

NeatScore gives property and facilities managers the retrievable records an audit depends on: dated inspections, photos per item, APPA 1—5 scoring, deficiency tracking with history, and a branded report per inspection. Try it free for 14 days, or see pricing.