What a management review record has to contain

Minutes that read “the quality system was discussed and no major issues were raised” are a common way to close out a management review, and they satisfy almost nothing ISO 13485:2016 Clause 5.6 actually asks for. The clause names, specifically, what has to go into the review and what has to come out of it — twelve required inputs at Clause 5.6.2, four required outputs at Clause 5.6.3 — at intervals the organization has to plan in advance under Clause 5.6.1. A record that can't be checked against that list line by line is documenting that a meeting happened, not that a review did.

The interval has to be planned, not incidental

Clause 5.6.1 requires top management to review the QMS at planned intervals to ensure its continuing suitability, adequacy and effectiveness. “Planned” is doing real work in that sentence: a review that happens because an audit is coming up, rather than on a schedule set in advance, is reactive by definition, and a reactive review is structurally biased toward finding what's already been fixed rather than what's quietly drifting.

Twelve inputs, and a gap that isn't invisible

Clause 5.6.2 lists what the review has to consider: feedback, complaint handling, reporting to regulatory authorities, results of audits, monitoring and measurement of processes, monitoring and measurement of product, status of corrective actions, status of preventive actions, follow-up actions from previous management reviews, changes that could affect the QMS, recommendations for improvement, and new or revised regulatory requirements. That last one is easy to treat as background reading rather than a standing agenda item, and it has the clearest recent test case: a management review held any time after February 2, 2026 that doesn't address the QMSR transition under the regulatory-requirements input is missing an item the clause requires, not skipping something optional. A record built as free-form minutes, rather than against this list, makes a missing input invisible until an auditor brings their own copy of Clause 5.6.2 to check it against.

The inputs already exist — two other trackers are supposed to feed them

Two of the twelve inputs aren't new work for a management review to generate; they're supposed to arrive already assembled from processes the organization runs anyway. Audit results are the direct output of a risk-weighted internal audit program; corrective and preventive action status is the direct output of a CAPA tracker with a working verification-of-effectiveness field. A management review that reconstructs these from scratch, in the meeting, is duplicating work two other records already did — and a review that can't produce them on request is a signal that the audit program and the CAPA tracker aren't actually feeding the loop they're supposed to close.

An output is a decision, not a topic that got mentioned

Clause 5.6.3 requires the review to produce decisions and actions on four things: improvement needed to maintain the suitability, adequacy and effectiveness of the QMS and its processes; improvement of product related to customer requirements; changes needed to respond to new or revised regulatory requirements; and resource needs. “Discussed the QMSR transition” is an input being acknowledged, not an output; the record still owes a decision — a specific action, an owner, a date — before that input has actually been closed out. A management review record that lists topics covered without a parallel list of decisions made has documented an agenda, not a review.

A management review record structured around these two lists — the twelve inputs of Clause 5.6.2, the four output categories of Clause 5.6.3 — is previewed in the launch catalog. If your program runs this review differently and catches something ours doesn't, the shelf takes that correction.