Quality document control: version, approval and evidence

Quality document control ensures that the right person finds the right information, in the current version, when an activity must be performed or demonstrated. Without control, updated procedures coexist with old copies and evidence disappears when an audit or decision requires context.

Document versus record

A document guides an activity: a policy, procedure, instruction, specification or form template. It changes when the intended way of working changes. A record proves what happened: a completed checklist, approval, test result or audit report.

Documents must remain current. Records must preserve trustworthy evidence. Applying the same rule to both creates unnecessary bureaucracy or weak protection.

The document lifecycle

Creation and identification

Define purpose, owner, scope and a clear title. Codes can help large structures, but identification should serve retrieval and control rather than complexity.

Review and approval

The reviewer checks technical adequacy; the approver authorizes use. The history should show who decided, when and which changes were introduced.

Publication and access

Make one source the official version. People should find what applies to their work without maintaining personal copies. Permissions must protect sensitive content without blocking legitimate access.

Change and communication

A revision is not complete when the file is uploaded. Identify affected roles, communicate relevant changes and determine whether training or acknowledgement is needed.

Retention and disposal

Set retention rules using legal, regulatory, contractual and operational needs. Protect integrity and confidentiality throughout the period, then dispose of information in a controlled way.

Preventing obsolete versions

The greatest risk is often not an unapproved document but an old version still being used. Remove or replace copies at points of use, identify historical versions clearly and avoid sending editable files as the primary distribution method.

Evidence an auditor can follow

A reliable system should answer: What was the valid version on a specific date? Who approved it? What changed? Who received the update? Which records demonstrate execution?

Connecting document changes to nonconformity management and actions provides that context. A well-designed Quality Management System reduces the time spent reconstructing history and strengthens daily execution.

Control information, not paperwork

Document control exists to support consistent work and reliable evidence. Start with critical documents, define one official source, clarify ownership and make the current version easier to use than any uncontrolled copy.

Official references

• ISO guidance on documented information
• ISO 10013:2021 guidance for documented information

Frequently asked questions

What is quality document control?

It is the set of rules used to create, identify, review, approve, distribute, protect, change, retain and dispose of documented information required by the QMS.

What is the difference between a document and a record?

A document guides what should be done and must remain current. A record demonstrates what was done and is preserved as evidence.

How can obsolete documents be prevented from use?

Maintain one official source, control permissions, replace previous versions at points of use, notify affected people and identify copies kept only for historical purposes.

How long should quality records be retained?

Retention depends on legal, regulatory, contractual and operational requirements. Define a schedule with period, owner, protection and disposal method.