Many companies have a quality manual on a shelf or as a PDF on the shared drive, often organized by clauses of the standard and last revised before the recertification audit. It can be much more than a document for the auditor.
A good quality manual is short, describes how your company actually works, and points to the documents where the details live. This guide shows what ISO 9001:2015 requires (less than many people think), which structure has proven itself, and how process descriptions and standard operating procedures feed into the manual. The quality manual is the top level of process documentation prepared for a quality management system.
What is a quality manual?
A quality manual (QM manual) is the overview document of your quality management system. In a few pages, it answers the questions a customer, an auditor, or a new manager asks first:
- What does the QM system cover, meaning which sites, products and services?
- What quality policy does the company follow, and which objectives follow from it?
- Which processes exist, and how do they connect?
- Who is responsible for what?
- Where are the details, and which process descriptions, SOPs and forms belong to it?
That makes the manual the top of the documentation pyramid, pointing to its content. How a complaint gets handled step by step is described elsewhere. The manual says that there is a controlled procedure for it, who owns it and which document describes it.
Is a quality manual still mandatory under ISO 9001:2015?
No, and that is good news for anyone currently looking at a blank document.
The previous version, ISO 9001:2008, explicitly required a quality manual in clause 4.2.2, plus six documented procedures (control of documents, control of records, internal audit, control of nonconforming product, corrective action, preventive action). The 2015 revision dropped both requirements. In their place came the term "documented information" (clause 7.5).
The standard distinguishes two kinds:
- Maintained documented information - what used to be called "documents": requirements that apply and must be kept current, such as an SOP.
- Retained documented information - what used to be called "records": evidence that something happened, such as an audit report or a training record.
Under clause 7.5.1, your QM system includes the documented information the standard explicitly requires, plus whatever you yourself determine is necessary for the system to be effective. The note to 7.5.1 makes clear that the extent can differ depending on the size of the organization, the complexity of its processes and the competence of its people. A 15-person business manages with much less paper than a large corporate plant.
Among other things, ISO 9001:2015 explicitly requires the following as documented information:
| Clause | What must be documented |
|---|---|
| 4.3 | Scope of the QM system, including justification for any requirement that is not applicable |
| 4.4 | Documented information to support the operation of processes, "to the extent necessary" |
| 5.2 | Quality policy |
| 6.2 | Quality objectives |
| 7.2 | Evidence of competence |
| 9.2 | Evidence of the audit programme and audit results |
| 9.3 | Results of management reviews |
| 10.2 | Nature of nonconformities, actions taken, and results of corrective actions |
The list is not complete, and further evidence requirements are spread across clauses 7 to 10. It does show the principle: the standard wants to see scope, policy, objectives and evidence, and which document they live in is up to you. Many companies, for example, keep the evidence of competence under 7.2 as a skills matrix.
Why a quality manual is still worth having
Even without the requirement, the manual has its place. The required content, namely scope, quality policy, objectives and process overview, is written down somewhere anyway. Many certified mid-sized companies still bundle it into one document, because that has three practical advantages:
- An entry point for auditors and customers. A customer supplier audit often starts with "Show us your QM system." A compact manual answers the overview questions in ten minutes.
- Orientation for new hires. Someone new to the company quickly understands how the business runs from a process map and a list of responsibilities, without first reading through several binders.
- A frame for the detailed documents. The manual is the table of contents for your process documentation. It puts 40 SOPs in order and shows which one currently applies.
A manual that describes your own way of working is the most useful. Sentences like "The organization shall determine and provide the resources needed for the establishment, implementation, maintenance and continual improvement of the quality management system" are already in the standard (clause 7.1.1). An auditor wants to see how you put that into practice, and that is what belongs in the manual.
The structure: an outline that works
There is no prescribed structure. Two approaches are common:
Organized by clauses of the standard (4 to 10). Advantage: the auditor finds their way immediately, because every requirement has its place. Disadvantage: the manual follows the logic of the standard, and employees find it harder to recognize their own workflows in it.
Organized by processes. Advantage: the manual follows the logic of your company, meaning management, sales, purchasing, production, shipping and support. Disadvantage: the auditor needs a mapping of where each requirement is met.
In practice, a mix works best: organized by processes, plus a mapping table from clause to process in the appendix. Employees read their company, and the auditor gets an index.
Quality manual template: an outline to copy
Quality manual <company> Version <x.y> As of <date>
Approved by <role>
1. The company
Short profile, sites, products and services, org chart
2. Scope of the QM system (ISO 9001, 4.3)
Scope, non-applicable requirements with justification
3. Context and interested parties (4.1, 4.2)
Key internal/external issues, customers, suppliers, authorities
4. Quality policy and quality objectives (5.2, 6.2)
Policy verbatim, objectives with metric and owner
5. Process landscape (4.4)
Process map: management, core, and support processes
Per process: owner, purpose, reference to process description/SOP
6. Roles, responsibilities and authorities (5.3)
Roles, deputies, quality management representative
7. Risks and opportunities (6.1)
Approach and reference to the risk assessment
8. Control of documented information (7.5)
How documents are created, reviewed, approved, distributed, archived
9. Evaluation and improvement (9, 10)
Internal audit, management review, handling errors and complaints
Appendix
A Mapping clause -> process/document
B List of related documents with number and version
C Change history
With this outline, a mid-sized company ends up with ten to twenty pages. More is rarely needed, and when the manual gets much longer, it usually contains content that belongs one level down.
A word on templates from the web: a search for "quality manual template PDF" turns up plenty of fully written manuals. They work well as an outline aid. The text is best written yourself, because an auditor usually recognizes a copied template quickly: it describes workflows that do not exist in the company in that form, and the actual workflows are missing. Take the structure and fill it with your own content.
The documentation pyramid: how process descriptions and SOPs feed into the manual
The manual holds up when it is clear what goes into it and what goes below it. A four-level model has proven itself:
Level 1 - Quality manual. The why and the overview: scope, policy, objectives, process map, responsibilities. Rarely changes.
Level 2 - Process descriptions and standard operating procedures. The what, who and when for a process or a bounded procedure, often across departments. This is where, for example, complaint handling from receipt to the 8D response is described. How such a document is structured is covered in the guides on writing standard operating procedures and the process description template.
Level 3 - Work instructions. The how in detail, at one workstation: click paths, machine settings, inspection steps. More in the guide on the work instruction template.
Level 4 - Forms and records. Checklists, inspection logs and audit reports, the "retained" documented information in the sense of the standard.
The link between level 1 and level 2 is the process map. In the manual, it shows all management, core and support processes on one page. Each box has an entry in the process overview with process owner, purpose in one sentence and number of the corresponding process description or SOP. How to build that map is covered in the guide on creating a process map.
An example of entries in chapter 5 of the manual:
| Process | Owner | Purpose | Document |
|---|---|---|---|
| Order fulfillment | Head of Inside Sales | Process customer orders completely, on time, without double entry | PD-03 |
| Complaint handling | Head of QA | Eliminate root causes, respond to customers within deadlines | SOP-07 |
| Incoming inspection | Head of Warehouse | Only released goods enter production | SOP-11, WI-11-02 |
This suggests a helpful sequence: the manual is finished last. The process map and the references in chapter 5 are as good as the process descriptions beneath them. If you work out level 2 first, the manual has content to point to from the start.
Step by step: how to write your quality manual
1. Define the scope. Which sites, products and services does the QM system cover? Are there requirements of the standard that do not apply to you, such as design and development (8.3) if you manufacture exclusively to customer drawings? That gets justified.
2. Sketch the process map. Which processes exist, who owns them, how do they connect? A first one-page draft is enough. It doubles as your worklist for the next steps.
3. Capture the processes - from the people who run them. This is the most laborious and most valuable step. The level-2 process descriptions come out of conversations with the people doing the work, because they know the special cases, the unofficial spreadsheets and the arrangements that have applied for years and so far are written down nowhere. The quality manager then gives them their final form. How to go about it is covered in the process documentation guide.
4. Write process descriptions and SOPs. One document per process or procedure, with owner, responsibilities, workflow, special cases and related documents. Prioritize by risk and start with the processes where mistakes are expensive or where knowledge depends on a single person.
5. Formulate the quality policy and objectives. Short and verifiable. "We strive for the highest customer satisfaction" describes an intention. "Complaint rate below 0.5 percent of shipped line items, measured monthly" is an objective you can check.
6. Assemble the manual. This is the step where the actual manual comes together: the outline from the template above, the process map, the process overview with references and the mapping table to the standard.
7. Define document control. Who reviews, who approves, how are changes made visible, where does the valid version live? Clauses 7.5.2 and 7.5.3 of the standard require exactly this: appropriate identification, review and approval, availability where needed, protection and control of changes.
8. Have someone test-read it. Give the manual to someone who knows the company but did not help write it. Where do they stumble? Where does something say what is not actually true? These ten minutes often deliver more than any formatting template.
Common mistakes with quality manuals
- Copying the standard. Standard text with the company name swapped in is common and helps neither auditors nor employees.
- Describing the target state. The manual shows how things should run, and practice looks a little different. This gap surfaces in the audit, at the latest when the auditor talks to someone on the shop floor.
- Putting everything in the manual. If click instructions and inspection steps are in the manual, it has to change with every ERP update. Details belong on levels 2 and 3.
- Names instead of roles. "Mr. Krüger approves" goes stale with the next job change, while "Head of QA approves" stays valid.
- No maintenance between audits. The manual gets updated before recertification and then left alone until the next audit. More on that next.
Staying current: upkeep between audits
A quality manual is usually right on the day it is approved. After that the company keeps developing: the new ERP is live, the head of purchasing has left, a process now runs differently. The document keeps up when events like these trigger a review.
Because the manual builds on the level-2 process descriptions, that is where upkeep matters most. Three habits have proven themselves:
- Define change triggers. System migrations, staffing changes, new products and complaints with a process root cause trigger a document review, as a fixed step in the routine.
- Owners with review dates. Every document has a named process owner and a date for the next review. The management review (9.3) is a good occasion to go through the list once a year.
- Check the practice regularly. Review the documents and talk to the people doing the work: is this still right? What has changed since last time?
Day-to-day business often leaves little time for the third point. This is where AI process documentation comes in. At wissa.ai, an AI conducts structured interviews with the employees who run the processes every day, in conversations of around 15 to 20 minutes via chat and whenever it suits them. The result is an overview of all areas and processes, an org chart and the first draft of the process descriptions, including the special cases that so far live only in people's heads. Contradictions between statements are flagged with their source and stay visible, and after every further conversation the documentation continues with a visible diff against the previous version. Editing, the check against the standard, approval and document control stay with QM, and level 2, the foundation of your manual, stays close to practice.
Conclusion
Since ISO 9001:2015, a quality manual is no longer mandatory, while the content it traditionally bundles still is: scope, quality policy, quality objectives and processes to the extent necessary. A lean manual of ten to twenty pages, organized by processes and referencing process descriptions and SOPs, is a good way for most mid-sized companies to meet that.
The real work sits one level down, in process descriptions that show lived practice and in a routine that keeps them current. If you would like to shorten that part, wissa.ai interviews your knowledge holders and delivers the first draft of your process documentation, traceable down to the individual statement, hosted in Germany, with AI processing in the EU. A free trial package (10 credits, once per company, terms) usually covers a first interview, and you can start right away. Try one interview for free
FAQ
Is a quality manual mandatory under ISO 9001:2015?
No. ISO 9001:2008 required a quality manual in clause 4.2.2; the 2015 revision removed that requirement. Instead, the standard requires "documented information" (clause 7.5), including the scope (4.3), the quality policy (5.2) and the quality objectives (6.2). This content must be documented; whether in a manual or in separate documents is your decision.
What goes into a quality manual?
The scope of the QM system, the quality policy and objectives, a process map with process owners and references to the corresponding process descriptions and SOPs, responsibilities, and the approach to risks, document control, audits and management review. In the appendix: a mapping of clauses to processes and a list of related documents.
How long should a quality manual be?
For a mid-sized company, ten to twenty pages is a good benchmark. The standard itself notes under 7.5.1 that the extent depends on size, process complexity and the competence of people. If the manual gets much longer, it usually contains details that belong in SOPs or work instructions.
What is the difference between a quality manual and an SOP?
The quality manual describes the quality management system as a whole: scope, policy, objectives, process landscape. An SOP describes a single workflow, meaning who does what and when, for example in complaint handling. The manual references the SOPs, and their content lives in the SOPs themselves.
Can I use a quality manual template from the internet?
The outline, yes; the text is better written yourself. A copied template describes workflows that do not exist in your company in that form, and auditors notice quickly, at the latest when they talk to employees. Use the structure of a template and fill it with your own processes, captured from the people who run them.
Sources
- ISO 9001:2015, clauses 4.3 (Scope), 4.4 (Quality management system and its processes), 5.2 (Policy), 6.2 (Quality objectives), and 7.5 (Documented information)
- ISO 9001:2008, clause 4.2.2 (Quality manual), withdrawn