What this is
What is an escalation and andon log?
What is an escalation and andon log?
It is a running record of every call for help raised from the floor: what triggered it, who responded, how long that took, and whether it was resolved on the spot. It is built against ISO 9001 cl.8.5 and sits within the Shift Management programme, linking the Downtime Log and Shift Handover.
What counts as 'response time', and why does the form score it rather than the outcome?
Response Minutes is the gap between Time Raised and Time Responded, scored because it can be trended shift over shift regardless of what the call turned out to be. Whether the call was resolved gets its own separate field; conflating the two would hide a system that answers slowly but happens to fix things well.
Why does Escalation Level exist alongside Trigger, aren't they the same thing?
Trigger says what kind of problem it was, quality, equipment, materials, safety, people or process. Escalation Level says how far up the tier structure it needed to go. The same trigger can sit at any level depending on whether the floor resolved it or it needed a manager, so collapsing them into one field would lose the escalation path entirely.
Scope
When is an escalation and andon log required?
This log is one step in a larger programme. Using it for work that belongs to a neighbour produces records hard to report on later.
Use this template when
- A line has stopped, or someone on the floor has called for help, and the response needs timing as it happens
- The workspace is being set up, or the register needs an entry added or retired
- You are running the Shift Management programme and this log is one of its steps
- A linked record needs this one to exist: it links the Downtime Log and Shift Handover
- A call is a repeat of one raised earlier in the shift and the pattern needs to be traceable, not just logged again
Do not use it for
- Operations Shift Handover, which passes the state of the operation from one shift to the next, not the timing of a single call for help
- Shift Start Up Check, which confirms the area, the people and the equipment are ready before the shift starts producing
- Manning and Labour Plan, which sets who is working where for a shift, against the competencies each position requires
- Shift Performance Log, which records planned output against actual hour by hour, not a single escalation and its response
- Anything outside KnowOps, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 9001 cl.8.5 requirements does this satisfy?
ISO 9001 cl.8.5 covers control of production; an andon call is that control breaking down in real time, and the log is the evidence of how the organisation responded.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.8.5.1 | Control production under monitored conditions, verifying criteria are met at each stage rather than assuming they are | Escalations |
| ISO 9001 cl.9.1.1 | Monitor a process characteristic, here response time, at a frequency that shows whether it is improving | Escalations |
| ISO 9001 cl.10.2 | React to a nonconformity, evaluate the need for action against its cause, and raise a corrective action where warranted | Shift summary |
| ISO 9001 cl.9.1.3 | Analyse and evaluate monitoring results, including trends by cause across a shift | Shift summary |
| ISO 9001 cl.7.5.1 | Retain documented information as evidence of conformity, identifiable and retrievable by its own key | Header |
| ISO 9001 cl.5.3 | Assign and communicate responsibility for reporting and for corrective action ownership | Shift summary |
| ISO 9001 cl.4.4 | Determine how this process's outputs feed the other processes that depend on it | Related records |
What it does not cover
- Time Raised and Time Responded entered together at end of shift, which manufactures a Response Minutes figure nobody can defend against the actual call.
- Repeat Of An Earlier Call marked No without checking the shift's own escalation list, which hides the same fault being called in and answered three times.
- Escalation Level set to Level 1 on a call where Line Stopped is Yes, which understates a stopped line against the tier structure the level is meant to drive.
- Dominant Trigger entered without a Repeat Calls count to support it, which leaves the summary's headline cause unverifiable against the entries beneath it.
- Work Order ID left blank on an equipment-triggered call, which breaks the link back to the maintenance record the escalation should have raised.
Global
Escalation and Andon Log requirements by country
ISO 9001 cl.8.5 sets a general duty to control production; when the trigger is Safety, other instruments engage on top of it, tied to the same timestamps this log captures.
ISO 9001:2015
Clause 8.5.1 requires production controlled under monitored conditions, verified at appropriate stages rather than assumed.
An andon log with no measured response time doesn't demonstrate the control the clause asks for, whatever the site's actual response speed happens to be.
RIDDOR 2013
The reporting clock for a reportable injury or dangerous occurrence starts from the actual event, not from whenever the record gets written up.
When Trigger is Safety and the call escalates into an injury, a backdated Time Raised understates how long the real reporting window has already been running.
OSHA 29 CFR 1904
Recordkeeping requires an incident logged within a set window of the employer becoming aware of it, not of it being written down.
A reconstructed Time Raised can no longer prove when the employer's knowledge, and the clock, actually started.
How to complete it
How to complete an escalation and andon log, step by step
Filling in the fields is easy. What decides whether the log is defensible later is judgement the form itself can't enforce.
Time Raised should be the moment the floor actually called for help, not the moment the responder got to a screen. A log entered fifteen minutes after the fact with a plausible earlier timestamp typed in looks identical to one entered live, and only the responder knows which it was.
Escalation Level is a judgement call tied to Trigger and Line Stopped, not a free choice. A stopped line, a safety trigger, or a call that needed a manager rather than a peer all argue for a higher level, and downgrading one in hindsight because it resolved quickly loses the signal the level exists to give.
Resolved At The Point Of Call answered Yes on an equipment-triggered call doesn't mean the underlying fault is fixed, only that the line restarted. Whether a Work Order ID still gets raised is the difference between a symptom answered and a cause addressed.
Repeat Of An Earlier Call being Yes still means a new row, linked by Case ID to the original, not an edit to the earlier entry. Overwriting the first call to reflect the second erases the very pattern the field is designed to surface.
What auditors find
Most common escalation and andon log findings
Findings against this log are rarely a missing field. They are timestamps that don't reconcile, or a summary answering questions the entries never raised.
| Finding | Clause | What fixes it |
|---|---|---|
| Response Minutes is typed rather than derived from Time Raised and Time Responded. | ISO 9001 cl.9.1.1 | Calculate Response Minutes from the two timestamps automatically rather than accepting a typed figure. |
| Escalation Level and Line Stopped disagree, a Level 1 entry against Line Stopped = Yes. | ISO 9001 cl.8.5.1 | Add a validation rule that a stopped line cannot be logged below Level 2. |
| Repeat Of An Earlier Call is answered Yes with no Case ID linking the two entries. | ISO 9001 cl.10.2 | Require Case ID whenever Repeat Of An Earlier Call is Yes, so the repeat is traceable to the original. |
| Work Order ID is blank against Trigger = Equipment and Resolved At The Point Of Call = No. | ISO 9001 cl.4.4 | Make Work Order ID required whenever an equipment-triggered call isn't resolved on the spot. |
| Dominant Trigger in the shift summary doesn't match the most frequent Trigger among that shift's own escalations. | ISO 9001 cl.9.1.3 | Derive Dominant Trigger from the entries rather than accepting a typed selection. |
| Second Signature or Area Manager is missing on a closed log with Action Required = Yes. | ISO 9001 cl.5.3 | Block Status = Closed until the Area Manager signature is present whenever an action has been raised. |
Case in point
Case in point: the andon call answered in two minutes, three times over
A filling line called for help three times in one shift, each time for the same intermittent valve fault. Each call was logged as Level 1, Trigger Equipment, Resolved At The Point Of Call Yes, Response Minutes a consistent two, and Repeat Of An Earlier Call answered No each time because the responder checking the box hadn't seen the earlier entries. Individually, every row was defensible.
The valve failed completely on the next shift, stopping the line for four hours. The maintenance investigation afterward found the andon log, correctly filled in three separate times, had recorded the exact pattern that would have flagged the fault days earlier, if anything had linked the three calls together. The fix wasn't a new field; Repeat Of An Earlier Call already existed. It was making the responder check the shift's own list before answering it.
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
- OPS-006
- Archetype
- Log
- Record ID
- AND-2026-000
- Scoring
- Response time
- Direction
- High is good
- Singleton
- Yes
- Basis
- ISO 9001 cl.8.5
- Links
- Links Downtime Log and Shift Handover
- Tags
- Shift, Escalation, Andon
- Sections
- 4
- Fields
- 40
- Follow up fields
- 3
- Repeating sections
- 1
- Links out
- 4
Header
10 fieldsLog ID*
Auto sequence. Format AND-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*
Shift*
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.
Judged Entirely On Response Time
An escalation system that takes eleven minutes to answer is a system people stop using. Nobody measures response time from a light on a pole.
Escalations
Repeats15 fieldsTime Raised*
Raised By*
Trigger*
Quality, equipment, materials, safety, people, or process.
Line Stopped*
Escalation Level*
Description*
Responder
Time Responded
Response Minutes
Resolved At The Point Of Call*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Time Resolved
Escalated Further
Repeat Of An Earlier Call*
The same call three times in a shift is a problem nobody fixed, only answered.
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Work Order ID
Links to MNT-002 Work Order ID
Case ID
Thread key
Related records
1 fieldDowntime Log ID
The stop this escalation relates to.
Links to OPS-010 Log ID
Shift summary
14 fieldsEscalations Raised*
Average Response Minutes*
Calls Unanswered*
Repeat Calls*
Dominant Trigger*
Feeds Tier Board Review*
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
Shift Lead*
Signature*
Area Manager*
Second Signature*
OPS-006 · record IDs look like AND-2026-000 · Links Downtime Log and Shift Handover
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 clock honest, catching the repeat call nobody flagged, and holding the evidence together is the work that actually slips.
Holds the escalation log against the Downtime Log and Shift Handover it links, and flags an entry with no Time Responded left open past shift end.
Checks an Equipment-triggered call against open work orders and flags a Case ID pattern before the fault it hides fails completely.
Watches for a Safety trigger and confirms the incident record and reporting clock line up with what this log actually timestamps.
Rolls response time and open escalations into one view across the shift, and holds every write for approval before it touches a record.
This template lives in KnowOps — frontline execution. Shift handover, production control, daily management, worker lifecycle and improvement.
Meet KnowOps→Glossary
Escalation and Andon Log definitions and key terms
- Andon
- A visual or physical call for help raised from the floor when a line stops or a problem needs attention, distinct from a routine escalation raised by a supervisor.
- Escalation level
- How far up the tier structure a call needed to travel, from a peer response at Level 1 to a manager-level response at Level 3, independent of what triggered it.
- Response minutes
- The gap between Time Raised and Time Responded, the figure this log is scored on, valid only if both timestamps reflect the real event.
- Tier board review
- The structured review, typically daily, where escalation trends are examined by cause and level; this log's shift summary is what it reads from.
- Case ID
- A thread key linking a repeat call back to the original entry, so a recurring fault is traceable as one pattern rather than several unrelated rows.
FAQ
Frequently asked questions about escalation and andon log
Why does response time matter more than whether the call was resolved?+
Because a system that answers quickly but fixes things badly is a different failure to a system that answers slowly. Conflating the two into one score would hide which problem an organisation actually has, so resolution gets its own field.
Why is this a singleton if a new entry gets raised for every call?+
Singleton describes the template's setup, not the record count: the log is configured once per workspace and every call becomes a new entry against that same configuration, rather than each call requiring its own separate form.
How does this log relate to the Downtime Log and Shift Handover?+
This log times the call and response; the Downtime Log holds the detail of any stop long enough to need one, referenced back by ID, and Shift Handover carries anything still open into the next crew.
Who has to sign off a completed log?+
The Shift Lead and the Area Manager, both as a required signature. A log with every call logged but no closing signature is incomplete evidence, not a finished record with a formality outstanding.
What triggers a CAPA from this log?+
Action Required answered Yes, at which point a Priority is set and a CAPA ID entered once the corrective action record has been raised elsewhere. The log holds the reference, not the investigation itself.
Why does Trigger repeat as Dominant Trigger in the shift summary?+
Trigger is answered per call; Dominant Trigger is the shift's own headline cause, meant to be derived from the individual entries rather than judged separately, so the two should always agree.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Shift Management
Shift Fatigue Screening
Screens work patterns for fatigue risk, covering shift length, rotation, breaks and consecutive days
Shift and Crew Register
Holds the shift pattern and crew structure for each area, so records can be grouped by the team that actually did the work
Operations Shift Handover
Passes the state of the operation from one shift to the next, covering what ran, what broke, what is held and what the next shift must know
Shift Start Up Check
Confirms the area, the people and the equipment are ready before the shift starts producing
Manning and Labour Plan
Sets who is working where for a shift, against the competencies each position requires
Overtime Authorisation
Authorises hours beyond the planned shift, with the reason and the cumulative position for that person
More in Shift Management
Operations Shift Handover
Passes the state of the operation from one shift to the next, covering what ran, what broke, what is held and what the next shift must know
Shift Start Up Check
Confirms the area, the people and the equipment are ready before the shift starts producing
Manning and Labour Plan
Sets who is working where for a shift, against the competencies each position requires
Overtime Authorisation
Authorises hours beyond the planned shift, with the reason and the cumulative position for that person
Shift Performance Log
Records what the shift actually achieved hour by hour against plan, and why it differed
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 9001:2015 cl.8.5 — Production and service provision
- ISO 9001:2015 cl.9.1 — Monitoring, measurement, analysis and evaluation
- Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 2013 (RIDDOR)
- OSHA 29 CFR 1904 — Recording and reporting occupational injuries and illnesses
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.