What this is
What is an emergency contractor engagement record?
What is an emergency contractor engagement record?
A record documenting a contractor brought onto site outside normal prequalification and approval because a genuine emergency made waiting unsafe. It captures why the route was justified, which minimum checks were done, and what controls, chiefly escort, stood in for the checks that were not.
When should the emergency route be used instead of normal approval?
When there is genuine risk to people, product or plant that cannot wait for prequalification, and no approved contractor can meet it in time. A deadline or contractor preference is not an emergency, and the genuine-emergency question exists to catch exactly that.
What happens after the emergency work is done?
The record does not close on the signature. It asks whether work was completed safely, whether full prequalification has started, whether access was removed, whether root cause was addressed, and whether the incident exposes an approved-list gap.
Scope
When is an emergency contractor engagement record required?
This record covers one specific situation: a contractor engaged outside the normal route because normal timing was not available. It is not a faster version of the standard approval record, and using it that way defeats the controls it exists to enforce.
Use this template when
- A genuine emergency, risk to people, product or the plant, requires a contractor on site before prequalification or approval can be completed
- No approved contractor is available to respond in the time the emergency allows
- The engagement needs authorising and evidencing at the moment it happens, not reconstructed the next day
- The minimum checks, identity, insurance and competency, need a record of what was verified before work started
- A full prequalification needs triggering as a follow-up to a contractor used under emergency access
Do not use it for
- Contractor Approval Record, the normal route, to be used whenever there is time
- Contractor Onboarding Checklist, the full onboarding this record hands off to once the emergency has passed
- Service Level Agreement Record, which holds response times and standards agreed with a contractor, not a single engagement
- Contractor Rate and Invoice Verification, which checks invoices against rates rather than whether the engagement was justified
- A contractor engagement that is inconvenient rather than urgent, which belongs in the normal approval route regardless of framing
Compliance mapping
Which ISO 45001 cl.8.1 requirements does this satisfy?
ISO 45001's contractor requirements do not disappear because the route was compressed. What changes under emergency access is which controls carry the weight, and this record shows that shift was deliberate.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 45001 cl.5.3 | Roles, responsibilities and authorities defined, so the engagement is authorised by someone who holds that authority | Header |
| ISO 45001 cl.6.1.2.2 | Risk evaluated at the point of decision, distinguishing genuine risk to people, product or plant from schedule pressure | Justification |
| ISO 45001 cl.8.1.4.2 | Contractor arrangements controlled, including the criteria under which a non-approved contractor may be used | Justification |
| ISO 45001 cl.8.1.4.2 | Minimum contractor checks, identity, insurance and competency, applied even where the normal route was unavailable | Minimum checks completed |
| ISO 45001 cl.8.1.1 | Operational controls, escort, scope limits, permit and isolation supervision, substituted for the checks the route skipped | Minimum checks completed |
| ISO 45001 cl.7.5.3 | Documented information linked forward, connecting this record to the onboarding checklist it triggers | Related records |
| ISO 45001 cl.10.2 | Root cause of the condition that created the emergency addressed, not just the immediate work signed off | Afterwards |
| ISO 45001 cl.9.1.1 | Repeated gaps in the approved contractor list monitored and fed back into procurement rather than absorbed as routine | Afterwards |
What it does not cover
- Contractor Approval Record, the normal route, which should be used whenever time allows rather than this one as a faster substitute.
- Contractor Onboarding Checklist, which tracks the full onboarding this record's follow-up triggers, and which it does not replace.
- Service Level Agreement Record, which holds ongoing response times and standards agreed with a contractor, not a single call-out.
- Contractor Rate and Invoice Verification, which checks what was billed against what was agreed, assuming the engagement was already justified.
- A convenience engagement, where the preferred contractor was used because the approved one was slower or costlier, a normal-route decision wearing the emergency form.
Global
Emergency Contractor Engagement Record requirements by country
The duty to control who a contractor is does not relax because the engagement was urgent. What differs by jurisdiction is who carries that duty on a shared site and how explicitly contractor vetting is named in law.
OSH Act General Duty Clause; multi-employer worksite doctrine
A host employer can be cited for hazards it created or controlled even where a contractor's own employer bears the direct duty to its workers.
Bringing an unvetted contractor on site under emergency access does not transfer the host's exposure; it is still the host's recognised hazard.
Health and Safety at Work etc. Act 1974, s.3; CDM 2015 where construction-related
Duty extends to persons not in the employer's employment who may be affected by the undertaking, contractors included.
An emergency engagement does not suspend the section 3 duty; escort and scope limitation are how it is discharged when normal vetting could not be.
ISO 45001, clause 8.1.4.2 (Contractors)
Coordination with contractors required to identify hazards and control risks arising from their activities, before and during the work.
An auditor examining this record looks for compensating controls, not an exemption, since the clause carves out no exception for urgency.
How to complete it
How to complete an emergency contractor engagement record, step by step
The form prompts for the checks and signatures. The judgement that makes the record defensible sits in four places the form cannot enforce on its own.
Answer the genuine-emergency question honestly, against risk to people, product or plant, before recording anything downstream. If the honest answer is Partly or No, redirect to standard approval, however much time pressure exists.
Where identity, insurance or competency was assumed rather than seen, continuous escort carries that weight until evidence catches up. Escorted At All Times marked No, alongside checks marked Assumed or Partly, means no compensating control exists.
Once a contractor is on site under emergency access, it is tempting to have them look at something else. Scope Limited To The Emergency exists to stop that: work outside scope has not had the minimum checks applied.
Work Completed Safely answers whether the job went well. It says nothing about whether prequalification has started, access was removed, root cause was fixed, or the approved list has a gap. All four need an answer before the record is finished.
What auditors find
Most common emergency contractor engagement record findings
Because this record is only raised under pressure, its common defects are not missing fields but fields answered too generously, and follow-up questions answered and then never acted on.
| Finding | Clause | What fixes it |
|---|---|---|
| Genuine Emergency scored Yes for a deadline or scheduling conflict rather than a risk to people, product or plant. | ISO 45001 cl.6.1.2.2 | Reserve Yes for genuine risk; route anything else back to standard approval regardless of time pressure. |
| Approved contractor was in fact available, but the emergency route was used anyway with no reason recorded. | ISO 45001 cl.8.1.4.2 | Complete 'Why an approved contractor was not used' before sign-off; leave it blank and block approval. |
| Identity, insurance or competency marked Assumed or Partly with no escort in place to compensate. | ISO 45001 cl.8.1.1 | Treat continuous escort as mandatory whenever any minimum check is incomplete, not optional good practice. |
| Full prequalification never started, or started and never tracked to completion, after the emergency closed. | ISO 45001 cl.8.1.4.2 | Record days to complete prequalification as a live figure and escalate it if it stalls. |
| Approved Contractor Gap Identified marked Yes repeatedly for the same trade, with no change made to the approved list. | ISO 45001 cl.9.1.1 | Route a repeated gap to the approved list and prequalification programme as its own action, not another emergency record. |
| Action Required marked Yes with no CAPA ID or owner ever entered against it. | ISO 45001 cl.10.2 | Raise the CAPA record when the action is flagged and enter its reference immediately, not later. |
Case in point
Case in point: the emergency that was handled correctly and then forgotten
A cold store's refrigeration plant failed at two in the morning. Both approved refrigeration contractors were unreachable, so the duty manager called one who was not on the list. The record was raised at the time: genuine emergency scored Yes against product risk, identity and insurance partly seen, the contractor escorted throughout, scope limited to the fault, and work completed safely by morning.
Six months later the same plant failed again, at the same time of night, with the same two contractors unreachable, and a third record was raised for a different unapproved contractor. Full Prequalification Started had been marked Yes the first time but never followed through, and Approved Contractor Gap Identified had been marked Yes twice with no change to the list. What never happened was fixing why a third approved contractor was needed.
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-041
- Archetype
- Record
- Record ID
- ECE-2026-000
- Scoring
- Retrospective approvals
- Direction
- Low is good
- Singleton
- Yes
- Basis
- ISO 45001 cl.8.1
- Links
- Links Approved list, Prequalification
- Tags
- Contractor, Emergency
- Sections
- 5
- Fields
- 39
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 4
Header
12 fieldsRecord ID*
Auto sequence. Format ECE-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
Emergencies Happen, Pretending Otherwise Means No Record
A refrigeration failure at two in the morning will bring somebody through the gate. Define the minimum checks now so the shortcut is a controlled one.
Nature Of The Emergency*
Time Contractor Called*
Authorised By*
Justification
3 fieldsGenuine Emergency*
Risk to people, product or the plant. A deadline is not an emergency.
- Yes3 pts
- Partly1 pt
- No0 pts
Approved Contractor Available*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Why An Approved Contractor Was Not Used
Minimum checks completed
9 fieldsIdentity Verified*
- Yes3 pts
- Assumed0 pts
Insurance Evidence Seen*
- Yes3 pts
- Partly1 pt
- No0 pts
Competency Evidence Seen*
- Yes3 pts
- Partly1 pt
- No0 pts
Short Form Induction Delivered*
- Yes3 pts
- Partly1 pt
- No0 pts
Escorted At All Times*
Escort is what substitutes for the checks you could not do.
- Yes3 pts
- Partly1 pt
- No0 pts
Scope Limited To The Emergency*
- Yes3 pts
- Partly1 pt
- No0 pts
Permit Issued Where Required*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Isolation Supervised By Us*
- Yes3 pts
- Partly1 pt
- No0 pts
Food Safety Controls Applied*
- Yes3 pts
- Partly1 pt
- No0 pts
Related records
1 fieldOnboarding Checklist ID
The full onboarding started after the emergency.
Links to CON-040 Checklist ID
Afterwards
14 fieldsWork Completed Safely*
- Yes3 pts
- With issues1 pt
- No0 pts
Full Prequalification Started*
- Yes3 pts
- Partly1 pt
- No0 pts
Days To Complete Prequalification
Access Removed After The Job*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Root Cause Of The Emergency Addressed*
- Yes3 pts
- Partly1 pt
- No0 pts
Approved Contractor Gap Identified*
Repeated emergency engagements mean the approved list has a hole in it.
- Yes3 pts
- Partly1 pt
- No0 pts
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
Site Manager*
Signature*
Contract Owner*
Second Signature*
CON-041 · record IDs look like ECE-2026-000 · Links Approved list, Prequalification
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
Raising the record correctly under pressure is the easy half. Protecting the approved list is the follow-up nobody has time for once the emergency has passed.
Holds the emergency record against the approved contractor list and prequalification programme, flagging when Full Prequalification Started has stalled beyond a stated number of days.
Tracks permit, isolation and food safety fields raised under emergency access and confirms they closed out with the same rigour as a normal-route engagement.
Picks up competency evidence marked Partly or Assumed and turns it into a verification task, so the gap identified under pressure gets closed.

