Audit Season Is

Ask a safety rep when audit season is and you will get a date and a look. For most companies the Certificate of Recognition audit is something that happens to them once a year: three weeks of digging through binders, chasing signatures, finding the inspection that was supposed to happen in March, and hoping the interviews go well. Then the score comes back, the corrective action plan goes in a drawer, and the cycle starts again.

The strange part is that almost none of that evidence is new. The inspections, the hazard assessments, the toolbox talks, the orientations, the investigations, the drills: they were done, or not done, on the day they were due. The audit only asks to see them. The scramble is not doing the safety work. It is finding it.

What the audit actually asks

We read the two audit tools our first customers work under, line by line. The BC Construction Safety Alliance's COR audit for 2026 has 14 elements, 115 questions and 321 points.¹ Energy Safety Canada's 2023 protocol has 10 elements, lettered A to J.² Both tell the auditor exactly how to check each question: by reading documents, by interviewing people, or by watching the work.

That split is the whole design brief. Forty-six of the 115 questions are checked from documents alone. Is there a written policy, and is it current? Is the inspection frequency written down, and is it being met? Are deficiencies corrected on time? Are investigation reports reviewed by management? If the records live in one system, those questions can be answered from the records, every night, without anyone opening a binder.

Inspections, investigations and training alone carry 106 of the 321 points, and all three are things crews already record day to day. That is where a monthly check pays off most.

“The evidence is created every day. The audit should be too.”

Kept current, not crammed

So that is what we are building. Each documentation question gets a rule that says which records answer it, and the score is kept current as crews file their work. Inspection frequency met is the inspections done against the frequency the policy states. Deficiencies corrected on time is the findings closed by their due date. Every score shows the evidence it was built from, so the safety rep can check it in one tap instead of taking it on trust.

Kept current, the audit turns into a monthly to-do list instead of a yearly verdict. This month the site inspections are four behind. The joint committee did not meet. Two corrective actions are past due. Each one is worth a known number of points, so the catch-up list can be ranked by what it protects, and each line can become an action item with an owner and a date before the month is out.

Where software should stop

The other 69 questions are why this has to be done carefully. Do workers understand the safe job procedures? Is the correct PPE actually worn? Do supervisors refer to the legislation when they plan a job? No database knows the answer to those, and a system that pretends to is worse than none, because it hands the auditor a confident number nobody earned. The protocol is clear that interviews are confidential and observations happen on site.²

So in our design those questions are never guessed. They become tasks for a person: an interview to schedule, a site walk to do, with the question in front of them and the place to record what they found. The software does the counting it is good at, and leaves the judgement to the people the audit is actually about. A person accepts or changes every score, and a person signs the result.