A fail is recorded, not hidden. Here is exactly what FourFoxes does.
- The corrective action is required. If the result is Fail, you must describe the action you took before the record will save. On the packaging screen, the Corrective action taken box opens as soon as you choose Fail. For a numeric reading outside the limit, it opens when you click Save and asks for the action.
- Your procedure is shown. If the CCP has a corrective action procedure written on it, the failed row on the packaging screen shows it as Corrective procedure, next to the Action taken.
- The record is saved and locked. Like every monitoring record, a failed check cannot be edited or deleted afterward. The failure and the action you took become part of the permanent log.
- Admins are alerted. An email goes to the account's admins and owners. It names the CCP, the batch, the measured value, the critical limit, and who recorded it, with a link to the record. Each failure triggers exactly one alert. The alert is on by default. Each admin or owner can turn off CCP failure alerts for themselves under Email alerts on Account Team.
Where failures show up later:
- The HACCP master log and the per-CCP logs show the failed reading with No under CCP Met? and the corrective action in the Corrective Actions column.
- The HACCP Reports hub shows a deviation count for the last 30 days on each CCP. Checks marked not performed count as deviations too. Acknowledged missed checks get their own count.
The corrective action is the audit record
What you type in the corrective action box is what an inspector will read next to the deviation. Write what you actually did: what happened to the product, what you changed, and who decided.
Related