The EHS Audit Checklist That Actually Gets Asked For
What an inspector requests, in the order they usually request it, where each piece of evidence comes from, and why the same eight items take one organisation an afternoon and another a week.
Most published EHS audit checklist templates are lists of topics. They tell you that training must be documented and that equipment must be inspected, which everybody already knows. What they rarely tell you is the shape of the actual request — that an inspector does not ask whether you train people, but whether this named person was competent for the task they were performing on the day of the event, and can you show it.
That difference is the whole discipline. Almost every organisation holds the underlying records somewhere. The ones that pass smoothly are the ones where those records refer to the same things, so a question about a person, a date and an asset can be answered without three people searching three systems and reconciling the results by hand.
This EHS audit checklist sets out the eight requests that come up most, what a strong answer looks like for each, and the failure that most often turns a routine inspection into a finding.
What gets asked, and where the answer lives
Run this EHS audit checklist against your own operation and time each row. Not whether you could eventually produce it — how long it takes today, for a specific person on a specific date.
| # | The request | A strong answer |
|---|---|---|
| 1 | Evidence the hazard was assessed before the work started | A hazard analysis with a revision date after the last process change, plus the permit that authorised the job. |
| 2 | Evidence the crew was briefed on that hazard that morning | A toolbox talk record with subject, date, deliverer and named attendance — not a generic training log. |
| 3 | Evidence protective equipment was issued and accepted | A signed issue record per person, with the specification tied to the risk group rather than to individual preference. |
| 4 | Evidence those certificates are still valid today | Validation against the issuing registry, not a stored certificate number. This is the one most often failed. |
| 5 | Evidence of competency for the specific task performed | Certificates in date at the moment of the work, with recertification tracked rather than reconstructed. |
| 6 | Evidence of exposure compliance | Time in the condition measured against the configured limit, with violations visible rather than derived afterwards. |
| 7 | The incident and near-miss record, and what followed | Investigation, corrective action with an owner and a date, and a re-scored risk showing the effect. |
| 8 | Evidence that evacuation actually works | Muster history with time to assembly and who was unaccounted for — not a note that a drill occurred. |
There is a ninth request that applies to every row above, and it catches people out because it sounds like a technicality: the instrument validity behind any reading you present. A measurement from an uncalibrated device proves nothing, so the calibration certificate for the specific instrument — not the model, the device — has to be produceable alongside the reading it produced.
The problem is not missing records. It is records that do not agree.
Ask a safety team why audit preparation takes so long and the answer is rarely that documents are missing. It is that assembling them requires reconciliation. The training system knows an employee by payroll number. The equipment issue log has a handwritten name. The incident record uses a badge ID. The sensor reading references a device serial that appears nowhere in the asset register.
Each of those systems is individually correct. What nobody owns is the mapping between them, so every audit question becomes a small research project, performed under time pressure, by people who have other jobs. And because the mapping is done by hand each time, it is done slightly differently each time — which is how two answers to the same question end up disagreeing in front of an inspector.
When the equipment record, the training record and the incident record refer to the same identity, and a reading, the instrument that took it and that instrument's certificate resolve to the same device, the eight requests above stop being research and become queries. That is the entire practical argument for running the safety lifecycle on one record rather than four, and it is administrative rather than glamorous. It is also the difference between an afternoon and a week.
The four findings that recur most
The lapsed certificate
Stored at purchase, never rechecked, revoked or expired since. Trivially verifiable by an inspector against the issuing registry, which is exactly why they check it first.
The stale hazard analysis
On file, correctly signed, and describing a method nobody has used since the line was reconfigured. It documents the gap between assessed and actual practice.
The open corrective action
An investigation from last year with actions still unclosed. Worse than no investigation, because it proves the hazard was known and shows what was not done about it.
The invisible contractor
Present on site, absent from the training register, the equipment log and the muster list — because those systems were built for employees.
Three of the four are lifecycle failures rather than documentation failures. The record was created correctly and then nobody owned what happened to it afterwards — which is why the organisations that struggle most are rarely the ones with the worst paperwork. They are the ones where creating a record and maintaining it are two different responsibilities.
Run the test before someone else does
The most useful way to use an EHS audit checklist internally is not as a document review. Pick a real job that happened last quarter — ideally a hazardous one, on a shift you were not present for — and try to answer all eight requests about it. Give yourself the time an inspector would give you.
Do it for a contractor as well as an employee. That single substitution reveals more than any checklist, because it tests the systems that were designed around payroll rather than around presence on site.
Then record how long each answer took and where it came from. That list is your real EHS audit checklist gap analysis, and it is considerably more honest than a maturity questionnaire. The rows that took longest are where to invest, in that order — and the baseline is what lets you prove the improvement afterwards.
How SmartX HUB shortens audit preparation
Permits, briefings, equipment issue, certificates, exposure, incidents and muster history all resolve to the same workforce identity and asset register — so the eight requests above are reports rather than reconciliation. Certificates are validated against the issuing registry instead of stored, calibration certificates stay attached to the device that produced each reading, and contractors sit in the same register as employees with their documents checked at the gate rather than at audit time.
The seven stages of the safety lifecycle and where each one breaks.
The four permit types and why one generic form fails.
Routine verification with timestamped evidence at each checkpoint.
Turn audit preparation into a set of reports
Tell us which of the eight requests takes your team longest today, and we will show where that evidence comes from when the whole lifecycle shares one record.
Explore our blog for insightful articles, personal reflections and ideas that inspire action on the topics you care about.
Explore more information about cases and news.
Stay informed with the latest updates and in-depth insights.
RFID Tool Tracking & MRO — Common Questions
Answers to the questions we hear most from teams evaluating RFID tool tracking for maintenance and MRO operations. Have another question? Reach out through our support center.
What are the main challenges of MRO tool control?
How does RFID compare to barcodes, NFC, BLE or GPS for tools?
How do you set up an RFID tool tracking system?
How does RFID integrate with our existing MRO and ERP systems?
What if some tools are too small or the wrong shape to tag?
How does RFID ensure calibration and maintenance compliance?
How does RFID support predictive and preventive maintenance?
What keeps tools accessible during downtime or power loss?
Still have questions about bringing RFID tool tracking to your operation?
Talk to Our Team
