ISO 9001 clause 7.5.1: decide what the QMS needs to document

What clause 7.5.1 requires in practice

Clause 7.5.1 sets the starting point for documented information. The quality management system must contain two sources of information. The first is whatever the standard itself calls for in its various clauses, such as the scope, the quality policy, objectives and certain kinds of evidence. The second is whatever the organisation decides is necessary for its system to be effective, which is a judgement it must be able to explain.

A note to the clause confirms that the extent can differ between organisations. Relevant factors are the size of the business and its type of activities, the products and services it offers, how complex the processes are and how they interact, and the competence of the people doing the work. A small team of experienced specialists may need very little written down; a multi-site operation with frequent staff changes may need much more. The clause does not require a quality manual, a fixed number of procedures or any particular document titles. The output is a reasoned decision about what to keep, supported by an understanding of the standard's own requirements and of the organisation's real risks.

Separate standard requirements from local needs

First identify documented information explicitly required by the applicable clauses. Examples include the QMS scope, quality objectives and evidence required for particular activities. Use the authorised standard to establish the complete requirements rather than relying on a generic internet checklist that may use an earlier edition.

Then examine what the organisation itself needs for effective operation. A customer-specific configuration rule or a complex handover instruction may be necessary even if ISO 9001 does not name that document. The organisation should be able to explain the need without claiming that every chosen document title is universally mandated.

Look for decisions that depend on shared information

Consider where people could act inconsistently without reliable information. Repeated questions, variation between teams or errors after staff changes may indicate a gap. Also consider evidence needed to support conclusions about completed work. Information that explains the method serves a different purpose from information showing the result.

Existing business records can meet the need. A controlled workflow, approved specification or suitable transaction system may be more useful than a separate quality form. Avoid duplicating information solely to make the QMS appear more substantial. Duplication can create conflicting versions and extra work without improving control.

Why deciding what to document matters

Too little information leaves people guessing, and different teams give customers different answers. Too much creates a burden that nobody maintains, and staff stop trusting any of it. Deciding deliberately what the system needs keeps the effort proportionate and the content useful. It also lets the business show an auditor a clear reason for each item, which is stronger than a long list that exists only to look complete. For growing organisations, the decision matters when new staff join or work moves between sites, because the information then carries what experienced people previously held in their heads. Getting this right early prevents duplicate records, conflicting versions and wasted maintenance time.

How to implement clause 7.5.1

Work from the standard first, then from your own operations. One way Sterling's teams do this is to build a short list of required items from the authorised text and then add items where the work shows a real need.

1. Read the clauses of the current edition and note each place that calls for documented information, using the authorised text rather than a generic checklist.
2. Map where each item already exists in your business systems, workflows or customer agreements.
3. Walk through key processes with the people who run them and ask where inconsistency, repeated questions or errors after staff changes occur.
4. For each gap, decide whether an instruction, a decision rule or a record would help, and write down the reason for the choice.
5. Prefer integrating the information into existing tools over creating a parallel quality form.
6. Review the decision when processes, customers, risks or team competence change, and remove items that no longer serve a purpose.

Evidence an auditor expects for clause 7.5.1

The auditor tests whether the organisation can explain its choices and whether the information it has actually supports the work. Typical evidence includes:

• the documented information the standard calls for, available and current for the scope of the system;
• an explanation from the process owner of why certain additional information was judged necessary;
• observation that instructions exist where staff need them and are consistent with actual practice;
• interviews showing that people know which information governs their work;
• signs that the extent has been reviewed when the business changed.

Common nonconformities with clause 7.5.1

Typical findings arise from either omission or excess.

• A document or record that the standard calls for is missing or out of date.
• A process depends on knowledge held by a few people and no information supports it, with inconsistent results.
• Duplicate records exist in two places with different values, because both were assumed to be compulsory.
• Information was copied from a generic template and does not reflect how the organisation really works.
• Nobody can explain why certain documents exist or whether they remain necessary.

Illustrative software example: customer-specific configuration rules

Illustrative manufacturing example: removing redundant records

A hypothetical manufacturer records inspection results in its production system and copies the same values onto a paper QMS form. The duplicate entry adds delay and sometimes creates discrepancies. Staff assume both are compulsory because the paper form was introduced during an earlier certification project.

The team reviews the applicable requirements and the evidence needed. It confirms whether the production record is reliable, accessible and sufficiently controlled, then removes unnecessary duplication where appropriate. The objective is not to eliminate evidence, but to preserve a trustworthy account without maintaining two competing records of the same event.

Use competence and complexity carefully

Competent, experienced people may need less detailed instruction for a simple task than a new team performing a complex activity. That does not mean competence removes every documented-information requirement. Explicit standard requirements still apply, and the organisation must consider continuity, consistency and interfaces as well as individual capability.

Similarly, a small business can have a technically complex process requiring substantial information, while a larger business may use a straightforward, well-controlled workflow. Headcount alone is a poor basis for deciding the necessary documentation. Examine the actual process and the consequences of missing or unclear information.

Review usefulness as the system changes

New services, technology or customer requirements may create information needs or make existing material obsolete. Review whether information remains necessary and sufficient. Documents retained without a clear purpose can obscure the information people actually need.

Common failures include adopting a full template library without tailoring, omitting locally necessary instructions and treating every business document as part of the QMS without considering relevance. Another is claiming that “the standard does not require a procedure” as a reason to ignore an obvious information gap. The organisation's own effectiveness requirement still matters.

Once information is needed, apply creation and updating and control arrangements. Choosing the right information is the first step; keeping it suitable and usable is the next.