The worst clause wins

A coverage level of eighty percent reads reassuringly. Four of five sub-clauses met, the fifth still open, the chapter sits at eighty. That is how almost every progress indicator counts. In an audit nobody counts that way.

So the standards cockpit does not either. A parent clause takes the status of its worst child. A clause with five sub-clauses, one of them missing, counts as missing itself, even if the other four are sufficiently evidenced. No average, no progress bar filling up nicely.

Why the hard rule is the honest one

An auditor does not examine an average. They look for the place where evidence is missing and write it down. Whether four neighbouring clauses are exemplary changes nothing about the finding. A display reporting eighty percent prepares you badly for that conversation. One that turns the chapter red shows exactly where the work is.

The side effect is uncomfortable and intended: a management system looks worse at the start than you would like. In exchange, its state on certification day means something.

Four levels instead of ticked or not ticked

Every piece of evidence carries one of four statuses: missing, partial, sufficient or exemplary. Plus an optional note, the date of assessment and the name of the assessor. The middle value "partial" is the one that does the work. It records that something exists but does not yet hold up, and that is precisely the state a yes-no list loses.

Evidence comes from day-to-day operations

On every clause the evidence picker offers fourteen possible sources from other modules: policies, audits and audit findings, measures, risks, processes, KPI measurements, training, supplier assessments, DMS documents. The cockpit suggests the fitting module based on the clause, so supplier assessment for chapter 8.4.

The QMS module creates records of its own only for those ISO 9001 artifacts that would otherwise have no home: context, interested parties, scope, quality objectives, management review, complaints and certifications.

A detail for anyone who has lived through a migration: the link between clause and evidence runs through a morph-map alias rather than the class name. Rename a class in the source module and the evidence stays attached.

What is out of scope still belongs on the record

The scope statement names exclusions explicitly and with justification, for instance that chapter 8.3 does not apply because no development falls within the scope. That is not a blemish in your coverage, it is evidence in itself. The difference between "not applicable, here is why" and an empty line decides whether the auditor asks.

Shipped with the module are the clause catalogues for ISO 9001 with 91 clauses, ISO 14001 with 45 and ISO 45001 with 50, together 186 ready-made clauses. Mandatory documents are marked as such, and an Excel export pulls every clause of a standard with its status, in the form an auditor can read.

More on the quality management module page.