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.9ISO/IEC 17025:2017 · Make the management system work

ISO/IEC 17025 clause 8.9: turn management review into laboratory decisions

Clause 8.9 requires laboratory management to review the system at planned intervals for continuing suitability, adequacy and effectiveness, including policies and objectives related to ISO/IEC 17025. Inputs must be recorded, and outputs must record decisions and actions. The purpose is informed management direction, not simply completion of a meeting agenda.

What clause 8.9 requires in practice

Clause 8.9 applies under Option A. Laboratory management reviews its management system at planned intervals to make sure it remains suitable, adequate and effective, including the policies and objectives related to meeting the standard.

The inputs to the review are recorded. They cover changes in internal and external issues; whether objectives were met; whether policies and procedures are suitable; the state of actions from earlier reviews; recent internal audits; corrective actions; assessments by external bodies; changes in the volume, type or range of work; customer and personnel feedback; complaints; the effectiveness of improvements; adequacy of resources; results of risk identification; outcomes of the assurance of validity of results; and other factors such as monitoring and training.

The outputs record all decisions and actions on at least four matters: effectiveness of the system and its processes, improvement of laboratory activities, provision of resources and any need for change.

Assemble the full input picture

The required inputs cover relevant internal and external changes, fulfilment of objectives, suitability of policies and procedures and progress on earlier review actions. Include recent internal audits, corrective actions and assessments by external bodies. These sources show whether known weaknesses are being addressed and whether the system still fits the laboratory.

Review changes in work volume, type and activity range, customer and personnel feedback, complaints and the effectiveness of improvements. Include resource adequacy, risk-identification results, outcomes from assurance of result validity and other relevant matters such as monitoring and training. Do not reduce the review to commercial performance while omitting technical capability.

The standard's list is a minimum input requirement, not a prescribed slide-deck format. Information can be assembled efficiently from existing records, but it must be sufficiently clear and current to support decisions. A list of document names without analysis may leave management unable to judge significance.

ISO/IEC 17025 consulting & certification support

Get clause 8.9 right the first time — with a global leader in ISO/IEC 17025 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.

Why management review matters to laboratory leaders

Management review is where the owner or director of a laboratory sees the whole picture at once: complaints, audits, equipment problems, workload and staffing. Without it, each issue is handled in isolation and patterns stay invisible.

The review also turns information into resource decisions. A laboratory that is growing may need more people, equipment or review capacity, and the review is the formal moment to say so and to commit. For accreditation purposes, the records show that senior management directs the system rather than leaving it to a quality officer. That visible ownership is a strong signal of a reliable laboratory.

How to implement clause 8.9

Prepare the review as a decision meeting, with information that has already been interpreted rather than merely collected. A review that simply reads out figures is a missed opportunity. Aim for a meeting where each input produces a view on what is working, what is not and what management will now do. Keep the minutes short, specific and owned by named roles.

  1. Set the review dates and the people who must attend, including technical and quality leaders.
  2. Assemble each required input from existing records, adding a short comment on what it means.
  3. Look across inputs for patterns, for example complaints that match audit findings or equipment trouble that matches workload growth.
  4. Discuss growth and change in scope alongside available resources and competence.
  5. Record the decisions and actions on effectiveness, improvement, resources and change, with owners and target points.
  6. Track those actions and report their status as an input to the next review.

Interpret the evidence before deciding

What counts as evidence

Compare performance with objectives and technical needs. Examine patterns across monitoring, complaints, audits and corrective actions. A recurring result issue may indicate a shared method, competence or system problem rather than unrelated incidents.

Consider changes in scope and workload alongside resources. Growth can expose gaps in authorisation, equipment availability or review capacity. A management review should bring those connections to the decision-makers instead of treating each department's report as an isolated update.

Record decisions and actions

Clause 8.9.3 requires outputs addressing at least system and process effectiveness, improvement of laboratory activities in relation to the standard, provision of needed resources and necessary changes. Record what management decided, including relevant actions. Assigning owners and due dates is a practical way to make action effective, though the clause does not prescribe one action-table layout.

Follow previous actions at the next appropriate review and through operational management. A decision that remains unimplemented can undermine the system even when minutes are well written. Planned intervals should suit the laboratory and applicable requirements; the standard does not impose one universal annual meeting date.

Two illustrative management reviews

Illustrative example 1

A calibration laboratory's workload grows while report-review capacity remains unchanged. The review combines turnaround information with authorisation, competence and error evidence. Management decides on appropriate resources and controlled service commitments rather than simply demanding faster release.

Illustrative example 2

A materials laboratory sees repeated monitoring warnings alongside customer complaints and incomplete corrective actions. Management reviews the combined evidence, prioritises the technical investigation and resources, and records the needed changes. A statement that “all departments are generally satisfactory” would ignore the available evidence.

Automate™ on Effivity · included in every Sterling engagement

Keep clause 8.9 alive in Effivity

Record what you decided under clause 8.9, 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/IEC 17025 programme.

Evidence and common weaknesses

Common weaknesses

Retain recorded inputs and outputs that show the basis of management's decisions. An agenda, attendance list and minutes may contribute, but they are not sufficient if required topics or decisions are missing. Keep technical detail accessible through linked records rather than overwhelming the meeting with unfiltered data.

Avoid copying last year's conclusions, omitting personnel feedback, treating external assessments as the only performance evidence, or closing actions without checking what was achieved. The review should demonstrate active management of laboratory capability and system effectiveness.

Frequently asked questions

Must management review be held annually?

The standard requires planned intervals, not one universal annual schedule. Choose an arrangement suited to the laboratory and meet any applicable external requirements.

Can inputs be reviewed through several connected meetings?

A practical arrangement may use connected reviews, provided management addresses the required inputs and outputs coherently and retains records demonstrating the complete review.

Is an attendance record enough to prove management review?

No. Required inputs and output decisions and actions must be recorded. Attendance alone does not show whether management evaluated suitability, adequacy and effectiveness.

Turn this requirement into reliable laboratory practice

Sterling can help turn laboratory performance information into a focused management review and actionable programme. Bring your current agenda and key technical concerns to a free consultation to identify missing inputs, decisions and resource priorities.

Build the team's understanding through ISO/IEC 17025 Awareness. Discuss the relevant scope, employee learning and agreed access to Effivity ISO & GRC automation software with Sterling; laboratory technical decisions remain with competent, authorised personnel.

ISO/IEC 17025 requirements hub · Management-system overview · Result-validity evidence · Risk and opportunity actions · Internal audits

Source basis and reading note. This is original practical guidance for ISO/IEC 17025:2017. Use an authorised copy for definitive requirements. Illustrative examples describe hypothetical situations, not client results. Implementation methods are distinguished from requirements; independent bodies decide accreditation for a defined laboratory scope 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/IEC 17025 in your organisation.