The approved instructions changed on Monday. On Tuesday, an operator starts a supplement run using the packet printed last week. The product name is right. The batch size looks familiar. Nothing on the bench makes the mistake obvious.
This is a document handoff problem, not simply a filing problem. As supplement SKUs grow, more people reuse familiar packets, saved PDFs, and local copies. A clean master file does little good if an obsolete version is still the easiest one to reach.
A practical supplement document version control process connects approval, the effective production boundary, packet issuance, and the record of what actually happened. Here is how to build that handoff without pretending that a filename alone controls production.
What is the difference between the approved master and the working packet?
The master manufacturing record defines the instructions for making the product. The batch production record captures the particular run. Those are related records, but they serve different purposes.
For U.S. dietary supplement manufacturing subject to these requirements, 21 CFR 111.205 requires a written master manufacturing record for each unique formulation and each batch size. 21 CFR 111.260 sets out batch-record contents, including component identifiers, actual results, and documentation at the time of performance.
The control sheet below is an operational aid, not a complete regulatory procedure or a substitute for qualified quality review. Its purpose is narrower: make the approved instructions reach the right production runs, and retain evidence of which instructions were used.
If you are still defining the underlying record set, start with the records to prepare before launching a supplement SKU. This article addresses what happens when those existing records change.
Why does “use the latest version” leave too much unanswered?
Latest can mean most recently edited, most recently approved, or most recently downloaded. Those are not necessarily the same document.
Suppose a powder-blending instruction receives a revised mixing sequence. The new version has approval, but an earlier run is already underway. Another run has materials staged but has not started. A contractor has downloaded the old packet for next week.
An announcement saying “new file available” leaves all three situations unresolved. Instead, specify the change boundary: which future run uses the revision, how existing work is assessed, and who authorizes any exception. Do not assume work already underway should switch instructions mid-process.
Avoid mixing draft and approved documents in one production folder. Make approval status visible, and give operators a clearly identified source for issued instructions rather than expecting them to compare timestamps.
What belongs on a revision-to-run handoff sheet?
Use a short change record with the following fields. Adapt it with your quality lead to fit the actual process and responsibilities.
- Record identity: product, formulation identifier, applicable batch size, and master record identifier.
- Revision identity: previous version, replacement version, approval reference, and responsible approver.
- Change summary: the actual instruction changed, not merely “updated document.”
- Effective boundary: the first covered batch or another unambiguous production trigger, with any exceptions documented.
- Open-work assessment: runs underway, packets issued but unused, and work staged for later production.
- Copy disposition: where superseded working copies were removed or blocked from new use, while historical records remain retained.
- Handoff confirmation: who received the change, what instruction or training was needed, and who checked completion.
Ingredient lots belong in the appropriate batch records; a revision sheet should link to affected work rather than becoming a competing lot ledger. Keep quality records connected through stable identifiers so reviewers can follow the decision without interpreting a string of email subjects.
How should you handle packets already printed or downloaded?
Separate them into three groups before the new instructions take effect.
Not yet used: identify the issued packet and withdraw it from production use through your controlled procedure. Issue the approved replacement and record the exchange. Do not rely on everyone noticing a new link.
Work already started: preserve what was issued and what was actually performed. Have the responsible quality personnel assess the situation and document the direction. An operator should not improvise a transition because the newer document appears preferable.
Completed historical records: keep them as evidence of the run. Superseded does not mean disposable. Do not replace an old executed record with a clean current template, or make historical work appear to have followed instructions that did not exist at the time.
Include contractor copies in this check. Ask for acknowledgement against the specific record and revision, not a vague confirmation that “the files” were received.
What would a clear handoff look like in practice?
Consider an illustrative capsule product whose approved instructions change from revision B to revision C. Run CAP-092 is underway with B. Packet CAP-093 is printed but unused. CAP-094 is planned for an outside manufacturing partner.
The handoff record identifies all three. Quality personnel document the direction for CAP-092 based on the actual change and work completed. CAP-093’s unused B packet is withdrawn and replaced before work begins. The partner confirms receipt and intended use of C for CAP-094.
At each start, the assigned person checks the product, batch size, master identifier, revision, and effective boundary against the issued packet. This is more useful than checking the product name alone.
The completed batch record then preserves the instructions used and actual execution evidence. If one bulk batch feeds several package configurations, maintain the separate relationships described in splitting a supplement bulk batch into finished-SKU records; a master revision should not erase those distinctions.
What should you do if an obsolete packet was used?
Pause the affected activity as appropriate under your procedures, identify the material and records involved, and notify the responsible quality personnel. Preserve the original packet and document the facts: which steps occurred, when, under whose instruction, and with which materials.
Do not backdate a replacement record or quietly copy results onto the new template. Quality personnel need the real sequence to assess the impact and determine disposition. Using the wrong revision does not, by itself, establish that a product is safe or unsafe; that requires an assessment of the actual differences and work performed.
Frequently asked questions
Can a document filename serve as the revision identifier?
It can help navigation, but put the controlled identifier and revision inside the document too. Renaming a download should not remove its identity or turn an unapproved file into an approved instruction.
Does a typo correction need the same treatment as a process change?
Your approved document-control procedure should define change categories and review requirements. Have the responsible reviewer classify the correction; operators should not independently decide that a changed instruction is insignificant.
Can we keep a reference copy beside the equipment?
Only with a clear way to control its status and prevent obsolete instructions being used. A convenient bench copy creates another location to check whenever the approved instructions change.
Make the next revision a traceable handoff
Choose one upcoming document change. Identify every unused issued packet, open run, and outside recipient before setting the effective boundary. Assign one person to confirm the handoff is complete. The goal is simple: nobody should have to guess which approved instructions apply when production starts.
