FDA preventive controls keep four record states separate

Monitoring proves performance at a defined control point

A monitoring record should identify the facility, food and process, hazard and preventive control, procedure and version, parameter or observation, required limit or condition, instrument or method, frequency, responsible person, date and time, result, lot or production scope, source record, and contemporaneous review. A lot code can connect the observation to material, but the code itself does not show that the control was performed or that its conditions were met.

The traceability layer should preserve that link without absorbing the control record. One control event may cover part of a lot, several lots, continuous production, rework, or a time-bounded run. Late entries, missing observations, instrument problems, and process interruptions should remain visible. A complete-looking genealogy should not make an absent or unacceptable monitoring result appear resolved.

Corrections and corrective actions answer different questions

FDA describes corrections as timely steps for a minor, isolated problem and corrective actions as work that addresses a preventive-control problem, reduces recurrence, evaluates affected food, and prevents unsafe food from entering commerce when safety cannot be assured. The operational record should identify which path was chosen, by whom, under which procedure, with what evidence, affected product, immediate disposition, cause assessment, recurrence action, and approval.

Traceback and forward-trace data can help define possible scope, inventory, shipments, customers, and quantities. That evidence does not decide whether a deviation was minor, whether food is safe, whether a corrective action is required, or whether product may be released. The qualified owner should record the decision and uncertainty. If genealogy is incomplete, the scope may need to remain broader until evidence supports narrowing.

Verification evaluates the control system, not just the lot

FDA's overview gives examples of verification that include validation of process controls, calibration or accuracy checks for instruments, record review, product testing, and environmental monitoring as appropriate. Those activities operate on different evidence and schedules. A passed product test does not erase a missed process record, and a completed record review does not establish that an instrument was accurate or a control was scientifically capable.

The verification record should preserve the activity type, protocol or procedure, control and hazard, evidence population and period, sampling basis, method, acceptance criteria, reviewer, exceptions, conclusion, approval, and follow-up. Lot and event identifiers should let reviewers locate relevant material while keeping the verification's own scope intact. A dashboard count of verified records is not meaningful without the expected population and unresolved exclusions.

Test the four states with one imperfect production run

A representative system test should run a monitored process across two ingredient lots and three finished lots, miss one scheduled observation, record a minor isolated correction, discover a broader control failure, place product on hold, investigate cause, reconcile quantities, and perform verification with an instrument accuracy issue. Reviewers should distinguish every state, reproduce affected scope, preserve late and corrected entries, and identify product whose safety or location remains unresolved.

Then release, rework, destroy, or recall product only through the applicable approved decision path and confirm that none of those dispositions silently closes the control record. FDA's page establishes the listed preventive-control concepts and documentation expectations. It does not establish a particular facility's applicability, hazard analysis, monitoring design, correction classification, corrective-action sufficiency, verification result, traceability completeness, or compliance.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Food Traceability Ledger will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.