Management Review
Management Review — a planned review by top management of how well the management system is performing, with decisions and actions recorded.
Editorial definition: The QHSE Standard, updated 3 October 2026 · https://qhsetech.com/glossary/management-review
Scope: The frequency, inputs and records depend on the standard or programme followed and on the organisation's own procedure.
Example for your evaluation: Follow one audit finding from the review input to the recorded decision and its closure.
What the sources say a management review is for
ISO's page for ISO 14001:2026 lists carrying out internal audits and management review among the steps in the certification process. ISO's page for ISO 9001:2026 (Edition 6, published 16 September 2026) says the standard requires organisations to monitor, measure, analyse and evaluate the performance and effectiveness of the quality management system, and emphasises improvement based on the results. The standards' own lists of what a review must consider are clause text, which this page does not reproduce; read the edition you work to.
OSHA's Recommended Practices for Safety and Health Programs, which sit outside the ISO framework, describe the same loop. Once a programme is established, employers should periodically, and at least annually, step back and assess what is working and what is not. OSHA says to involve workers in the evaluation, including in reviewing information such as incident reports and exposure monitoring results, and to correct shortcomings promptly. It adds that an evaluation may also be triggered by a change in process or equipment, or by an incident such as a serious injury, significant property damage or an increase in safety-related complaints, and that results should be shared within the workplace.
In practice the common thread is a decision, not a presentation. A review is useful where it examines evidence (indicators, audit findings, incident and corrective-action data, changes, objectives), reaches a view on whether the system is suitable and effective, and assigns resources or actions with owners and dates. OSHA's pages say both leading and lagging indicators belong in that evidence. Which items a certified organisation must show to a certification body is a matter for the standard and the body concerned, so this page gives no list.
What a management review record holds in software
- The date, the attendees and the role of each (top management, process owners, workers' representatives where used), with the agenda kept as a controlled record.
- The inputs tabled, each linked to its source: audit results, performance and compliance data, incident and corrective-action trends, feedback from customers and other interested parties, changes, risks and objectives.
- The conclusions on suitability and effectiveness, and the decisions on improvements, resources and changes to the system.
- Actions with owner, due date and status, carried into the next review so that they are not lost.
- Evidence for any decision not to act, with the reason.
- Follow-up from earlier reviews: what was agreed, what was done and whether it worked.
Management review, internal audit and board reporting
An internal audit examines evidence against criteria and reports findings; a management review is where top management considers those findings with other information and decides what to do. A leadership report of KPIs may be an input, but a dashboard sent to executives is not a review unless decisions follow and are recorded. Conversely, a safety committee meeting, which usually deals with operational matters, is not automatically the management review, although it may feed it.
A hypothetical example: a quarterly review in a 140-person plant
This case is invented and describes no real organisation. A plant with combined quality and safety systems holds a management review each quarter. A week beforehand the quality and safety leads assemble the inputs: audit findings and their status, the rate and severity of incidents with the leading indicators the site tracks, open corrective actions and their ageing, customer complaints, a change in a legal requirement, and progress on each objective. Two items stand out: three corrective actions overdue by more than two months, and a rise in near-miss reports from one area.
In the meeting the managing director asks for reasons rather than numbers. The overdue actions share an owner who also runs a new product line, so the review reassigns two of them and allocates a day a week of a supervisor's time. The near-miss rise is read as better reporting after a campaign, but the group asks for the same area's inspection results before accepting that. Decisions and actions go into the minutes with owners and dates, and the next review begins by checking them. An auditor can follow one item from the audit finding to the review decision and on to its closure.
Common misunderstandings about management review
- A management review is not an annual slide deck. How often it takes place is a matter for the standard and the organisation's own procedure; OSHA's programme guidance says periodic and at least annual evaluation, and also says an incident or a change can trigger one.
- Attendance is not review. The conclusions and decisions are the output, so minutes that record only that a presentation was given do not show that a review took place.
- Top management is not a courtesy. A review without the people who can allocate resources and change priorities can only recommend.
- Reviewing KPIs alone is not enough. Indicators such as injury rates say little about whether the system works; OSHA recommends both lagging and leading measures, and evidence from audits and corrective actions adds what the numbers miss.
- One review for several systems is possible but needs care. Combined reviews are common in integrated systems, yet decisions should show which system each applies to, because requirements and owners differ.
How management review relates to other glossary terms
Management review is where the outputs of many other processes meet, so its neighbours are the systems it reviews and the records it draws on.
- ISO 9001: the quality standard, whose published edition is now 2026, with its own expectations for reviewing the system.
- ISO 14001: the environmental standard, with its own aspects and compliance records to bring to a review.
- ISO 45001: the occupational health and safety standard, with its own incident, hazard and participation records to bring to a review.
- CAPA: where open and recurring corrective actions and their effectiveness are examined.
- QHSE: the combined scope in which one review often covers quality, safety and environment.
Records and evidence that usually exist for management review
- The procedure that sets the frequency, participants, inputs and records.
- A calendar or log showing that reviews took place at the planned intervals, and the reason for any change.
- The input pack for each review, with the source of each item.
- Minutes with decisions, resource allocations and actions.
- Action tracking from one review to the next, with evidence of closure.
- Evidence that outputs reached the people affected, such as revised objectives or changed procedures.
What a software tool needs to capture for management review
- A review record that pulls inputs from audits, incidents, actions and objectives, linked to their source records rather than pasted summaries.
- Agenda templates that can be adapted by system or site and kept under version control.
- Minutes that record decisions and actions separately from discussion, with owners and dates.
- Carry-over of open review actions into the next review, with status and history.
- Attendee and role recording, and permission controls for confidential items.
- Reports that show review frequency against the planned schedule and the outcome of earlier actions.
Catalog profiles documenting management review
Same rule for every product: tagged “Quality Management”, “ISO Management”, “Audit Management”, “Compliance Management” or “EHS Management”, with a sourced management review or review meeting capability in its record, or one the vendor stated to us, labelled as vendor-stated. Documented and conditional capabilities qualify; check the linked scope before treating a module as included.
Tekmon pays for a sponsored placement (above); its place in this list follows the same rule as every entry. How lists are ordered
Effivity · Management review records and follow-up · Documented
Vendor source · Profile checked
Tekmon · Management Review (vendor-stated) · Vendor-stated, not yet publicly confirmed
Ask to see it in a demo · Profile checked
Q-Hub · Risk assessment, safety observations and forms · Conditional
Vendor source · Profile checked
All 3 matching profiles are shown. Documentation review, not hands-on testing or a claim of compliance.
Related software
Frequently asked questions
How often should a management review take place?
At the interval your procedure and the standard you follow set. OSHA's recommended practices say evaluate at least annually, with an earlier review after a change or serious incident; choose the frequency from risk and change, not only from the calendar.
Who must attend?
Top management as defined in your system, together with the people who own the processes and data under review. Check the edition of the standard and your certification body's expectations.
Can the review be combined with other meetings?
Yes, if the inputs are covered and the decisions are recorded. The record should show which management system each decision applies to.
More quality terms
Related guides
- KPI (Key Performance Indicator) — definition, software & FAQs
Definition of a key performance indicator.
- ISO 19011 — definition, software & FAQs
Definition of ISO 19011.
- Leading Indicator — definition, software & FAQs
Definition of an indicator of preventive activity.
- Lagging Indicator — definition, software & FAQs
Definition of a lagging indicator.
- Recordable Incident — definition, software & FAQs
Definition of a recordable incident.