Summary
- The problem
- A method’s history is split across procedures, validation reports, transfer packages and routine results. When a revision is proposed, it is hard to see which evidence supports it, and for which laboratory.
- Seal’s approach
- Intended use, procedure versions, development and validation studies, transfer work and routine performance stay connected. Each laboratory’s readiness is assessed on its own evidence rather than inferred from the newest procedure version.
- What changes
- A sending-lab study supports review without marking the method transferred. Routine runs keep preparation, processing and reprocessing history against the version used, so the next change starts from recorded performance.
- Where to start
- One method revision and the evidence needed to put it into use at another lab. Book a demo.
From an analytical question to a routine result.
A reportable result depends on more than the current procedure: the performance the method was developed for, the study that validated it, the transfer to the lab that runs it and its routine history. Seal keeps those four stages connected, so a proposed revision can be assessed against the evidence behind it. Select a stage to see the record it keeps and what it hands on.
Routine performance informs method change.
Carry the analytical purpose into the method.
Record the analytical target profile (ATP) where used: intended decision, matrix, range and required performance. Connect development experiments, risk assessments and robustness work to the preparation, instrument and calculation controls they inform.
Select the procedure and performance claims to assess. Preserve exploratory results and limitations alongside the chosen approach.
Method development record
- Purpose
- Attribute, matrix and intended decision
- Experiments
- Factors, source results and interpretation
- Controls
- Preparation, suitability and processing
Run the study against its agreed design.
Configure the applicable performance characteristics, preparations, replicates, factors, analysis and acceptance criteria before execution. Keep source files, calculations, invalid runs and protocol exceptions with the resulting assessment.
Retain the procedure, data and calculation versions supporting the claim. A repeat or reprocessed result does not erase the original.
Analytical validation study
- Design
- Characteristics, factors and acceptance
- Execution
- Preparations, sequences and source data
- Assessment
- Supported claims, limitations and review
Make local readiness part of the transfer.
Agree the receiving-lab strategy and its rationale. Coordinate shared samples, standards, instruments, analyst training and comparative work. Record local differences and discrepancies rather than treating a document handover as proof of readiness.
Review suitability for the receiving lab’s intended use. Validation, verification and transfer remain distinct assessments.
Method transfer package
- Strategy
- Scope, rationale and acceptance
- Readiness
- Equipment, materials and trained analysts
- Evidence
- Local execution, comparison and discrepancies
Keep the method version with the result.
Execute the effective preparation, suitability, acquisition, calculation and review workflow. Retain actual standards, reagent and column lots, instrument identity and processing context. Review routine performance by method version and relevant source population.
Assess signals and proposed changes against affected claims, specifications, studies, laboratories and training before implementation.
Routine analytical record
- Assignment
- Sample, specification and method version
- Actual use
- Preparations, materials and instrument
- Performance
- Suitability, invalid runs and investigations
Readiness is decided lab by lab.
A revised procedure and a sending-lab study are available for AM-018. The receiving lab still has an open comparability assessment. The method version alone does not establish that QC South can use it.
AM-018 / method lifecycle
Procedure
AM018-DEF- Current procedure
- AM-018 / v03
- Candidate
- AM-018 / v04
- Change state
- Proposed
AM-018 v04 is a proposed procedure revision. The intended use and change rationale belong with the preparation, acquisition, processing and suitability instructions.
What follows
Review the procedure comparison and the performance characteristics affected by the change.
AM-018 v04 is still proposed. The sending-lab study is available, but QC South’s comparability assessment remains open. I would carry the development knowledge forward without marking the method transferred.
AM-018 / receiving-lab readiness
DraftComplete the receiving-lab evidence review and procedure-change assessment before deciding routine-use readiness.
Method owner
Review the v03-to-v04 change and affected performance characteristics.
Analytical lead
Confirm the scope and applicability of AMD-018.
Receiving QC lead
Complete TR-018’s agreed comparison and readiness decision.
Keep the full analytical record with each result.
Why teams choose Seal for the method lifecycle
A method revision usually starts by reassembling the method’s history from development notebooks, validation reports, transfer packages and routine LIMS results. Seal keeps the intended use, procedure versions, studies, transfer work and routine performance connected, and assesses each laboratory’s readiness on its own evidence.
Routine suitability failures and investigations inform the next revision; runs after it takes effect use it, and earlier runs keep the version they used.
Preparation is part of the method.
Carry standards, sample preparation, column requirements and processing settings with the procedure.
Retain actual lots, concentrations, quantities, timings and calculations in the execution record. A result without its preparation and processing context is not the full analytical record.
Routine performance informs the next change.
Keep suitability failures, invalid runs, investigations and method revisions in one reviewable history.
Review patterns against the intended use and source population. Keep reprocessing and retesting distinguishable from original results. A trend can trigger investigation without proving a cause.
Connected to the surrounding work.
Keep specialised systems where they belong. Agree the source of each record, the permitted actions and the reconciliation at each handoff.
Explore integrationsAQuestions and answers
Are validation, verification and transfer the same work?
No. Their purpose and required evidence differ. Agree the applicable strategy for the procedure, intended use and receiving laboratory rather than treating the labels as interchangeable.
How does this relate to Q14 and Q2(R2)?
Q14 addresses analytical procedure development and lifecycle knowledge; Q2(R2) addresses validation. Seal connects the work and evidence. Your team determines the applicable performance characteristics, criteria and assessment.
Can instrument data stay in our CDS?
Yes. Preserve the acquisition and processing records in their source system and scope the links or transfers needed for the workflow. An imported result does not replace the original record.