Red-line markups on printed procedures. Email chains with 'Final_v3_FINAL_USE_THIS.docx'. If this sounds familiar, you're not alone. Here's the revision control system that actually sticks.
There is a procedure pinned to the pegboard at workstation 7. It has coffee stains on one corner, three handwritten annotations in red pen, and a red-ink stamp in the corner that reads "OBSOLETE — DO NOT USE" applied in 2023.
It is now 2026. The procedure is still there. Operators still consult it.
This is not a hypothetical. Variations of this scenario exist in manufacturing facilities at every scale, in every sector, in every country with a manufacturing base. Poor revision control is among the most pervasive quality problems in manufacturing and among the most expensive. It does not look expensive until it produces a nonconformance. Then it looks exactly as expensive as it always was.
The failure modes cluster around a few predictable patterns.
An engineer updates a critical dimension. They send an email to the production supervisor. The supervisor reads it, makes a mental note, perhaps prints and attaches a sticky note to the relevant page. Meanwhile, three other supervisors and two leads on different shifts never received the email. The formal procedure still shows the old dimension.
Three weeks later, a second-shift operator runs 140 parts before the discrepancy is noticed. The email is evidence that the engineer communicated the change. It is not evidence of a controlled document release. The corrective action requirement will be painful.
When a formal procedure update takes too long to process through document control, someone with authority annotates the current printed copy. It is faster. It gets the information to the floor. And it creates a document control problem that compounds with every subsequent annotation.
Annotated procedures are uncontrolled. There is no approval signature on the annotation. There is no revision number. There is no way to know how many annotated copies exist, which annotations are current, or which have been superseded by later annotations. Operators learn to look for red ink as the "real" instruction. The formal procedure becomes background noise.
The transition to digital document storage was supposed to solve this. In practice, most shared drive implementations create new version control problems.
Files get named with version indicators that look controlled: "Assembly_Proc_Rev12_FINAL.docx." Then someone makes a change and saves as "Assembly_Proc_Rev12_FINAL_v2.docx." Then "Assembly_Proc_Rev12_FINAL_v2_updated_JR.docx." Within a year, the folder contains twelve versions of the same procedure with no controlled mechanism for determining which is current or ensuring obsolete versions are inaccessible.
Operators learn to open the most recently modified file, which is sometimes the right answer and sometimes not.
You do not need enterprise QMS software to have functional revision control. You need four things, applied consistently.
A single authoritative source. Every document must have exactly one controlled version that is the official current version. Whether it is a physical binder in the supervisor's office or a controlled directory, there must be a clear and unambiguous single source of truth that operators know to use.
A release process. Every change to a procedure must go through a defined process that includes review, approval, and controlled release before operators use the changed procedure. The process does not have to be elaborate. It does have to happen every time, without exception.
Obsolescence handling. When a new version is released, the old version must be removed from use. This is the most commonly skipped step. "Released the new version" is not complete without "removed all copies of the old version." These are two required steps in the same process.
Point-of-use currency verification. Operators must have a mechanism to verify that the procedure they are using is current. A revision number and date on every procedure, combined with a posted list of current revisions accessible to operators, satisfies this at minimal cost and effort.
These four elements are the minimum. They are also sufficient to pass most document control audits if implemented consistently. Most organizations that fail document control audits are missing one of these four — usually the third or fourth.
The assumption that electronic document control is always superior to paper is not well-supported by actual manufacturing experience.
Electronic systems have real advantages: searchability, controlled distribution through system-enforced access, audit trails, and the ability to ensure only current documents are accessible. For large facilities with complex procedure libraries and multiple manufacturing sites, electronic document management is clearly superior.
Electronic systems also have failure modes. Systems go offline. Tablets at workstations need charging. Operators who are accustomed to physical procedures do not trust digital ones and print them anyway, creating the same uncontrolled copy problem that existed before. And unauthorized copies proliferate outside the system as soon as the system creates friction.
Paper-based systems can be made to work with disciplined process execution. The four minimum requirements apply regardless of medium. A well-run manual document control system beats a poorly run electronic one every time. The system matters less than the discipline.
A manufacturing facility with functional revision control has visible characteristics.
Every procedure at every workstation has a visible revision number and issue date. When you ask an operator how they would know if a procedure changed, they can tell you — and the answer is something other than "the supervisor would let me know."
When a procedure is superseded, the old version is physically removed or marked unmistakably as obsolete the same day the new version is released. There is no lag, and there is no exception.
The QE who owns document control can tell you, without hesitation, how many active procedures exist, what the current revision is of any specific document, and when each was last reviewed.
Engineering changes have a defined, documented process for translation into procedure updates, with a defined maximum lag time between drawing change release and work instruction update.
None of this is technically sophisticated. All of it requires consistent discipline. Consistent discipline requires clear ownership, regular auditing, and leadership that treats document control as an operational requirement rather than an administrative formality.
The procedure at workstation 7 is still there because no one with authority made removing it their responsibility. That is the entire problem — and it has nothing to do with software.
Coplain makes creating and maintaining current work instructions fast enough that staying current stops being the obstacle. Free trial at coplain.com.
Coplain turns any work instruction into a print-ready, audit-proof job aid in minutes.
Try Coplain free →