Glossary · Food cold chain
HACCP temperature alert escalation
HACCP temperature alert escalation is the process of notifying a responsible person when a temperature excursion breaches a HACCP critical control point, and automatically escalating to the next person — and the next — until someone acknowledges and the corrective action is recorded.
In practice
Closing the corrective-action gap
A walk-in cooler at a critical control point breaches its limit. HACCP temperature alert escalation notifies the on-shift responsible person first, with a push to their my-iris app and a voice call in the receiver group’s language if the push goes unanswered. If they do not acknowledge, it escalates to the next person and then a supervisor — push first, then a call, person by person — so the deviation is never left unattended. When a human acknowledges, my-iris resolves the alert and writes a timestamped record linking the excursion, the notifications and the acknowledgement — who took responsibility for the corrective action, and when — the documentation a HACCP plan and a food-safety audit expect.
A worked example
From CCP breach to verified corrective action
A sensor at the critical control point detects the limit breach and fires a webhook to my-iris.
my-iris sends a push to the on-shift responsible person, calls if the push goes unanswered, then climbs the chain until someone acknowledges.
The acknowledgement is timestamped against the excursion — who took it, and when. Messages the team posted on the alert while it was open are kept with it.
The trail is exportable evidence that monitoring and corrective action happened — for the HACCP plan and an audit.
HACCP escalation — frequently asked
Why does HACCP need escalation, not just an alert?
HACCP requires that excursions at critical control points are detected and that corrective action is taken and documented. A single unacknowledged alert leaves a gap: if the first person misses it, the deviation continues unrecorded. Escalation closes that gap by climbing the responder chain until a human acknowledges, so the corrective-action trail is never broken.
What does the escalation chain look like in practice?
my-iris sends a push to the first person’s my-iris app and waits for the push window (5 minutes by default). With no acknowledgement it calls the same person, then moves to the next responder and on down the list to a supervisor — up to 20 attempts by default. Every push, call and answer is timestamped, and so is the outcome, giving you the monitoring-and-corrective-action record HACCP documentation expects.
Does it integrate with our existing temperature monitoring?
Yes. my-iris sits on top of your sensors and monitoring system. Any platform that can fire a webhook posts the excursion to one REST endpoint (a system that can only send email uses a secret email address instead), and my-iris handles routing, escalation and the audit record. It does not replace your monitoring — it makes sure the excursion reaches a human and is provable.
See HACCP-ready temperature-excursion alerting built for the food cold chain.
my-iris for food & cold chainNever miss a CCP excursion
Tell us about your critical control points, and escalate every excursion until a human acknowledges.