What this is
What is a contractor near miss report?
What is a contractor near miss report?
A contractor near miss report documents an event involving or observed by a contractor where harm nearly occurred but did not, without a confirmed breach of a rule necessarily having happened. It captures what was seen, whether the site's own conditions or the contractor's method contributed, and whether the loop was closed back to the person who reported it.
Who should raise it?
Whoever saw it: a contractor's worker, their supervisor, or one of your own people who witnessed a contractor near it. Contractors on site are often the only ones who still notice a hazard a permanent workforce has stopped seeing, and they usually assume, wrongly, that flagging it is not their place.
How is a near miss different from a violation?
A near miss is an event where harm nearly occurred and no rule was necessarily broken; a violation is a confirmed breach of a stated rule, whether or not harm resulted. A contractor can follow every rule correctly and still generate a near miss because of a site condition or an interface nobody accounted for, and routing that event to a violation record would misdescribe what happened.
Scope
When is a contractor near miss report required?
This record is one step in a larger programme. Using it for work that belongs to a neighbouring template produces records that are hard to report on later.
Use this template when
- A contractor's worker, supervisor, or one of your own people observes an event involving a contractor where harm nearly occurred
- The event needs capturing at the time, before the detail is lost to memory or smoothed over
- Whether the site's own conditions, the contractor's method, or the interface between the two contributed needs establishing
- Feedback needs closing back to the reporter, and sharing onward to your own workforce or other contractors where relevant
- The report should count toward the contractor's standing, and feed the site's wider hazard picture
Do not use it for
- Contractor Safety Violation Record, where a stated rule was actually broken rather than harm nearly occurring without one
- Contractor Incident Record, where harm or damage to person or property actually resulted
- Contractor Permit Compliance Check, which checks a contractor working under permit against what the permit specifies at the work point
- Contractor Emergency Drill Participation, which records contractor involvement in a planned evacuation or emergency exercise
- Anything outside KnowContractor, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 45001 cl.10.2 requirements does this satisfy?
ISO 45001 does not name near miss reporting directly, but treats it as an input to hazard identification and corrective action, and as something that has to be actively invited rather than assumed to happen on its own.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 45001 cl.6.1.2.1 | Hazard identification proactive and ongoing, explicitly including past incidents both internal and external to the organisation | What happened |
| ISO 45001 cl.8.1.4 | Contracted processes controlled, with the contractor's activity on site within scope of the OH&S management system | Header |
| ISO 45001 cl.5.4 | Consultation and participation of workers, extended in practice to contractors as people exposed to the same site | Header |
| ISO 45001 cl.10.2 | Nonconformity and corrective action: cause determined and evaluated even where no injury has occurred | Cause |
| ISO 45001 cl.7.4 | Communication determined for what, when, with whom and how, applied to feeding a finding back to the person who reported it | Response |
| ISO 45001 cl.10.3 | Continual improvement, using near miss data as a leading measure rather than waiting for a lagging one | Response |
What it does not cover
- Contractor Safety Violation Record, for a confirmed breach of a stated rule rather than an event where no rule was necessarily broken.
- Contractor Incident Record, where harm or damage has actually resulted rather than nearly occurring.
- Contractor Permit Compliance Check, which checks the contractor's work against the permit at the work point.
- A general hazard report for your own workforce, which follows its own route and register rather than the contractor-facing one.
- Contractor Emergency Drill Participation, which records a planned exercise rather than an unplanned event.
Global
Contractor Near Miss Report requirements by country
Near miss reporting is rarely a standalone legal duty anywhere. It is treated as good practice feeding an assessment or a management system that is itself required, which makes the encouragement to report as important as any rule about it.
OSH Act General Duty Clause; voluntary recordkeeping practice
No standalone requirement to log near misses, but a pattern of unreported ones can surface as evidence a recognised hazard went unaddressed.
Near miss data functions as an early warning a site can use in its own defence, not something a regulator asks to see routinely.
Management of Health and Safety at Work Regulations 1999
Not itself a recordable event under RIDDOR, but treated by HSE as one of the change triggers that should prompt a risk assessment review.
A near miss report that never reaches the relevant risk assessment has not done the job HSE guidance expects of it.
ISO 45001
Clause 6.1.2.1 requires hazard identification to consider past incidents, near misses included, as part of a proactive process.
Certification auditors expect to see near miss data actually feeding hazard identification, not sitting in a log nobody revisits.
How to complete it
How to complete a contractor near miss report, step by step
A near miss report is easy to fill in and easy to make useless. What decides which one happens is whether the cause is assessed honestly and whether the reporter hears back.
A near miss between a contractor and your own site rarely has one clean cause. Simultaneous operations and an unclear handover between your team and theirs cause more contractor near misses than either party acting alone, and a report that assigns the whole cause to one side has usually stopped one field too early.
Whether your site's own conditions contributed and whether the contractor's method contributed are genuinely different findings, and both need an honest answer even when one is more comfortable to write than the other. A report that only ever finds fault on one side will eventually stop being trusted by the side it always blames.
Feedback given to the person who reported it is not a courtesy step; it is the mechanism that produces the next report. A report that is logged, assessed and closed without the reporter ever hearing what happened to it teaches them that reporting goes nowhere.
A near miss that has occurred in a similar form previously is a different finding from a first occurrence, and it should carry more weight toward action, not less. Treating each report as a fresh, isolated event misses the pattern the report exists to reveal.
What auditors find
Most common contractor near miss report findings
The report itself is usually completed. What tends to be thin is the causal assessment and the feedback that follows it.
| Finding | Clause | What fixes it |
|---|---|---|
| Cause assessed against only one side, contractor method or site conditions, rather than the interface between them. | ISO 45001 cl.6.1.2.1 | Require both contributing-factor fields to be answered, and treat a blank one as unassessed rather than as a 'no'. |
| No feedback given back to the reporter once the report has been assessed. | ISO 45001 cl.7.4 | Make feedback to the reporter a required field before the report can be closed, not an optional courtesy. |
| A genuine near miss report scored negatively against the contractor's standing. | ISO 45001 cl.5.4 | Confirm the scorecard mapping credits timely, genuine reporting rather than penalising it. |
| A near miss during permitted work not linked to the relevant permit compliance check. | ISO 45001 cl.8.1.4 | Cross-reference the open permit at the time of the event so the two records read together. |
| A similar prior event not identified, so a recurring pattern is treated as a one-off each time. | ISO 45001 cl.10.2 | Search prior reports for the same area, contractor or activity before closing the causal assessment. |
| Report not shared with your own workforce or other contractors where the hazard is common to the site. | ISO 45001 cl.7.4 | Route relevant reports to a toolbox talk or briefing rather than filing them as contractor-only information. |
Case in point
Case in point: the near miss that was reported once and never again
A cleaning contractor's supervisor reported that one of her staff had nearly stepped into a floor opening left uncovered after a maintenance crew removed a grating and did not replace it before shift change. The report was logged, the opening was found already covered by the time the site investigated, and the record was closed with the cause left blank because nobody followed up with the supervisor to ask what she had actually seen.
She never reported another near miss in the eighteen months her contract ran after that. When asked directly during a later review, she said she had assumed the first report had been dismissed because nothing came back to her about it, and that raising it again did not seem worth the trouble. The site had not scored the report against her, but silence had the same effect as a penalty would have.
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.
5 sections
- Reference
- CON-038
- Archetype
- Record
- Record ID
- CNM-2026-000
- Scoring
- Reports received
- Direction
- High is good
- Singleton
- No
- Basis
- ISO 45001 cl.10.2
- Links
- Links Hazard reports, Scorecard
- Tags
- Contractor, Near miss
- Sections
- 5
- Fields
- 41
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 5
Header
14 fieldsCase ID*
Auto sequence. Format CASE-2026-00000.
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 and Time*
Completed By*
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.
Contractor*
Vendor ID*
Format VEN-0000.
Links to FDN-005 Vendor ID
They See What We Stopped Noticing
Contractors walk into your plant with fresh eyes and usually assume it is not their place to say anything. Asking for near misses explicitly is what changes that.
Reported By*
- Yes3 pts
- Partly1 pt
- No0 pts
Time Of Event*
Time Reported*
What happened
7 fieldsDescription*
Potential Severity*
- First aid4 pts
- Medical treatment3 pts
- Lost time2 pts
- Serious injury1 pt
- Fatality0 pts
Involved Our Workers*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Involved Our Equipment*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Photograph
Immediate Action Taken
Work Stopped*
- Not required3 pts
- Yes2 pts
- No0 pts
Cause
6 fieldsOur Site Conditions Contributed*
- No3 pts
- Partly1 pt
- Yes0 pts
Their Method Contributed*
- Yes3 pts
- Partly1 pt
- No0 pts
Interface Between Us Contributed*
Simultaneous operations and unclear handovers cause more contractor near misses than either party alone.
- Yes3 pts
- Partly1 pt
- No0 pts
Covered By The Method Statement*
- Yes3 pts
- Partly1 pt
- No0 pts
Covered By Induction*
- Yes3 pts
- Partly1 pt
- No0 pts
Similar Event Before*
- Yes3 pts
- Partly1 pt
- No0 pts
Related records
1 fieldPermit Compliance Check ID
Where a permit check was in progress.
Links to CON-036 Check ID
Response
13 fieldsFeedback Given To The Reporter*
- Yes3 pts
- Partly1 pt
- No0 pts
Shared With Our Workers*
- Yes3 pts
- Not relevant3 pts
- No0 pts
Shared With Other Contractors*
- Yes3 pts
- Not relevant3 pts
- No0 pts
Counts Positively On Scorecard*
Penalising a contractor for reporting a near miss guarantees you never hear another one.
- Yes3 pts
- Partly1 pt
- No0 pts
Scorecard ID
Links to CON-014 Scorecard ID
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Contract Owner*
Signature*
Safety Lead*
Second Signature*
CON-038 · record IDs look like CNM-2026-000 · Links Hazard reports, Scorecard
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The report is the easy part. Closing the loop with the reporter, catching the repeat, and keeping the score honest is the work that actually slips.
Holds the near miss library against the contractor's other records, flags an unclosed feedback field, and keeps a repeat event visible across sites.
Checks a reported near miss against the hazard register and the relevant risk assessment, and raises a review where the report shows the assessment no longer holds.
Watches for a genuine report scored negatively against a contractor, and holds that write for your approval before it reaches the scorecard.
This template lives in KnowContractor — contractor management. Prequalification, approval, induction, permits and performance.
Meet KnowContractor→Glossary
Contractor Near Miss Report definitions and key terms
- Near miss
- An event where harm nearly occurred to a person or damage nearly resulted, without a confirmed breach of a rule necessarily having taken place.
- Interface risk
- Risk arising from the point where a contractor's activity and the host site's own operations meet, such as an unclear handover or simultaneous operation.
- Contributing factor
- A condition, on either the site's or the contractor's side, that made the near miss possible, assessed separately from who was physically present.
- Positive reporting culture
- A design choice to credit, rather than penalise, genuine and timely near miss reporting, so that the behaviour continues.
- Leading indicator
- A measure, such as near miss frequency, that reflects exposure before an injury occurs, as distinct from a lagging measure counted after harm.
FAQ
Frequently asked questions about contractor near miss report
What is a contractor near miss report?+
It is a record of an event involving or observed by a contractor on site where harm nearly occurred, raised immediately by whoever saw it. It is built against ISO 45001 clause 10.2 and sits within the Contractor Onboarding and Management programme.
Does a rule have to be broken for something to count as a near miss?+
No. A near miss can happen with every rule followed correctly, because the cause is often a site condition or an interface nobody had accounted for. Where a rule was in fact broken, that event belongs on a violation record instead.
Why does a high count of reports count as a good score?+
Because a low count almost always means contractors have stopped reporting, not that nothing is happening. Reporting has to be actively encouraged, and the score is designed to reward the behaviour of raising a report rather than the absence of one.
Should a near miss ever count against the contractor?+
A genuine, timely report should not. Penalising a contractor for reporting a near miss guarantees you never hear about the next one, which is a worse outcome than the near miss itself. What can fairly count against a contractor is a pattern of the same near miss recurring after it was already raised and addressed.
Who should the report be shared with?+
Back to the reporter first, as feedback, and then onward to your own workforce or other contractors where the hazard is common to the site rather than specific to one contractor's method.
How does this connect to a permit or an emergency drill?+
Where a near miss happens during permitted work, it should be linked to the relevant permit compliance check so the two records read together. A planned emergency drill is a separate, scheduled exercise and is recorded on its own template rather than here.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Contractor Onboarding and Management
Contractor Prequalification Questionnaire
Collects a contractor's safety, insurance, training and performance information before they are approved
Contractor Safety Statistics Review
Reviews a contractor's injury rates, citations and experience modifier over recent years
Contractor Risk Classification
Classifies a contractor by the risk of the work they do, from low risk services to high risk construction
Contractor Approval Record
Records the decision to approve a contractor to work on site
Contractor Safety Program Review
Reviews the contractor's own written safety programme against your requirements
Subcontractor Declaration
Records any subcontractors a contractor intends to use
More in Contractor Safety
Contractor Permit Compliance Check
Checks that a contractor working under permit is doing what the permit says, at the work point
Contractor Emergency Drill Participation
Records contractor involvement in an evacuation or emergency drill, including whether they were accounted for
Contractor Fatigue and Hours Check
Checks hours worked and rest taken by contractors on extended shutdowns or overnight work
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 clauses 6.1.2.1, 10.2, 10.3 and 7.4
- HSE guidance on risk assessment review triggers and near miss reporting
- OSH Act Section 5(a)(1), General Duty Clause (US)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.