Sector notes
The CCP record is still a clipboard. The sensor next to it already has the number
Critical control point monitoring is one of HACCP's seven founding principles, not paperwork attached to it. Most of that monitoring is still handwritten, even where the equipment already produces the same reading digitally, and audit findings keep landing on exactly that gap.
Executive summary
S$8,000
fine issued to a Singapore caterer after 395 people fell ill — a case a temperature sensor would not have caught
Core conclusions
- Codex Alimentarius treats monitoring and record-keeping as two of HACCP's seven founding principles — poor records can nullify an otherwise sound plan.
- An automated CCP feed fixes missing or incomplete monitoring records but has nothing to say about culture, allergen management, or food fraud.
- Automate the record, not the judgement — a logger cannot replace the walk-through a supervisor or auditor actually does.
Most critical control point records at food processing plants are still handwritten on a laminated sheet, even where the equipment involved already has a digital sensor producing the identical reading. That gap between what is measured and what is recorded is not cosmetic. Codex Alimentarius treats monitoring and record-keeping as two of HACCP's seven founding principles, and its own guidance is direct about the consequence of getting the second one wrong: a scientifically sound, fully validated plan can be nullified by poor records, because there is nothing left to show an auditor, a regulator, or a court that the monitoring actually took place.
In the plants I audit, the pattern repeats: a chiller with a digital display sits beside a clipboard filled in by whoever is on shift, at whatever interval the shift actually allows, and the two numbers are never reconciled because nothing requires it until an auditor asks.
What automated capture actually fixes
SGS's 2026 review of FSSC 22000 audits and FSNS's ranking of recurring non-conformities both point at the same handful of categories. Automated CCP monitoring closes some of them and has nothing to say about the rest:
| Recurring finding | Does an automated CCP feed fix it? |
|---|---|
| Missing or incomplete records for devices monitoring or controlling a food safety hazard — FSNS's second most-cited non-conformity | Yes. This is precisely what a logged, timestamped feed replaces. |
| Overdue calibration on monitoring instruments with no documented risk assessment | Partly. The logger can flag its own due date; it cannot decide whether the risk assessment was adequate. |
| Documentation not updated to the current scheme version | No. That is a document-control gap, not a data gap. |
| Food safety culture | No. Culture is a management and training question a sensor has no view on. |
| Allergen management, food fraud and food defence | No. These turn on procedure, labelling and intent, not a measured value. |
What a logged CCP record buys, specifically
- The number an auditor reviews is the number the instrument produced, not one transcribed from memory at the end of a shift.
- Every reading is timestamped, closing the common failure where one entry stands in for eight unmonitored hours.
- A missed reading shows up as a gap the system flags, rather than a blank cell an auditor has to notice.
- The monitoring device itself becomes part of the same maintenance record, rather than a separate spreadsheet nobody reconciles against FSNS's own second-ranked finding.
The kind of lapse this does and does not catch
In April 2025, Singapore's Food Agency fined Shiok Kitchen Catering Pte Ltd S$8,000, following a joint inspection with the Ministry of Health after 395 people fell ill with gastroenteritis from food it catered in November and December 2023. Inspectors found a dirty chiller, a dirty ice-making machine, cockroaches in an unused chiller, and a sample of ready-to-eat spinach unfit for consumption. None of that required a temperature sensor to catch — it required someone to look, and to have looked recently enough that the record meant something.
That is the honest limit of the argument above. A logger records what happened; it does not decide whether a reading should have triggered a corrective action, and it is no substitute for the walk-through a supervisor or an auditor actually does. Automate the record, not the judgement, and expect it to move one category of finding — not the audit.