Every company I have audited has a quality manual. Almost nobody in the company has read it. The production manager has not read it. The operators have not read it. Most quality engineers have skimmed it once during their onboarding and never opened it again. The quality manager knows where it is saved but could not tell you what is on page seven without checking.
And yet, this document — universally ignored, perpetually outdated — is still, quietly, running your company.
The manual is the shadow constitution
Here is what I mean. Your quality manual describes — or is supposed to describe — how your quality management system operates. It defines the structure, the processes, the interfaces, the authorities. It is the document that maps your organisation to ISO 9001. And because nobody reads it, nobody knows when it stopped being accurate.
I inherited a quality manual at one plant that described an organisational structure from three reorganisations ago. It referenced departments that no longer existed. It assigned quality responsibilities to a role that had been eliminated. But the manual was still certified, still audited, still on the shelf. The auditor had signed it off because the manual existed and was controlled. Nobody checked whether the manual described reality.
A document that describes the wrong system perfectly is more dangerous than no document at all. It creates the illusion of control.
The three purposes a quality manual should serve
A quality manual has three legitimate jobs. Most manuals fail at all three.
1. Onboarding. A new engineer or manager should be able to read the quality manual and understand how the QMS works, who owns what, and where to find things. If your manual is a forty-page restatement of ISO clauses with "the organisation shall" language, it fails. A new hire does not need to read the standard reworded. They need a map of your system.
2. Alignment. When departments disagree about who owns a process — "is supplier development quality's job or procurement's job?" — the manual should resolve it. If the manual is vague enough that both departments can point to it and claim ownership, it is not a manual. It is a Rorschach test.
3. Audit defence. The manual is the top-level document the certification body reviews. If it is inaccurate, the auditor finds gaps between the described system and the actual system, and those gaps become findings. An accurate manual prevents findings. A decorative manual creates them.
Why nobody reads it
Quality manuals are unread for a simple reason: they are unreadable. They are written in standards language, not human language. They describe what the standard requires rather than what the company does. They are structured to satisfy auditors rather than to serve the organisation. And they are almost never written by the people who actually run the processes.
I rewrote a quality manual for a 900-employee greenfield plant I set up in France. The original draft, produced by a consultant, was 52 pages of clause-by-clause mapping. I threw it out and wrote a 12-page document that described how the plant actually worked: who approved what, how nonconformances flowed, what the escalation paths were, where records lived. The certification auditor read it in fifteen minutes and said it was the clearest manual he had seen in years. The plant manager read it on a Friday afternoon and said "now I finally understand what quality does here."
The manual is a living document, not a monument
If your quality manual has not been substantively revised in the last twelve months, it is almost certainly wrong. Processes change. People change. Systems change. The manual that was accurate at the last surveillance audit has been silently overtaken by three reorganisations, two system migrations, and a new production line that nobody bothered to document.
The test is simple. Pick up your quality manual. Turn to the process map or the responsibility matrix. Does it describe the organisation as it exists today? If not, your manual is not a document — it is a fossil. And fossils do not run quality systems.
ISO 9001:2026 will likely de-emphasise the mandatory quality manual even further, aligning with the trend toward leaner documentation. This is good. But it does not eliminate the need for a top-level description of how your system works. It just means the description should be short, accurate, and useful.
If nobody reads your quality manual, the problem is not the people. The problem is the manual. Fix it or kill it. But stop pretending it serves a purpose it does not.
