Skip to content

Guide · ISO 9001 documented information

ISO 9001 required documents: what you must keep.

ISO 9001 requires you to maintain four things: the scope of your quality management system (clause 4.3), the information your processes need (4.4), your quality policy (5.2) and your quality objectives (6.2). It also requires you to retain about twenty kinds of records as evidence, from calibration and competence to internal audits, management review and corrective action. A quality manual and named procedures are not required. Everything else is your call.

Last verified October 30, 2026

Keep current (maintain)
Scope, process information, quality policy, quality objectives.
Keep as evidence (retain)
About twenty kinds of records, across clauses 4 and 7 to 10.
Not required
A quality manual or named procedures. Keep them only if they help.
Format
Anything: paper, ERP, shared drive, photos, master samples.

Maintain versus retain

ISO 9001 uses one term, documented information, for what used to be called documents and records. Two verbs tell you which is which. ISO/TC 176 explains the split this way:

  • Maintain means keep it up to date. It applies to information that can change: procedures, instructions, the policy, the objectives. What used to be called a document.
  • Retain means keep it as evidence. It applies to information that does not normally change once created: an inspection result, an audit report, a training record. What used to be called a record.

The clause numbers below are ISO 9001:2015, the edition most certificates are to today. Labels and the auditor's view are ours; the list follows ISO/TC 176's own guidance on documented information.

Documented information you must maintain

ISO 9001:2015, documented information to maintain
ClauseWhatWhat an auditor looks for
4.3Scope of the quality management systemWhether the scope matches the work you actually do and the certificate wording, and whether any requirement you treat as not applicable is justified.
4.4Information your processes need to runWhatever your people rely on to do the work consistently: process descriptions, instructions, specifications. The auditor checks the version in use is the current one.
5.2Quality policyThat it exists, is current, and that people can explain what it means for their job.
6.2Quality objectivesThat objectives are measurable, someone owns each one, and results are tracked.

Two of these have their own glossary entries: the quality policy and the quality objectives. The scope is also where an auditor expects to see which requirements you treat as not applicable, most often design and development, and why; see exclusion.

Documented information you must retain

ISO 9001:2015, documented information to retain
ClauseWhatWhat an auditor samples
4.4Evidence that processes run as plannedWhatever you decided you need to be confident; the auditor tests that decision against what happens.
7.1.5.1Monitoring and measuring resources fit for purposeCalibration and check records for the gauges and instruments that decide accept or reject.
7.1.5.2Basis for calibration where no national or international standard existsHow you verified a tool when there was nothing to trace it to.
7.2CompetenceTraining, qualifications or experience for people whose work affects quality, matched to the job they do.
8.2.3Review of customer requirementsOrder or contract review before you commit, including what happened when requirements changed.
8.3.2 to 8.3.6Design and development: planning evidence, inputs, controls, outputs, changesOnly if you design. Reviews, verification and validation results, and approved changes for a sample project.
8.4.1Evaluation, selection, monitoring and re-evaluation of external providersWhy each key supplier is approved, how you track performance, and what you did when one let you down.
8.5.2Unique identification of outputs, where traceability is requiredLot, serial or job identifiers that link a delivered output back through production.
8.5.3Customer or external provider property lost, damaged or unsuitableWhat happened and how the owner was told.
8.5.6Review of changes to production or service provisionWho authorized a process change, on what review, and what follow-up was needed.
8.6Release of products and servicesEvidence the output met acceptance criteria, and who released it.
8.7Nonconforming outputsWhat went wrong, what was done, any concession, and who decided.
9.1.1Results of monitoring, measurement, analysis and evaluationThe data you use to judge how the system performs.
9.2.2Internal audit program and resultsThe plan, completed audits, and findings carried to closure.
9.3.3Management review resultsDecisions and actions, not just attendance. The auditor checks they were followed up.
10.2.2Nonconformities, actions taken and corrective action resultsRoot cause, the fix, and evidence the fix worked.

Clause 8.3 splits into five separate record points (8.3.2, 8.3.3, 8.3.4, 8.3.5 and 8.3.6) and applies only if you are responsible for design. Clause 8.1 e) adds a judgment call: ISO/TC 176 notes that it leaves you to decide what documented information operational planning and control needs. You are free to keep any other records you find useful; once you keep them, they are controlled like the rest.

What is not required, but often useful

ISO/TC 176's guidance lists documents that are not specifically required but can add value. None of them is mandatory:

  • Organization charts
  • Process maps, flow charts or process descriptions
  • Procedures and work or test instructions
  • Specifications, test and inspection plans, quality plans
  • Approved supplier lists and production schedules
  • Forms
  • A quality manual

The quality manual is the one people ask about most. ISO/TC 176 says it is no longer specifically required, and that keeping one is perfectly acceptable if it is a convenient way to describe your system. The same goes for procedures: specific documented procedures are no longer named. A manual or procedure that nobody uses is a liability, because it still has to be current, and an auditor will compare it with what people actually do.

