Document control is the system that guarantees the documents people actually use on the plant floor, procedures, SSOPs, HACCP plans, work instructions, forms, are the current, approved versions, and that superseded versions are pulled out of use. It is not glamorous, and it is where a surprising number of audits go sideways, because it only takes one operator following a two-revisions-old procedure to prove your control system is fiction.
This post covers what a document-control system has to do: version control, approval, controlled distribution, obsolete-document removal, and retention. It ends on the shift most plants are somewhere inside, moving from paper and shared drives to a real digital system.
What is document control in food safety?
Document control is the discipline of managing a document through its whole life: creation, review, approval, release, distribution, revision, and eventual retirement. The goal is simple to state and hard to hold: everyone using a document is using the same, current, approved version, and nobody is using an old one. It applies to the controlling documents that tell people how to keep food safe, your HACCP plan your sanitation SSOPs your standard operating procedures specifications, and the blank forms those procedures generate.
It is worth separating two related ideas. Document control governs the living documents that instruct work, the version you follow. Records control governs the completed evidence those documents produce, the filled-in log you cannot change after the fact. Both live under the same program, but they have different rules: a procedure is meant to be revised on a schedule; a record is meant to be permanent.
What does version control actually require?
Version control means every controlled document carries an identity that says, unambiguously, which version it is, and that identity changes every time the content does. In practice each document header carries a document number, a revision number or date, an effective date, and an approval signature or reference. When the content changes, the revision advances, the old revision becomes obsolete, and the change is logged. Without this, “the current SSOP” is an opinion, and two people can both believe they are following it while holding different paper.
Why does approval before release matter?
Approval is the control that separates a draft idea from a rule people must follow. No controlled document should reach the floor until a defined, authorized role has reviewed and approved it, and the approval has to be recorded, so an auditor can see who signed off and when. This is where document control connects to change management: a change to a HACCP plan, a critical limit, or a sanitation step is a food-safety decision, and letting it reach production without review is how unvalidated changes slip in. Approval also has to be role-based; the authority to approve an SSOP or a HACCP document should sit with defined positions, not with whoever happened to save the file last.
How do you control distribution and remove obsolete documents?
Controlled distribution means the current version reaches every point where the work happens, and only the current version. Obsolete-document removal is its inseparable twin: when a new revision is released, every copy of the old one is pulled from use. This is the single most failed element of document control on paper. Superseded procedures survive in binders, on clipboards, taped to equipment, and in the desk drawers of people who “know how it's really done.” An operator running Rev 4 while Rev 5 is the law is a finding, and worse, it is a real food-safety risk if the change mattered.
On paper, the defenses are physical: stamp obsolete masters “OBSOLETE,” keep a distribution list of who has controlled copies, and reconcile that list on every revision. Uncontrolled copies, anything printed for reference, must be marked so nobody mistakes them for the live version. The whole approach is fragile, which is the strongest argument for going digital. Every uncontrolled printout is a future finding waiting to happen, because the moment a revision drops, that printout becomes wrong and nobody is tracking it.
How long do you retain records?
Retention is where document control hands off to records control. Completed food-safety records, monitoring logs, corrective actions, verification, training, have to be kept for a defined period and be retrievable when a regulator or customer asks. Under FDA's preventive-controls rule, most required food records must be kept for at least two years, and records relating to the food-safety plan's adequacy (like validations) are held for at least two years even after you stop using them. Different schemes and customers may demand longer, so plants usually set a retention policy that meets the strictest requirement they face.
| Item | Typical practice |
|---|---|
| Preventive-controls / monitoring records (21 CFR Part 117) | Retain at least 2 years; retrievable within 24 hours to FDA on request |
| Food-safety plan & validation records | Retain at least 2 years, including after superseded |
| Superseded controlled documents (masters) | Archive one obsolete master per revision for traceability of change history |
| Customer / GFSI scheme records | Follow the strictest applicable requirement, often longer than regulatory minimum |
How do you build a document-control system?
- Inventory the controlled documents. List every document that instructs food-safety work, HACCP plan, SSOPs, SOPs, specs, forms, and assign each a unique number.
- Define the header standard. Require document number, revision, effective date, and approver on every controlled document, so version identity is unambiguous.
- Set approval roles. Define who may review and approve each document type, and require recorded approval before release.
- Control distribution. Maintain a list of where each controlled document lives, and push new revisions to every point of use.
- Remove and archive obsolete versions. On each revision, pull old copies from use, mark the master obsolete, and archive it for change history.
- Set retention rules. Define how long each record type is kept and how fast it can be retrieved, meeting the strictest requirement you face.
- Audit the system. Periodically walk the floor and confirm the documents in use match the current revisions, the real test of whether control is working.
How do you move from paper to digital?
Most document-control failures are paper-management failures: the obsolete copy nobody pulled, the revision that reached three of five lines, the binder last reconciled a year ago. A digital document-control system attacks those directly. There is one controlled source, so “current version” is a fact, not a hope; releasing a revision instantly makes the old one inaccessible at the point of use, so obsolete copies cannot linger; approvals are captured with the identity and timestamp of the approver; and every point of use sees the same live document.
If those approvals and records are electronic, they fall under 21 CFR Part 11 which sets the controls for electronic records and signatures, audit trails, access control, and signature integrity. That is not a burden to avoid; it is the same evidence you were trying to produce on paper, captured automatically. Connecting controlled documents to the work that uses them, so the operator opens the current SSOP at the machine, and the completed check flows into a retained record, is exactly the kind of workflow Harmony runs on the plant floor. When a document change also drives a process change, tie it to your corrective-action and change-management records so the reason for every revision is traceable, and make sure the same discipline covers the master records behind your Part 111 supplement or Part 117 GMP program.
By the numbers
The record-keeping expectations behind document control, from primary sources:
- FDA's preventive-controls rule requires most food records to be retained at least two years and made available to FDA, generally within 24 hours of request, and to be created concurrently with the activity (21 CFR Part 117, Subpart F).
- Records and signatures kept electronically must meet the controls in 21 CFR Part 11 including audit trails, access controls, and signature integrity.
- Dietary-supplement manufacturers must keep master manufacturing and batch records and control them under 21 CFR Part 111.
Document control is invisible when it works and catastrophic when it doesn't: the whole edifice of a food-safety system rests on the assumption that the procedure in someone's hands is the one you approved. Get the loop right, version, approval, distribution, obsolete removal, retention, and every other program becomes auditable. To see how a food operation runs controlled procedures and the records they generate on one connected system, look at the CLS case study.