ITF Digital

Food safety records that exist on the day

CCP monitoring, prerequisite checks and corrective actions captured when they happen, so an inspector or a retailer's auditor sees records rather than a promise.

In a Saudi food plant the HACCP system is a licence condition, and records are what fails. Checks get done and not filed, and a missed check disappears instead of showing as missed. We build capture that records each check when it happens, forces a corrective action on an out-of-limit reading, and keeps every record findable.

Top left, readings at CCP 1, pasteurisation, run above a dashed critical limit and cross below it once. The crossing, highlighted, opens a corrective action that must exist before the reading can be saved, which puts the batch on hold in the record, which goes to a named person in QA who decides to hold, rework or release; the decision, the name and the time are kept. Below, the production line as a strip of five stages, receipt, pasteurise, cool, fill and seal, and metal detect, with three CCPs marked. At CCP 3 a check that was not done is recorded as missed. Verification is signed by a named person who is not the operator.CCP 1 · PASTEURISATION READINGSCRITICAL LIMITEACH CHECK TIMESTAMPED AT THE LINECORRECTIVE ACTIONREQUIRED BEFORE SAVEBATCH ON HOLDIN THE RECORDQA DECIDESHOLD, REWORK OR RELEASEDECISION, NAME AND TIME KEPTTHE LINERECEIPTPASTEURISECOOLFILL, SEALMETAL DETECTCCP123CCP 3: A CHECK NOT DONERECORDED AS MISSEDVERIFIED BY A NAMED PERSON, NOT THE OPERATOR
A deviation, and who decidesThe record holds the batch. QA decides its fate.Swipe to pan
01

Records fail, not practice

A CCP check is done at the right temperature at the right time, and the log sheet is filled in at the end of the shift from memory, all in one pen. A verification is done and not signed. A training session runs and the attendance sheet stays in a drawer. SFDA lists a HACCP certificate among the documents for a food manufacturer's licence, and its inspection campaigns look at whether HACCP is present and effective and whether products can be traced. A retailer's auditor looks for the same things. Both judge what they can see on the day.

  • CCP logs filled in after the fact, or a missed check left blank and forgotten
  • Cleaning, pest control, glass and hand hygiene checks done but not recorded against the day they were due
  • Chiller and freezer logger data that nobody reviews until something has already gone wrong
  • A probe calibration check with nothing linking that probe to the readings it took
  • A mock recall that takes most of a day, because batch and supplier lot live in different places
  • Supplier certificates found expired by the auditor rather than by the plant
  • Corrective actions raised and left open, with no evidence of the fix
03

The rules the capture holds each record to

An inspector and a retailer's auditor judge the record. These are the rules that decide what the record shows.

RequirementWhat it means on site
A CCP reading outside its critical limitIt cannot be saved without a corrective action, and the batch goes on hold in the record until a named person in QA decides.
A check due and not doneRecorded as missed at its due time. Uncomfortable to look at, and exactly the kind of record an auditor trusts.
Verification of monitoringSigned by a named person who is not the operator who took the reading.
The HACCP plan and its formsHeld under document control. When the plan changes revision, the capture screens change with it on the same day.
TraceabilityBatches are linked to supplier lots at receipt, so a mock recall becomes a search rather than a day of paper.
Supplier approvalEach supplier certificate is held with its expiry date, and the supplier's owner is chased before it lapses.
04

What QA teams ask

Q01

Who decides what happens to a batch after a deviation?

A named person in QA. The software places the batch on hold in the record, shows the reading and the corrective action, and hands the decision to that person: hold, rework or release. It records the decision, the name and the time. Your HACCP team sets the critical limits the capture checks against.

Q02

Will SFDA accept digital records?

The inspector judges the record in front of them. What the capture produces is a record that is timestamped, attributed to a named person and findable, which is what an inspection looks for.

Q03

Can data come straight from our temperature loggers?

Often, through the logger system's export or interface. We check yours during the systems audit, before quoting.

Q04

Our operators speak several languages.

The capture screens run in Arabic and English, with icons doing most of the work. Other languages are a specification question we settle before the build.

Q05

Will you write our HACCP plan?

ITF Consult writes HACCP plans. This page is about the records the plan requires, and the two fit together: the plan's forms become the capture screens.

Q06

What does a typical engagement look like?

A dairy dessert plant in Riyadh's Second Industrial City records pasteurisation temperatures, metal detector checks and chiller temperatures on paper, and a mock recall takes most of a day. Operators now record each CCP check on a tablet at the frequency the plan sets. An out-of-limit pasteurisation reading opens a corrective action and places the batch on hold in the record until the QA supervisor decides. Missed checks show on a daily report, and batches are linked to supplier lots at receipt, so a mock recall becomes a search. The plant holds its CCP and prerequisite records, a missed-check report, a corrective action register and a traceability record it can rehearse.

Start from last month's log sheets

The systems audit walks your CCP and prerequisite records against the plan and shows where each one breaks today. Bring last month's sheets.

Book a systems audit