← Notes · · auto
ISO 9.3 Management Review Without the Four-Hour Slog
Most management reviews run long because nobody read clause 9.3 carefully. Here is what the standard actually requires in your minutes.
Most management reviews run long because the person chairing them has not read clause 9.3 carefully. They have read a training slide that said “management review is a top-management requirement” and booked a half-day in a conference room and invited everyone they could think of.
The clause itself is four pages in the standard. The meeting does not need to be four hours.
What ISO 9.3 Actually Asks For
Clause 9.3 has three parts. The first (9.3.1) says top management must review the quality management system at planned intervals. It does not say annually. It does not say quarterly. It says planned. You decide the interval, you record it, you stick to it.
The second part (9.3.2) lists the inputs. This is where most reviews go wrong, because people treat the input list as an agenda and talk through each item in real time. You do not need to do that. The inputs are data. They can be gathered, formatted, and circulated before anyone sits down.
The third part (9.3.3) lists the outputs: decisions about improvement opportunities, decisions about changes needed to the system, decisions about resources. That is what the minutes must capture.
If your minutes record the inputs considered, the discussion that followed, and the decisions made with owners and dates, the auditor has what they need.
Gather the Data Before You Meet
The fastest management reviews happen when someone has done the legwork the week before. Pull together:
- Audit results and any open nonconformances
- Customer complaints and satisfaction scores
- Quality objectives and whether you are hitting them
- Supplier performance data
- Status of actions from the last review
Put this on a single page or a short slide deck. Circulate it two or three days before the meeting. Ask attendees to read it. The meeting then becomes a conversation about what the data means and what to do about it, not a tour through the data itself.
A thirty-minute review is entirely achievable with this approach. Sixty minutes is more comfortable. Four hours usually means nobody prepared anything.
What the Minutes Must Include
Auditors look for a few specific things when they check management review records. They want to see that the inputs from 9.3.2 were considered, even if some were straightforward. “No changes to external context since last review” is a perfectly acceptable note. They want to see outputs with clear owners and dates. And they want to see a trail back to previous reviews, confirming that actions were followed up.
You do not need a twenty-page report. A structured one-page template with sections for each required input and a table for actions is sufficient. The length is not the point. The completeness is.
If an input was considered and nothing needed to change, say so in one line. If something needed action, record the action with a name and a date.
Common Gaps That Catch People Out
The inputs most commonly missed in review minutes are resource adequacy and the performance of external providers. Suppliers and contractors get talked about in operational meetings all year, but the management review record does not mention them.
Also watch for reviews that record the discussion but not the decisions. “We talked about customer complaints being higher this quarter” is not a management review output. “We have assigned Sarah to investigate root cause on the top three complaints, report by end of October” is.
A third gap is the link to risks and opportunities. You do not need a formal risk register review in every meeting, but the minutes should confirm that actions to address significant risks were checked.
Keeping It Sustainable
The companies that struggle most with management review are the ones that treat it as an annual event. One long meeting, one document, filed away until the next audit.
Run it quarterly, or for smaller sites every six months, and the data is fresher, the meetings are shorter, and the outputs are more useful. You are not just ticking a box. You are catching problems before they compound.
If your quality objectives sit in a spreadsheet that nobody opens between reviews, that is a signal that the system is not working as it should. The losses analysis at losses.cadencestandard.com can help surface where the real gaps are before you walk into the room. Once you have identified the priority areas, the management review template in the toolkit is structured around the 9.3.2 inputs, so you spend your preparation time filling in data rather than designing a format.