PublishedISO 9001:2026 published 16 Sept 2026 · 2015 certificates must transition by 30 Sept 2029What changed →
Internal Auditor course (ISO 19011:2026):free until 31 Oct · then $59 for three monthsStart free now →
← Back to Clause Explorer
9.3.2ISO 27001:2022

Management review inputs

Plain-language summary

The set of things the management review must consider — actions from last time, changes in context and in what interested parties expect, how the ISMS is performing, feedback, the risk picture and improvement opportunities.

What the clause is really asking

The clause lists the inputs so that no review can quietly skip the uncomfortable ones. Top management considers: the status of actions from previous reviews; changes in external and internal issues relevant to the ISMS; changes in the needs and expectations of interested parties (new in 2022 — a new regulation, a customer's new security schedule, an insurer's new conditions); feedback on information security performance, including trends in nonconformities and corrective actions, monitoring and measurement results, audit results and the fulfilment of objectives; feedback from interested parties; the results of risk assessment and the status of the risk treatment plan; and opportunities for continual improvement. Each input is a question — what changed, what do the numbers say, where are we exposed — and the review record should show the question asked and answered, even when the answer is 'no change'.

What auditors look for

Auditors hold the minutes against this list. For each input they look for evidence it was considered with content, not a heading: the 'changes in interested parties' item should mention the actual new requirement; 'risk assessment results' should cite the register version and the top risks; 'audit results' should name the findings. They probe the 2022 addition specifically. They also look for the inputs being current — a review in November using metrics from March is not reviewing performance.

Typical evidence

Management review pack and minutes addressing every input with specifics; the data behind them: metrics report, audit summary, nonconformity and corrective action trends, risk register and treatment plan status, objectives status, interested-party feedback (customer audits, questionnaires, complaints, regulator correspondence); previous action register.

How to comply — recommendations

Make the input list the agenda template and never remove an item — write 'no change this period' where that is true. For each input attach the one-page evidence: the metrics trend, the audit coverage matrix, the top ten risks with movement, the treatment plan status, the objectives page, a summary of customer and regulator feedback. Ask the owner of each input to speak to it for two minutes and to propose a decision. Close the pack a week before the meeting so the review works from current data.

Common nonconformities

One or more required inputs not considered (most often changes in interested parties' needs, feedback from interested parties, or risk treatment plan status); inputs listed as headings without content; stale data; trends in nonconformities and corrective actions not analysed; objectives status not reported; previous actions not reviewed.

Related clauses

ISO 27001 4.1–4.2 (changes in context and interested parties), 6.1.2–6.1.3 and 8.2–8.3 (risk inputs), 6.2 (objectives), 9.1 (measurement results), 9.2 (audit results), 10.2 (nonconformity trends); ISO 9001 9.3.2 (similar input list).

Resources for this clause

Get the free ISO 27001:2022 Gap Analysis Checklist

Free, instant download. We'll only email you the occasional practical quality update — no spam, unsubscribe anytime.

Qlause provides interpretive guidance only and is not a substitute for the standard. Refer to your licensed copy of the relevant standard for the authoritative text.

Certification & implementation

Working on a certification or system implementation project?

Implementing ISO 9001, moving to the 2026 edition, getting ready for a certification audit, or stuck on a clause that doesn't seem to fit your operation? Tell us where you are and where you're stuck. We'll look at it and suggest a practical next step, or connect you with people we trust who can help.

Email hello@qlause.app

No sales pitch, no obligation — we read every message.