Summary
- The problem
- Writing a revised SOP is the easy part. Someone must also change the form, train the right people, verify the behaviour and make sure the next run uses the right version, and when those live in separate systems every improvement becomes a coordination project.
- Seal’s approach
- The instruction is linked to the training, forms and execution rules it governs. A revision carries its reason, impact assessment, configuration and verification through change control, and completed records keep the version they used.
- Evidence
- Bioventix: 80% less document admin time. Acclinate: 50% shorter quality cycle times and 40% less time preparing for audits.
- Where to start
- One effective SOP, a proposed revision and the form or training requirement it affects. Book a demo.
1A new check in the SOP should become a check in the process.
Writing the new instruction is only the beginning. Someone must change the form, train the right people, verify the behaviour and make sure the next run uses the right version. When those live in separate systems, every improvement becomes a coordination project.
Seal connects the instruction to the work it governs. Documents, training, manufacturing, laboratory and quality share one platform. Carry the change from its reason through implementation and verification to controlled release. The records already created keep the version they used.
1.1Why teams choose Seal for document control
A standalone document system controls the file: its approval, effective date and read-and-understood training, while the form, the training matrix and the workflow that should change with it are updated by hand elsewhere, if at all. Seal links the instruction to the forms, qualifications and execution rules it governs, and Neil can prepare the revision and its configuration change together for your team to review. Once verified and approved, the revision is implemented in the work itself: the next run follows the new version, and completed records keep the one they used.
2Assess what a revision touches before approving it.
A wording correction and a new process step do not need the same implementation plan. Record the reason for the change first. Then assess the roles, forms, references and work affected by it.
In this example, adding an independent line-clearance check affects the operator’s instruction, a supervisor’s qualification and the form used to record the result. Those are linked changes to one operation, not three documents to reconcile later.
v04 v05
Add independent line-clearance verification
Packaging supervisor
Demonstrate the independent checkAssess the changed responsibility and assign the required qualification before v05 use.
Explore qualificationFRM-PKG-014
Record the second checkAdd the verifier, result and time. Verify that the configured step requires this evidence.
Explore executionCOPY-000044
Replace the line-side instructionReconcile the v04 copy at packaging line 2 when the new version becomes effective.
Explore copy controlOne change set connects the instruction and its implementation evidence.
3Turn an instruction into an execution rule.
“Get a second person to check” becomes something specific: who can perform the check, which result is acceptable and what evidence must be recorded. The proposed configuration below makes those conditions explicit.
Explore the verification cases. A missing verifier, failed check or missing qualification keeps the work blocked. Meeting this check allows the process to continue to its remaining requirements—it does not release the batch.
The instruction becomes a check.
“A qualified second person verifies clearance before starting the line.”
Verifier recordedRequirement not met
Qualification metPresent in this case
Clearance passedPresent in this case
Time retainedPresent in this case
Keep line start blocked
A clearance result without an identified verifier is incomplete.
4Approval and effectiveness are different decisions.
Approval records agreement to a version. Effectiveness determines when it can be used. Plan the cutover around the applicable training, verification, implementation tasks and outstanding copies, not only a date on a PDF.
Keep the outgoing version effective until the required conditions for the replacement are met. Preserve a clear distinction between an approved version awaiting implementation and the instruction currently in use. Historical versions remain available to authorised reviewers without being presented as current instructions.
The record keeps the version used.
Earlier instruction and approval history retained.
v03 retained
Current instruction for the defined scope.
v04 retained
Impact, verification and required approval still open.
No v05 execution
Training follows the change, not only the document. The impact assessment determines who needs training and what they need to demonstrate. A clarification may need acknowledgement; a changed operation may need instruction, an assessment or observed practice. Do not treat opening a document as proof of competence.
Connect assignments to the relevant procedure version, role and activity. Configure qualification checks where the work runs so a completed training record can support the task it was intended for. A proposed revision should not automatically invalidate every person’s existing qualification before the cutover has been assessed.
Different roles. Different evidence.
Perform the independent check
Verify the area and equipment before the next batch starts.
Observed practice
An assessor observes the check and records the demonstrated scope.
Version-specific qualification
Use the reviewed evidence for the assigned role when v05 becomes effective.
Proposed training plan. Selecting a role does not record completion or grant qualification.
Explore training and qualification.
5Record the work against the instruction that governed it.
An SOP explains what to do. A linked form or workflow captures what happened: required fields, measurements and units, calculations, observations, attachments and signatures where needed.
Define the form once as a controlled template. Each execution retains its version, values and history. Revising the template prepares future work; it does not silently rewrite a completed record.¹ An investigation can therefore follow the recorded result back to the exact instruction and configuration used.
See manufacturing execution or laboratory workflows.
6Continuous validation makes improvement part of the operation.
A validated system should be able to improve. When a procedure revision changes an executable workflow, assess the affected requirements, configuration and risk.² Keep the user requirements specification (URS), functional specification (FS), design specification (DS) and configuration specification (CS) linked to the implementation in Seal.³
Neil can help prepare that change. It works with the connected instruction, requirements and records: it can draft the revised instruction, fields and checks from the source procedure, find the forms, training requirements and process records that reference it, and carry the agreed change into a proposed configuration with its specifications and test evidence. Reviewers check its proposals against the source and confirm the scope. Neil does not sign for an approver or make a procedure effective by itself. Meet Neil and see how AI works with your data.
Run automated verification and repeatable UAT checks for the changed behaviour, retain results and exceptions against the proposed version, and review the evidence before release. The assurance effort follows intended use and risk; an editorial correction does not need to be treated as a new manufacturing process.
The configuration specification below belongs to the same change as the SOP and impact assessment. Requirements, implementation and verification remain connected as the process evolves. Going live should start that lifecycle, not freeze it.
Inspect the verification plan at full size.
Explore continuous validation and change control.
7Keep the full document lifecycle in view.
The same records support the rest of document control. Review content and implementation impact together, with the required people and signature meanings defined by your process.⁴
| Activity | What Seal records |
|---|---|
| Authoring and review | Templates for procedures, policies, work instructions, specifications and protocols, with owner, scope, references, reason for revision and reviewers |
| References and external documents | Whether a reference is fixed to a version or follows the current instruction; for external standards, the issuer, edition, owner and applicability. A new edition is assessed before the local process changes |
| Controlled copies | Copy identifier, version, recipient or location, issue record and replacement responsibility, reconciled during cutover. A digital status cannot retrieve a physical printout, so local confirmation remains part of the control |
| Periodic review | An interval set by document type and risk, the inputs considered (source changes, deviations, audit findings, feedback) and the decision to retain, revise or retire |
| Access, retention and archive | Who can author, approve, use or retrieve a record; superseded content, approvals and links to executed work kept for the required period and intelligible after the process changes |
8Start with one procedure and its dependencies.
Bring an effective SOP, a proposed revision and the form or training requirement it affects. We can work through the current process, model the relationships and agree what needs to be demonstrated before use.
For migration, inventory the source population, map document types and owners, preserve available versions and approval evidence, and reconcile imported records. Do not invent missing history or treat a file upload as an approved baseline. Agree the migration scope and acceptance checks before expanding to the next document family.
References
- 1EudraLex Volume 4, Part I, Chapter 4, Documentation (2011), sections 4.8 to 4.10: records should be made at the time each action is taken, alterations should be signed and dated and permit reading of the original information, and secure controls must ensure record integrity throughout the retention period. European Commission
- 2EudraLex Volume 4, Annex 11, Computerised Systems (2011), sections 4 (validation) and 10 (change and configuration management). European Commission
- 3ISPE, GAMP 5: A Risk-Based Approach to Compliant GxP Computerized Systems, second edition (2022).
- 421 CFR 11.50, Signature manifestations: signed electronic records must show the printed name of the signer, the date and time of signing, and the meaning of the signature (such as review, approval, responsibility or authorship). eCFR
ACapabilities
| Capability | What it covers |
|---|---|
| Procedure management | Keep the procedure’s owner, scope, instructions, references and lifecycle together. Distinguish the effective version from the revision being prepared. |
| Approval workflows | Bring the change proposal and its impact into review. Required people and signatures govern approval; implementation readiness governs effective use. |
| Training integration | Assess training impact by role and activity. Retain assignments and qualification evidence against the relevant procedure version. |
| Controlled distribution | Connect effective instructions to point-of-use access and copy records. Include replacement and reconciliation of physical copies in the change plan. |
| AI document drafting | Ask Neil to help draft from source instructions, compare revisions and prepare impact questions. Review the proposal before it becomes the next controlled version. |
| Periodic review | Set the review interval and owner. Consider source changes, deviations and feedback, then record whether to retain, revise or retire the instruction. |
| Full audit trail | Follow a change to its version, recorded actions and approval evidence. Earlier executions retain the instruction and configuration used at the time. |
| Migration support | Map document types, owners, versions and references. Reconcile the imported population and review the baseline before operational use. |
BConnected records
CQuestions and answers
How is this different from a document library?
The distinction is the connection to execution. Seal links the procedure to its training requirements, forms, quality changes and the laboratory or manufacturing records it governs. You can assess and implement the operational impact of a revision in the same platform, rather than reconcile separate lists of files, people and tasks.
Can we use document control without replacing every system?
Yes. Start with a document family and the relationships needed for its intended use. Agree which system owns each record and how existing systems exchange information. Add training, quality or execution workflows in Seal as the scope grows.
Does every revision require retraining?
No blanket rule should replace the impact assessment. The change type, affected roles and intended activity determine whether acknowledgement, instruction, assessment or practical qualification is appropriate. Keep the rationale and required evidence with the revision.
Can an approved document wait before becoming effective?
Approval and effectiveness are distinct. Define the implementation conditions and cutover date for the configured workflow, including applicable training, verification and copy reconciliation. The outgoing instruction remains effective until the replacement is ready for controlled use.
What happens to existing records when a procedure changes?
Previously created records retain the version and history used for that work. Decide how open work is handled during cutover as part of the impact assessment; do not silently reinterpret it under the new instruction. New work uses the version made effective for its scope.
Can reviewers still see obsolete versions?
Historical versions remain part of the evidence available to authorised users. Point-of-use access should make the effective instruction clear, while reviewers and investigators can trace the earlier content, approvals and executions.
How does Neil help with document control?
Neil can help draft structured instructions, compare changes, find the records that use an instruction and prepare an impact assessment from permitted sources. People verify the content and completeness of the assessment. Neil does not supply a required person’s signature or bypass release controls.
Are our procedures used to train AI models?
No. Customer data is not used to train AI models. Records in Seal provide working context for Neil; that is different from training the underlying model. Neil follows the requester’s access permissions.
How do paper copies fit into the process?
Define how copies are issued, identified, located and reconciled. Link each copy record to its document version and plan replacement during cutover. A system cannot physically recall a printout, so the responsible person’s confirmation remains important.
Can we control external standards and supplier documents?
Yes. Keep the external source’s issuer, identifier, edition, owner and applicability. Assess replacements against the local documents and processes that depend on them. Internal acceptance of an external edition is separate from authorship or approval by its issuer.
How do we validate changes to executable procedures?
Assess the affected intended use, requirements and configuration. Keep the specifications, automated verification, repeatable UAT evidence and required approvals with the proposed version. The checks should match risk and scope; changing prose and changing an execution gate are different cases.
How should we migrate from an existing system?
Start with an agreed inventory and mapping for document types, owners, versions, references and approval evidence. Trial the import, resolve exceptions and reconcile the population before approving the baseline. The schedule depends on source quality and scope; missing history must remain an explicit exception.