What this is
What is a hazard hunt log?
What is a hazard hunt log?
It is a record of a short, focused search for hazards in one defined area, carried out by a small team rather than a single inspector. It differs from a routine safety inspection in scope: a hunt covers one area in depth rather than a whole site at a shallow pass, and it is timed to when familiarity is likely to have set in.
What counts as a hazard here, as opposed to an incident?
A hazard is a source of potential harm that exists whether or not anyone has been hurt by it yet, an exposed drive belt, an ammonia line near a walkway, a step with no handrail. An incident has already happened. The hunt log exists specifically to catch the first kind before it becomes the second, which is why it sits upstream of the incident and near-miss reports in the same programme.
Why does a hunt need a team rather than one person?
Familiarity blindness is the whole reason this template exists. A person who walks the same area daily stops registering hazards they have adapted around. A small mixed team, including someone who does not normally work there, sees the area with fresh eyes and catches what routine has made invisible.
Scope
When is a hazard hunt log required?
A hazard hunt is one step inside the Incident and Investigation programme, not a catch-all for anything found on a walk. Using it to log a single reported hazard, an unsafe condition already flagged by someone else, or an unsafe act observed in passing produces records that overlap with other logs and are hard to report on cleanly later.
Use this template when
- A small team is doing a scheduled, area-specific search for hazards, not responding to a single report
- The area is due its monthly hunt, or has changed enough (new equipment, layout, process) to warrant one off-cycle
- A new record is needed; each hunt gets its own ID in the form HH-2026-000
- The intent is to surface hazards before they become incidents, feeding any unresolved finding into a CAPA
- The team includes at least one person who is not a daily occupant of the area being searched
Do not use it for
- Hazard Report, which is filed by one person the moment they notice a single hazard, not a scheduled team search of a whole area.
- Unsafe Condition Report, which covers a specific physical defect, such as a damaged guard or a blocked exit, reported as it is found.
- Unsafe Act Report, which records a way of working that puts someone at risk, not a static condition in the environment.
- Housekeeping Deficiency Report, which is scoped to cleanliness and order issues rather than the full range of hazard categories a hunt covers.
- Ergonomic Concern Report, which is a single-topic log for posture, lifting and repetitive strain, filed independently of any scheduled hunt.
Compliance mapping
Which ISO 45001 cl.6.1.2 requirements does this satisfy?
The clause references below are scoped to what a hazard hunt log can actually demonstrate: hazard identification and initial risk assessment, not the full corrective-action or management-review cycle that follows it.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 45001 cl.6.1.2.1 | Identify hazards arising from routine and non-routine activities in the area under review | Hazards found |
| ISO 45001 cl.6.1.2.1 | Account for human factors, including how work is actually carried out rather than how it is designed to be carried out | Header |
| ISO 45001 cl.6.1.2.2 | Assess the likelihood and severity of each hazard identified | Hazards found |
| ISO 45001 cl.6.1.2.2 | Determine the resulting level of risk so it can be prioritised | Hazards found |
| ISO 45001 cl.6.1.2 | Maintain documented information on the hazard identification and risk assessment process | Header |
| ISO 45001 cl.6.1.2.1 | Take action on hazards that can be eliminated or reduced immediately | Hazards found |
| ISO 45001 cl.10.2 | Ensure corrective action is initiated and tracked for anything that cannot be closed on the spot | Related records |
| ISO 45001 cl.9.1.1 | Determine what needs to be monitored and at what interval, and act on the results | Summary |
What it does not cover
- The same route walked by the same two people every month, which stops finding anything new once the obvious hazards have already been fixed.
- A hazard logged with no likelihood, severity or risk band recorded against it, which leaves nobody able to say whether it needs fixing today or next quarter.
- "Fixed on the spot" ticked with no description of what was actually done and no CAPA ID, which is a fix that nobody downstream can verify happened.
- A hunt record showing zero hazards found, which reads either as a genuinely clean area or as a team that did not look hard enough, with nothing else in the record to say which.
- An area quietly skipped for a full quarter because it is hard to access or unpleasant to inspect, which means the space most likely to hide a serious hazard gets the least scrutiny of any area on site.
Global
Hazard Hunt Log requirements by country
ISO 45001 is the common spine here, but what a regulator expects a hazard hunt log to prove, and how hard it will look for one, still varies by jurisdiction.
Management of Health and Safety at Work Regulations 1999, reg.3
Suitable and sufficient risk assessment is a standing legal duty, not satisfied once at setup.
A dated, team-led hunt log with real area coverage is treated as live evidence the duty is met on an ongoing basis, not archived proof from a one-off exercise.
OSH Act, General Duty Clause, sec.5(a)(1)
No explicit federal mandate to run scheduled hunts exists, but the duty to keep a workplace free of recognised hazards is absolute.
A hunt log becomes the paper trail showing recognised hazards were actively searched for, which matters if an inspector later asks why a known hazard type went unaddressed.
ISO 45001 cl.6.1.2.1
Hazard identification is an explicit, auditable requirement assessed at every surveillance audit.
Auditors sample hunt logs directly against this clause; a log with real variation in area, team and findings passes far more easily than one that reads as templated.
How to complete it
How to complete a hazard hunt log, step by step
Filling in the fields is the easy part. The judgement calls below decide whether the finished record can actually be defended later.
One name in Team Members technically satisfies the required field but defeats its purpose. Treat a single-name hunt as incomplete in substance even where the form accepts it.
"Change now" should map to a defined, non-negotiable response, agreed in advance rather than decided in the moment by whoever is holding the pen that day.
A tick with no note on what was done is evidence of an intention, not a fix. Require enough description that someone who wasn't there could tell what changed.
A few days late from a genuine scheduling conflict is normal drift. A full cycle late, or an area with no hunt on record for a quarter, is the gap an auditor will go looking for first.
What auditors find
Most common hazard hunt log findings
Patterns that show up once a set of hunt logs is reviewed side by side, rather than read one at a time.
| Finding | Clause | What fixes it |
|---|---|---|
| Hunts completed with a single name in Team Members, defeating the fresh-eyes purpose of the field | ISO 45001 cl.6.1.2.1 | Add a minimum-count check on the field, or a required co-lead field, rather than relying on help text alone. |
| Hazard Category offers only six catastrophic options (ammonia release, fire, major food safety failure, structural collapse, confined space, major environmental release), so a routine hazard has nowhere accurate to sit | ISO 45001 cl.6.1.2.1 | Extend the category list to cover routine hazard types alongside the catastrophic ones already there. |
| A hazard fixed on the spot has no field to record what the fix was, only a CAPA ID field conditional on the opposite answer | ISO 45001 cl.10.2 | Add a short free-text "action taken" field that applies regardless of the Fixed On The Spot answer. |
| Highest Risk Band Found in the summary is entered by hand rather than derived from the repeating rows, so it can silently disagree with what was logged | ISO 45001 cl.6.1.2.2 | Calculate the summary field automatically from the worst risk band in the repeating hazards-found rows. |
| Next Hunt Due is optional, so the cadence the template depends on is not enforced by the form itself | ISO 45001 cl.9.1.1 | Make the field required, defaulting to one month out from the current hunt's date. |
| Duration Minutes is optional and unscored, so a rushed five-minute pass can't be distinguished from a thorough walk | ISO 45001 cl.6.1.2.1 | Make the field required and flag durations well below what the area size would reasonably take. |
Case in point
Case in point: the ammonia line that scored "Rare" for three hunts running
A refrigeration line near a walkway by the chill store was logged in three consecutive monthly hunts, each time with Likelihood set to Rare and Risk Band landing on Acceptable. The same two people led all three, and the assessment was carried forward from memory rather than checked.
On the fourth hunt, a rotated-in team member who did not work in that area asked why likelihood was Rare when the ammonia detector log showed two alarm events in the preceding six months. Likelihood moved to Possible, the risk band to Investigate, and a CAPA opened, three cycles later than it should have been, purely because the team never changed.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- SAF-020
- Archetype
- Log
- Record ID
- HH-2026-000
- Scoring
- Count and severity mix
- Direction
- High is bad
- Singleton
- No
- Basis
- ISO 45001 cl.6.1.2
- Links
- Feeds CAPA
- Tags
- Hazard, Leading
- Sections
- 4
- Fields
- 25
- Follow up fields
- 1
- Repeating sections
- 1
- Links out
- 3
Header
9 fieldsHunt ID*
Auto sequence. Format HH-2026-0000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date*
Duration Minutes
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area*
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Team Members*
Small mixed teams find more than individuals. Include someone who does not work here daily.
Hazards found
Repeats8 fieldsHazard Description*
Hazard Category*
Photograph
Likelihood*
- Rare3 pts
- Possible1 pt
- Likely0 pts
Severity*
- Minor3 pts
- Moderate1 pt
- Serious0 pts
Risk Band*
- Acceptable4 pts
- Investigate2 pts
- Change soon1 pt
- Change now0 pts
Fixed On The Spot*
- Yes2 pts
- No0 pts
CAPA ID
Links to FDN-014 CAPA ID
Related records
1 fieldHazard Case ID
A hazard raised from this hunt.
Links to SAF-013 Case ID
Summary
7 fieldsHazards Found*
Fixed On The Spot Count*
Actions Raised*
Highest Risk Band Found*
- Low5 pts
- Medium4 pts
- High2 pts
- Very high1 pt
- Extreme0 pts
Next Hunt Due
Led By*
Signature*
SAF-020 · record IDs look like HH-2026-000 · Feeds CAPA
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The log itself is short. What determines whether it holds up is whether the cadence stays enforced, findings connect to a real fix, and the pattern across many hunts gets looked at, not just each hunt in isolation.
Holds the hunt schedule against every area on site, flags an overdue hunt before it becomes a missing cycle, and keeps each finding linked through to its CAPA.
Picks up a hazard needing a physical fix, an exposed belt, a failed guard, and tracks the work order through to a genuinely closed state.
Tracks who has actually led or joined a hunt for a given area recently, so rotation can be enforced with evidence instead of memory.

