Skip to content
Try eQMS free for 14 days The all-in-one QM software
All modules for one price. View pricing
Resources

QM manual

Content, structure and sample outline based on ISO 9001

The QM manual, also called a quality manual, describes a company's quality management system at a glance: scope, quality policy and objectives, processes and responsibilities, and the way to all other documents. It is the entry point for employees, customers and auditors. On this page, you will find content, structure and a sample outline to download.

Reading time 9 minutes

Do you still need a QM manual?

Since the 2015 version, ISO 9001 no longer requires a QM manual under that name. Up to the 2008 version, it was explicitly required. The manual originated in the era of paper binders: one volume gathered all of a company's rules in one place. Today, the standard specifies which information must be documented: among others, the scope of the QM system, the quality policy, the quality objectives and the information you need for your processes. You decide in what form you do this.

In other standards, the manual remains explicitly required. ISO 13485 for medical devices requires a quality manual in clause 4.2.2, including the scope, justification for exclusions, reference to the procedures, a description of the interaction of the processes and an overview of the document structure. IATF 16949 for the automotive industry also requires a quality manual.

A manual in a binder shows the status on the day it was printed. A digital manual, on the other hand, is a part of your QM system that grows with it: each chapter has its own revision level, and every reference leads directly to the valid document.

What belongs in a QM manual

A good QM manual describes how your company works and refers to related documents for details. The table shows the usual contents and the matching clause of ISO 9001:2026.

Chapter in the manualContentsISO 9001:2026 clause
Company and contextCompany profile, products and services, internal and external issues, interested parties4.1, 4.2
ScopeSites, products, activities, non-applicable requirements with justification4.3
Process landscapeManagement, core and support processes and their interaction4.4
Quality policy and leadershipPolicy, management commitment, customer focus5.1, 5.2
OrganizationOrganizational chart, roles, responsibilities and authorities5.3
PlanningRisks and opportunities, quality objectives, planning of changes6.1 to 6.3
Resources and competenceStaff, infrastructure, test equipment, knowledge, training, communication7.1 to 7.4
DocumentationDocument structure and control of documents7.5
Delivery of servicesSales, development, purchasing, production or service delivery, release, handling of errors8.1 to 8.7
EvaluationMetrics, customer satisfaction, internal audits, management review9.1 to 9.3
ImprovementCorrective actions, continual improvement10.1, 10.2

The chapter names in the first column are an example. Many companies structure their manual exactly by the standard, others by their own processes and refer to the standard chapters in a table. Both are permissible as long as every requirement has a place.

Structure your QM manual by ISO 9001: layout based on the High Level Structure

ISO 9001, ISO 14001, ISO 45001 and other management system standards follow the same basic structure, the High Level Structure (now the Harmonized Structure). Clauses 4 to 10 have the same names in all of these standards. If you structure your manual accordingly, you can add another standard later and the structure stays the same. This is the basis for an integrated management system.

Clauses 4 to 10 of ISO 9001, assigned to Plan, Do, Check and Act

Sample outline based on ISO 9001:2026 (an example, your outline may differ):

  1. Introduction: Purpose of the manual, scope, change history
  2. Company: Company profile, sites, products and services
  3. Terms and abbreviations
  4. Context of the organization: 4.1 Company and environment, 4.2 interested parties, 4.3 scope, 4.4 process landscape
  5. Leadership: 5.1 Management commitment, 5.2 quality policy, 5.3 roles and responsibilities
  6. Planning: 6.1 Risks and opportunities, 6.2 quality objectives, 6.3 planning of changes
  7. Support: 7.1 Resources, 7.2 competence, 7.3 awareness, 7.4 communication, 7.5 documented information
  8. Operation: 8.1 Planning, 8.2 customer requirements, 8.3 development, 8.4 purchasing and suppliers, 8.5 production and service provision, 8.6 release, 8.7 nonconforming outputs
  9. Performance evaluation: 9.1 Metrics and customer satisfaction, 9.2 internal audit, 9.3 management review
  10. Improvement: 10.1 Continual improvement, 10.2 corrective actions

For medical devices under ISO 13485, the outline looks different. This standard follows the older structure with clauses 4 to 8. There, for example, risk management, validation and traceability belong firmly in the manual.

The manual begins with a cover page and a change history. The cover page names the company, document number, revision level and who created, reviewed and approved the manual. Depending on your needs, you add further details, for example sites, scope or the contact person for quality management. Keep the cover page clear so readers can grasp everything at a glance. The change history shows what changed and when for each revision.

In eQMS, you set up this structure directly in the software with an outline template, and you upload an existing manual including its revision numbers. The section on eQMS below shows how.

QM manual template: download a sample outline

Sample outline of a QM manual based on ISO 9001

