Most labeling errors that reach the market don't come from a lack of expertise. They come from a version problem: the right change made to the wrong file, an approval recorded against a document that later changed, or an obsolete label picked up for a reprint.
Document version control is the discipline that prevents this. In most industries, it means knowing which file is the latest. In a GxP-regulated labeling environment, that isn't enough. You need to know which version was approved, which version is in production, which versions are obsolete, and be able to prove all three to an inspector.
This guide covers what regulators actually require, the four failure modes that "latest version" thinking misses, what a defensible version control process looks like, and the questions an inspector is likely to ask.
What Version Control Means in GxP Labeling
General document management answers one question: where is the current file? GxP labeling version control has to answer four:
- Which version was approved? Not "the label," but a specific, uniquely identified document state, approved by named individuals.
- Which version is in use? The version that production, the printer, or the packaging line is actually working from.
- Which versions are obsolete? Every superseded version, and confirmation that none of them can still be used.
- What changed between them, and why? A documented reason for every change, and evidence of what was reviewed.
When these four answers diverge, and nobody notices, a labeling error follows. The approved version says one thing, the printed version says another, and the approval record can't tell you which is which.
What Regulators Require
There is no single regulation called "version control." The requirement is spread across the rules for labeling, quality systems, and electronic records.
Pharmaceuticals (US)
21 CFR Part 211 sets the current good manufacturing practice requirements for finished pharmaceuticals, and several sections bear directly on labeling versions:
- Labeling and packaging materials (211.122) require labeling to be examined before use, stored separately and identifiably by product and version, and obsolete or outdated labeling to be destroyed.
- Labeling issuance (211.125) requires strict control over the labeling issued for a packaging operation, so only the correct, current labeling reaches the line.
- Master production records (211.186) must include a specimen or copy of each approved label and piece of labeling, signed and dated by the person responsible for approval.
Where these records are electronic, 21 CFR Part 11 applies: audit trails, electronic signatures linked to specific records, and validated systems. (We cover the common misreadings of Part 11 in 21 CFR Part 11: The Compliance Assumptions Pharma Teams Make.)
Medical devices (US)
Since February 2, 2026, device manufacturers have operated under FDA's Quality Management System Regulation (QMSR), which incorporates ISO 13485:2016 by reference into 21 CFR Part 820.
That makes ISO 13485's document control clause (4.2.4) a US regulatory requirement. It expects documents to be reviewed and approved before issue, changes and current revision status to be identified, the relevant versions to be available at the point of use, and obsolete documents to be prevented from unintended use.
FDA also kept its own labeling section, 820.45, because it judged ISO 13485's labeling coverage insufficient. It requires manufacturers to inspect labeling for accuracy before release, and to document that release. For devices, version control and label verification are now explicitly linked in the regulation itself. (For the full device picture, see our Medical Device Labeling Requirements guide.)
European Union
In the EU, EU GMP Chapter 4 (Documentation) governs how GMP documents are created, approved, controlled, and retained. The current 2011 version remains in force.
A draft revision was published in July 2025 and, as of late September 2026, has not yet been finalized. It is expected together with the revised Annex 11 on computerized systems. It points clearly to where inspections are heading: data governance across paper, electronic, and hybrid systems, full lifecycle control from creation to archiving, and the ALCOA++ principles (attributable, legible, contemporaneous, original, accurate, complete, consistent, enduring, available, and traceable) as the basis for document integrity. If your labeling documents move between a design tool, a shared drive, email, and a print vendor, "hybrid" describes you.
Why "Latest Version" Isn't Enough: Four Failure Modes
1. Approval recorded against a name, not a document state
A reviewer approves "Carton_EU_v7.pdf." The file is edited afterwards, still called v7, and shipped. The approval record says v7 was approved. It doesn't say which v7. Unless the approval is tied to a specific, unchangeable document state, an approval record proves much less than it appears to.
2. Parallel edits that split the version history
Regulatory updates a dosage line while the studio fixes a layout issue, each working from the same starting file. Two "latest versions" now exist, each missing the other's change. Whichever is finalized, one correction is lost. We walk through how this plays out in review cycles in Promotional Review Has a Version Problem Nobody Is Fixing.
3. An obsolete version picked up for a reprint
A superseded file is still sitting in a shared folder, a print vendor's archive, or a colleague's downloads. A reprint is ordered, someone grabs the file that looks right, and an outdated label goes back into production. This is exactly what 21 CFR 211.122's requirement to destroy obsolete labeling is meant to prevent, and it's especially likely during transition periods, when old and new versions of the same product legitimately coexist.
4. Comparing against the previous version instead of the master
The final check before release compares the new file against the last version. That shows what changed since last time. It doesn't show whether the complete document matches what was approved, so an error introduced two revisions ago, and never caught, passes every subsequent review. This is the single most consistent root cause we see behind late-stage labeling errors, covered in depth in Why Pharma Artwork Errors Happen at the End of the Process.
What a Defensible Version Control Process Looks Like
These are the document version control best practices that hold up in a regulated labeling environment:
A single approved master. One controlled source of truth for each label's approved content, from which every language, market, and pack variant is derived and against which each is verified.
Unique version identifiers. Every version carries an identifier that can't be reused or edited, so an approval always points to exactly one document state.
Approval tied to the specific version. Sign-off is linked to the identified version in a way that can't be separated from it, meeting Part 11 electronic signature expectations where applicable.
Change control with a documented reason. Every change records what changed, why, who requested it, and who approved it. A change without a reason is a finding waiting to happen.
Master comparison at release. The release candidate is compared against the approved master, not just the previous draft, so unintended changes are caught along with intended ones.
Controlled access and withdrawal of obsolete versions. Only the current approved version is available at the point of use. Superseded versions are archived and clearly marked, and can't be issued to production or a print vendor by mistake.
A complete audit trail. Every version, comparison, deviation, and approval is recorded automatically and can be retrieved without reconstruction.
Periodic review. Approved labeling is reviewed on a set schedule, not only when someone requests a change, so outdated content doesn't survive simply because nobody touched it.
For how this fits into the wider approval workflow, see our Pharma Artwork Approval guide.
Version Control Across Languages and Markets
Version control gets harder with every variant. A single product might have twenty language versions, several pack sizes, and market-specific regulatory text, each with its own version history.
The practical rule: each variant's version history should trace back to a specific version of the master. When the master changes, every variant derived from it is affected and needs to be updated and verified. A change applied to the master that reaches eighteen of twenty language versions is the most common way a labeling error enters a multi-market product.
The same logic applies to device packaging levels. Unit, intermediate, and case labels are variants of a single specification, and all of them must stay consistent, as we cover in our UDI Labeling Requirements guide.
What an Inspector Will Ask
A useful test of your process is whether you can answer these quickly, for any label, without reconstructing anything:
- Which version of this label is currently approved, and who approved it?
- Can you show that the printed label matches that approved version?
- What changed between this version and the previous one, and why?
- How do you ensure obsolete versions can't be used?
- How do you know every language and market variant reflects the latest approved change?
- Where is the audit trail, and is it complete?
If answering any of these means searching email threads or comparing files by hand, that's where to start. (Our article on cutting inspection prep time covers why reconstructed evidence is itself a risk.)
Choosing Document Version Control Software for Labeling
General-purpose document version control software handles storage, check-in and check-out, and file history well. What it usually doesn't do is verify content: it can tell you a file changed, but not whether the new version still matches the approved master character by character, in every language.
For regulated labeling, look for tools that combine version history with automated comparison against the approved master, audit trails that meet Part 11 and Annex 11, and validation support for GxP use. Our Buyer's Guide to Artwork Verification Software covers what to evaluate in detail.
Version control isn't just a file-naming convention. It's how you prove that what shipped is what was approved.
Content Compare verifies every label version against the approved master, text, graphics, barcode and Braille, with a timestamped audit trail linking each comparison to a specific document version. See how it works on your own artwork.