Manufacturing: Avoiding Uncontrolled Versions of Drawings and Quality Docs
Drawing-A102-Rev3-FINAL-use_this_one.dwg isn't a joke, it's someone's actual file. Why uncontrolled revisions are a production problem, not just an organization one.
In most plants or engineering shops, some version of this problem already exists: a drawing circulates by email or a shared folder, someone edits it, uploads the new revision under a different name, and the old one stays right there — accessible, with no clear mark that it's now obsolete. Sooner or later, someone on the shop floor works off the wrong revision.
The real problem: which revision is current?
The symptom is easy to recognize: Drawing-A102-Rev2.dwg, Drawing-A102-Rev3.dwg, Drawing-A102-Rev3-FINAL.dwg, and Drawing-A102-Rev3-FINAL-use_this_one.dwg all sitting in the same folder. Each name is an attempt to signal "this is the right one" with no real mechanism guaranteeing it — it depends on the right person having seen the right file before printing it or sending it to production.
Getting this wrong isn't just an administrative cost: a part built off an obsolete revision can mean rework, wasted material, or in the worst case, a nonconformance that reaches the customer.
Why this isn't just an organization problem
Quality management systems like ISO 9001 require documented revision control as a formal requirement, not an optional best practice — a quality document or drawing without a clear revision history is, on its own, an audit finding. "We keep it organized in folders" isn't the same as being able to show, document by document, who approved each revision and when the previous one stopped being current.
What real revision traceability actually looks like
When a drawing is a Record instead of a loose file, every new revision is uploaded as an additional version of the same record — never as a new file with a similar name. That means there's only ever one "current version" at any given time, unambiguously visible, with earlier revisions kept in the history instead of floating around under names that invite confusing them with the current one.
Whoever searches for drawing A102 finds a single result: the current revision, with earlier ones accessible but explicitly marked as history, not as valid alternatives.
What changes day to day on the floor
On the shop floor, looking up a drawing by its code stops being a bet on whether someone named the file correctly — it always lands on the current revision. In a quality audit, showing revision history stops being a manual reconstruction task (digging through email, asking who has the newest version) and becomes a direct query against the record.
Frequently asked questions
Does this replace my CAD or PLM software?
No — design and version control during a drawing's development still live in your CAD or PLM tool. The gap this closes is what happens after a drawing gets released: how it's distributed, searched, and kept current for everyone who needs it (the floor, quality, purchasing), who typically don't have and shouldn't need access to the design system.
How does this relate to the revision traceability a customer asks for in an audit?
Directly — it's the same question in a different shape: "show me who approved revision 4 of this drawing, and when revision 3 stopped being used." With a real version history, that question has an immediate answer instead of requiring the history to be reconstructed by hand.