Cognatum

Standards

Management review never reviews your knowledge

Management review is the one forum where top management formally judges the quality system. Its required inputs all measure the machinery. None of them measures the state of the knowledge the company answers from.

Cognatum Team · Oct 7, 2026 · 6 min read

Once or twice a year, top management sits down and formally judges whether the quality system still works. The agenda is not improvised. The standard names what has to be on it. Audit results. Nonconformities. Corrective action status. Customer feedback. Process performance. Risks and opportunities. Resources. It is a careful list, and every item on it has the same shape. Each one measures the system. None of them measures the knowledge the company answers from.

Served to one approved entry
AI assistants & agents
Proposal tools
Internal search & chat
Customer portals
Compliance & audit

Cognatum governs the entry

source · version · approver · permissions

What the clause asks for

ISO 9001 puts management review in clause 9.3. Top management reviews the quality management system at planned intervals. The test is whether the system stays suitable, adequate and effective, and whether it still lines up with the strategic direction of the business. The requirement is old. It arrived in 1994, and took its current form in 2015. The current edition of the standard is ISO 9001:2026.

A short list, strictly kept

Guides to the clause list the inputs plainly. Data on system performance. Customer feedback. Process performance and effectiveness. The status of corrective and preventive actions. Audit results. Changes that could affect the system. The outputs are decisions: improvement opportunities, changes to the system, and resource needs. Minutes are kept as evidence.

How practitioners read it

On The Quality Forum Online, an ISO consultant paraphrases the whole requirement in six lines. It shall occur. At planned intervals. It verifies the effectiveness of the management system. There is a list of inputs for consideration. The outputs are actionable. Keep documented evidence. He adds that the standard does not require a meeting at all. In the same thread, a quality manager says the review at his own company is done solely for conformance and adds no value.

The same forum, in every regulated sector

This is not an ISO 9001 quirk. Qualio notes that management review mechanisms are required by ICH Q10 for pharmaceutical quality systems, by ISO 13485 for medical devices, and by the US device regulation at 21 CFR 820. ISO/IEC 42001, the management system standard for artificial intelligence, adds a further review on top of those. So most regulated companies already have the forum. Several of them have more than one. The forum is not what is missing.

Every input is about the machinery

Read the input list again and notice what each item measures. An audit result says the process was followed. A nonconformity says an output was wrong. A corrective action status says the fix is moving. Customer feedback says somebody complained. Process performance says the line ran. Every one of these is a fact about the machinery.

What gets assumed instead

Underneath all of it sits an assumption nobody tables. The documents the business runs on are approved, current, and do not contradict each other. Document control is meant to hold that assumption up, and for paper it mostly does. A controlled document has a revision, an approver and a date. What document control never measured is the health of the whole body of knowledge. How much of it is stale. How much is duplicated. Where two approved documents say opposite things. Where there is nothing at all.

Why the gap stopped being harmless

For decades the gap was tolerable. A person with a question reached for a controlled document, and the control sat on that document. That is no longer how the question gets answered. The person asks an assistant, and the assistant assembles an answer across documents, drives, tickets and threads. Nothing in the review pack describes that answer. It leaves no artifact to count.

Grounding is not a review input

The obvious reply is that the assistant reads company material, so it inherits the company's controls. A preregistered study of commercial legal research tools tested that claim. Products from LexisNexis and Thomson Reuters, marketed as eliminating hallucinations, were wrong between 17 and 33 percent of the time. Retrieval narrows the error. It does not remove it, and it does not report itself to top management.

Pharma already named the missing thing

The pharmaceutical standards come closest to saying it out loud. ICH Q10 names knowledge management as one of two enablers of a working quality system, alongside quality risk management. It defines it as a systematic approach to acquiring, analysing, storing and disseminating information about products, processes and components. It adds that product and process knowledge should be managed from development through commercial life, up to and including discontinuation. EU GMP 1.4(ii) says it in one line. Product and process knowledge is managed throughout all lifecycle stages.

Expected, but never inspected

So does an inspector demand a formal knowledge management system? The ICH Q9(R1) questions and answers are blunt. No. There is no regulatory requirement for a formal knowledge management system. However, it is expected that knowledge from different processes and systems is appropriately utilised. Read those two sentences together and the position is clear. The knowledge has to be managed and used well. Nothing in the review cycle checks whether it is.

What the AI regulation asks a deployer

The EU AI Act is more specific and still leaves the gap open. Article 26 tells deployers of high-risk systems to follow the instructions for use, to assign human oversight to people with the necessary competence, training and authority, to keep logs for at least six months, and to monitor the operation of the system. Where the deployer controls input data, that data has to be relevant and sufficiently representative for the intended purpose.

A fit test, not an approval test

Representative is not the same as approved, current or uncontested. A document can be a perfect fit for the intended purpose and six months out of date. Software can supply the evidence a reviewer needs here. No product confers compliance with the Act.

One page your next review does not have

A knowledge input to management review would be short. Four figures and a list. How many approved entries exist, and how many of them are at risk. At risk means more than overdue for review. It covers duplicates, entries that contradict each other, and gaps where the company has no answer at all. Which sources changed since the last review, and what depended on them. Which questions came back with no confident match.

Where the figures come from

This is the work the Cognatum Knowledge Loop is built around. Cognatum is a knowledge base that scores what a company knows and splits it into healthy and at risk. When two sources disagree, it presents both and shows where the disagreement sits rather than picking a winner. When a source changes, it notifies the people whose entries depended on it. Every approved entry carries a named approver, a date and a source.

The AI does the finding, the gathering and the surfacing. A named person approves. That hand-off is what produces a number a reviewer can read.

A test before the next one

Ask whoever builds the management review pack for one more page. Approved entries. Entries at risk, and why. Sources that moved since last time. Questions that got no good answer. If nobody owns that page, you have found something worth minuting.

Your company's knowledge isn't missing. It's unusable. Cognatum changes that.

Common questions

Questions this raises.

What are the required inputs to a management review?

ISO 9001 puts them in clause 9.3. Guides to the clause list data on system performance, customer feedback, process performance and effectiveness, the status of corrective and preventive actions, audit results, and changes that could affect the system. Each item describes the system or its outputs. None of them describes the state of the knowledge the organization answers from.

Does ISO 9001 require a management review meeting?

No. The clause asks for a review at planned intervals by top management, with inputs considered, actionable outputs and retained evidence. Practitioners on The Quality Forum Online point out that nothing in the text requires a meeting, and that many companies already satisfy the requirement through existing leadership reviews. What tends to be missing is the retained evidence, not the discussion.

Should AI use be on the management review agenda?

Putting it on the agenda is a start, but the usual framing repeats the gap. Reporting tool usage, incidents and policy exceptions measures the system again. The useful input is the state of the knowledge the assistant answers from: how much is approved, how much is at risk, which sources changed, and which questions returned nothing confident.

Does ISO/IEC 42001 close the gap?

ISO/IEC 42001 is the management system standard for artificial intelligence, so a company that adopts it gains a second management review alongside the quality one. That helps with oversight of the AI system itself. It is still a review of a management system. Neither standard asks for a measured account of the knowledge the system retrieves from, and software aligns with these frameworks and supplies evidence rather than conferring compliance.

Is grounding an answer on company documents enough?

It reduces the error rather than removing it. A preregistered study of commercial legal research tools found that products from LexisNexis and Thomson Reuters, marketed as eliminating hallucinations, were wrong between 17 and 33 percent of the time. Grounding also says nothing about whether the retrieved document was approved, current, or contradicted by another one.

Knowledge governed. Intelligence everywhere.

See it on your own content, in your own environment.