Emergency Drill Records That Pass a Clause 8.2 Audit

The last time a site I know picked up a clause 8.2 nonconformance, it wasn’t because they hadn’t done the drills. They had. Four of them in the previous twelve months. The problem was that nobody could find the records when the auditor asked.

That is the whole game with clause 8.2 under both ISO 14001 and ISO 45001. The clause is short, but what it asks you to demonstrate in writing is not.

What Clause 8.2 Actually Requires

Both standards use almost identical language. You must establish, implement and maintain processes to prepare for and respond to potential emergency situations. You must plan your response actions, test them where practicable, review them after testing or after an actual incident, and communicate responsibilities to relevant parties.

“Where practicable” is doing a lot of work in that sentence. Auditors know it. They will ask why a particular scenario was or wasn’t drilled, and “we didn’t think we needed to” is not a satisfying answer. You need a documented list of foreseeable emergencies, derived from your environmental aspects register (14001) and your hazard register (45001), and then a clear record of which ones you tested and when.

What the Evidence List Looks Like

When an auditor sits down with your management system, they are building a picture from documents and records. For clause 8.2, expect them to ask for:

A list of identified emergency scenarios. It doesn’t need to be long, but it needs to reflect your actual site. A chemical storage facility and a light assembly workshop have different lists. Generic ones copied from a template stand out immediately.

Dated drill records. Date, location, scenario, who participated, how long it ran. A one-line entry in a shared spreadsheet is often enough, as long as it’s there and signed off by someone responsible.

Post-drill reviews. This is where most sites fall short. The drill happens, people go back to work, and the debrief never gets written up. Auditors want to see that you assessed what went well, what didn’t, and what you intend to change. Even a brief paragraph counts.

Action items and their closure. If the drill revealed that fire extinguisher locations weren’t known, there should be a corrective action, a responsible person, a target date, and evidence it was done. An open action list from a drill held eight months ago is a red flag.

Training records. Staff need to know the procedures. Not just the fire warden, everybody relevant to the scenario. A drill record that shows twelve people participated is also evidence of practical training, which can reduce duplication elsewhere in your system.

Communication records. If external parties are involved, contractors, neighbours, the local fire authority, there should be some record of how responsibilities were communicated to them.

The Common Failures

Most clause 8.2 findings are administrative rather than operational. The site did the work, they just didn’t record it.

The second most common failure is narrow scope. Sites focus entirely on fire evacuation because it’s familiar, and forget that their 14001 scope requires them to cover environmental emergencies too. A chemical spill, a fuel leak into a drainage channel, an uncontrolled release of process gases, these are foreseeable scenarios that need to appear in the record.

The third is a gap between the written procedure and what actually happened. If your procedure says the site manager leads the debrief within 24 hours, and the evidence shows the debrief form was completed three weeks later, that is a finding. Not always a major one, but it raises questions about whether the procedure is real or just paper.

Keeping the Records Straight

The practical fix is a simple drill log, one row per exercise, with columns for date, scenario, participants, debrief date, actions raised, and actions closed. It doesn’t need to live inside a formal quality management system. A controlled spreadsheet works fine.

Pair that log with a scheduled annual review of your emergency scenario list. As your site changes, as new chemicals arrive or processes are modified, the scenarios should reflect that. A list that hasn’t been touched in four years will attract scrutiny.

If you want to identify where the gaps sit before an auditor does, losses.cadencestandard.com can help you work through the operational picture systematically. And if clause 8.2 is one part of a wider effort to tighten up your site’s management disciplines, the Cadence Six framework gives you a structured route through the operational areas that feed directly into your ISO evidence base.