Document control.

1An approved procedure must reach the point of use.

Consider an operator who opens a procedure at the start of a shift. The copy of Procedure-017 in the clean room is version 3.1, printed and laminated last month, and it says to add Excipient B at 45°C. Version 3.2 was approved three weeks ago and changed the window to 42°C on the basis of process data. The new version is on the shared drive and an announcement was emailed, but the copy at the point of use was never replaced.

The approval was correct and the work still followed the wrong instruction. Document control has to govern the whole path from a request to change a document to the instruction people actually use, and to the record of who was qualified to use it.¹

Swipe to see the full diagram →

2File names and emails do not establish the effective version.

SOP_Cleaning_Final.docx, SOP_Cleaning_Final_v2.docx and SOP_Cleaning_FINAL_reviewed.docx can sit in the same folder. One was emailed to a team lead, another is posted in the clean room and a third is what QA approved. When an auditor asks for the current procedure, who approved it and who is trained on it, the answers come from different places.

The same gap appears between approval and training. Version 3.2 is approved, but the people trained on version 3.1 still show as current, because the training record does not know the procedure changed.

2.1Why teams choose Seal for document control

Document control is often a file repository, email announcements and a training spreadsheet, so the approved version and the copy at the point of use can quietly differ. The document, its approval, the training it requires and the work that uses it are connected. A revision can identify the affected roles, assign the training through a configured automation and, where configured, govern whether a person may perform the step that depends on it, so the instruction in force is the one the work follows.

3Approval and training are connected.

When Procedure-042 moves from version 2 to version 3, a configured automation can identify the people trained on version 2, mark that training as superseded for the new version and assign the required retraining. Where the workflow is configured with a training prerequisite, a person without the current qualification cannot complete the step that depends on it.

Not every revision needs the same response. The change record decides whether it requires no training, awareness, read-and-understand, a knowledge check, practical demonstration or requalification, by affected role and task. That decision retains the changed requirement, population, due date and the approver.

4Each document has one effective state.

Each version of a document moves from draft through review and approval to effective, and is later superseded by the next effective version or retired with the document. Approval alone does not make a version effective. Search and point-of-use views are configured to serve the effective version. Version history keeps every change, comparisons show what differs between versions and signature records show who approved each version, when and with what meaning.² The history is complete, and the current state is not ambiguous.

Forms work the same way. Form FRM-001 version 2.0 is a controlled template. When an operator completes it for batch B-047, the result is a record that retains the form version, the person, the time and the data. Once approved, the record is protected from change, and completed records become searchable data rather than PDFs in folders.³

5Requests, authorship and review are part of the record.

A change starts with a request: a new document, revision, correction, translation, consolidation, retirement, temporary instruction or emergency change. The request retains its source, the problem it addresses, proposed scope, affected sites and products, urgency and approval to proceed. Rejected and deferred requests stay searchable, so the same concern does not disappear into email.

The document type determines the required metadata, sections, review disciplines, signature meanings, training expectation, retention and periodic-review policy. Authors can collaborate while drafts, comments and accepted changes remain distinct from the approved record.

Reviewers receive the relevant scope and the change delta. Each comment keeps its location, severity, proposed resolution, response and disposition. Configure approval so that an unresolved critical comment blocks it.

6Change impact connects the instruction to operations.

A procedure rarely changes alone. The impact assessment draws on the records that reference the procedure to propose the affected forms, specifications, methods, recipes, equipment, roles, validation and filings, and accountable reviewers confirm the list. It then defines the implementation tasks, training, cutover and any restriction on using existing stock or templates.

Approval and effectiveness are separate gates. Approval confirms the content and readiness to implement. The effective date is when the new version becomes the instruction in force, coordinated with training, configuration, form deployment, controlled-copy exchange and translations. If implementation is delayed, the approved version waits with its reason recorded instead of appearing effective early.

Emergency changes follow a controlled exception path: a narrow scope, abbreviated review, named approvers, an expiry and a retrospective assessment. A temporary instruction cannot remain active indefinitely.

7Distribution, periodic review and retirement keep the state accurate.

Electronic access, controlled prints, posted copies and external distribution retain the recipient or location, version, copy identifier and issue date. Printed copies carry the document ID, version and print date, and holders of outstanding copies are notified when a revision is issued. Uncontrolled reference copies are visibly marked and are not used as point-of-use instructions.

Where procedure or policy requires periodic review, the interval, reminders and escalation belong to the document record. The review draws on deviations, audit findings, CAPAs, changes and user feedback, and ends in a recorded decision: continue, revise, consolidate, replace or retire.

At effectiveness, the prior version becomes superseded, point-of-use views and execution templates switch, and outstanding copies are reconciled. Exceptions remain visible as holds or follow-up actions. A retired document keeps its content, approvals, signatures, audit trail and distribution history for the retention period.⁴

8Show the instruction in force on any date.

For a given date and activity, the connected records show the instruction in force, its approval, implementation and training status, distributed copies, linked templates and exceptions, and who was qualified to do the work. That is the evidence behind a controlled process, rather than a PDF with a signature page.

Document control is the quality workflow: why content changes, who challenges it, what is affected, when it takes effect, who must be trained and whether implementation is complete. The DMS is the foundation for content, files, metadata, search, permissions, records and archival. Seal composes the workflow with that foundation rather than duplicating it.

Start with one procedure family and its forms. Bring an existing revision, map it to the roles it affects and follow it through approval, training and effectiveness before extending the workflow.