Summary
- The problem
- A finished test is the start of another search. The reviewer needs the sample identity, method and specification versions, original instrument data and any investigation, and those live in separate systems.
- Seal’s approach
- Each result is captured as the work runs, with its sample, preparation, method, specification and instrument file attached. Manufacturing and quality use the same records, so laboratory review feeds batch disposition without copies.
- What changes
- A reviewer follows a reported value back to its inputs, standard lot and acquisition. A method change carries its impact assessment and verification, and earlier runs keep the version they used.
- Where to start
- One release test, incoming-inspection workflow or stability study, with representative data and one connected instrument source. Book a demo.
1The result is ready. The evidence should be too.
An analytical result is only part of a release decision. The reviewer also needs the sample identity, method, specification, original instrument data and any investigation. When these live in separate systems, a finished test becomes the start of another search.
Seal’s shared ontology defines the record types and relationships across laboratory, manufacturing and quality work. The sample links to the manufacturing step it informs, the result to its specification and the investigation to the affected sample and batch. neil follows the records it is permitted to access to help configure methods, assemble investigation evidence and prepare controlled improvements.
S-041-12
Final blend / release testing
0.72%
Limit ≤ 0.50% · outside limits- Original source
- KF-02 / determination 118
- Laboratory review
- Pending investigation
Tested using
AM-022 v02
Analytical method
Preparation, calculation and suitability requirements for this test.
The executed version stays linked.Evaluated against
SP-041 v04
Product specification
Water content ≤ 0.50%. The original result is 0.22 percentage points above the limit.
A revision does not rewrite this test.Collected from
B-041
Manufacturing batch
Material genealogy, execution records and the collection point behind the sample.
Batch disposition remains pending.Investigated in
INV-041
Quality investigation
Original result, laboratory assessment and any justified further testing.
The investigator records the conclusion.neil follows these same relationships.
“Which other samples used this method and instrument?”
Compare the linked runs, inspect their sources and prepare the investigation with the evidence in view. The requester’s permissions still apply.
1.1Why teams choose Seal for the QC laboratory
The laboratory’s work feeds directly into manufacturing and quality decisions. Seal connects the sample, method, instrument file, investigation and batch, so reviewers can follow the result to the work that produced it. They can assess a result with its preparation, source data and investigation in view.
Use neil to build a method workflow, compare results or investigate an exception. When the method improves, revise the configuration with its impact assessment and verification in Seal. Earlier results retain the method and specification they used. The same platform supports development, routine testing and the changes between them.
| LIMS beside the batch | Seal | |
|---|---|---|
| Review evidence | A PDF of the final result | The original acquisition, preparation, calculation and audit-trail entries |
| Specification | Limits copied into the test | The assigned, versioned specification, retained with the result |
| Investigation | A form filled from exports | Opens from the result with its sample, method, instrument and standard linked |
| Method change | A separate change project, with its evidence kept outside the method record | A reviewed configuration change with impact and verification evidence |
| AI | Answers from isolated documents | neil follows a result to its sample, method and batch and proposes changes for review |
2Take the sample from receipt to a reviewed result.
Receive
Sample S-041-12
Identity, origin and chain of custody
Assign the test plan and specification version.
Test
Method AM-014 v03
Analyst, instrument and source output
Record execution against the approved method.
Evaluate
Specification SP-041 v04
Result, units and acceptance criteria
Flag exceptions and link any investigation.
Review
Batch B-041
Test evidence and outstanding decisions
Authorised reviewers assess the complete record.
Sample evidence stays with the batch. Disposition follows the required reviews and approvals—not a passing result alone.
Register the sample with its material, batch, collection point and required tests, and assign the method and specification versions before execution. Configured checks identify missing results, values outside limits and outstanding review. Manufacturing and inventory use the authorised disposition from the same record; completing a test is not the same as releasing a batch.
A result starts before the instrument run. Link the received sample to the aliquots, preparations and dilutions used for each test, with quantities, units, reagent lots, preparation time and analyst. If a preparation is repeated, keep its identity and the reason rather than blurring two preparations into one result. Configure calculations as part of the method, with explicit inputs, units and reporting rules, and verify boundary values, missing inputs, division by zero and rounding whenever the calculation changes.
Record what was fit for use when the test ran. Connect the reference standard’s certificate, assigned value, storage requirements and permitted use period to the preparation, so an investigator can find the work affected by a standard-lot issue. Bring instrument calibration and qualification together with the analyst’s method-specific training and authorisation, and retain the evidence applicable at execution. A later training update should not obscure who was qualified for the original work.
3Check the result against the right version.
S-041-12
Batch B-041Each test uses its own scale and assigned limits.
The version used for this sample stays with its results.
Water content
Outside limits
0.22 percentage points above the limit. Original result retained; INV-041 remains open.
- Method
- AM-022 v02
- Source
- KF-02 / determination 118
Batch disposition remains pending.
Specifications are structured, versioned records. Keep the measured value, unit, calculation and assigned limits together. A water content result of 0.72% against a limit of ≤ 0.50% is outside limits, and the investigation must retain that result even when further testing is justified.¹
A revised specification does not silently rewrite the basis of earlier decisions. Its applicability to products, markets and work in progress is reviewed as part of the change. Historical testing retains the version used, so a reviewer can establish which limit applied and why.
4Review the evidence, not only the number.
Water content
0.22 percentage points above the limit
The original result stays in the record.
What supports this reported value?
Follow the result to its original acquisition and processing history. Keep the reported value alongside the evidence used to assess it.
- Original determination and calculation inputs
- Blank, drift and suitability evidence
- Relevant processing and audit-trail entries
“Bring together the source evidence for this result. What is missing from the review?”
A source-linked evidence brief, with gaps called out for the investigator.
neil works within your access. Your team assesses the evidence and approves the decision.
Review the original acquisition and relevant processing history, not only a PDF of the final result.² Connect the preparation, system-suitability evidence, calculations and relevant audit-trail entries, and record questions and their resolution against the work they concern. An investigation starts from the same context, with missing evidence left as a visible gap, and records the laboratory assessment, hypotheses, further work and conclusions.
Keep three decisions distinct: whether the reported value meets its assigned limits, whether the laboratory evidence is complete and acceptable, and whether the batch can be released. Laboratory review contributes to batch disposition alongside manufacturing exceptions and quality events. Record the reviewer, signature meaning and approval against the version reviewed.³
Because the records are shared, neil can answer questions that cross the usual boundaries: “Which batches used standard lot WS-041, and which still have an open laboratory review?” It can compare findings by product, method version, instrument or standard lot and prepare a source-backed brief that states the records compared, the pattern found and what is still unknown. Your procedure governs further testing and escalation. Neither a suggested cause nor a passing repeat result closes an investigation by itself.
5Capture instrument data once.
Instrument workstation
HPLC-07 / sequence 041
- Original acquisition and report
- Available method and sequence files
- Sample identifiers and acquisition times
Seal IoT
Installable capture agent
- File trigger on the approved export folder
- Run the configured upload script
- Upload using outbound HTTPS
Laboratory record
Sample S-041-12
- Original source file retained
- Reported values and units mapped
- Method and specification linked
- Evidence available for review
Verify the connection with real example files.
Check missing and duplicate files, sample matching, units and recovery after a failed transfer. A file arriving successfully does not establish that the acquisition is complete or its result is valid.
For file-based acquisition, install Seal IoT on the instrument workstation or an appropriate local computer. Configure the watched folder, processing script and destination record. Retain the original export and map available sample identifiers, values, units and acquisition metadata into the workflow.
Other sources may use supported interfaces or APIs. Assess the model, software version and actual output, not just the manufacturer’s name, and exercise missing files, duplicates, failed transfers and recovery before relying on the connection. Scientific data management explains the capture route; the instrument directory helps scope the source.
6Incoming, environmental and stability work share the same records.
Incoming inspection connects the supplier lot, CoA, sampling plan and analytical work. Supplier values are compared with the required tests, discrepancies are recorded for assessment, and inventory uses the authorised material disposition without copying the decision into another application.
For environmental monitoring, retain the location, sampling method, time, conditions and result. Compare like-for-like populations and keep action limits distinct from trend signals: a rising count can warrant investigation below an action limit, but its interpretation depends on the sampling context.
A stability study connects the protocol, storage conditions, pull schedule, samples and results, with each timepoint carrying its assigned method and specification. Missed pulls, chamber excursions and atypical results stay with the study evidence. Trends across batches and conditions help reviewers assess emerging changes; any extrapolation needs a scientific basis and review, and a projected trend is not a shelf-life decision.
7Change methods and configuration under control.
Develop the method
AM-014 / development
- Compare conditions and replicate runs
- Keep preparation and calculation records
- Retain the rationale for selected parameters
Establish intended use
AM-014 v03 / proposed
- Define performance and acceptance criteria
- Assess method evidence and suitability
- Verify the configured workflow
Run the approved version
AM-014 v03 / QC use
- Use the assigned method and limits
- Retain source data with each result
- Record departures for assessment
The next improvement is a controlled revision.
A proposed v04 carries its reason, impact assessment, configuration specification and verification evidence. Approved v03 runs retain their version and history.
Develop methods in Seal’s ELN, then bring the approved version into QC with defined parameters, calculations, system-suitability checks and review requirements, keeping the development evidence that explains those choices. An analyst runs the approved version. A new column, revised calculation or updated limit becomes a reviewed configuration change with its impact and verification evidence, and earlier runs keep their original context.
Continuous validation is part of that change. Keep the user requirements, functional and design specifications, configuration specification, verification results and approval together in Seal, and update them with the configuration they describe.⁴ Automated verification and repeatable UAT checks exercise both intended behaviour and failure cases: a missing unit, an out-of-range result, an unapproved method version or an incomplete review. Your team assesses impact, reviews the evidence and approves release. Explore continuous validation.
Earlier runs keep their version.
- Requirement
- URS-014Review required
- Verification
- TC-0143 checks passed
- Release
- QA approvalPending
v05 cannot govern new runs yet.
8Give neil the next method to configure.
Bring an approved specification, method or validation report. neil helps turn it into a proposed workflow: test names, parameters, calculations, acceptance criteria and review gates. Your team checks the interpretation against the source and resolves ambiguity before release. For a potency method, evaluate the preparation calculation, required system-suitability records and assigned limits, and test that an outside-limit result follows the investigation route and that missing evidence prevents completion.
Start with one release test, incoming-inspection workflow or stability study. Agree the intended use, representative sample data and acceptance criteria; connect one source and exercise the workflow. Existing systems can continue serving the work outside that scope.
8.1What to bring to the first conversation
- The work: one method or procedure and the bottleneck you want to remove.
- The evidence: a redacted specification, representative result and instrument export.
- The decision: who reviews the configuration and what must be demonstrated before use.
References
- 1FDA, Investigating Out-of-Specification (OOS) Test Results for Pharmaceutical Production, guidance for industry, Revision 1 (2022), sections III (Phase I laboratory investigation) and IV (Phase II full-scale OOS investigation). FDA
- 221 CFR 211.194, Laboratory records: laboratory records must include complete data derived from all tests necessary to assure compliance with established specifications and standards. eCFR
- 321 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
- 4EudraLex Volume 4, Annex 11, Computerised Systems (2011), sections 4 (validation) and 10 (change and configuration management). European Commission
ACapabilities
| Capability | What it covers |
|---|---|
| Release testing workflows | Run required tests against the assigned method and specification. Retain results, source evidence and review status with the sample and batch. |
| Specification checking | Evaluate results against the assigned specification version. Keep values, units and limits together, with exceptions routed for assessment. |
| OOS investigation | Keep the original result, laboratory assessment, further testing and conclusions connected. neil helps assemble source-backed context for the investigator. |
| Instrument integration | Capture supported instrument outputs through Seal IoT, interfaces or APIs. Preserve the original source and verify identifiers, units and transfer recovery. |
| Incoming inspection | Link supplier lots and CoAs to sampling and testing. Record discrepancies and use the authorised material disposition in inventory. |
| Environmental monitoring | Connect locations, sampling schedules and results. Review trends, excursions and investigations with the area and operating context. |
| Stability management | Define protocols, generate pull schedules and keep chamber conditions and results with each timepoint, trended over the life of the study. |
| CoA generation | Prepare Certificates of Analysis from reviewed results, specifications and batch records using the configured reporting and approval requirements. |
| AI-assisted spec setup | Give neil a method or specification. Review the proposed parameters, calculations and limits against the source, with checks and approval in the change. |
| QMS integration | Follow an outside-limit result into quality review. Keep the sample, source acquisition, method execution and wider batch impact together in the investigation. |
| MES integration | Connect in-process samples to manufacturing steps and make reviewed results available with the batch. Required release decisions remain explicit. |
BConnected records
CQuestions and answers
Why use Seal instead of a standalone LIMS?
Laboratory work shares records with manufacturing, quality, research, training and inventory. A reviewer can follow the sample to its batch, method and investigation without assembling copies from separate applications. neil works across the records it is permitted to access, while the same platform retains configuration changes, verification evidence and release approvals.
Can a validated workflow change after go-live?
Yes, through controlled revision. Keep the reason, impact assessment, updated requirements and configuration specification with the proposed version. Run automated verification and repeatable UAT checks for the change, then review evidence and approve release. Existing runs retain their version and history. The assurance work for software configuration does not replace the scientific evidence needed for an analytical method.
What should we test in an initial evaluation?
Bring a method, specification and representative instrument export. Exercise a complete sample, an outside-limit result, missing evidence and a proposed method change. Check source traceability, units, calculation behaviour, investigation routing and release permissions. Agree what must be demonstrated and who reviews it before extending the scope.
Is this for method development or QC?
This blueprint focuses on QC execution. Method development can run in the ELN on the same Seal platform. Bring an approved method version into QC with its defined parameters, calculations, specifications and review requirements, while retaining the development context.
How do you handle OOS investigations?
Configure the outside-limit route around your approved procedure. Link the original result, source data, method, instrument, standards and analyst records. Document laboratory and wider assessments, justified further testing and conclusions. Original results remain available; a passing repeat does not replace them.
Can we configure our own specifications?
Yes. Define versioned criteria, units and applicability for each product and test. A revision goes through impact assessment, verification and approval. Decide how it applies to new and in-progress work; historical results retain their assigned specification version.
What instruments do you integrate with?
The connection depends on the model, software version and available output or interface. Bring an example file and the workflow it supports. We assess the capture route, data mapping, units, timestamps and failure handling, then verify the connection for that intended use. The instrument catalogue lists manufacturers and models to help start that discussion.
How does incoming inspection work?
Record materials at receipt, assign the inspection plan and link supplier CoA information to the test evidence. Testing and exceptions feed the material review. Inventory uses the authorised disposition; passing a test alone does not bypass required review or release controls.
What about environmental monitoring?
Each result retains its location, sampling method, time, conditions and value on the same records used for other laboratory work. Trend review compares like-for-like populations and keeps action limits distinct from trend signals, and an investigation opens from the result with its location and sampling context linked.
How does this integrate with batch release?
The batch links to its samples, results and laboratory review. A value within limits does not complete the review by itself: missing evidence, unresolved investigations and required approvals still matter. Authorised disposition considers laboratory evidence alongside manufacturing exceptions and quality decisions in the same platform.
How does Seal support 21 CFR Part 11?
Seal provides access controls, audit history, versioned records and electronic signatures as platform capabilities. Review their configuration and evidence against your intended use. Requirements, configuration specifications and verification evidence belong with the controlled change; your team approves production release. The assurance page explains the controls and responsibilities in more detail.
How do we handle calculations, units and rounding?
Define the inputs, units, formula and reporting rules in the method configuration. Retain the calculation inputs with the result. Verify normal cases, boundary values, missing inputs, invalid units and rounding against the intended use. A formula revision follows change control; earlier work retains its method version and calculation context.
Can we trace a standard or reagent lot to the tests that used it?
Link the lot to its preparations and analytical runs, rather than recording only an unconnected lot number. Keep the certificate, assigned value and permitted use period with the lot record. Those relationships support finding affected samples and batches when a lot is questioned. Configure the required status and expiry checks for the workflow.
Do we need to replace the whole lab system at once?
Start with a defined workflow, representative records and one acquisition source. Agree which system owns each record during the transition, how identifiers map and what must reconcile. Evaluate historical records, original files, versions and review status before deciding what to migrate. Work outside the initial scope can stay in the existing system.
How does neil help set up specifications?
Bring an approved specification, method or validation report. neil helps turn it into a proposed configuration of test names, parameters, calculations and acceptance criteria. Your team checks the interpretation against the source, resolves any ambiguity and approves the change before release.