Turn procedures into the way work runs.

A 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.

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.

AI can do more for an operation when it can work with the process itself—not only search documents about it. In Seal, neil can use the connected instruction, requirements and records to help prepare the next version of the way you work.

Draft with context. Bring the source procedure, intended use and local requirements. neil can help structure the instruction, fields and checks. Review its proposals against the source before accepting them.

Investigate the impact. Ask which forms, training requirements or process records reference the procedure. Use the linked evidence to prepare an impact assessment; reviewers confirm its scope and resolve missing information.

Prepare the next version. Carry the agreed change into a proposed configuration. Keep the reason, specifications, test evidence and required approvals with it. neil does not sign for an approver or make a procedure effective by itself.

Meet neil and see how AI works with your data.

“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.

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 just 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 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.

Explore training and qualification.

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.

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.

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.

Authoring and review

Use templates for procedures, policies, work instructions, specifications and protocols. Capture the owner, scope, references, reason for revision and review responsibilities. Review content and implementation impact together, with the required people and signature meanings defined by your process.

References and external documents

Distinguish a reference to a fixed version from one intended to follow the current instruction. For external standards, manuals and supplier specifications, retain the issuer, edition, owner and applicability. Assess a new edition before changing the local process; receiving it does not make it approved for use.

Controlled copies and distribution

Where paper is needed, define the copy identifier, version, recipient or location, issue record and replacement responsibility. Reconcile copies during cutover. A digital status cannot retrieve a physical printout: local handling and confirmation remain part of the control.

Periodic review

Set review intervals appropriate to document type, risk and applicable requirements. Bring changes to source documents, deviations, audit findings and user feedback into the review. Record whether to retain, revise or retire the instruction, together with the decision and next review date.

Access, retention and archive

Define who can author, review, approve, use or retrieve a record. Retain superseded content, version history, approvals and links to executed work for the required period. Plan archive access, export and any retention holds as part of the deployment; historical evidence must remain intelligible after the process changes.

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.

Scope your first procedure with neil.