hello@sterling-grc.com +1 201 263 4443 New York ISO & GRC consulting in 60+ countries
SterlingInternational Consulting Talk to a consultantTalk to us
Clause 8.7ISO 22000:2018 · Connect food safety hazards with effective controls

ISO 22000 clause 8.7: trust the measurements used for food safety decisions

ISO 22000 clause 8.7 requires evidence that monitoring and measuring methods and equipment used for PRPs and the hazard-control plan are adequate. It covers equipment controls, measurement traceability, assessment of earlier results when requirements are not met, and validation of relevant software. A calibration sticker is useful, but it does not answer every question about measurement reliability.

What clause 8.7 requires in practice

Food safety decisions often depend on a number on an instrument or a reading in software. Clause 8.7 asks the organisation to show that the methods and equipment used to monitor and measure PRPs and the hazard control plan are adequate for the task. Equipment is calibrated or verified at set intervals before use, adjusted when needed, identified so its status is known, protected from adjustments that would spoil results, and protected from damage. Results are kept, calibration is traceable to international or national measurement standards, or the basis used is recorded where none exist. If equipment or the environment is found to be out of requirements, the validity of earlier results is assessed and action taken on equipment and affected product. Software used for monitoring and measuring is validated before use and changes are controlled.

Establish suitability for the actual task

Identify what must be measured or observed and the decision that depends on the result. The method and equipment need suitable capability for that use. An instrument appropriate for a general indication may be unsuitable for a decision close to a critical limit.

Establish calibration or verification at defined intervals so equipment is within its required status before use. Adjust or readjust where necessary, identify calibration status, protect against invalidating adjustments and prevent damage or deterioration.

Retain calibration and verification results. Calibration must be traceable to international or national measurement standards; where none exist, retain the basis used for calibration or verification. Do not assume a certificate's presence establishes that its scope and results suit the intended use.

ISO 22000 consulting & certification support

Get clause 8.7 right the first time — with a global leader in ISO 22000 implementation

A Sterling consultant works the requirement through with your team, links it to the rest of the system and carries it to certification readiness. Expert and experienced consultants, 8,100+ client engagements in 60+ countries.

Look backwards when reliability is in doubt

If equipment or the process environment does not meet requirements, assess the validity of previous measurement results. Take appropriate action concerning the equipment or environment and any affected product. Maintain the assessment and resulting action as documented information.

This retrospective question is often missed. Repairing or replacing an instrument restores a capability going forward, but earlier decisions may still need evaluation. Determine the relevant period and evidence with competent technical input.

Connect the assessment with product-control arrangements. Do not assume every instrument problem has identical product consequences, or that every result remains acceptable without examination.

Control software used for monitoring and measuring

Relevant software needs validation before use by the organisation, supplier or a third party, with validation information maintained by the organisation. It also needs timely updating. Changes, including configuration changes to commercial software, must be authorised, documented and validated before implementation.

The standard recognises that widely used commercial software within its designed application range can be considered sufficiently validated. That does not justify ignoring a local configuration or use outside the supported range. Assess what the software actually does in the food safety decision.

Keep software changes aligned with instructions and user competence. A correct calculation can still be misused if units, product associations or displayed status are misunderstood.

Why clause 8.7 matters to the business

A control is only as trustworthy as the reading that tells you it is working. An uncalibrated thermometer or an uncontrolled spreadsheet can allow unsafe product to pass or safe product to be thrown away, and neither shows up until someone asks how the number was obtained. Looking back at earlier results after a fault is particularly valuable, because it turns a single instrument problem into a bounded, managed decision rather than an open question. Customers, certifiers and regulators regularly test this area, so having it in order reduces both risk and audit friction.

How to implement clause 8.7

Start from the decisions that depend on measurements, and work out what each needs from its equipment. Prioritise by consequence, giving the closest attention first to the instruments and software behind CCP decisions, then widening the effort to the measurements that support OPRPs and PRPs.

  1. List every instrument, observation method and software tool used to monitor PRPs and CCPs or OPRPs, and the decision each supports.
  2. Check each is suitable for that decision, including its range, resolution and conditions of use.
  3. Set calibration or verification intervals, label status on the equipment, and protect settings and handling.
  4. Make sure calibration can be traced to recognised measurement standards, or record the basis used where none exist.
  5. Write a rule for what happens when equipment fails a check: remove it from use, review earlier results back to the last good check, and decide what to do about affected product.
  6. Validate software used for measuring or monitoring before use, and control any configuration or version change.
  7. Retain calibration, verification, validation and assessment records under document control.

Illustrative food-processing example

Illustrative example 1

A processor finds that an instrument used in a monitoring decision does not meet its requirements. The team removes it from inappropriate use, assesses previous results and identifies the product decisions potentially affected. It records the basis and actions rather than closing the issue with a replacement instrument.

Illustrative example 2

The assessment uses the actual error and process context. This example does not prescribe a universal correction factor or automatic release rule.

Automate™ on Effivity · included in every Sterling engagement

Keep clause 8.7 alive in Effivity

Record what you decided under clause 8.7, link it to the records and controls it affects, and let the review date trigger the next look. Effivity is the ISO & GRC software used in 50+ countries — and part of every Sterling ISO 22000 programme.

Illustrative food-logistics example

A food-logistics operation changes software that converts monitoring data into a displayed result. Before implementation, it checks the authorised configuration and validates the relevant function against suitable expected outcomes. The review discovers a unit-display inconsistency.

The organisation corrects the issue before use and retains evidence of the validation. A supplier's general product description would not have established the suitability of that local configuration.

Evidence and common weaknesses

What counts as evidence

Useful evidence links the measurement task with equipment or software identity, suitability, calibration or verification, validation where relevant, status and action after problems. Keep records sufficiently clear to support investigation.

Common weaknesses

Common weaknesses include relying only on stickers, overlooking environmental effects, accepting unexplained calibration results and changing spreadsheet formulas without review. Another is assessing the instrument but never asking which earlier product decisions depended on it.

Read this requirement with CCP and OPRP monitoring and the operation overview.

Frequently asked questions

Does a calibration certificate prove suitability?

Not by itself. Its scope, results and measurement capability need to suit the intended food safety decision.

Must previous results be reviewed after a problem?

Yes, when equipment or the process environment is found not to meet requirements. Assess validity and take appropriate action for affected product.

Do spreadsheet changes matter?

They can where the spreadsheet is used for FSMS monitoring or measuring. Relevant changes need appropriate authorisation, documentation and validation.

Review the measurement behind a critical decision

Discuss a monitoring and measurement evidence review with Sterling. Scope can connect technical competence, records and suitable Effivity ISO & GRC automation software support without replacing specialist calibration work. Explore ISO 22000 Food Safety Awareness and the requirements hub.

Source basis and reading note. This is original practical guidance for ISO 22000. Use an authorised copy for definitive requirements. Illustrative examples describe hypothetical situations, not client results. Implementation methods are distinguished from requirements; independent bodies decide management-system certification outcomes. Issuer standard record: iso.org.
Disclaimer. This guide is provided for general information only. It is not the text of the standard, not legal or professional advice, and not a representation of how any certification body will assess your organisation. Sterling International Consulting accepts no liability for any loss arising from reliance on it. Requirements are applied to each organisation's own context through an engagement; contact us to implement ISO 22000 in your organisation.