Document Control: From Draft to Retirement, Without Superseded Copies
The question an auditor always asks: which version applied when this batch was made? Document control is how you answer in seconds.
In Short
- Only the current approved version should be available where work happens.
- Train people before a new version takes effect.
- Archive old versions; never delete them.
Quality Management Buyer Guide
For quality, regulatory and operations teams choosing quality management software. Use it with or without V5.
- Map every issue from raised to human closure.
- Set CAPA effectiveness criteria before you act.
- Separate regulation, configured workflow and lab features.
We ask for your name and email so we can handle this request. The full guide then opens on this site, ready to translate, print or save. Privacy policy. Practical orientation, not legal advice; your quality unit decides which rules apply.
UltimateFree guide
Quality Management Buyer Guide
For quality, regulatory and operations teams choosing quality management software. Use it with or without V5.
Document control makes sure people work from the current approved version of a procedure, instruction, specification or form, and that older versions are withdrawn but kept. When it fails, the failure is often invisible until an audit finds someone working from a superseded copy. This guide covers the requirements behind document control, the lifecycle from draft to retirement, common audit findings, the link to change control and training, and retention.
What document control is
Document control covers documents that tell people what to do: procedures, work instructions, specifications, master records and blank forms. Records, the completed evidence of what was done, are controlled differently: they are kept unchanged for a set period.
More on what document control is
Document control answers four questions for every document: which version is current, who approved it, who needs to know it changed, and where the old versions are.
The requirements behind it
ISO 13485:2016 clause 4.2.4 and ISO 9001:2015 clause 7.5 set out document control for quality systems; for US devices, ISO 13485 applies through the QMSR (21 CFR Part 820, effective 2 February 2026). US drug manufacturers need written, approved procedures (21 CFR 211.100) and controlled master production records (211.186).
More on the requirements behind it
Supplement makers need written procedures and master manufacturing records under 21 CFR Part 111. EU GMP Chapter 4 covers documentation. Where documents and signatures are electronic, 21 CFR Part 11 and EU GMP Annex 11 apply.
The Document Lifecycle
Draft: the author writes or revises the document and states what changed and why. Review: subject experts check content.
Worked Example: SOP-014 Revision C to D
- 1 MarAuthor drafts Rev D under change CC-81; states what changed and whyAuthor
- 6 MarReviewer and QA approve, each signature with its meaningReviewer, QA
- 7–13 MarAffected operators trained on Rev DSupervisor
- 14 MarRev D effective; Rev C withdrawn from use and archivedDocument control
More on the Document Lifecycle
Approval: authorised people sign, with the meaning of each signature recorded. Effective: the document takes effect on a set date, after the people affected are trained where needed. Use: only the current version is available at the point of use. Periodic review: the owner confirms it is still correct at the interval your procedure sets. Superseded or retired: the old version is withdrawn from use but kept for the retention period.
Common Audit Findings
Uncontrolled printed copies on the floor. Procedures in use before the people doing the work were trained.
Pre-Audit Self-Check
More on common Audit Findings
Approvals missing, or signed by someone without authority. Periodic reviews overdue. Changes made with no record of what changed or why. Forms in use that do not match the current procedure. Old versions deleted rather than archived.
Change Control and Document Control
Most document changes start as a change request: a CAPA action, a process improvement, a new supplier or a regulatory update. Change control assesses the impact, including validation, training and other documents affected, and records approval before the change is made.
More on change Control and Document Control
The document revision then carries a reference to the change. Keeping both linked lets a reviewer see why a document changed and what else changed with it.
Retention and Retrieval
Keep each version and its approval history for the retention period your regulations and procedures require; for example, 21 CFR 211.180 sets drug record retention relative to batch expiry. Make sure you can show which version was effective on a given date, because inspectors often ask what procedure applied when a particular batch was made.
Questions
What is the difference between document control and records control?
Documents tell people what to do and change through controlled revisions. Records show what was done and must not change after completion.
Is a shared drive or SharePoint enough for document control?
It can be, if you configure and validate approvals, versioning, access, effective dates and audit trails, and control printed copies. Many teams find that hard to maintain, so test the controls you need rather than the storage.
How often should documents be reviewed?
Regulations generally do not set one interval. Set intervals by risk in your procedure, often every two to three years, and review sooner when processes or requirements change.
What is an effective date and why does it matter?
It is the date a new version takes effect. It lets you train people before the change and show which version applied to any batch or record.
Practical orientation, not legal advice. Rules differ by jurisdiction; your quality and compliance team decides what applies.
Keep reading
Supplement Allergen Control: Validated Cleaning and Labelling
Bakery Label and Date Code Control: a Practical US Guide
Bakery Pack Weight Control: Net Weight, Tare, and Sampling
Bakery Recipe Control: Versions, Scaling, and Batch Evidence
Bakery Waste and Yield Control: Measurement and Reconciliation
Electronic Batch Record (eBR) Explained