Codex HACCP principle 4 requires a monitoring procedure at every critical control point, and principle 5 requires a corrective action when monitoring shows a loss of control. Read together they assume one thing: that the monitoring happens. In practice, the HACCP failure that appears most often in audits, and the one we see most often behind the withdrawals we have helped manage, is not an out-of-limit reading. It is a reading that was never taken. A cook temperature that was not checked on the night shift. A metal detector test skipped at a changeover. On paper those gaps are found days later as blank lines. On a system that knows when each check is due, they are found within minutes, by an alert to someone who can act.
What the HACCP standard actually expects of monitoring
Every monitoring procedure has to say what is measured, how, how often, by whom and against what limit, and the record has to show each of those. The frequency is the part that paper handles worst. A procedure that says “every two hours” produces a sheet with twelve lines per shift, and the only control on whether all twelve were done is whether somebody looks at the sheet. Under FSSC 22000, BRCGS and SQF, and under Regulation R908 of 2003, which governs HACCP systems in South Africa, the auditor will look at frequency against the record and will raise a non-conformance for a gap, regardless of whether the product was safe.
Why gaps happen
Gaps are rarely negligence. The operator is covering two lines because someone is off. The thermometer is being calibrated. The changeover ran long and the check fell between two people. The sheet was in the office. None of those reasons help at an audit, and none of them are visible to the supervisor until the shift is over. The supervisor’s verification signature at the end of the day confirms that the gaps were seen, not that they were prevented.
What an alert changes
On ASCloud each CCP has its monitoring schedule built in. When a check falls due, it appears on the operator’s screen. When it is not recorded within the tolerance set by the site, typically fifteen minutes, the system sends an alert to the supervisor and logs the missed check. The supervisor can then do the check, assign it, or record why it was not possible and what was done about the product in the meantime. The record of the gap is created at the time of the gap, with the reason and the action, which is exactly what principle 5 asks for. The auditor sees a missed check with a corrective action, not a blank line with a question mark.
The same mechanism handles an out-of-limit reading. The entry screen knows the critical limit. A reading outside it opens a corrective action form that cannot be dismissed, asks what happened to the product since the last good reading, and alerts the HACCP team leader. The operator cannot write the number and walk away.
Verification, separated from monitoring
Principle 6 is verification, and auditors increasingly check that the person verifying a record is not the person who made it and that verification happened near the time of the record rather than in a batch. A paperless system makes both of those visible. Verification is a separate action by a separate login with its own timestamp. A week of records verified in ten minutes on a Friday is visible as exactly that.
The records you can produce when something goes wrong
When a customer complaint or a positive test result leads to a review, the question is always what the monitoring showed at the time. On a paperless system the HACCP team can pull every CCP record for a production window in minutes, with any missed checks and corrective actions in the same view, and can show exactly what was known and when. That record is what lets a site make a confident decision about the scope of a withdrawal, and it is the record a retailer or the Department of Health will ask for.
CCP monitoring with alerts
Every CCP scheduled, every missed check alerted, every deviation forced into a corrective action. HACCP on ASCloud from R3,800 per site per month on the full document FSMS plan, with GFSI plans from R1,820.
Frequently asked questions
Who receives the alert?
You decide per CCP. Typically the shift supervisor first, then the HACCP team leader if the check is still missing after a second interval.
Can readings come straight from the instrument?
Where an instrument supports it, yes. Otherwise the operator enters the reading and identifies the instrument, which keeps calibration traceable.
What if the tablet is down?
The app works offline and syncs later. For a full outage, the site’s documented contingency is a paper fallback that is entered into the system afterwards with the original times.
Does this replace the HACCP plan?
No. The plan is still built and validated by your HACCP team, with ASC’s help if you want it. ASCloud runs the monitoring, verification and records that the plan requires.