Watches for repeated Approved Contractor Gap Identified answers on the same trade or site and raises it as a procurement action.
This template lives in KnowContractor — contractor management. Prequalification, approval, induction, permits and performance.
Meet KnowContractor→Glossary
Emergency Contractor Engagement Record definitions and key terms
- Genuine emergency
- A risk to people, product or plant that cannot wait for the normal prequalification and approval route, distinct from a deadline, cost preference or scheduling conflict.
- Approved contractor
- A contractor who has completed prequalification and sits on the approved list, whose unavailability is what this record justifies working around.
- Escort
- Continuous supervision of a contractor on site, used here as the compensating control for identity, insurance or competency checks the emergency route could not complete.
- Retrospective approval
- Approval granted after the fact for an engagement already started, tracked here as a count, since a low count means the approved list is meeting demand.
- Root cause
- The underlying condition that produced the emergency, such as a plant fault or a gap in the approved list, addressed separately from the immediate repair.
FAQ
Frequently asked questions about emergency contractor engagement record
How is 'genuine emergency' different from an urgent job?+
An urgent job is one where waiting is inconvenient or costly. A genuine emergency is one where waiting would itself create risk to people, product or plant. A merely urgent engagement should go through standard approval instead.
What if none of the minimum checks could be completed before the contractor started?+
Escort becomes the primary control. Where identity, insurance and competency evidence was unavailable, continuous escort for the work's duration is what makes the engagement defensible rather than undocumented.
Does this record replace the normal contractor approval process?+
No. It documents a justified departure from that process for one engagement, and Afterwards routes the contractor into full prequalification once the emergency has passed.
Why does the record ask whether an approved contractor was available?+
Because if one was available and not used, the emergency justification does not hold. That question, and the reason recorded when the answer is No, stops the route becoming a way to prefer an unapproved contractor.
What does 'low is good' mean for a record raised in response to an actual event?+
The record itself is neutral; a genuine emergency is not a failure. Low-is-good tracks the count over time. A rising count for the same site or trade indicates a gap the approved list should be closing.
What happens if the same gap in the approved list keeps recurring?+
Approved Contractor Gap Identified exists to catch this. A repeated Yes with no list change means the same unresolved gap is documented each time, and the fix belongs in procurement, not another emergency engagement.
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 Commercial
Contractor Onboarding Checklist
Tracks every step from first contact to first day on site, so nothing is missed under time pressure
Service Level Agreement Record
Holds the response times, availability and performance standards agreed with a contractor
Contractor Rate and Invoice Verification
Verifies contractor invoices against agreed rates, hours recorded on site and work actually completed

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 clause 8.1 — Operational planning and control
- ISO 45001:2018 clause 8.1.4.2 — Contractors
- ISO 45001:2018 clause 6.1.2 — Hazard identification and assessment of risk
- Health and Safety at Work etc. Act 1974, section 3 (UK duty to non-employees)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.