CCP: Critical Control Point in HACCP
Understand how critical control points connect food safety hazards to measurable limits, operational decisions and defensible records.

On this page · 11 sections
- 1What a CCP is—and what it is not
- 2How CCPs are identified from hazards and process steps
- 3Critical limits: the boundary that monitoring must test
- 4Monitoring and corrective action: detect, decide and document
- 5Validation versus verification: effectiveness and implementation are different questions
- 6U.S. regulatory mapping: meat/poultry requirements versus juice requirements
- 7CCP records: connect the plan, measurements, actions and evidence
- 8Record handoffs and exception recovery without losing the original observation
- 9Two worked CCP cases: limit deviation and missing observations
- 10Common CCP failures and the controls that expose them
- 11A source-attributed implementation and review checklist
How does CCP apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What a CCP is—and what it is not
CCP stands for critical control point. FDA's HACCP Principles & Application Guidelines define it as “A step at which control can be applied and is essential to prevent or eliminate a food safety hazard or reduce it to an acceptable level.” Two words in that definition do the work: the CCP is a *step* in the process, and control there is *essential* to a food safety hazard. It sits inside the wider HACCP framework and is not a label for every important production check.
The same guidance separates two neighbouring terms. A Control Point is “Any step at which biological, chemical, or physical factors can be controlled.” Prerequisite Programs are “Procedures, including Good Manufacturing Practices, that address operational conditions providing the foundation for the HACCP system.” Every CCP is therefore a control point, but most control points are not CCPs, and prerequisite programmes such as Good Manufacturing Practices support the plan rather than replace hazard-specific control. These are guidance definitions; which legal rule applies depends on the product, as the regulatory section below explains.
| Term | Operational question | Relationship to the plan |
|---|---|---|
| CCP | Where is control essential to address a food-safety hazard? | Identifies the step where essential hazard control is applied. |
| Control point | Can biological, chemical or physical factors be controlled at this step? | Any controllable step; becomes a CCP only where that control is essential to a food safety hazard. |
| Prerequisite programme | What operational conditions support the system? | Provides the foundation on which the HACCP system operates. |
| Critical limit | What maximum and/or minimum value defines hazard control? | Sets the boundary for the parameter controlled at the CCP. |
| Monitoring | Do planned observations or measurements show the CCP is under control? | Assesses control and produces an accurate record for later verification. |
Read the table as moving from the broad to the specific: many steps are control points, a few are CCPs, and each CCP carries a critical limit and monitoring. In practice, calling a check “critical” is not enough. The question is whether losing control at that step would leave a food safety hazard uncontrolled, rather than whether the check matters for quality, yield or customer specification.
02How CCPs are identified from hazards and process steps
CCP selection follows preparation and hazard analysis; it is not the starting point for a HACCP plan. The FDA guidance’s Developing a HACCP Plan headings organise that preparation in this sequence:
- Assemble the HACCP team.
- Describe the food and its distribution.
- Describe the intended use and consumers of the food.
- Develop a flow diagram describing the process.
- Verify that flow diagram.
The FDA guidance definition of hazard analysis centres on collecting and evaluating information about hazards associated with the food, then deciding which are significant and must be addressed in the plan. This is a food-safety assessment, not a generic business-risk ranking.
Under Determine critical control points (Principle 2), information developed during hazard analysis is essential to identifying CCPs. Appendices E and F contain example CCP decision trees. They can help assess a process step for a previously identified hazard, but the guidance expressly treats a decision tree as a tool—not a mandatory HACCP element or a substitute for expert knowledge.
For a practical determination record, the following are suggested documentation fields, not mandatory field names. Their purpose is to make the reasoning traceable rather than leave an unexplained CCP label beside a process step.
| Suggested field | What to capture |
|---|---|
| Process step | The operation being assessed on the flow diagram. |
| Hazard | The food-safety hazard under consideration. |
| Significance reasoning | Why the hazard does or does not need addressing in the plan. |
| Proposed control | The measure proposed to control that hazard. |
| CCP decision | Whether the step is a CCP, with the reasoning supporting that conclusion. |
- Identify hazardsEvaluate which food safety hazards need the plan.
- Determine CCPsConnect significant hazards to their control points.
- Set critical limitsDefine the controlled parameter and its boundary.
- MonitorRecord observations or measurements against the limit.
- Address DeviationsCorrect the cause, determine product disposition and document actions.
- VerifyEvaluate plan validity and operation against the plan.
- Retain evidenceKeep linked monitoring, action and verification records.
03Critical limits: the boundary that monitoring must test
In HACCP, a critical limit connects a controlled parameter to a specific food safety hazard. The FDA guidance definition of critical limit describes a maximum and/or minimum value for a biological, chemical or physical parameter at a CCP, used to prevent, eliminate or reduce the occurrence of that hazard to an acceptable level.
A minimum sets a lower boundary; a maximum sets an upper boundary. Combined boundaries can define a range or conditions that must be met together. The symbolic examples below illustrate how to express those comparisons—not suitable limits for any particular food. Each assumes that supporting information connects the selected parameter and boundary to the identified hazard.
| Parameter | Boundary description | Monitoring observation | Supporting rationale |
|---|---|---|---|
| Temperature T | Minimum: T ≥ Tmin | Measured T, with unit | Support connecting Tmin to the named hazard |
| Concentration C | Maximum: C ≤ Cmax | Measured C, with unit | Support connecting Cmax to the named hazard |
| Parameter x | Combined range: L ≤ x ≤ U | Measured x, with unit | Support for both boundaries |
| Temperature T and duration t | Combined conditions: T ≥ Tmin and t ≥ tmin | Temperature and corresponding duration | Support for the joint conditions controlling the named hazard |
Numerical precision alone does not establish adequacy. FDA guidance Appendix G includes validation of critical limits to confirm that they adequately control significant hazards. A parameter tolerance band can describe a range, but the critical-limit rationale addresses hazard control, not merely whether a process stays within a chosen band.
The FDA guidance definition of deviation is failure to meet a critical limit. An observed out-of-limit result establishes that the recorded value did not meet the boundary. A missing observation does not establish what the process value was: it is neither proof of an acceptable value nor a measured excursion. Keep those evidence states distinct rather than filling a blank with an assumed result.
An illustrative implementation structure is a limit record containing parameter, boundary direction, value, unit, associated hazard and supporting information. For combined conditions, identify each component and how they relate. This is a suggested record structure, not a prescribed database schema or a source of universal numerical limits.
04Monitoring and corrective action: detect, decide and document
The FDA guidance definitions describe monitoring as planned observations or measurements that assess whether a CCP is under control and produce an accurate record for later verification. Monitoring therefore connects the process as operated with the written HACCP plan: the observation supports both an immediate decision and subsequent review.
From observation to recorded outcome
A practical operating sequence is:
- Observe or measure. Follow the monitoring procedure for the CCP and capture the actual result, rather than only a pass/fail status.
- Compare. Assess that result against the documented critical limit. Use the meaning of deviation established in the preceding section.
- Respond. If a deviation occurs, follow the applicable corrective-action instructions and involve the people assigned responsibility in the plan.
- Document the outcome. Connect the observation to the cause assessment, action taken and product-disposition decision so a reviewer can follow what happened.
Prepare corrective actions before they are needed
Under Principle 5, FDA guidance recommends developing specific corrective actions in advance for each CCP and including them in the HACCP plan. Its three corrective-action elements are:
- Determine and correct the cause of non-compliance.
- Determine the disposition of non-compliant product.
- Record the corrective actions that have been taken.
These are guidance elements, not a combined statement of FSIS meat/poultry and FDA juice legal requirements. Principle 5 also recommends that the plan specify what happens when a deviation occurs and who is responsible for implementing corrective actions.
For an illustrative cause/action/product-disposition record, keep three entries distinct: the cause identified; the process correction made; and the decision about affected product, with the responsible person's recorded decision. Restoring a process parameter answers a different question from deciding what happens to product associated with the deviation. One entry should not silently stand in for another.
Keep decisions with the responsible people. Do not treat a subsequent in-range reading, a completed form or a software status as product release. If responsibility passes between shifts, use a shift handover report to identify unresolved actions and pending disposition decisions, rather than implying closure.
The resulting monitoring and corrective-action record is the handoff to verification, addressed next.
05Validation versus verification: effectiveness and implementation are different questions
In FDA’s HACCP guidance, validation is an element of verification—not a separate, unrelated programme. It asks whether scientific and technical information supports the conclusion that the HACCP plan, when properly implemented, will effectively control the hazards.
The FDA guidance definitions describe verification more broadly: activities other than monitoring that determine the plan’s validity and whether the system operates according to the plan. The comparison below separates those evidence questions without treating them as independent programmes. These are guidance concepts, not a standalone legal checklist.
| Question | Evidence purpose | What it does not establish by itself |
|---|---|---|
| Validation: will the properly implemented plan control the hazards? | Scientific and technical support for the plan’s effectiveness. | That the system actually operates according to the plan. |
| Verification’s implementation question: is the system operating according to the plan? | Evidence of operation against the planned procedures. | Why those procedures and limits are scientifically adequate to control the hazards. |
For example, suppose a monitoring record shows that a stated critical limit was met. That observation does not, by itself, explain why the limit controls the hazard. This is an analytical consequence of the guidance’s definitions: evidence that a specified condition occurred answers a different question from evidence supporting its effectiveness. Conversely, scientific support for the limit does not show that the condition occurred during the operation being reviewed.
06U.S. regulatory mapping: meat/poultry requirements versus juice requirements
The applicable product rule matters: FDA’s HACCP guidelines explain an approach to food safety, while the meat/poultry and juice provisions below impose requirements within their respective scopes. These are not interchangeable requirements for every food, supplement, pharmaceutical, device or chemical operation.
| Product context | Authority and status | Specific provision | Operational consequence |
|---|---|---|---|
| Food operations applying HACCP principles | FDA HACCP Principles & Application Guidelines — guidance, not a substitute for applicable regulations | Introduction | Use the guidelines to support HACCP plan development and implementation, adapting their application to the food-industry segment. |
| FSIS meat/poultry establishments subject to 9 CFR Part 417 | 9 CFR Part 417 — binding regulation | 417.2(c)(5); 417.2(c)(7) | The HACCP plan must include all corrective actions developed in accordance with 417.3(a), and list verification procedures and the frequency with which they will be performed. |
| Juice processors subject to 21 CFR Part 120 | 21 CFR Part 120 — binding regulation | 120.8(a)(1)–(2) | Plan coverage addresses each location where the processor processes juice and each type of juice processed. See the FAQ for conditional juice-type grouping. |
For FSIS establishments, the corrective-action entry is an inclusion requirement tied to the actions developed under the referenced provision. The verification entry requires both procedures and their frequency; it does not state a single review interval to copy across all HACCP systems.
Two further FSIS inclusion requirements bear directly on CCP evidence. 9 CFR 417.2(c)(6) requires the plan to “Provide for a recordkeeping system that documents the monitoring of the critical control points. The records shall contain the actual values and observations obtained during monitoring.” 9 CFR 417.2(c)(7) requires it to “List the verification procedures, and the frequency with which those procedures will be performed, that the establishment will use in accordance with § 417.4 of this part.” Under 9 CFR 417.3(c), “All corrective actions taken in accordance with this section shall be documented in records that are subject to verification.” Read together, these mean an FSIS establishment's CCP record cannot be a pass/fail tick alone: the actual value, the corrective action when one was taken, and the planned verification activity each need their own retrievable entry. The juice rule sets out its own parallel list in 21 CFR 120.8(b), including critical limits, monitoring procedures and frequency, corrective action plans and validation and verification procedures, so a juice processor should map its records to that list rather than to the FSIS paragraphs.
For juice, possession of a written plan is not the whole test. Under 21 CFR 120.9, evaluation concerns the processor’s overall implementation of its HACCP system when determining whether its actions are consistent with ensuring juice safety. Location and juice-type coverage therefore need to be read alongside implementation, rather than treated solely as document labels.
Separately, FDA’s Principle 6 guidance recommends frequent HACCP plan reviews, verification that the plan is correctly followed, and review of CCP monitoring and corrective-action records. That recommendation should retain its guidance status, not become an invented statutory schedule.
The following records section addresses the distinct record-content provisions. For another product category or jurisdiction, check its applicable current rules separately. Related starting points include 21 CFR 117 and 21 CFR 211; neither should be substituted for this product-specific scope assessment.
07CCP records: connect the plan, measurements, actions and evidence
For FSIS-regulated meat and poultry establishments, 9 CFR 417.5(a)(3) requires records documenting CCP monitoring and critical limits, including actual times, temperatures or other quantifiable values prescribed by the HACCP plan. It also covers process-monitoring instrument calibration; corrective actions, including all actions responding to a deviation; verification procedures and results; and product code(s), product name or identity, or slaughter production lot. Each record must include the date it was made.
For juice, 21 CFR 120.12(a)(4)(i) requires records of CCP monitoring and critical limits, including actual times, temperatures or other measurements prescribed by the HACCP plan. This provision addresses monitoring measurements; the FSIS list above is not a list of requirements under this juice provision.
Separately, FDA’s monitoring guidance, Principle 4, recommends that all CCP monitoring records and documents be dated and signed or initialled by the person doing the monitoring. That recommendation is guidance, distinct from the binding provisions above.
An illustrative five-entity evidence model
The following model is an implementation suggestion, not a regulator-prescribed database schema. Field names, identifiers, relationships and timestamp granularity are design choices.
| Entity | Illustrative fields and connections |
|---|---|
| Plan/CCP | Plan version, CCP identifier, critical limit and prescribed measurement; referenced by observations. |
| Product/lot | Product identity and lot identifier; linked to relevant observations and actions. |
| Monitoring observation | Original value, unit, observation time, record date, monitor identity and separate limit assessment; links to CCP, lot and instrument. |
| Instrument/calibration | Instrument identifier, calibration record and date; linked to observations using that instrument. |
| Action/verification evidence | Action taken, procedure, result and record date; linked to the relevant observation, lot or instrument. |
Use production context tagging to organise those links. For machine data acquisition, keep the original measured result distinguishable from its interpretation: a pass/fail assessment should accompany, not replace, the measurement. This preserves a readable path from the plan through the observation to subsequent evidence.
HACCP Plan
Defines the food, site and hazard-analysis basis.
- plan_id
- product_identity
- processing_location
- hazard_analysis_ref
Critical Control Point
Connects the hazard, parameter and critical limit.
- ccp_id
- plan_id
- hazard
- parameter
- critical_limit
- monitoring_procedure
Monitoring Record
Captures the original result, product identity and monitor.
- record_id
- ccp_id
- product_code
- record_date
- actual_value
- unit
- observation
- monitor_initials
Corrective Action
Documents the cause, disposition and actions taken.
- deviation_id
- monitoring_record_id
- cause
- product_disposition
- actions_taken
Verification Record
Records the activity performed and its result.
- verification_id
- plan_id
- ccp_id
- activity_type
- result
- record_date
08Record handoffs and exception recovery without losing the original observation
An optional handoff design can connect a measuring instrument or paper worksheet to the monitoring record, then link that record to related corrective-action and verification records. This is a suggested operating practice, not a mandated integration or a software capability claim.
At each handoff, preserve or explicitly reference the CCP, actual observation, applicable unit, product identity, record date and person recording the observation. These map to the record elements discussed above. A proposed observation ID or transfer ID can link records; these identifiers are design choices, not additional source-stated record content. Keep the original worksheet or instrument output accessible alongside the linked batch record.
| Exception | Reconciliation question | Evidence to retain |
|---|---|---|
| Missing observation | Was a reading taken but not transferred, or never recorded? | Available original records, gap identification and investigation outcome. |
| Transferred value with the wrong unit | Does the original show a different unit, and was conversion intended? | Original value and unit, correction or conversion calculation, reviewer identity. |
| Product-code mismatch | Which product does the original observation identify? | Original code, supporting production context and documented resolution. |
Apply the earlier deviation/evidence-gap distinction: never replace an absent observation with an assumed in-range reading. If both record recovery and process correction are needed, track them separately and link their outcomes for verification. Carry unresolved exceptions into the shift handover report. Responsible people assess product disposition and approve corrections or other decisions; successful data transfer does not release product.
09Two worked CCP cases: limit deviation and missing observations
Case one: temperature below the minimum
Assumptions: a hypothetical process has an established minimum temperature critical limit L, expressed in degrees Celsius. The measured temperature is L − 0.4 °C. No numerical value for L is proposed.
Measured temperature minus minimum limit = (L − 0.4 °C) − L = −0.4 °C. The observation is therefore 0.4 °C below the assumed minimum. This is a hypothetical measurement difference, not a proposed food-safety limit.
Apply the earlier corrective-action framework. FDA’s guidance under Principle 5 identifies three elements: determine and correct the cause, determine the disposition of non-compliant product, and record the actions taken. In this example, connect the observation to the affected product and document the responsible person’s disposition decision; related investigation concepts appear in out-of-spec handling.
A later reading at L meets the assumed temperature minimum at that later observation. It does not, by itself, resolve the disposition of product associated with the earlier reading.
Case two: one monitoring observation is undocumented
Assumptions: the relevant plan calls for 20 monitoring observations during a defined production run. Only 19 observations are documented. These counts are illustrative, not a universal monitoring frequency.
Documented-observation coverage = 19 observations ÷ 20 observations × 100 = 95%. Missing observations = 20 − 19 = 1 observation. The units are observations and percent.
Here, 95% describes evidence coverage only. It is not a compliance score, food-safety result or acceptable threshold. The count alone cannot establish whether monitoring occurred without documentation, a record failed to transfer, or the observation was never made.
Use the missing-observation recovery approach above: seek the original record and reconcile its run, time and identity. Until resolved, the missing result—and whether it met the critical limit—remains unknown. Do not substitute a neighbouring reading or let the percentage decide product disposition.
10Common CCP failures and the controls that expose them
Use these practical diagnostic examples to locate a gap, not to estimate how often failures occur. Each control points back to its owning topic above; the table adds no legal requirements.
| Failure scenario | Diagnostic question | Control or evidence |
|---|---|---|
| CCP designation without a documented hazard rationale | Which hazard explains this step’s designation? | Determination record: connect the hazard, step and control rationale. |
| Limit without an adequacy rationale | What supports this boundary for the hazard and process? | Critical-limit support: locate the applicable scientific or technical basis. |
| Record contains only a status | Which measurement or observation supports “pass”? | Monitoring evidence: trace the status to its underlying observation. |
| Mismatched product reference | Does the transferred record identify the product actually monitored? | Handoff reconciliation: compare the original and receiving references. |
| Process correction without a product-disposition decision | Is the affected product addressed separately from restoring the process? | Corrective action: locate the documented product decision. |
| Routine record checking treated as the entire validation argument | Where is the support that the plan can control the hazard? | Validation: distinguish effectiveness support from implementation checks. |
For related operational context, see the shift handover report for communicating unresolved record issues and the critical process parameter glossary for parameter terminology. Use the owning topics above for the full reasoning rather than treating this index as a standalone approval checklist.
11A source-attributed implementation and review checklist
Use these examples from FDA guidance Appendix G as a review aid for your HACCP system—not as mandatory review elements for all manufacturers:
- Review CCP monitoring records.
- Review records for deviations and corrective actions.
- Validate critical limits to confirm they adequately control significant hazards.
- Validate the HACCP plan, including on-site review.
- Review modifications to the HACCP plan.
- Sample and test to verify CCPs.
Keep these guidance examples separate from the sector-specific legal requirements mapped above. Finish with two scope checks:
- Meat/poultry: For establishments subject to Part 417, use the meat/poultry mapping above and its distinct provisions.
- Juice: For processors subject to Part 120, use the juice mapping above and its distinct provisions.
Frequently asked questions
Q.How should a CCP be monitored when continuous measurement is not possible?+
FDA’s Principle 4 guidance calls for a monitoring frequency and procedure reliable enough to indicate that the CCP remains under control. Statistically designed data collection or sampling can support this approach; the guidance does not prescribe one interval for every process. Monitoring records should be dated and signed or initialled by the person monitoring. Related topics are the in-process check and contemporaneous recording.
Q.Why can finished-food microbiological testing be unsuitable for CCP monitoring?+
FDA’s Principle 4 guidance identifies two problems: microbiological tests take time, and sampling may not reliably detect contaminants. CCP monitoring commonly needs rapid results during processing. Physical and chemical measurements are therefore often preferred for controlling microbiological hazards. FDA illustrates this with pasteurised milk: monitoring heating time and temperature rather than testing heated milk for surviving pathogens. The guidance also acknowledges situations where microbiological testing has no alternative. See microbial testing gates.
Q.Which changes in equipment, ingredients or processing can prompt verification?+
FDA’s verification guidance calls for verification to assess whether changes in the process, equipment or ingredients mean the HACCP plan should be modified. It also identifies a separate purpose after modification: confirming that changes were implemented correctly. Emerging product-safety concerns and foods implicated in foodborne disease are additional circumstances listed in the guidance. Related operational topics include change control and equipment maintenance management.
Q.When can supplier certificates and storage records support a CCP?+
FDA’s Appendix H gives specific examples: supplier certification records documenting an ingredient’s compliance with a critical limit, processor audit records verifying supplier compliance, and storage records when ingredient storage is a CCP. Its storage examples include time and temperature. These examples connect the record to the relevant critical limit or storage CCP, rather than treating every supplier document as CCP evidence. Related topics include lot pedigree and frozen-food warehousing.
Q.When are packaging, labelling or sealing records relevant to HACCP food-safety controls?+
FDA’s Appendix H includes records indicating compliance with critical limits when packaging materials, labelling or sealing specifications are necessary for food safety. The qualifying point is the food-safety role of those specifications, not simply that packaging or labelling occurs. The example concerns evidence of compliance with critical limits; it does not describe a general packaging-document checklist. For the related topic of specification information, see material master data.
Q.Can one juice HACCP plan cover several juice types?+
Under 21 CFR 120.8(a)(2), a plan must be specific to each type of juice, but “The plan may group types of juice products together, or group types of production methods together, if the food hazards, critical control points, critical limits, and procedures required to be identified and performed by paragraph (b) of this section are essentially identical,” provided features unique to a product or method are clearly delineated in the plan and observed in practice. Section 120.8(a)(1) separately requires the plan to be specific to each location where juice is processed. This grouping provision belongs to the juice rule and should not be assumed for other product categories.
Q.What information may a HACCP verification report contain under FDA guidance?+
FDA’s verification-report guidance says reports may address the presence and adequacy of the plan and its administrators; CCP monitoring records; direct recording during operation; certification of monitoring-equipment calibration and working order; corrective actions; sampling and testing methods; plan modifications; monitoring personnel’s training and knowledge; and validation activities. This is a guidance list of possible report content, not a universal mandatory report template. Related topics are audit management and data integrity.
Q.Who should oversee corrective actions, and when might expert advice help?+
FDA’s Principle 5 guidance assigns oversight to people with a thorough understanding of the process, product and HACCP plan. The plan should identify who implements corrective actions and provide for recording the actions taken. Experts may be consulted, as appropriate, to review information and help determine the disposition of non-compliant product. The guidance describes the necessary understanding rather than naming a particular job title. See also deviation management.
Primary sources
Explore this topic
CCP sits inside this topic cluster in our glossary. Every neighbour is one click away.
HACCP, FSMA, allergen control and the GFSI-recognised certification schemes.
Want to see how CCP could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
