Metal Detector CCP Verification Log

It covers the routine verification of a metal detector critical control point using ferrous, non-ferrous, and stainless steel test pieces. The log captures setup status, test-piece detection and rejection, interval timing, and corrective action when a check fails. It is meant to document that the detector is working as intended before and during production.

Use it at startup, after defined intervals during production, and any time the detector is restarted, adjusted, or suspected of drifting out of tolerance. It is also useful after maintenance, product changeovers, or sanitation events that could affect detector performance. If your HACCP plan or SOP requires more frequent checks, the log should follow that cadence.

A trained line operator, quality technician, or other designated employee can complete the check if your SOP allows it. The person recording the result should be competent to run the test pieces, recognize a failed rejection, and escalate issues immediately. Final review is often assigned to a supervisor or QA representative.

Yes. It is designed to support HACCP verification records and the kind of documented control expected in food manufacturing and processing. It also aligns with common food safety management expectations for traceability, corrective action, and release control. Your site-specific HACCP plan, customer requirements, and audit rules should determine the exact fields and retention period.

Common mistakes include skipping the startup check, using the wrong test-piece size, failing to record the last successful verification time, and not placing product on hold after a failed test. Another frequent issue is documenting that a test was performed without confirming the reject device actually diverted the test piece. This template helps prevent those gaps by separating setup, test results, interval control, and corrective action.

Add the exact detector model, approved sensitivity settings, product family, and the test-piece sizes required by your SOP. You can also add fields for line speed, reject confirmation method, lot or batch number, and hold-release authorization if your process needs them. If you run multiple lines, duplicate the log by line ID so each detector has its own record.

Yes. The fields map well to digital forms, QA workflows, and MES or traceability systems because the log captures time, equipment ID, result, and disposition. Many teams also connect it to corrective action records and hold/release approvals. If you automate it, keep the ability to attach evidence such as photos or rejected test-piece confirmation.

An ad hoc checklist may confirm that a detector was checked, but it often misses the details needed for auditability and product disposition. This template records the actual test pieces, the interval requirement, the last good check, and the response to failures. That makes it easier to prove control of the CCP and to investigate any product affected by a missed or failed verification.