The file that destroyed a batch
The operator opens the procedure on their workstation. Version 3.1, the one they printed last month and laminated for the clean room. The procedure says to add Excipient B at 45°C. They add it at 45°C. The batch fails.
Nobody told them about version 3.2. It was approved three weeks ago. The temperature window changed to 42°C based on process optimization data. The updated procedure is on SharePoint. The email announcement went out. But the laminated copy on the production floor still says 45°C.
This batch cost $180,000. The investigation took two weeks. Root cause: document control failure.
The archaeology of version control
SOP_
When the auditor asks for the current procedure, you're not sure which one to show. When they ask who approved it, you search for the signature page. When they ask who's trained on it, you check a different spreadsheet. One that may or may not reflect reality.
The gap between approval and the floor
A procedure gets approved on Tuesday. It's uploaded to SharePoint. An email goes out. But the operator doesn't read that email until Friday. If they read it at all. Meanwhile, they're executing the old version. They don't know the procedure changed.
The deeper problem: procedure version 3.2 was approved, but forty-seven people are still trained on version 3.1. Their training records say "current." The system doesn't know the procedure changed. Nobody invalidated their training.
In Seal, document approval and training are structurally connected. When Procedure-042 updates from version 2 to version 3, everyone trained on version 2 has their status changed to "expired." Retraining tasks are assigned automatically. Until they complete training on version 3, they cannot execute tasks requiring that procedure. The operator on the floor doesn't use the old procedure because the system won't let them.
One truth, one place
Every document exists in exactly one state: Draft, In Review, Approved, or Obsolete. When someone searches for Procedure-042, they see version 3.2. They cannot find 3.1 and use it. They cannot print an old version and post it. The system serves the current version and only the current version.
Version history shows every change. Comparison tools highlight what changed between versions. Signature records capture who approved each version, when, and with what meaning. The complete story is preserved. But the current state is never ambiguous.
Forms that become records
Form FRM-001 version 2.0 is the template. Version-controlled like any document. When an operator executes that form for Batch B-2024-047, it becomes a record. The record captures which form version was used, who completed it, when, and with what data. Once approved, records are immutable.
Search works across records: "Show me all batch records where Operator Chen was involved" or "Find all deviation reports from Building 3 in Q1." The forms you filled out years ago become searchable data, not PDFs buried in folders.
Controlled printing and periodic review
When you print a document, the system logs who printed, when, how many copies. Printed copies include watermarks showing document ID, version, and print date. When a document is revised, holders of outstanding prints are notified that their copies should be replaced.
Where procedure or company policy requires periodic review, the configured interval, basis, reminders, and escalation remain part of the document record. Thirty days before review is due, the owner is notified. Overdue reviews escalate through the approved path.
The request states why a document should change
New document, revision, administrative correction, translation, consolidation, retirement, temporary instruction, and emergency change requests retain source, problem or opportunity, proposed scope, affected sites and products, urgency, regulatory relevance, owner, and approval to proceed.
Rejected and deferred requests remain searchable, preventing the same concern from disappearing into email.
Authorship uses an approved structure
Document type determines required metadata, sections, clauses, numbering, terminology, references, format, review disciplines, signature meanings, training expectation, retention, and periodic-review policy.
Authors can collaborate while drafts, comments, accepted changes, resolved issues, and source references remain distinguishable from the approved record.
Review is a documented challenge
Subject-matter, process, quality, regulatory, safety, data-integrity, validation, training, and site reviewers receive the relevant scope and change delta.
Each comment retains location, issue, severity, proposed resolution, response, disposition, reopen history, and reviewer acceptance. Approval cannot hide an unresolved critical issue.
Change impact connects the instruction to operations
Affected documents, forms, specifications, methods, recipes, systems, equipment, materials, products, roles, curricula, validation, regulatory filings, partners, labels, inventory, and effective records are derived from links and confirmed by accountable reviewers.
The assessment defines implementation tasks, training mode, cutover, verification, and any restriction on using existing stock or templates.
Approval and effectiveness are separate gates
Approval confirms content and implementation readiness. Effectiveness determines when the new version becomes the instruction in force.
The planned window coordinates training, system configuration, form or template deployment, controlled-copy exchange, translated versions, partner notification, and inventory disposition. A delay preserves the approved version and reason without pretending it is already effective.
Training impact is proportional to the change
No training, awareness, read-
The decision retains the changed requirement, population, due date, effectiveness dependency, exception handling, completion threshold, and accountable approver.
Controlled distribution knows the recipient and copy
Electronic access, controlled print, posted copy, external distribution, translated copy, and read-only export retain recipient or location, document version, copy identifier, issue date, expiry, acknowledgement, retrieval, replacement, and destruction.
Uncontrolled reference copies are visibly marked and never serve as point-of-use instructions.
Periodic review is an evidence-based decision
Applicable regulations and standards, source references, deviations, audit findings, CAPAs, changes, user feedback, linked process performance, training outcomes, document usage, duplicate content, and owner currency inform the review.
Continue, revise, consolidate, replace, or retire dispositions retain rationale, actions, approval, and the next review basis.
Emergency changes are controlled exceptions
Urgency, safety or supply reason, narrow scope, abbreviated review, temporary controls, authorized approvers, immediate communication, training, effective time, expiry, retrospective assessment, permanent disposition, and closure define the emergency path.
Fast does not mean undocumented, and a temporary instruction cannot remain active indefinitely.
Supersession closes every implementation thread
At effectiveness, the prior version becomes superseded; point-of-use views update; execution templates and training rules switch; outstanding copies and translations reconcile; dependent records receive the correct version; and open implementation tasks are verified.
Exceptions produce visible holds or follow-up, not a superficially complete status.
Retirement preserves the historical obligation
Retirement considers active products, records, markets, equipment, contracts, commitments, references, forms, training, retention, legal hold, and replacement instructions.
The obsolete content, metadata, approvals, signatures, audit trail, distribution history, and relationships remain protected and retrievable for the applicable period.
Document Control and DMS are deliberately distinct
Document Control is the quality workflow and decision model: why content changes, who challenges it, what is affected, when it becomes effective, who must know or qualify, and whether implementation completed.
The DMS is the broader system foundation for content, files, metadata, search, permissions, rendering, records, external documents, archival, and migration. Seal composes the workflow with that foundation rather than duplicating it.
The result is a reconstructable effective state
For any date and activity, Seal can show the instruction in force, its approval basis, implementation and training status, point-of-use distribution, controlled copies, linked templates, exceptions, and the people authorized to work.
That is the evidence behind a controlled process—not merely a PDF with a signature page.
