ISO 9001 Clause 7.5: Control Documents Where Work Happens

What clause 7.5 requires in practice

Clause 7.5 deals with documented information, which means information the organisation needs to control and maintain, together with the records it keeps. It has three parts. Clause 7.5.1 says the system must include the documented information the standard calls for and whatever else the organisation decides it needs to be effective. Clause 7.5.2 covers creating and updating it, with suitable identification, format, media, and review and approval. Clause 7.5.3 covers control, so that information is available and suitable where needed, protected, and managed through distribution, storage, changes, retention and disposition.

The clause also reaches information that comes from outside, where the organisation has decided it is needed for planning or operating the system, and it expects evidence of conformity to be protected from unintended alteration. The amount of documentation is for the organisation to decide, taking into account its size, activities, process complexity and people's competence. The clause does not require a quality manual, a document register, an approval stamp or specific software. Those are choices, and the requirement is met by results: current, trustworthy information at the point of work.

Decide what information serves the process

Start with the decision or task the information supports. An instruction may explain how work should be performed; a completed record may show what happened. Both can fall within documented information, although their controls differ. Avoid assuming that every activity needs a separate procedure or that an electronic workflow removes the need to preserve evidence.

The extent of information depends on the organisation, process complexity, interactions and people's competence. Existing business systems can contribute. Check whether they preserve the necessary content and provide reliable access, rather than creating duplicate documents merely to give them ISO-related titles. Duplication can increase the risk that users select inconsistent versions.

7.5.2: create and change information deliberately

Suitable identification, description, format and media help users recognise the information. Review and approval should establish suitability and adequacy before release or change. The reviewer needs enough understanding to judge the content; a signature without that capability is a weak control.

For implementation, distinguish the authority to propose a change from the authority to approve it. Consider who needs to be told, what other information depends on the change and whether a transition creates ambiguity. These are practical ways to make revision control meaningful, rather than additional universally mandated document fields.

Why document control matters to the business

Poorly controlled information produces expensive mistakes quietly. People work from an outdated instruction, a customer specification is misread, or a record cannot be found when a customer asks what was done. Good control saves time because staff trust what they find, and it protects the business when a dispute or claim depends on proof of what was agreed and performed. It also supports growth, since new people and new sites can rely on one reliable source rather than on the memory of long-serving colleagues. For auditors, document control is where weak discipline shows first, because they can sample a live instruction and a completed record and compare them against what the team actually does.

How to implement clause 7.5

Aim for the smallest set of information that makes the work reliable, and control that set well. One way Sterling's teams begin is by following one process from request to delivery and noting where people look things up.

1. Identify the information each process needs, separating instructions that guide work from records that show what happened.
2. Check which items the standard calls for and which are needed because of your own risks, customers or staff changes.
3. Reuse existing business systems where they already hold reliable content, instead of duplicating it into separate quality files.
4. Decide how items are identified, who may propose a change and who reviews and approves it before use.
5. Set the access routes, protection, storage, retention and disposal arrangements, including for documents received from outside.
6. Remove or clearly mark superseded copies so that users cannot mistake them for current work instructions.
7. Sample a few live uses and completed records to confirm the arrangements work in practice.

Evidence an auditor expects for clause 7.5

An auditor checks that information is available where work happens and that records are trustworthy. Expect them to look at:

• a current instruction at the point of use, compared with the approved version and with what staff actually do;
• records of review and approval showing who judged suitability before release or change;
• how superseded information is withdrawn or identified so it is not used by mistake;
• completed records that remain legible, identifiable and protected from unintended alteration;
• interviews with users about how they find information and what they do when it seems out of date.

Common nonconformities with clause 7.5

Findings usually concern control in daily use rather than the existence of documents.

• Obsolete instructions remain in use at a workstation, shared folder or messaging channel.
• Documents were changed without evidence of review or approval by someone able to judge them.
• Records cannot be retrieved, are illegible, or have been edited after the event without a trace.
• External specifications or customer documents are used without anyone knowing which version applies.
• The organisation keeps extensive documents that nobody uses while a needed instruction is missing.

Illustrative software example: a release instruction and its evidence

7.5.3: control the full information life cycle

Information must be available and suitable where needed, while protected against loss of integrity or confidentiality and against improper use. Relevant controls address distribution, access, retrieval, storage, preservation, changes, retention and disposition. Necessary external information also needs identification and control. The objective is reliable use, not unrestricted access or restriction for its own sake.

Consider what happens when a person changes role, a supplier issues an updated specification or information must remain readable after a system change. Define retention using applicable obligations and business needs; ISO 9001 does not provide one retention period for every record. Protect retained evidence from unintended alteration and preserve enough context to interpret it.

Illustrative construction example: an external specification changes

A hypothetical construction contractor receives a revised client specification while work is underway. Saving it to a project folder is only the beginning. The responsible team checks which activities and subcontractors are affected, obtains appropriate review and makes the authorised revision available at the point of work.

Useful evidence could include the received revision, its review, the communication to affected owners and a sample showing the applicable version in use. The company also preserves the basis for work already completed. This example illustrates information control; it does not decide whether the technical change is acceptable or whether affected work needs reinspection.

What reviewers may examine

A reviewer may ask a worker to find an instruction, compare its version with the approved source and follow how a record is retrieved. They may examine externally provided requirements or test access after a role change. The evidence should demonstrate operation of the controls, not simply the existence of a document-control policy.

Frequent mistakes include approving content without checking technical suitability, treating a backup as a complete retention method, leaving uncontrolled copies in normal use and retaining personal access after responsibility changes. Another is making the system so cumbersome that workers build an unofficial parallel source. Investigate why that happens before adding another approval step.

Explore each numbered part