Metal Detector Validation - What It Is and What Auditors Look For

Metal detectors are one of the most common controls in food manufacturing, and one of the most commonly misunderstood. Almost every plant has one. Far fewer can show an auditor clear, defensible proof that it finds the contaminants it's supposed to find, in the products it actually runs.

That proof is what validation is about. Here's what it involves, how it differs from your daily checks, and where we see plants run into trouble.

Why it matters

Metal gets into food from worn equipment, broken screens, loose bolts, blades, and raw materials. The FDA considers hard or sharp foreign objects between 7 and 25 mm long a potential injury hazard, and even smaller fragments can trigger recalls, customer complaints, and lost accounts.

If your food safety plan names the metal detector as a critical control point or preventive control, you're responsible for proving it works. That applies under FDA's preventive controls rules, USDA HACCP, and GFSI schemes like SQF and BRCGS. "The light turned red when we tested it" isn't enough. Auditors want documented evidence.

Validation, verification, and calibration

These words get used interchangeably, but they mean different things:

What it answers Who does it How often
Validation Is this system capable of detecting the contaminants we care about, in our products, and removing them from the line? Usually a qualified third party or the manufacturer At installation, after major changes, and typically once a year
Verification Is it still working right now? Your line operators At start-up, at set intervals during production, and at shutdown
Calibration and maintenance Is the hardware set up and working as designed? Maintenance or the equipment manufacturer Per manufacturer recommendations

Your daily verification checks depend on a solid validation. If nobody ever proved the detector can find a 2.5 mm stainless steel sphere in your product, passing a 2.5 mm test every hour doesn't mean much.

What a proper validation covers

A thorough metal detector validation looks at the whole system, not just whether the head beeps.

Sensitivity with all three metal types. Detectors respond differently to different metals, so testing uses certified test pieces in three categories:

Testing in your actual product. Moist, salty, and conductive foods like meat, cheese, sauces, and brined products create a signal of their own, called "product effect," which can mask small pieces of metal. A detector that performs well on an empty belt can miss the same test piece inside a package of deli meat. Validation should use your real products, especially the ones hardest to inspect.

Worst-case positioning. A detector is least sensitive at the center of its opening, so test pieces should pass through there and not just along the edges or taped to the top of a package. Testing at the leading edge, middle, and trailing edge of the product helps confirm the reject timing too.

The reject system. Detection is only half the job. Validation should confirm that contaminated product is actually removed from the line, every time, at your normal line speed. That includes checking the reject timing, any confirmation sensors, bin-full alarms, and whether the reject bin locks so rejected product can't quietly make its way back into production.

Fail-safe features. Many standards expect the system to respond safely when something goes wrong, like the belt stopping or an alarm sounding if the detector faults, the reject fails, or the air supply drops.

Documentation. The final report should state what was tested, how, with which certified test pieces, the results, and whether the system meets your sensitivity standards. This is the document your auditor will ask for.

What auditors look for

When an auditor reviews your metal detection program, expect questions like these:

  1. Are your sensitivity standards justified? Why did you choose these test piece sizes for this product and line? "That's what the last company used" isn't a justification.
  2. Is there a current validation report? Does it cover every detector and the products each one runs?
  3. Are your test pieces certified? Are they in good condition and clearly identified?
  4. Are verification checks happening as written? Are they recorded, signed, and done at the frequency your plan says?
  5. What happens when a check fails? Your procedure should say to hold all product made since the last successful check, re-inspect it, and document the corrective action.
  6. Are operators trained? Can the person running the line explain how to do a check and what to do if it fails?

Common gaps we see

After working with food manufacturers across Utah, these are the issues that come up most often:

Any one of these can turn a routine audit into a finding.

When to revalidate

Plan to validate each detector at least once a year, and again whenever something significant changes, including:

The bottom line

A metal detector protects your customers only if it's set up correctly for your products and backed by documentation that proves it. Validation gives you that proof, and it gives your auditor confidence that your program is under control.