Every Management Review Topic Should End with a Decision

Yesterday a client asked me to go over her company's first management review and comment on it before their certification audit.

I opened the document and saw thorough work. She had covered all the right topics, the data was neatly organized, and overall the presentation looked good.

So I looked at the end of each section for what had been decided: what came out of the discussion, and who was doing what and by when.

There was almost nothing.

This is the pattern I usually see in medical device companies. Once a year, the quality manager prepares a presentation with charts of corrective actions, customer complaints and supplier performance.

Management listens, and the managers leave the meeting. The quality manager writes in the minutes that they discussed the topics (with a lot of copy-paste from the slides), and everyone signs.

A year later, it is the same presentation with different numbers.

This structure works against the management review discussion. When you present data without requiring a decision at the end of each topic, the meeting turns into a lecture with documentation.

And when the auditor arrives and asks, "What came out of this review? What changed?", the answer "we discussed it" is not enough.

First, where the data comes from: clause 8.4

Before talking about the management review itself, you need to understand what stands behind the data presented in it.

Clause 8.4 of ISO 13485 requires the organization to collect and analyze data on an ongoing basis throughout the year, not only in the run-up to the review. The aim is to demonstrate that the quality management system is suitable and effective, and to identify opportunities for improvement.

The data to be analyzed includes customer feedback, conformity to product requirements, process characteristics, complaints, supplier performance and audit results.

The important point is that this analysis does not wait for December. It happens in real time, when a complaint comes in, when a CAPA is closed, or when an internal audit reveals a finding.

By the time you reach the management review, you should have a full, analyzed picture of everything that happened during the year.

An organization that analyzes data only to prepare a presentation for the review misses the whole point of 8.4.

Ongoing analysis is what turns raw data into insights you can bring to the meeting and make decisions on.

What does clause 5.6 actually say?

Many organizations treat the management review as an event to tick off on a checklist, but clause 5.6 describes a mechanism. Top management must review the quality management system at planned intervals to make sure it remains suitable, adequate and effective.

Those three words are real questions that the meeting has to answer:

• Suitable: does the quality management system fit the type of products, the company's stage of development and the markets it operates in?

• Adequate: does it have everything it needs, such as procedures, forms and measurement methods?

• Effective: does it really prevent problems and achieve the quality objectives?

If the meeting ends and nobody has answered these questions, the review has not been completed.

What has to go into the meeting: clause 5.6.2

The outputs of the ongoing analysis under 8.4 are the basis for the management review input.

Clause 5.6.2 defines what has to be on the table, and none of these topics can be left out:

• Customer feedback and complaints

• Reports to regulatory authorities, if there were any

• Audit results, both internal and external

• Monitoring and measurement of processes and products

• Status of corrective and preventive actions

• Follow-up of actions from the previous management review

• Changes that could affect the quality management system, whether regulatory, operational or organizational

• Recommendations for improvement

• New regulatory requirements that have come into force

Each of these topics is an input, a source of information that needs to be analyzed and lead to a conclusion.

I wrote a checklist of the topics that must appear in a management review that breaks each topic down into concrete questions, including PMS under the EU MDR, risk management under ISO 14971, resources and training. I recommend downloading the checklist and comparing it with your current management review.

What has to come out of the meeting: clause 5.6.3

The output of the review must be decisions and actions in four areas:

• Improvement of the quality management system and its processes

• Improvement of the product in relation to customer requirements

• Changes needed in response to new or revised regulatory requirements

• Resource needs

According to the standard, data analysis that does not lead to a decision is analysis that has not been completed.

This is where the common pattern breaks down. The action items come at the end of the meeting, when everyone is tired, and they are written down in a hurry, sometimes without clear ownership and without a follow-up date.

By the next review they have disappeared, and the quality manager finds herself explaining to the auditor why there was no follow-up on actions recorded a year earlier.

Change the structure, not the content

The solution comes from changing the order of thinking in the meeting itself.

There is a difference between a dashboard and a decision board.

A dashboard presents data. A decision board presents the same data under a defined question: what are we deciding on the basis of this?

On a dashboard you will see: CAPAs opened: 7. Closed: 5. Average days to closure: 34.

On a decision board you will see the same numbers, but with a question:

Is the CAPA process working effectively? Two corrective actions are open past their due date. Is intervention needed?

In other words, at the end of each topic you have to choose one of two answers:

"No improvement needed" is a conscious decision.

"At this stage" signals that the organization's management reviewed the data and decided that no action is needed.

An organization that can say this with confidence, after reviewing the data, shows deliberate analysis.

An auditor who understands what to look for will value this more than a long list of action items that nobody follows up on.

Improvement does not wait for the review

This is the point that is easiest to miss.

The management review is not where you decide to improve. It is where you report on improvements that have already happened and decide on the next steps.

Improvements happen all the time throughout the year. A corrective action leads to a change in a procedure. An audit finding prompts an update to the training plan. A customer complaint reveals a defect that is then fixed in the process. These are real improvements that should not wait for December, but they do need to be documented and to appear in the review as part of a continuous story.

A successful review has two tracks:

Track A, what we improved: documentation of the improvements implemented during the year, linked to the data that led to them. This is the proof that the quality management system is alive and not just documented.

Track B, what we are deciding now: based on the data presented in the meeting, which actions we commit to for the coming period.

An organization that presents only the next steps, without reporting what it did this year, is missing half the story. And the auditor will ask, "What has actually changed in your processes over the last 12 months?"

An example from the field: supplier performance

The usual presentation:

Supplier A: score 82. Supplier B: score 91. Supplier C: score 67.

A presentation with a decision question:

What we improved this year: after a low score in Q1, the supplier evaluation procedure was updated in Q2 and criteria for response times were added. Supplier D was replaced in Q3 after a sustained decline in performance.

The decision question: Supplier C dropped from a score of 78 to 67. That is below the minimum threshold we set. Is action required?

Decision: a meeting between representatives and Supplier C, and a source inspection within 60 days | Owner: quality manager | Due: March 31

One field that changes the meeting

You can leave the whole structure of the review as it is and add just one mandatory field at the end of each topic:

This field forces management to close every topic with a clear position. It creates documentation that an auditor can follow from each finding through to the action, and it prevents the dynamic in which everything is discussed but nothing is decided.

At the end of the meeting, the minutes contain a focused list of decisions rather than a general summary.

Every topic is closed either with an action and an owner, or with an explicit statement that nothing is needed.

It is the same data, with a different question, and it leads to a different result.