What this is
What is an escalation record?
What is an escalation record?
It is a standalone engine that captures the act of raising an issue to a higher level of authority, separately from the record that stalled. It names the original owner, the reason escalation was needed, who it went to, and whether that produced a decision. It exists so escalation has the same evidential weight as the action it followed from, rather than being an informal conversation nobody can point to later.
What counts as a systemic pattern in an escalation record?
It is the finding that this is not the first time the same owner, or the same type of blocker, has needed escalating. One overdue action is an individual lapse; the same blocker recurring across several escalations points at a resourcing or process gap that the individual owner cannot fix on their own.
How does an escalation record differ from a CAPA?
A CAPA record fixes a cause once it has been identified and tracks the corrective action to closure. An escalation record only documents that something was raised upward because it stalled or needed a decision above the current owner — it may result in a CAPA being opened, but it is not itself the action record.
Scope
When is an escalation record required?
This engine documents that something was raised upward, not the underlying decision or the corrective work that follows. Using it to record the fix itself, rather than the act of escalating, buries the chase inside a template that was never built to hold it.
Use this template when
- An action, decision or response is overdue and informal chasing has not moved it
- A decision genuinely sits above the current owner's authority and needs a more senior call
- You need evidence that an issue was raised formally, not just discussed
- A linked record — a CAPA, a Finding, an Action — has stalled and needs its escalation history captured
- The same owner or blocker keeps recurring across escalations and the pattern itself needs surfacing
Do not use it for
- Approval Workflow Record, which sequences planned sign-offs rather than routing something that has stalled or gone overdue.
- Corrective and Preventive Action, which is the action record itself; escalating its delay belongs here, not inside it.
- Root Cause Analysis, which finds out why something happened rather than documenting who it was raised to.
- Risk Assessment, which is the single risk assessment used across the whole business, not a routing mechanism.
- Anything outside General, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 45001 cl.7.4 requirements does this satisfy?
ISO 45001's communication clause anchors the record, but the fields it captures — authority, response time, systemic pattern — draw on how the standard expects issues to be raised and acted on internally.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 45001 cl.7.4.2 | Internal communication must ensure relevant information reaches the right level of the organisation | Escalation |
| ISO 45001 cl.5.3 | Authority to make the decision an escalation seeks must sit with a defined role | Escalation |
| ISO 45001 cl.9.1.1 | Performance of key processes, including response time to raised issues, must be monitored | Escalation |
| ISO 45001 cl.10.2 | Where an escalation reveals a recurring cause, corrective action must be raised and tracked | Escalation |
| ISO 45001 cl.6.1 | Increased risk identified during an escalation must feed back into risk evaluation | Position |
| ISO 45001 cl.7.5.3 | The escalation, once raised, must be retrievable and traceable to the record it originated from | Header |
What it does not cover
- Escalated In Writing marked Verbal only or No, which leaves the escalation as an undocumented conversation rather than evidence.
- Response Received marked No with the record left open indefinitely, which means the escalation stalled a second time with nothing forcing it further.
- Systemic Pattern Identified marked Yes with Action Required marked No, which acknowledges a recurring problem and then does nothing about it.
- Item Resolved marked Partly with Further Escalation Needed marked No, which closes a partial outcome as if it were complete.
- Resource Released marked Yes with no New Owner Assigned or New Due Date recorded, which frees up the blocker without actually re-establishing who owns the work.
Global
Escalation Record requirements by country
ISO 45001 sets the communication expectation everywhere it is certified, but three regimes shape how formally a safety-related escalation needs to be evidenced.
ISO 45001:2018 cl.7.4.2 and cl.5.3
Certification bodies expect evidence that hazards and stalled actions reach a level of the organisation with authority to act, not just that they were mentioned somewhere.
An auditor will ask for the escalation trail on a sampled overdue action, not just the closed-out final status.
OSHA General Duty Clause (29 U.S.C. §654) and 29 CFR 1904 recordkeeping
An employer that becomes aware of a hazard through an internal escalation and fails to act on it can be judged to have had actual knowledge for enforcement purposes.
A written escalation record with no resolution can become the evidence used against the employer, not for them, if the hazard later causes harm.
Health and Safety at Work etc. Act 1974, s.2 and s.7
Duty holders must ensure information about risk is communicated up the management chain and acted on; individual workers have a parallel duty to report.
HSE inspectors reviewing an incident routinely ask whether the hazard had been escalated beforehand and what happened to that escalation.
How to complete it
How to complete an escalation record, step by step
The fields are straightforward to fill in. Judging whether the escalation actually worked, rather than just happened, takes four calls.
Days Overdue is a number, not a verdict. A one-day slip on a low-risk item does not need the same escalation weight as a week-long slip on something feeding a high-risk activity — Risk If Not Resolved should shape the decision to escalate, not just the clock.
Level offers department manager through to board. Escalating too low wastes the record's purpose; escalating too high for a routine delay burns credibility for the next genuinely serious one. The honest test is whether the person named actually has authority to remove the blocker.
Marking Systemic Pattern Identified Yes is easy; deciding it deserves a CAPA rather than just an acknowledgement is the real call. If the same owner or blocker has appeared before, treat this as a resourcing finding and raise the action, not just the flag.
Resource Released and New Owner Assigned can look like resolution while the underlying blocker — budget, conflicting priority, unclear ownership — is still unaddressed. Item Resolved should reflect whether the blocker itself is gone, not just whether the paperwork moved on.
What auditors find
Most common escalation record findings
The same recurring gaps show up when escalation records are checked against the timeline of the item they were meant to unblock.
| Finding | Clause | What fixes it |
|---|---|---|
| Escalation raised weeks after the item first became overdue, with no record of informal chasing in between | ISO 45001 cl.7.4.2 | Require Previously Chased to be answered honestly and set an expectation for how many informal chases precede a formal escalation. |
| Escalated In Writing marked Yes with no corresponding written trail attached or referenced anywhere | ISO 45001 cl.7.5.3 | Require a reference — an email thread, a message log, a minute — before the written answer is accepted. |
| Days To Response left blank on escalations that clearly took weeks to answer | ISO 45001 cl.9.1.1 | Calculate the field automatically from Date and Time to the date Response Received was recorded. |
| Systemic Pattern Identified marked No despite three prior escalations against the same owner in the same quarter | ISO 45001 cl.10.2 | Surface prior escalations against the same Original Owner or Blocker at the point this field is answered, rather than relying on memory. |
| Further Escalation Needed marked No while Item Resolved is still Partly | ISO 45001 cl.7.4.2 | Block this combination and require either full resolution or a further escalation before the record can close. |
| Action Required marked Yes with no CAPA ID entered weeks after the escalation closed | ISO 45001 cl.10.2 | Keep the record open, or flag it for follow-up, until a CAPA ID is entered whenever Action Required is Yes. |
Case in point
Case in point: the blocker that outlived three escalations
A maintenance action kept slipping because the parts budget for that site had been frozen. It was escalated to the department manager, resolved on paper by extending the due date, and slipped again a month later. It was escalated a second time, resolved the same way, and slipped a third time.
Each individual escalation record looked complete — a level, a response, a new due date. What none of them asked was whether this was the same blocker as before. Once the records were reviewed together and Systemic Pattern Identified was answered honestly, the issue went to the board as a budget decision instead of being re-escalated to the same manager a fourth time.
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
- FDN-029
- Archetype
- Engine
- Record ID
- ESC-2026-000
- Scoring
- Escalations closed
- Direction
- High is good
- Singleton
- No
- Basis
- ISO 45001 cl.7.4
- Links
- Used by CAPA, Findings, Actions
- Tags
- Engine, Escalation
- Sections
- 4
- Fields
- 38
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 2
Header
10 fieldsEscalation ID*
Auto sequence. Format ESC-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
Make The Chase Visible
An overdue action chased three times in a corridor leaves no record. Escalating it formally does, and that is usually what makes it move.
Item Escalated*
Source Record ID*
Immediate predecessor record
Escalation Trigger*
Position
7 fieldsOriginal Owner*
Original Due Date*
Days Overdue*
Risk If Not Resolved*
- Low3 pts
- Medium1 pt
- High0 pts
Previously Chased*
- No2 pts
- Once1 pt
- More than once0 pts
Blocker*
Blocker Detail
Related records
1 fieldStalled Action ID
The action that stalled.
Links to FDN-014 CAPA ID
Escalation
20 fieldsEscalated To*
Level*
Escalated In Writing*
- Yes3 pts
- Verbal only1 pt
- No0 pts
Response Received*
- Yes3 pts
- Late1 pt
- No0 pts
Days To Response
Decision Made*
- Yes3 pts
- Deferred1 pt
- No0 pts
Resource Released*
- Yes3 pts
- Partly1 pt
- No0 pts
New Owner Assigned
New Due Date
Item Resolved*
- Yes3 pts
- Partly1 pt
- No0 pts
Further Escalation Needed*
- No3 pts
- Yes0 pts
Systemic Pattern Identified*
Repeated escalation on the same owner or the same blocker is a resourcing problem, not an individual one.
- No3 pts
- Yes0 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
Raised By*
Signature*
Escalated To 2*
Second Signature*
FDN-029 · record IDs look like ESC-2026-000 · Used by CAPA, Findings, Actions
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 the escalation moving, chasing the right level and holding the evidence together is the work that actually slips.
Watches open escalations against their Days Overdue and Days To Response, and nudges the next level when a response has gone quiet.
Ties escalations back to the hazard or risk that triggered them, so a repeated blocker shows up against the site's risk register, not just this one record.
Rolls systemic pattern findings into the wider governance picture, so a recurring owner or blocker surfaces at portfolio level before it needs a fourth escalation.
Flags escalations still open past their expected response window, and links resolved items back to whichever CAPA or action they generated.
This template lives in General — control tower. The orchestration layer. Registries and engines every other workspace reads from.
Meet General→Glossary
Escalation Record definitions and key terms
- Escalation trigger
- The reason an item is being raised upward — an overdue action, a decision above the owner's authority, a blocked resource, increased risk, or a repeated failure.
- Systemic pattern
- A finding that the same owner, blocker, or type of failure has required escalation more than once, pointing to a resourcing or process gap rather than an individual lapse.
- Resource release
- Confirmation that whatever was blocking the original owner — budget, people, priority — has actually been freed up, not just acknowledged.
- Days to response
- The measured time between an escalation being raised and a response being received from the level it was escalated to.
- Escalation level
- The tier of authority an issue is raised to — department manager, site manager, group, or board — chosen to match who can actually remove the blocker.
FAQ
Frequently asked questions about escalation record
Does every overdue action need a formal escalation record?+
No. Minor, low-risk slips are usually resolved through normal chasing. This engine is for cases where informal chasing has failed, the risk of leaving it is meaningful, or the decision needed sits above the current owner.
Who should raise the escalation — the original owner or someone else?+
Raised By can be the original owner or whoever noticed the stall, but it should not be the same person as Escalated To. The point is to move the decision to someone with more authority, not to have the same person re-approve their own delay.
What happens if the person escalated to does not respond?+
Response Received should be marked No and the record should not close. Further Escalation Needed exists precisely for this case — the issue moves to the next level rather than sitting unresolved at the first one.
Can an escalation record exist without a linked stalled action?+
It can — Escalation Trigger includes Decision above owner and Risk increased, which do not always originate from an overdue action. The Related records link to a stalled action is optional for that reason.
Does resolving the immediate issue close out the systemic pattern too?+
No. Item Resolved reflects the individual escalation. Systemic Pattern Identified should be answered on its own merits and, if Yes, should lead to action that outlives this one record.
Why are there two signatures on this record?+
The first signature is the person raising the escalation; the second belongs to the person it was escalated to, confirming the response and decision were actually theirs and not entered on their behalf.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Master Data and Foundations
Site and Location Register
Holds every site, building, area and zone your organisation operates
Asset Register
Holds every piece of equipment, machine, vehicle and tool you track
Worker Profile
Holds a record for each worker, including role, department, site and start date
Job and Task Register
Lists the jobs and tasks people perform, so risk assessments and ergonomic assessments can be tied to real work rather than job titles
Vendor and Contractor Register
Holds every supplier, contractor and service provider you work with, including their status and approval level
Chemical and Substance Register
Lists every chemical and hazardous substance held on site, with quantity, location and hazard class
More in Engines
Risk Assessment
The single risk assessment used across the whole business
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
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.7.4.2 — Internal communication
- ISO 45001:2018 cl.5.3 — Roles, responsibilities and authorities
- ISO 45001:2018 cl.10.2 — Incident, nonconformity and corrective action
- OSHA General Duty Clause, 29 U.S.C. §654
- Health and Safety at Work etc. Act 1974, s.2 and s.7
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.