Data & documents
Nobody's sure which version of the document is current
Engineering released revision D of the work instruction on Monday. On Wednesday, a machine operator builds to revision C—the one printed and taped above the workstation. Nobody did anything wrong. The paper just didn't get the news.
Version problems rarely announce themselves. They surface as scrap, as a customer comparing your quote to last year's spec sheet, or as an auditor standing at a workstation holding a document your system says was superseded months ago.
What it looks like
- The floor works from printed copies whose revision nobody verifies against anything—paper has no 'check for updates' button.
- A spec sheet emailed to a customer turns out to be last year's version, and now the order is negotiated against specs you've already changed.
- Folders fill with files named final, FINAL_v2, final_REVISED, and the only version control is whoever saved last.
- An audit or customer visit finds superseded work instructions at stations, triggering findings, scrambling, and a document-purge weekend.
- When a document changes, announcing it means an email—and hoping the people who printed it see the email.
Why it happens
Documents live in three places at once: a shared drive where anyone can save anything, inboxes where copies detach from their source, and paper at the point of work where updates never arrive. None of these has a notion of 'current.' Each is a pile, and the newest pile-item wins only if everyone looks in the same pile.
The heavier tools meant to solve this—ERP or PLM document modules—often go unused because releasing a document takes twelve steps and reading one takes a VPN. So the organization routes around them, and the shared drive wins by convenience. The gap isn't discipline; it's that control and convenience were never designed into the same place.
What it costs
The honest answer is that it depends on your volumes, your margins, and how long it has been going on. What is consistent across companies is where the cost shows up:
Scrap and rework
Work built to a superseded revision is waste with a paper trail—material, machine time, and labor spent making the wrong thing correctly.
Quality escapes
A customer working from your old spec sheet becomes a dispute, a concession, or a lost account when the delivered work follows the new one.
Audit findings
Superseded documents at workstations are among the most common audit findings—and each one costs prep time, corrective actions, and credibility.
Labor
People hunt for the right document, verify it by phone, and re-print binders on every change—small costs, endlessly repeated.
How a purpose-built system fixes it
A purpose-built document library makes 'current' a property of the system, not a hope. Every controlled document has exactly one released version. Drafts move through a review-and-release step; superseded versions archive automatically, still retrievable but clearly not current.
The important half is delivery: the floor accesses documents by station or by job—scan a work order, get the instruction at its current revision. Printing carries a watermark with the revision, so stray paper can be checked at a glance. And when a critical document changes, acknowledgment is tracked, so 'did everyone see rev D?' has an answer.
Illustrative Workflow
The system wins the same way the shared drive won: by being the easiest path. When the current document is faster to pull up than the old printout is to find, version control stops requiring discipline.
When a simpler fix is enough
At small scale—few controlled documents, few stations, infrequent revisions—a disciplined shared-drive convention plus a named document controller can carry you: numbered folders, one RELEASED location, read-only for everyone else. It works until it doesn't, and the failure mode is silent.
The line is crossed by regulated customers or audits, many workstations, frequent revisions, or printed documents that travel. When a wrong rev becomes scrap, a finding, or a customer dispute, a controlled document workflow costs less than the next escape.
Related systems and industries
- Document & data workflowsRelease control, point-of-work delivery, and acknowledgment tracking for controlled documents.
- Internal portalsOne place each role—and each workstation—finds the current version, and only the current version.
- Food manufacturingWhere specs, SOPs, and allergen documents carry audit weight.
- Dental laboratoriesWhere prescriptions and case instructions must match the work, every case.
Somewhere on your floor, a superseded document is taped to a machine.
A Workflow Review traces one document from release to the point of work—and finds where versions escape.