A quality manual is a top-level document that describes an organization's quality management system, its scope, its quality policy, how its processes fit together, and where to find the procedures that run them. Since ISO 9001:2015, it is no longer mandatory, but a lean, honest manual is still one of the most useful maps a quality system can have.
For decades the quality manual was the thick binder every ISO-certified company kept on a shelf, often a near copy of the standard, written to pass an audit and read by no one. The 2015 revision quietly killed the requirement, and a lot of people took that as permission to throw the manual out. That is half right. The bloated compliance artifact deserved to go; the map it was supposed to be is still worth having. This guide covers what a quality manual is, what changed in 2015, whether you still need one, what a modern manual should contain, and how to write a lean one that people actually use.
What is a quality manual?
A quality manual is the highest-level document in a quality management system, the one that describes the system as a whole and points to everything beneath it. It typically states the scope of the QMS (what products, sites, and processes it covers), the quality policy, the organization's processes and how they interact, and references to the procedures and work instructions that carry out the detail. Think of it as the table of contents and the map for the whole system, not the detail itself.
It sits at the top of a documentation hierarchy. Below the manual are the procedures (how a process is run), below those the work instructions (how a specific task is done), and below those the records and forms (the evidence that it happened). A quality management system is all of it working together; the manual is the layer that lets a newcomer, an auditor, or a customer understand the system without reading every procedure in it.
The purpose is orientation. A good quality manual answers, in a few pages, three questions: what does this quality system cover, how does the work flow through it, and where do I go to find the rule for a given process? When it does that well, it saves everyone, new hires, auditors, customers running a supplier assessment, hours of hunting. When it does it badly, it is a document that restates the standard back to the standard and helps no one.
Did ISO 9001 drop the quality manual requirement?
Yes. ISO 9001:2008 explicitly required a documented quality manual; ISO 9001:2015 removed that requirement entirely, along with the six mandatory documented procedures and the prescriptive documentation structure the older versions dictated (ISO 9001:2015). The 2015 standard replaced "documents" and "records" with a single term, documented information and gave organizations the freedom to decide what documentation their system actually needs, based on their size, context, complexity, and risk.
The change was deliberate, not an oversight. The intent was to move quality systems away from documentation for its own sake and toward documentation that adds value, to stop rewarding thick manuals and start rewarding effective processes. Crucially, "not mandatory" does not mean "not allowed." A quality manual is still fully compatible with ISO 9001:2015, and the standard still requires certain documented information, the scope of the QMS, the quality policy, and the quality objectives all have to be documented somewhere. A quality manual is a perfectly good place to keep them.
Do you still need a quality manual?
You do not need one to be compliant, but many organizations keep a lean quality manual because it earns its keep in ways the standard does not require. Whether it is worth it comes down to what the manual is for.
Keep a lean one if you value a single, current reference that orients new hires and shortens supplier audits, auditors and customers routinely ask for a system overview, and a good manual hands it to them in ten minutes instead of a scavenger hunt. It is also a genuine aid to onboarding: a new quality engineer who reads a ten-page manual understands the shape of the system far faster than one handed forty procedures. And for smaller organizations, one concise manual can hold the scope, policy, objectives, and process map that the standard requires be documented anyway.
Skip it, or fold it into other documents, if your manual would just restate the standard, or if your quality system is already well mapped in a QMS platform where the scope, policy, and process interactions are documented and current in context. The worst outcome is a manual that exists to satisfy a requirement that no longer exists, a document maintained out of habit, drifting out of date, read by no one.
| Section | What it covers | Maps to ISO 9001:2015 |
|---|---|---|
| Scope of the QMS | Products, sites, processes covered; any exclusions | Clause 4.3 |
| Context and interested parties | The issues and parties that shape the system | Clause 4 |
| Quality policy | Leadership's commitment and direction | Clause 5 |
| Process map and interactions | How the core processes connect and hand off | Clause 4.4 |
| Roles and responsibilities | Who owns what in the system | Clause 5.3 |
| Reference to procedures | Pointers to the documented information beneath | Clause 7.5 |
What should a modern quality manual contain?
A modern quality manual should be a short map of the system, scope, policy, process interactions, and pointers, not a restatement of ISO 9001. The single biggest improvement over the old binder is length: a useful manual is usually ten to thirty pages, not two hundred, because it references the detail instead of duplicating it.
The core content is the scope of the QMS, the quality policy, the organization's context and the interested parties that shape it, a process map showing how the core processes interact, the roles and responsibilities in the system, and references down to the procedures and work instructions. What it should not contain is a clause-by-clause recital of the standard, procedures copied in full, or anything that will be out of date the moment a process changes. The test for every sentence is simple: does this help someone understand or navigate the system, or is it here to look thorough for an auditor?
What does the standard still require you to document?
Even without a mandatory manual, ISO 9001:2015 still requires specific documented information, which is why the manual did not truly disappear so much as become optional packaging for it. The standard requires that the scope of the quality management system, the quality policy, and the quality objectives be maintained as documented information, along with the documented information the organization determines is necessary for its processes to operate effectively (ISO 9001:2015). The American Society for Quality notes that a quality manual remains a common and legitimate way to hold this required information and to demonstrate the maturity of a quality system to customers and auditors (ASQ, Quality Management System). In other words, the required content still exists; the standard just stopped telling you it had to live in a document called a manual.
How do you write a lean quality manual?
You write a lean quality manual by starting from what the system actually does and documenting only what helps someone understand or navigate it. The sequence:
- Define the scope first. State what the QMS covers, products, sites, and processes, and note any clauses you exclude and why. Scope is the one section everything else depends on, and it is required documented information.
- Capture context and interested parties. Summarize the internal and external issues and the parties (customers, regulators, suppliers) that shape the system. Keep it to the factors that actually drive quality decisions.
- State the quality policy and objectives. Put leadership's commitment and the measurable objectives in one place. These are required to be documented; the manual is a natural home.
- Map the processes and their interactions. Draw how the core processes connect and hand off, ideally as a single diagram. This is the part of the manual people actually use, because it shows how the work flows.
- Assign roles and responsibilities. Name who owns each process and the key quality roles. Keep it to the level that helps someone find the right person, not a full org chart.
- Reference, do not duplicate. Point to the procedures and work instructions that hold the detail instead of copying them in. This is what keeps the manual short and stops it from going out of date every time a procedure changes.
- Set an owner and a review cadence. Name who maintains the manual and when it is reviewed, at minimum during management review and whenever the scope or structure changes. A manual with no owner is the binder-on-a-shelf failure mode returning.
Why do quality manuals go stale?
Quality manuals rot for one reason: they describe a system that has moved on. The old binder went stale because it was a static copy of processes that kept changing, and even a lean manual drifts if nobody maintains it. Two things keep it alive.
The first is discipline, a named owner, a review cadence, and the rule that the manual references detail rather than duplicating it, so a process change touches one procedure instead of the manual too. The second is keeping the system it describes visible and current in the first place. A manual is only as honest as the processes underneath it. When the real state of quality lives on paper and in scattered spreadsheets, the manual and the floor drift apart the same way the old binders did, the document says one thing, the shift does another. When the checks, records, and process data flow into one live layer, the system the manual describes is actually observable, and keeping the map current gets far easier. Harmony connects the checks operators already run and the systems around the line into one live operational layer with no rip-and-replace of existing software, so a quality system is something you can see running rather than something you assert in a manual. When CLS moved its production and quality logging off paper the data it was already generating became visible and current, which is exactly what keeps any quality document honest, whether or not you call it a manual. In a batch production environment especially, where every lot generates records, that living view is what a shelf binder never could be. Keep the manual lean, keep it a map, and keep the system it points to visible.