Notices when the same names keep showing up as the hunt team, rolls open findings across every hunt into one view, and holds any automated write for your approval first.
This template lives in KnowSafe — safety and compliance. Incidents, hazards, permits, inspections and the critical controls behind them.
Meet KnowSafe→Glossary
Hazard Hunt Log definitions and key terms
- Hazard
- A source with the potential to cause harm, independent of whether it has caused harm yet. The subject of a hunt, as distinct from an incident, which is harm or damage that has already occurred.
- Risk band
- The combined output of likelihood and severity, used to prioritise which hazards get attention first rather than treating every finding as equally urgent.
- CAPA
- Corrective and Preventive Action, the tracked record that a hazard which could not be closed on the spot is followed through to a verified fix.
- Leading indicator
- A measure that predicts future harm rather than counting past harm. A hazard hunt is a leading indicator; an incident report is a lagging one.
- Familiarity blindness
- The tendency for people who work in an area daily to stop consciously registering hazards they have adapted their behaviour around, the specific failure mode a rotated hunt team is designed to counter.
FAQ
Frequently asked questions about hazard hunt log
How is a hazard hunt different from a routine safety inspection?+
A routine inspection typically covers a whole site or line against a fixed checklist. A hunt is narrower and deeper: one area, done by a small team specifically briefed to look for what daily familiarity would otherwise hide.
Does every hazard found need its own CAPA?+
No. Anything fixed on the spot, and properly described, does not need a separate CAPA. The field only becomes relevant once Fixed On The Spot is answered No.
What happens if the same area comes back clean every month?+
A genuinely clean result is possible, but a long unbroken run of zero findings from the same team is worth checking, since it is the exact pattern familiarity blindness produces.
Who should lead the hunt team?+
The template requires a Led By field, but the standard does not mandate a specific role. What matters more than seniority is that the team composition changes cycle to cycle.
Can a hazard hunt substitute for a full risk assessment?+
No. It is one input into ongoing hazard identification under cl.6.1.2, not a substitute for a documented risk assessment covering routine and non-routine activities across a process.
Why does the form track duration if it is not scored?+
Currently it is not scored, which is itself a gap: an unscored duration field cannot flag a hunt that was too rushed to be credible, which is why extending it is listed as a finding above.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Incident and Investigation
Root Cause Analysis
Finds out why something happened rather than who was involved
Corrective and Preventive Action
The single action record used everywhere
Finding
Records a single deficiency picked up during an audit, inspection or check
Effectiveness Verification
Checks whether an action actually worked, some time after it was put in place
Just Culture Determination
Separates a system problem from a genuine choice to take a risk, using a consistent set of questions
Extent of Condition Review
Asks two questions after an investigation: where else does this same condition exist, and where else could this same cause bite us
More in Hazards
Hazard Report
Reports something that could hurt someone, before it does
Unsafe Condition Report
Reports a physical problem such as a damaged guard, a spill, poor lighting or a blocked exit
Unsafe Act Report
Reports a way of working that puts someone at risk
Stop Work Record
Records that work was stopped because it was not safe to continue
Safety Suggestion
Captures an idea for making work safer or easier
Housekeeping Deficiency Report
Reports untidy or obstructed areas that create slip, trip and fire risk

Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 45001:2018 cl.6.1.2 — Hazard identification and assessment of risks and opportunities
- ISO 45001:2018 cl.10.2 — Incident, nonconformity and corrective action
- ISO 45001:2018 cl.9.1.1 — Monitoring, measurement, analysis and performance evaluation
- UK Management of Health and Safety at Work Regulations 1999, reg.3 — Risk assessment
- US OSH Act sec.5(a)(1) — General Duty Clause
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.