The outline with chapters 1 to 10, a sample cover page and a template for the change history. As an editable Word file. All content consists of examples that you adapt to your company. The outline gives you the framework, and the content comes from your own processes. It is best to describe them together with the employees who carry them out every day.

Download sample outlineWord

What makes a good QM manual

Readers who open a manual look for answers about your company rather than the wording of the standard. Good manuals share these five characteristics:

  1. It describes your work. Every chapter explains how your company meets a requirement, in your words and with your examples. Write in the language of your readers and explain technical terms the first time they appear. That way, production understands the manual as well as the auditor does.
  2. It stays lean. The manual gives the overview, and the details are in procedures (SOPs) and work instructions. A reference is enough, and the reader gets there with one click.
  3. Management stands behind it. Quality policy and objectives are derived from the strategy and approved by top management.
  4. Roles instead of names. Responsibilities are tied to functions such as "Head of Purchasing". That way, the manual stays valid when people change.
  5. It is up to date. Every chapter has a revision level, an approval and a date for the next review.
Map it in eQMS

Here is how to build your QM manual, for example with eQMS

Chapters in Word, forms on the network drive, approvals by email: this is how a manual quickly gets spread across many places. In eQMS, you manage the manual, related documents and approvals in one place, and your employees directly find the valid documents. The following sequence has proven itself at the start. The names in the examples are examples, and you set up the outline and document types according to your needs.

  1. Choose an outline template.

    eQMS comes with outlines based on standards, including ISO 9001, ISO 13485, ISO 50001 and IATF 16949. This gives your manual the chapter structure of the standard in just a few minutes.

  2. Upload existing chapters.

    Upload your Word files, even several at once. You keep the previous revision number and continue counting in eQMS. If you wish, we will take care of the import for you.

  3. Assign document types.

    Identify each document as a manual chapter, procedure (SOP), work instruction or form, for example. This way, you distinguish specifications and records at a glance.

  4. Assign to multiple places.

    One document appears in the standard chapter and in the department at the same time. The auditor finds it through ISO 9001, and employees through their area. Your organizational chart can also serve as an outline.

  5. Link related documents.

    Attach forms, checklists and instructions to the manual chapter that requires them. The reader jumps from the overview straight to the detail.

  6. Set up headers and footers.

    Title, document number, revision level, and reviewer and approver with date are placeholders in the header and footer, and the approval workflow enters them itself. This way, every chapter carries the key details from your cover page.

  7. Review, approve, distribute.

    Every chapter goes through review and approval based on the four-eyes principle. After publication, employees confirm they have read it with one click, and a follow-up reminder prompts you for the next review. The document control page shows how this works in detail.

With every change, the chapter receives a new revision level, and the earlier version moves to the archive. This creates your manual's change history as you work. To learn how you build the entire QM documentation beyond that, with the document pyramid and outlines for multiple standards, read the QM documentation page.

What must a QM manual contain?

Typical contents are the scope with justification for non-applicable requirements, quality policy and quality objectives, the process landscape, roles and responsibilities, and references to related documents. Many companies structure the content by clauses 4 to 10 of ISO 9001. Under ISO 13485, the description of the document structure and the references to the procedures are also required.

Is a QM manual mandatory?

Since the 2015 version, ISO 9001 no longer requires a manual under that name. The standard does require documented information, such as scope, policy and objectives, and the manual is the usual place for it. ISO 13485 for medical devices still explicitly requires a quality manual. If in doubt, ask your certification body what it wants to see in the audit.

How long should a QM manual be?

As long as necessary to describe your QM system clearly. A lean manual gives the overview and refers to procedures (SOPs) and work instructions for details. For small and medium-sized companies, a few dozen pages are often enough. What matters is that every requirement of the standard has a place and every reference leads to the valid document.

Who writes the QM manual?

Usually, the Quality Management Representative (QMR) coordinates the manual. The content comes from the departments, because they know their processes best. Top management approves the quality policy and objectives. In eQMS, everyone involved works on the same document, and review and approval are assigned to defined people.

QM manual or process descriptions: what do I need?

They complement each other. The manual shows the big picture: how the processes connect, who is responsible, which rules apply. Process descriptions and procedures (SOPs) show each workflow step by step. In eQMS, you link the two, and the reader jumps from the manual chapter directly to the matching process description.

How do I keep the QM manual up to date?

Give each chapter an owner and a review date, for example once a year before the management review. Changes go through review and approval and receive a new revision level. In eQMS, follow-up reminders prompt the review, the read confirmation shows who knows the new version, and the change history is created automatically.

Can I adopt a sample manual?

A sample works well as an outline. It shows which chapters you need and where each requirement has its place. You write the content from your own workflows, ideally together with the employees who carry them out every day. That way, the manual describes your company, and the sample outline to download is the starting point.

Standard understood.
Now put it into practice with eQMS.

Try free for 14 days With a personal demo, followed by 14 days of the full version with support.