Skip to Content
ISO 9001Quality manual

Quality manual ISO 9001

A quality manual for ISO 9001 has not been mandatory since the 2015 version. The standard  asks for “documented information”, not a thick book. Still, many companies think they must write hundreds of pages. On this page you read what the standard does require, how to build a lean manual and how to reuse existing documents. Want to see the full requirements? Read the ISO 9001 requirements and the step-by-step plan. You can buy the official standard from NEN .

The word “quality manual” no longer appears in the 2015 standard. The term “documented information” has replaced it. You may still write a manual, but you do not have to.

On this page

We cover four questions that companies ask most often about the quality manual. Use the cards to jump straight to the right section.

Is a quality manual for ISO 9001 mandatory?

No. Up to the 2008 version, the standard required a quality manual with six fixed procedures. Since ISO 9001:2015 , that is no longer the case. The standard now only asks for “documented information” and leaves the form up to you.

That means you choose how you document. A manual is allowed, but a set of separate procedures, a wiki, checklists or a combination also works. As long as the information is available and controlled.

Common mistake: writing an 80-page manual that nobody reads. A system that the shop floor does not use is dead text. The auditor sees through it, and you gain nothing from it.

Why do companies still hold on to the thick manual? Three reasons come up often:

  • Old habit: anyone certified before 2015 still knows it that way.
  • Consultants who reuse templates instead of delivering tailored work.
  • The idea that “more paper” is safer during an audit. That is not true.

Which documented information does ISO 9001 require?

The standard names a number of topics that you must record. You decide the rest. Below you see the mandatory documents and records, linked to the chapter they come from.

Required document or recordStandard clauseType
Scope of the quality management system4.3Document
Quality policy5.2Document
Quality objectives6.2Document
Evidence of staff competence7.2Record
Information needed to run processes8.1Document
Results of the review of customer requirements8.2Record
Design and development records (if applicable)8.3Record
Evaluation of external suppliers8.4Record
Identification and traceability8.5.2Record
Customer or supplier property8.5.3Record
Evidence of release of products and services8.6Record
Nonconforming output8.7Record
Results of monitoring and measurement9.1Record
Audit programme and audit results9.2Record
Results of management review9.3Record
Nonconformities and corrective actions10.2Record

The difference is simple. A document describes how you do something (policy, procedure, scope). A record is proof that you actually did it (a signed report, a completed form).

You find more explanation of each chapter on the page with the ISO 9001 requirements. For how to fill in chapter 6, read risk management and the risk analysis for ISO 9001.

What does a lean quality manual look like?

If you still want one central document, a lean manual works well. It acts as a framework: a short description of your system with references to your procedures and records. It often fits on five to fifteen pages.

A workable structure looks like this:

SectionWhat do you put in it?
Introduction and scopeWhat your company does and which parts of the system apply (clause 4.3)
Context and interested partiesInternal and external factors, and who your interested parties are
Quality policyYour policy, signed by top management
Process overviewA diagram of your core processes and how they connect
Roles and responsibilitiesWho is responsible for what
ReferencesLinks to procedures, forms and records

Example: an installation company with eight employees writes a seven-page manual. The process overview is one flowchart: quote, planning, execution, handover, aftercare. Each process step lists the form that belongs to it. No separate ten-page procedures, but checklists of half a page.

Keep the manual short and refer onwards. That way, when something changes, you only update the underlying document, not the whole manual.

Reusing existing documents

You do not have to start from zero. Most companies already have much of what the standard asks for, just not under the right name. Check what you have before you write something new.

Common examples:

What you probably already haveCounts as
Quotes and order confirmationsReview of customer requirements (8.2)
Job profiles and diplomasEvidence of competence (7.2)
Complaints registerNonconformities and corrective actions (10.2)
Supplier evaluation or purchasing listEvaluation of external suppliers (8.4)
Handover reportsRelease of products and services (8.6)
Minutes of team meetingsPart of the management review (9.3)

Start with a gap analysis: compare the mandatory list with what you already have. Fill in what is missing. You find practical templates for policies, processes and objectives in the resources.

Never write an ideal picture that does not match practice. Describe how things really work. An auditor checks whether you do what the document says, not whether it sounds good.

Common mistakes with the quality manual

  • Documenting too much. More paper does not make your system better, only heavier.
  • Copying a template. A copied policy stands out at once during the audit.
  • Not managing documents. Versions, approval and date belong to them (clause 7.5).
  • Never updating the manual. A document that does not grow with your company soon becomes wrong.

Next step

Now that you know how to keep documentation lean, look at the table with all mandatory ISO 9001 documents per chapter, read the full ISO 9001 requirements or follow the step-by-step plan to certification. Still unsure about something? Check the frequently asked questions or go back to what ISO 9001 is.