The same template every year, the same sentences and a one-line conclusion that “the ISMS was found to be effective”: management review minutes are the record auditors most easily recognize as box-ticking. Yet management review is the only point where the measurement, audit and risk information gathered in the ISMS turns into top management decisions. If no decisions come out of it, the meeting was a waste. Below we turn the inputs and outputs of ISO 27001 clause 9.3 into a workable agenda, and give data sources, minutes structure and action tracking with examples.
The purpose and frequency of management review
ISO/IEC 27001:2022 clause 9.3.1 requires top management to review the ISMS at planned intervals to ensure its continuing suitability, adequacy and effectiveness. These three concepts also set the meeting’s questions:
- Suitability: Does the ISMS still fit the organization’s context and strategy?
- Adequacy: Are the scope, resources and controls enough to meet the requirements?
- Effectiveness: Are objectives being met, and are risks coming down to the desired level?
The standard doesn’t give a frequency. A full meeting once a year is the most common practice; but a single annual meeting can leave important decisions that arise during the year waiting for months. A firewall replacement awaiting budget approval, or a decision on migrating a server whose support is ending, shouldn’t wait until December. A practical model is to run a full management review once a year together with short quarterly ISMS reviews. If the quarterly meetings don’t discuss all the mandatory inputs, don’t call them management reviews; call them interim reviews that produce inputs for the management review. It’s expected that at least one management review has been held before the Stage 2 certification audit.
Mandatory inputs and data sources
Clause 9.3.2 requires the management review to consider the inputs below. The table shows where each input is fed from in practice:
| Input (9.3.2) | Data source | Presented by |
|---|---|---|
| a) Status of actions from previous reviews | Action tracking list | ISMS manager |
| b) Changes in internal and external issues | Context analysis revision | ISMS manager |
| c) Changes in the needs and expectations of interested parties | Interested parties table, new contracts, legislation tracking | Legal / ISMS manager |
| d1) Nonconformities and corrective actions | Corrective action log, trend chart | ISMS manager |
| d2) Monitoring and measurement results | KPI report (patching, backup, access review, etc.) | IT manager |
| d3) Audit results | Internal and external audit reports | Internal audit lead |
| d4) Fulfilment of information security objectives | Objective planning cards | Objective owners |
| e) Feedback from interested parties | Customer audits, complaints, questionnaire questions | Sales / quality |
| f) Results of risk assessment and status of the risk treatment plan | Risk register, risk treatment plan | Risk owners |
| g) Opportunities for continual improvement | Suggestions log, post-incident reviews | All participants |
Input “c” was added as a separate item in the 2022 revision; how to keep the context and interested parties analysis is in the guide interested parties analysis. For input “d”, the standard explicitly asks for trends: not a single period’s value but comparison with previous periods. Presenting measurement data as a series over the last three or four periods makes the trend readable. How to write and measure objectives is explained in the guide information security objectives, and the program that produces audit results in the guide internal audit program.
Don’t prepare the KPI report in row d2 by hand. The patch management tool’s compliance report, the backup software’s job history and access review records should be pulled straight from the systems; numbers gathered in Excel the night before the meeting fall apart at the first question. Although not listed in the standard, incident statistics, supplier assessment results, business continuity exercises and resource status (budget, staff) are useful inputs to add to the meeting.
Sample agenda
Build the agenda around the logic of decision-making, not the order of the mandatory inputs. The agenda below is an example for an annual management review of about two hours:
MR-2026 AGENDA (example)
1. Opening, participants, status of previous review decisions [9.3.2 a]
2. Changes in context and interested parties [9.3.2 b, c]
- Security annexes of new customer contracts
- Changes in legislation
3. Performance summary (with trends) [9.3.2 d]
3.1 Status of objectives
3.2 KPI results
3.3 Internal / external audit findings
3.4 Nonconformities and corrective action status
4. Feedback from interested parties [9.3.2 e]
5. Risk assessment and risk treatment plan status [9.3.2 f]
- Residual risks proposed for acceptance (decision)
6. Improvement opportunities and proposals [9.3.2 g]
7. Decisions: needs for change, resources, new objectives [9.3.3]
8. Assigning actions and close
Send the presentation material to participants a few days before the meeting. Meeting time should be spent not on passing on information but on items requiring a decision: residual risks proposed for acceptance, a risk treatment action proposed for postponement, an improvement that needs budget. People don’t meet to read slides.
Active participation of top management
Clause 9.3 explicitly gives the review to top management; clause 5.1 also requires top management to demonstrate leadership and commitment to the ISMS. A weakness you may come across is the meeting turning into a self-assessment by the ISMS manager. Typical signs by which auditors recognize a box-ticking management review:
- The minutes contain only “information was given” statements instead of decisions
- The same text being reused every year with the date changed
- Accepted residual risks being recorded without management approval
- Nobody with decision authority on the participant list
- Actions in the minutes having no owner or date, or their status not being asked about at the next review
- When the auditor talks to top management, they don’t know the ISMS objectives and significant risks
Certification auditors usually hold a short interview with someone from top management. The manager being able to explain the decisions made in the management review and their reasons in their own words is stronger evidence than the record. A memorized sentence is spotted immediately.
Outputs: decisions, changes, resources
Clause 9.3.3 requires the results of the management review to include decisions related to continual improvement opportunities and any needs for changes to the ISMS; documented information must be kept as evidence of the results. Resource decisions aren’t listed separately within 9.3.3 in ISO 27001; however, under 5.1 and 7.1, providing the necessary resources is top management’s responsibility, and the management review is the natural place to record these decisions. Typical outputs:
- A decision to change the scope, policy or objectives
- Acceptance of residual risks or a decision on additional risk treatment
- A decision on budget, staff, tools or external service resources
- Approval of the next period’s objectives
- Process improvements and assigned actions
Residual risk acceptance is the output that causes the most problems in the field. If the decision “The old production server can’t be disconnected from the network; the risk is accepted” is made without writing down whose signature it carries, with which compensating control (a separate VLAN, strict ACLs, monitoring) and until when it’s valid, two years later nobody can find the decision’s owner. For these decisions, the structure described in the risk treatment plan guide can be matched one-to-one with management review decisions.
Meeting minutes and action tracking
The minutes should follow the same structure as the agenda and contain a brief assessment and, where there is one, the decision for each input. Annexes (KPI report, audit summary, risk report) are linked to the minutes by reference. Keep a separate record for actions; that’s the only way tracking works:
| Field | Example content |
|---|---|
| Decision/action no. | MR26-04 |
| Agenda item and input | 5 – Risk treatment plan (9.3.2 f) |
| Decision | Budget approved for an endpoint detection and response solution |
| Owner | IT manager |
| Target date | End of period |
| Status and evidence | Purchase request no., installation record |
| Verification | At the next management review, under input 9.3.2 a |
Approval of the minutes (signature or electronic approval), the distribution list and the storage location are subject to document control rules. If the meeting was held online, the attendance record can also be kept as evidence.
Preparation checklist
- Has the status of actions from the previous review been updated?
- Has the context and interested parties analysis been reviewed?
- Are KPI and objective data ready, with trends?
- Are the internal audit report and corrective action status ready on a single page?
- Is the current status of the risk register and risk treatment plan ready?
- Are items requiring a decision clearly marked on the agenda?
- Will top management representatives with decision authority attend the meeting?
To design the indicators and reporting that feed the management review, see the management review and KPI design page; to have the ISMS cycle run externally throughout the year, the ongoing ISMS consulting page. The primary source for the clause texts is the ISO/IEC 27001 standard.
Frequently asked questions
Who should attend the management review?
The review is top management’s responsibility; that’s why managers with decision-making and resource authority over the ISMS should attend. The ISMS manager, IT manager, internal audit lead and, where needed, legal, HR or risk owners take part to present the inputs.
Is a management review once a year enough?
The standard doesn’t give a frequency; it requires planned intervals. A full management review once a year is common; adding quarterly interim reviews so important decisions aren’t delayed is good practice.
What must the management review minutes contain?
Sections showing all the inputs in clause 9.3.2 were considered, decisions on continual improvement and changes to the ISMS, actions with an owner and date, participants and approval details.
Can the management review be held in a single meeting in an integrated management system?
It can. However, each standard’s mandatory inputs must be discussed separately and be traceable in the minutes; the risk treatment plan and objectives specific to information security mustn’t get lost among general quality data.