CCP vs OPRP Examples: How to Document a Food Safety Control Decision

1. Understand what the distinction changes

A CCP versus OPRP discussion becomes useful when it explains what operators must check, what result is acceptable and what happens to affected food if the check fails. A coloured category in a spreadsheet cannot answer those questions on its own. The decision needs a traceable connection to the hazard and the actual process.

ISO 22000 distinguishes critical control points, operational prerequisite programmes and prerequisite programmes; ISO's practical guide preview identifies categorisation, monitoring and validation as separate tasks. A CCP uses critical limits; an OPRP uses action criteria. Both need controls capable of addressing their identified hazards. General hygiene arrangements remain essential alongside these controls.

FAO's Codex-based CCP guidance places the decision within review of the complete process. OPRP is ISO 22000 terminology; do not treat a Codex decision tree as an automatic OPRP classifier.

For a further comparison, the European Commission's 2022 guidance discusses CCPs and OPRPs, including monitoring feasibility and timely response to failure. It is EU guidance; its examples do not classify another business's process or replace the applicable food law and the team's documented evaluation.

2. Describe the fictional process before classifying

Fictional worked example: Cedar Prepared Foods is an invented business making chilled cooked vegetable meals, including one recipe containing milk. The team is reviewing its cooking step and changeover from the milk-containing recipe to a recipe intended to contain no milk ingredient. The examples illustrate documentation, not a validated production process or a claim about allergen absence.

Before deciding categories, Cedar records ingredients, consumer groups, storage, distribution, intended preparation and the confirmed process flow. Its study distinguishes survival of Salmonella spp. identified in its ingredient hazard study from unintended milk presence at changeover. These are assumed hazards for the fictional study, not a complete hazard list for chilled meals. A reference to contamination without naming the hazard would make it hard to judge whether the proposed control can work. The team also records what happens after each step: later operations may change the hazard picture.

3. Write a conditional control decision

The following entries assume Cedar has completed its own hazard assessment and control evaluation. The classifications are conditional outcomes for this fictional study. They are not rules that cooking is always a CCP or that changeover is always an OPRP. Different ingredients, equipment, hazards or subsequent steps may change the conclusion.

Add an evidence reference and approval beside each conclusion. An entry saying industry practice without explaining applicability leaves the next reviewer unable to reconstruct the decision. A HACCP plan template can organise hazard analysis and control records; the team still supplies the technical justification.

4. Connect validation with workable monitoring

FAO's validation guidance explains that supporting evidence must apply to the actual operation and product. For Cedar, copying a cooking setting from a different meal would leave questions about portion geometry, equipment loading and the identified microorganism. This article deliberately supplies no generic temperature, holding time or allergen test limit.

Before implementing the hazard control plan, Cedar validates that the selected controls and their combination can control the identified hazards under its intended production conditions. A completed template or a supervisor's signature cannot substitute for that evidence.

In Cedar's proposed cooking record, an operator identifies the batch and uses the approved measurement method at the defined locations and frequency. The supervisor checks whether the instrument and method can detect loss of control soon enough to identify affected food. A box labelled checked without a result would not show what was measured.

For changeover, the team specifies the cleaning steps, inspection points and any test method justified by its validation. It defines what an acceptable result looks like and who may authorise line release. A visual check can monitor visible residue where justified, but does not by itself establish allergen absence; any removal conclusion needs a suitable, justified assessment.

5. Follow the record when a check fails

During a fictional changeover, the operator cannot confirm completion of a required cleaning step. Cedar withholds line release, identifies potentially affected material and informs the authorised food safety lead. The record captures the last acceptable check, relevant batches, times and evidence available. Restarting the line does not settle the disposition of food already produced.

The team evaluates the failure under its approved arrangements and applicable product release requirements. It records the decision, supporting evidence and responsible authority. An OPRP label is never permission to disregard potentially unsafe food. For a CCP failure, the response must likewise address affected product, not merely adjust the equipment and continue.

Investigate why the step was missed: the instruction may be unclear, equipment may be inaccessible or shift handover may have failed. Assign a corrective action and check its effectiveness. Keeping the original failed result preserves the history that a clean replacement sheet would erase.

6. Review the decision and tailor the documents

Cedar reviews the study periodically and when it changes a recipe, adds equipment or introduces a new consumer group. It asks whether existing evidence still applies, whether monitoring remains practical and whether affected staff need retraining. Verification records then show how the approved arrangements perform during operation; they serve a different purpose from the initial justification of capability. Changes with a potential food safety impact require review and, where necessary, revalidation before relying on the revised plan.

Verification adds checks beyond routine monitoring, such as reviewing monitoring records, checking instrument accuracy and auditing the arrangements. Following Codex section 19.11.2, Cedar assigns verification to a competent person other than the person responsible for monitoring and corrective actions. Where a verification activity cannot be performed in-house, an external expert or qualified third party performs it on the business's behalf.

The ISO 22000 templates provide editable food safety documentation for organising this work. Tailor the hazard analysis, responsibilities, control records and review process together. FAO's record-keeping guidance supports using generic materials only where they reflect the business's actual operation.

To audit the records behind a control decision, use the free audit evidence pack to log the sampled record, requirement, conclusion and follow-up. Its evidence-log structure supports traceability; it does not supply a validated food safety plan or product-release authority.