NCQM — National Committee for Quality Management

Search NCQM

Standards & technical reference

Management system auditing

An audit follows evidence against defined criteria. Its value depends on a clear purpose, a credible method and findings that can be traced to the work examined.

Reference family
ISO 19011
Document context
Technical guidance
Source organization
ISO

Scope and technical question

Management system auditing examines whether evidence supports conclusions against stated criteria. An audit may serve internal oversight, a customer’s supplier review or independent certification, but those purposes are not interchangeable. Before selecting questions, the organization needs to identify the objective, the activities and locations included, the criteria and the intended users of the report. ISO 19011 belongs in this discussion as auditing guidance. It is not a product test method or a certificate that an auditor can issue to a company.

Reference and publication context

The audit family separates three matters often combined in a single purchasing request: guidance on conducting audits, requirements for a certification body and the detailed rules of an assessment program. ISO 19011 addresses the first. ISO/IEC 17021-1 concerns bodies providing audit and certification of management systems. A sector program can add its own audit approach and acceptance rules. Recognizing these layers prevents a reference to general guidance from obscuring the actual criteria and authority of the assessment.

Editions and related documents

The selected publication records are ISO 19011:2026 (edition 4, published 2026-05-27). These identities were checked on 19 October 2026 in ISO Open Data. ISO 19011 is guidance for management system auditing. The documented 2026 edition must be distinguished from certification body requirements and sector audit programs. A program’s own procedures and transition arrangements determine how its audits are conducted; a newer general guide does not itself revise those arrangements.

Application in organizations

A supplier audit of traceability illustrates the method. The auditor can select a delivered item, follow its material records through processing and examine the handling of a change or a nonconformity. Interviews explain how the work is done; records and observations test that explanation. Findings remain attached to the selected criteria and sample. The report has practical value when it identifies where evidence was examined, what was found and which limits affect the conclusion, rather than simply recording that documents existed.

Adoption and regulatory context

The FDA MDSAP demonstrates why a named program matters. Participating regulatory authorities use a specific program for audits of medical device manufacturers. A supplier’s routine audit against general quality criteria does not become an MDSAP audit because it follows ISO auditing guidance. Program recognition, the auditing organization and the relevant regulatory requirements must be established separately. The same distinction applies when a buyer accepts an audit only under a named industry scheme.

Evidence and assessment questions

Examine the audit plan before relying on the report. Does the scope cover the manufacturing site or service process of interest? Are technical specialists available for the products examined? How were records and activities sampled? Are findings supported by identifiable evidence, and can the auditee understand the criterion involved? A closed corrective action also needs a basis: revising a procedure and showing that the revised process works are different forms of evidence. These questions concern the strength of the audit, not just the length of the checklist.

Research findings and limits

An audit is a sampled examination, so the absence of a finding does not prove that every transaction or product is conforming. A clear report makes that limitation intelligible without making the work meaningless. It can still identify persistent system failures, weaknesses at process interfaces and the effect of changes. This reference explains audit logic and the boundaries between guidance and programs. It does not reproduce ISO’s audit guidance or establish qualification requirements for a particular industry or certification scheme.

Related research and reading

Read this topic with management system certification bodies when selecting an external auditor. For an internal program, quality management supplies the organizational context and risk management helps explain how attention is directed. The standards and regulations study distinguishes a guide from the rules of a particular assessment scheme.

Official sources, access and corrections

Official sources were checked on 19 October 2026. Publication identifiers, editions and dates are based on the ISO deliverables dataset, licensed under ODC Attribution License 1.0; ISO is the source of that metadata. The sources establish the guide’s identity and the existence of a separate regulatory audit program; they do not make a generic audit checklist an approved MDSAP method. Full standards remain available through their publishers. Send a correction request with the reference, source and disputed statement so the evidence can be reviewed.

Document record

The entries below identify the publications examined. Catalogue status, regulatory adoption and scheme acceptance are separate questions.

Scroll horizontally to view all columns.

ReferenceEdition / publicationRecorded status or context
ISO 19011:2026 ↗4 · 2026-05-27Published

Source record

Official sources & access

Sources checked 2026-10-19. This date records preparation of this resource; publication, legal and transition dates are identified separately.

  1. Licensed publication identity, edition, date and catalogue stage

    ISO Open Data: Deliverables Metadata www.iso.org
  2. Example of a defined regulatory audit program, distinct from general audit guidance

    FDA Medical Device Single Audit Program www.fda.gov

This work is based on the iso_deliverables_metadata dataset from ISO Open Data, licensed under ODC Attribution License (ODC-By) v1.0.