Is a management review mandatory?

For a certified management system under, for example, ISO 9001, 14001 or 45001, the standard expects top management to review the system, and the certification body checks this. Without a certificate no standard enforces it, but it remains the most efficient way to turn improvements into decisions. Check the current requirements with the publisher of your standard.

Can the management review be combined with the management team meeting?

Yes, as long as the topic gets its own agenda item with prepared input and the outcomes are recorded separately in the minutes. An auditor wants to see which inputs were discussed and which decisions were taken. If the management team meeting is already overloaded, plan a separate session, otherwise it gets buried.

How long does a management review take?

With good preparation a review fits in an hour and a half to two hours. If it takes longer, the input is usually too extensive or topics from daily operations are being pulled in. Better to split it into a short quarterly meeting and a thorough annual review, so that decisions stay sharp.

What do you show the auditor as evidence?

The agenda and the input used, the minutes with decisions and actions, and proof that those actions were followed up. Make it visible that management itself reviews and decides, and that the QHSE department only prepares. Also show how decisions come back in objectives, budget or procedures.

Management review example: agenda and minutes

What is a management review and why hold one?

A management review is a fixed meeting in which top management looks at the management system as a whole. Not this week's individual incidents, but the question: does our system still fit our direction, does it deliver results and do we have enough resources to improve? Management takes decisions on this and records them.

Standards such as ISO 9001, ISO 14001 and ISO 45001 expect such a review by the highest level of management, and a certification body will normally ask about it. Apart from the standard, it is also the moment when improvements get budget and attention. Without it, quality, safety and environment remain a matter for a few specialists.

What inputs do you put on the table?

A good review stands or falls with preparation. The QHSE coordinator collects the data in advance and puts it on one or two pages, with trends instead of isolated numbers. Those papers go to the participants at least a week beforehand.

The standard itself also names topics that must be covered; you will find those with the publisher of the standard. The list below is a practical interpretation. Adapt it to your own system and leave out what does not apply to you:

Status of the actions from the previous review
Changes in the organization, the market, legislation or the expectations of stakeholders
Progress on objectives and KPIs, with the trend over several periods
Customer satisfaction, complaints and quality deviations
Incidents, near misses and inspection results
Outcomes of internal and external audits
Performance of suppliers and contracted parties
Status of the risks and opportunities
Available resources: people, time, budget and training

How often, and with whom?

Most organizations hold the management review at least once a year. What applies to you depends on the standard or certification scheme you work with; check this with the publisher of the standard or with your certification body. In a fast-changing organization, a quarterly round with a smaller agenda is often more useful than one heavy session a year.

Around the table sit the directors or the management team, joined by the QHSE coordinator as preparer and secretary. Invite department heads for their part of the system. Decisions must be taken by people with authority, otherwise they remain discussion points without an outcome and everyone waits for the next round.

If you run a small company, the review can be shorter and more informal: an hour with the owner and two or three key people, with the input on one A4 page. The form matters less than the fact that decisions are really made and recorded.

An example agenda for 90 minutes

Do not plan more time than needed and keep the order fixed: first look back, then results, then look ahead and decide. That keeps the conversation on the big picture and prevents it from sinking into the details of one department. The chair watches the clock and makes sure the last minutes really go to decisions.

An agenda that works well in practice looks like this. The timings are a guideline: give the topic that is most pressing in this period, such as a serious incident or a series of complaints, more room and keep the rest shorter.

Opening and look back: have the actions from last time been completed? (10 minutes)
What is changing in our environment and organization? (10 minutes)
Results: objectives, customers, safety and environment (25 minutes)
Audits and findings: what do we see recurring? (10 minutes)
Risks, opportunities and suppliers (10 minutes)
Resources and improvement opportunities (15 minutes)
Confirm decisions and actions (10 minutes)

Decisions and actions: what it is really about

The outcome matters more than the presentation. Let every agenda item end with a decision, or with a deliberate decision to do nothing. Typical decisions concern improvement opportunities, changes to the management system, new or adjusted objectives and the release of resources such as budget, people or time.

Translate every decision into an action with an owner and a date. An action without a name stays on the shelf. The next review therefore opens with the question of what became of the previous actions, so management sees whether decisions really set something in motion.

Minutes in miniature: an example

Minutes do not have to be a report. An auditor wants to see that the input was discussed and that management took decisions. So note per topic briefly what the conclusion was, which decisions follow and who does what, and leave out the discussion itself. A fictional example for an installation company shows how short that can be:

Look back: most actions are completed. The supplier evaluation moves to next quarter (owner: purchasing).
Results: the number of complaints is falling, the number of reported near misses is rising. Management sees this as a possible sign of a better reporting culture and asks for an analysis.
Decision: the objective for projects delivered on time stays. The objective for the number of reports is raised.
Decision: release budget for extra fall protection training (owner: HR, date: end of quarter).
Action: the QHSE coordinator presents the trend in near misses to the management team at the next review.

Common mistakes

The classic is a presentation in which the QHSE coordinator reads out numbers while management looks on. That is not a review, only a report. You also see management teams that receive the input only on the spot and therefore cannot decide, or that mostly confirm what the coordinator already proposed.

Other mistakes: discussing only quality while the system also covers safety and environment, holding the review just before an audit to tick it off, and minutes without owners and dates. It then looks like a formality and behaves like one.

How BrydgeOne supports this

In BrydgeOne you compile the management review from live data in the Management review module, so you do not have to gather the inputs by hand. With Objectives & KPIs you steer on measurable goals and trends, Audits supplies the findings and Actions tracks the follow-up of the decisions.

Management review: example with agenda, inputs and minutes