What this is
What is a contractor safety violation record?
What is a contractor safety violation record?
A contractor safety violation record documents a confirmed breach of a stated safety rule by a contractor's worker, supervisor or crew, at the point someone observed it. It captures what was broken, whether the site responded immediately, why it happened, and what consequence followed, so that a pattern of violations by the same contractor can be seen and acted on rather than absorbed as individual incidents.
Who raises it, and when?
Whoever observes the breach raises it, at the time. That is deliberate: a violation reconstructed the next day from memory loses the detail that matters, such as whether the supervisor was standing next to the worker when it happened. The contract owner then completes the assessment of cause and consequence.
How is a violation different from an incident or a near miss?
A violation is a confirmed breach of a rule or procedure, whether or not it caused harm. A near miss is an event where harm nearly occurred and no rule was necessarily broken. An incident is where harm or damage actually resulted. The same afternoon can produce all three from unrelated events, and routing each to the wrong record breaks the trail that later explains a pattern.
Scope
When is a contractor safety violation record 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 crew is observed breaching a stated site safety rule or procedure
- The breach ranges from an unsafe act by a worker to a supervisor knowingly allowing one
- The event needs an immediate response captured at the time: stopped, made safe, and the right people informed
- A pattern needs checking, so a new violation can be marked against a contractor's prior record before a consequence is decided
- The outcome needs to feed the contractor's performance scorecard ahead of the next award decision
Do not use it for
- Contractor Near Miss Report, where no rule was necessarily broken and the event is one where harm nearly occurred rather than a confirmed breach
- Contractor Incident Record, which records an incident where harm or damage to person or property actually resulted
- Contractor Performance Scorecard, which aggregates safety, quality, schedule and cooperation over a period rather than a single breach
- Contractor Suspension Record, which documents the formal decision to suspend or remove a contractor and is its own record once that line is crossed
- Anything outside KnowContractor, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 45001 cl.8.1.4 requirements does this satisfy?
ISO 45001 has no single clause titled 'violations'. The obligations that a violation record actually discharges sit across contractor control, the duty to eliminate hazards on the spot, awareness of consequences, and corrective action, which is why the record has to do more than log the breach.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 45001 cl.8.1.4 | Criteria for OH&S applied to contractors, with their conduct on site controlled as part of operational planning and control | The violation |
| ISO 45001 cl.6.1.3 | Legal and other requirements determined and applied, of which a site's own safety rules form part for anyone working under them | Header |
| ISO 45001 cl.8.1.2 | Elimination of hazards and reduction of risk, applied at the point a hazardous act is observed rather than deferred | Immediate response |
| ISO 45001 cl.5.4 | Consultation and participation, including informing the relevant supervisor and contract owner as the event is handled | Immediate response |
| ISO 45001 cl.7.3 | Awareness of the consequences of departing from established procedures, and whether that awareness was actually provided | Why it happened |
| ISO 45001 cl.10.2 | Nonconformity and corrective action: cause determined, action taken, and its effectiveness reviewed | Consequence |
| ISO 45001 cl.9.1.1 | Monitoring and measurement of the effectiveness of controls, including verification before work resumes | Consequence |
What it does not cover
- Contractor Near Miss Report, for an event where harm nearly occurred without a confirmed breach of a rule.
- Contractor Incident Record, where harm or damage to person or property has actually resulted.
- A full root cause investigation or CAPA record, which this record can trigger but does not itself replace once the corrective action grows beyond the immediate contractor response.
- Contractor Suspension Record, which documents the formal suspension or removal decision once a violation, or a pattern of them, crosses that line.
- An internal disciplinary record for your own employees, which follows an entirely different process and reporting line.
Global
Contractor Safety Violation Record requirements by country
The duty to control a contractor's conduct on site is close to universal, but how directly a regulator holds the host site responsible for a contractor's own breach differs sharply.
OSH Act General Duty Clause; multi-employer worksite doctrine
A controlling or host employer can be cited for hazards created by a contractor if it had the ability to detect and correct them.
An unaddressed pattern of violations is evidence the host site knew and did not act, which is precisely what the doctrine targets.
Health and Safety at Work etc. Act 1974, section 3
A duty extending to persons not in your employment who may be affected by how your undertaking is conducted, contractors included.
A record showing consistent, evidenced enforcement helps demonstrate that duty was discharged.
ISO 45001
Clause 8.1.4 requires OH&S criteria to be applied to contractors and their work controlled, not merely specified in a contract.
Certification auditors look for evidence that a breach was actually acted on, not just that a rule existed to be broken.
How to complete it
How to complete a contractor safety violation record, step by step
Most of what makes this record defensible happens in the minutes around the observation, not in the paperwork written afterward.
A record stating what was seen but not whether work was stopped or made safe has documented an observation, not a response. It needs both: the breach as it happened, and what was done about it, because the second half is what an investigator will ask for first.
A worker acting alone and a supervisor watching and allowing it are different findings. The first points to a training gap; the second points to a site where the rule is known and tolerated, a heavier problem than the individual act.
If the safe way to do the job was not actually available, a missing barrier, an unavailable tool, an impractical rule, the violation is partly the site's. Recording that honestly puts the corrective action on the right side of the interface, not solely on the contractor.
A first violation and a third by the same contractor are not the same event even if the breach looks identical. The prior history needs checking at the point the consequence is decided, so escalation through warning to removal follows the pattern rather than resetting every time.
What auditors find
Most common contractor safety violation record findings
The violation record is unusual in that most sites write the first half well: the breach itself is almost always clearly described. What gets missed is what happens next.
| Finding | Clause | What fixes it |
|---|---|---|
| Violation recorded with no evidence work was stopped or made safe at the time. | ISO 45001 cl.8.1.2 | Require the immediate response fields at the point of observation, not deferred to a later write-up. |
| Supervisor awareness not established, so a tolerated breach and an isolated act are treated the same. | ISO 45001 cl.5.4 | Ask explicitly whether a supervisor was present and what they did, and record it even when the answer is uncomfortable. |
| The site's own contribution, missing equipment, an impractical rule, is not assessed. | ISO 45001 cl.8.1.4 | Record whether the safe way was actually available before assigning the consequence solely to the contractor. |
| Repeat violation not checked against the contractor's prior record before a consequence is set. | ISO 45001 cl.10.2 | Search prior violations by the same contractor at the point of raising, and route the consequence through the defined escalation path. |
| Corrective action closed as complete without verification before the work restarted. | ISO 45001 cl.9.1.1 | Separate 'action taken' from 'verified before restart', and require the second before the record is closed. |
| Violation not linked to the contractor's performance scorecard. | ISO 45001 cl.8.1.4 | Flag every closed violation to feed the scorecard automatically, so the next award decision has the full history in view. |
Case in point
Case in point: the warning that was never checked against the file
A refrigeration contractor's technician was observed working at height on a chill store roof without the fall restraint the method statement required. The supervisor stopped the work, the technician was made safe, and a written warning was issued that afternoon. The record was closed within a week.
Four months later the same contractor's crew did the same thing on a different site belonging to the same company. Nobody caught it as a repeat, because the two records had never been checked against each other; each had been raised and closed by a different contract owner with no reason to look at the other site's file. Only at the contractor's annual review did both records surface together, by which point the escalation path had already been skipped twice.
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-015
- Archetype
- Record
- Record ID
- CSV-2026-000
- Scoring
- Severity band
- Direction
- High is bad
- Singleton
- No
- Basis
- ISO 45001 cl.8.1.4
- Links
- Links Vendor, Worker; feeds CAPA
- Tags
- Contractor, Performance
- Sections
- 5
- Fields
- 49
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 5
Header
14 fieldsViolation ID*
Auto sequence. Format CSV-2026-000.
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
Contractor*
Vendor ID*
Format VEN-0000.
Links to FDN-005 Vendor ID
Area
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Consistent Every Time
Contractors watch how you respond. Letting something pass once makes the rule optional for everybody, and the next enforcement looks arbitrary.
Observed By*
Time Observed*
Work Package
The violation
6 fieldsViolation Type*
Severity*
Minor, serious, or critical where somebody could have been killed.
- Minor3 pts
- Moderate1 pt
- Serious0 pts
Description*
Photograph
Workers Involved
Supervisor Aware*
A supervisor watching a violation happen is a much bigger problem than a worker acting alone.
- No2 pts
- Yes, and allowed it0 pts
Immediate response
6 fieldsWork Stopped*
- Not required3 pts
- Yes2 pts
- No0 pts
Time Stopped
Made Safe Immediately*
- Yes3 pts
- Delayed1 pt
- No0 pts
Contractor Supervisor Informed*
- Yes3 pts
- No0 pts
Contract Owner Informed*
- Yes3 pts
- No0 pts
Workers Removed From Site
Why it happened
6 fieldsCause*
Unaware of the rule, equipment not available, time pressure, deliberate shortcut, or the rule was impractical.
Was The Safe Way Available*
If we did not provide what they needed, the violation is partly ours.
- Yes1 pt
- Partly1 pt
- No0 pts
Our Contribution
Induction Covered This*
- Yes1 pt
- Partly1 pt
- No0 pts
Method Statement Covered This*
- Yes1 pt
- Partly1 pt
- No0 pts
Repeat Of Previous Violation*
- No3 pts
- Yes0 pts
Consequence
17 fieldsAction Taken*
Verbal warning, written warning, individual removed, work suspended, or contractor suspended.
Consistent With Policy*
- Yes3 pts
- Partly1 pt
- No0 pts
Suspension Record ID
Links to CON-035 Record ID
Corrective Action Required From Contractor*
Response Received
- Yes3 pts
- Late1 pt
- No0 pts
Response Adequate
- Yes3 pts
- Partly1 pt
- No0 pts
Verified Before Restart*
- Yes3 pts
- No0 pts
Feeds Scorecard*
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
Observed By*
Signature*
Contract Owner*
Second Signature*
CON-015 · record IDs look like CSV-2026-000 · Links Vendor, Worker; feeds CAPA
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the easy part. Keeping it current, catching the repeat, and holding the evidence together across sites is the work that actually slips.
Checks a new violation against the contractor's prior record across every site, not just the one it was raised on, and routes the consequence along the defined escalation path.
Connects an induction or method statement gap surfaced by a violation to the training record it should have prevented, so the same crew is not re-exposed to the same rule unbriefed.
Watches for a corrective action closed without verification before restart, and holds the write for approval before the record is marked complete.
This template lives in KnowContractor — contractor management. Prequalification, approval, induction, permits and performance.
Meet KnowContractor→Glossary
Contractor Safety Violation Record definitions and key terms
- Violation
- A confirmed breach of a stated safety rule or procedure by a contractor, independent of whether harm resulted.
- Escalation path
- The defined sequence a repeated violation follows, typically from coaching or warning through to work suspension or contractor removal.
- Make safe
- The immediate action taken to remove the hazard or stop the unsafe condition at the point the violation is observed, distinct from any later corrective action.
- Contract owner
- The person responsible for the contractor relationship, who completes the assessment of cause and consequence once a violation has been raised.
- Corrective action
- The action taken to prevent recurrence of the violation, verified for effectiveness before the work it applies to resumes.
FAQ
Frequently asked questions about contractor safety violation record
What is a contractor safety violation record?+
It is a record of a confirmed breach of your safety rules by a contractor's worker, supervisor or crew, raised by whoever observed it and completed by the contract owner. It is built against ISO 45001 clause 8.1.4 and sits within the Contractor Onboarding and Management programme.
Does a violation need to have caused harm?+
No. A violation is a breach of a rule or procedure, and it stands regardless of outcome. An event where harm nearly occurred but no rule was necessarily broken is a near miss, and one where harm actually resulted is an incident; both are separate records.
What happens if the same contractor violates the same rule twice?+
The second violation should be checked against the first at the point it is raised, and the consequence should follow the defined escalation path rather than restarting at the same level. Recording repeat violation as its own field is what makes that check possible without relying on memory.
Who decides the consequence?+
The contract owner, working from the violation as recorded, the contractor's prior history, and whether the site's own contribution, an unavailable safe method or an impractical rule, played a part. The action should also be checked against what policy sets out for that class of breach.
Should the record close once a warning is issued?+
Only once any corrective action required from the contractor has been received, judged adequate, and verified before work restarts. A record closed on the warning alone, without that verification, has documented an intention rather than a confirmed outcome.
How does this connect to the contractor's ongoing standing?+
Every violation record is designed to feed the contractor's performance scorecard, so that a pattern across sites and time is visible at the point the contractor comes up for renewal or a new award, rather than being buried in individual files nobody cross-references.
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 Performance
Contractor Performance Scorecard
Scores a contractor on safety, quality, schedule and cooperation over a period
Contractor Incident Record
Records an incident involving a contractor worker on your site
Contractor Toolbox Talk Record
Records safety talks the contractor delivers to their own crew on your site
Contractor Work Completion Record
Confirms contractor work is finished, the area is clean and safe, and any permits are closed
Contractor Review Meeting Record
Records a periodic review meeting with a contractor covering performance, issues and improvements
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 8.1.4, 8.1.2, 7.3 and 10.2
- Health and Safety at Work etc. Act 1974, section 3 (UK)
- OSHA multi-employer worksite policy and the General Duty Clause (US)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.