How much more you need

Beyond the required list, the amount is yours to decide. ISO/TC 176's guidance says it differs from one organization to another depending on size and type of activity, how complex your processes are and how they interact, and how competent your people are. Three practical tests:

  • Would a competent new hire get it wrong without it? Then write it down. If skilled people do stable work the same way every time, an instruction may add nothing.
  • Does a customer, regulator or contract require it? Customer quality clauses can ask for specific records or retention periods. Those become part of your system.
  • Does a record prove something an auditor will ask about? Objective evidence does not have to be a document, except where ISO 9001 specifically asks for one. Auditors also observe work and talk to people.

ISO/TC 176 puts it simply: analysis of your processes should set the amount of documented information, not the other way around. Our guide to ISO 9001 for small business shows how that plays out in a firm of 10 or 50 people.

Keeping it under control

Everything in your system, required or not, falls under the control rules of clause 7.5. In an audit those rules come down to a few questions. Can you tell which version this is, and who approved it? Is the copy at the workstation the current one? Could it be lost, or changed without anyone noticing? Can you find last year's record when the auditor picks it?

Mistakes auditors find most

  • Obsolete copies in use. A printed instruction at a workstation that no longer matches the controlled version.
  • Template documents nobody follows. A procedure copied from a template describes a process you do not run. Each one is a finding waiting to happen.
  • Records that cannot prove anything. A training sign-in sheet with no link to the job, or a supplier list with no reason why each supplier is approved.
  • Management review with no decisions. Minutes that record attendance and nothing else.
  • Corrective action without evidence it worked. The fix is recorded; the check that it worked is not.

ISO 9001:2026 and documented information

ISO published ISO 9001:2026 on September 16, 2026. ISO's own summary of the edition lists clearer wording, more emphasis on leadership, quality culture and accountability, clearer handling of risks and opportunities, a new Annex A explaining terms and intent, and closer alignment with other management system standards. It does not mention documented information, and the summary is thematic, with no clause numbers.

Until March 31, 2028, initial certification can still be to the 2015 edition, and existing 2015 certificates must transition by September 30, 2029. For what the published 2026 text does and does not change, including clauses that moved, see what changed in ISO 9001:2026.

Common questions

What documents are mandatory for ISO 9001?

Four things you keep current: the scope of the quality management system (clause 4.3), the information your processes need to run (4.4), the quality policy (5.2) and the quality objectives (6.2). On top of those, about twenty kinds of records you keep as evidence, at clauses 4.4, 7.1.5, 7.2, 8.2.3, 8.3, 8.4.1, 8.5.2, 8.5.3, 8.5.6, 8.6, 8.7, 9.1.1, 9.2.2, 9.3.3 and 10.2.2. Everything else is your choice, based on what your people need. The list here follows ISO/TC 176's own guidance on documented information for ISO 9001:2015.

Is a quality manual required for ISO 9001?

No. ISO/TC 176 says a quality manual is no longer specifically required. If a manual is a convenient way to describe your system, keeping one is fine, but it then has to be kept current like any other document. Customers or sector programs sometimes ask for one, which is a business reason rather than an ISO 9001 requirement.

How many mandatory procedures does ISO 9001:2015 have?

None by name. ISO/TC 176 confirms that specific documented procedures are no longer mentioned. Instead you decide what documented information your processes need, and keep the records that show they ran as planned. Where you have no document for an activity and the standard does not require one, auditors can assess the activity directly against the standard.

What is the difference between maintaining and retaining documented information?

Maintain means keep it current: information that can change, such as procedures, the policy and the objectives. Retain means keep it as evidence of what happened: information that does not normally change once created, such as inspection results, audit reports and training records. Together they replace the older terms documents and records.

Did ISO 9001:2026 change the documentation requirements?

ISO's public descriptions of the 2026 edition list clearer wording, more emphasis on leadership, quality culture and accountability, clearer handling of risks and opportunities, a new Annex A and closer alignment with other management system standards. None of them mentions documented information. For what the published text does and does not change, clause by clause, see our page on what changed in ISO 9001:2026.

Do ISO 9001 documents have to be on paper or in special software?

No. ISO/TC 176's guidance says documented information can be in any format or medium, including paper, electronic files, photographs and master samples. An ERP, a shared drive or a well-organized folder structure all work, as long as people can find the current version where they work and it cannot be lost or changed without anyone noticing.

Related

Sources

Changelog

  • 2026-10-30 — Published. Clause list from ISO/TC 176/SC 2's Guidance on the requirements for Documented Information of ISO 9001:2015 and its ISO 9001:2015 FAQs. ISO 9001:2026 status from iso.org/9001-2026 and ISO/TC 176/SC 2's September 28, 2026 news item, neither of which describes a change to documented information.