Skip to main content

Neil reads every page. Your QA decides.

Batch review often takes weeks, and careful reviewers still miss about one error in ten. Overnight, Neil reads each lot and leaves QA a short list.

  1. Pencil drawing: a tired seal at a desk near midnight, peering at one page from a leaning tower of binders.

    11:40 pm. 272 pages to go.

    By hand, a reviewer reads every page, then chases the lab, the line log and the inbox.

  2. Pencil drawing: at night a seal with a magnifying glass reads a fan of pages, with red threads from three places to an email, a line log and a lab result.

    Overnight, Neil reads all of it.

    Every page, result, line event and message, held against the release plan.

  3. Pencil drawing: in the morning a seal with a mug looks at a laptop showing a short list of three red-marked lines.

    7:00 am. Three things to judge.

    47 of 52 checks met, each linked to its page. A short list needs a person.

  4. Pencil drawing: one seal signs a sheet marked Released while a second seal waits to sign.

    QA disposes. The QP certifies.

    People decide and sign. Neil never releases a lot or changes the record.

What a page-by-page read misses.

Each is in the test lot, outside the page a reviewer is reading.

  • Line’s log
    20 min 49 s stop
    Interventions recorded
    None

    A stop the record says didn’t happen.

    A night-shift Teams post agrees with the log. Three people checked the record.

  • Limit
    24 h
    Actual
    29 h 40 min

    A hold that ran over, across pages.

    Formulation ended on one page and filtration began on another.

  • Lab system
    Invalid endotoxin run
    Batch record
    No mention

    A lab run the record never mentions.

    Nothing on the pages a reviewer reads points to it.

  • 27 °C
    1825
    The limit

    A tick that may disagree with its number.

    Ticked within limit. The ink may read 21, so a person checks the original.

  • Analyst
    Initialled
    Verifier
    Blank

    A printout no one verified.

    Two printouts. Neil names who may verify them.

  • Unrecorded stops
    9
    Same fault
    4

    The same fault, lot after lot.

    Line 2, over two years: the same stopper bowl feed.

One lot, the morning after.

Real Seal screens from a fictional test lot that Acme Biologics filled for Acme Therapeutics.

  1. 1

    Every lot in release, with what is open on each.

    The board QA opens first.

    The release board in Seal: 111 lots in release across three sites, $123M waiting, 86 with nothing open, and a table of the lots with findings, each with Neil’s summary, its value and a predicted certification date.
    1. The morning, in two lines111 lots and $123M waiting. 86 need only a decision.
    2. Neil’s summary of each lotWhat is open, and where Neil found it.
    3. A predicted certification dateFrom how long this site’s lots have taken.
  2. 2

    Open a lot: what is met, what is open, and what the record doesn’t show.

    Neil’s brief for lot 24-0917, from 272 pages and 653 messages.

    Neil’s brief for lot 24-0917 in Seal: not ready for a decision, 47 of 52 checks met, three events to judge, one reading to settle, three entries to complete, and who releases the lot. The review’s structure is in the sidebar.
    1. 47 of 52 checks metEach links to the place in the record that meets it.
    2. Three events the record doesn’t showFrom the lab system, the line’s log and the night shift’s messages.
    3. A proposal, not a changeNothing is published until QA accepts it.
  3. 3

    Every check, at its place on the page.

    A met check, with the scanned record open beside it.

    Check C-09, pre-filtration bioburden, in Seal: why it is met, decided by code, the places Neil read, and the scanned batch record open at page 41 with the sampling entry outlined.
    1. Why it is metSampled 45 min after bulk completion, 0 CFU against a limit of 10.
    2. Decided by codeTimes and limits are calculated, not judged by the model.
    3. The page, at the lineThe scan opens at the entry Neil read, outlined.
  4. 4

    A finding brings what the record left out.

    The record says there were no interventions during filling. The line’s own log disagrees.

    A finding in Seal: what the batch record says and who checked it, what the Line 2 event log and a Teams post say, the requirement the stop breaks and the line’s history, with the drafts for QA listed beside it.
    1. What the other sources sayThe line stopped for 20 min 49 s, in its event log and a Teams post.
    2. Not the first time9 stops on Line 2 in 376 lots reached neither a batch record nor a deviation.
    3. Drafted in the client’s formThe deviation, in Acme Therapeutics’ own form, for QA to correct and raise.
  5. 5

    People decide, and sign.

    Acme QA disposes, then Acme Therapeutics’ QP certifies.

    The release decision for lot 24-0917 in Seal, as Acme QA sees it: checks met, checks open and open findings, a blank decision, the QA disposition statement waiting to be confirmed and the QP certification statement, with 0 of 2 signed.
    1. The decision is QA’sLeft blank for QA to choose.
    2. Then Acme Therapeutics’ QP certifiesUnder EU GMP Annex 16, once QA has disposed.
    3. 0 of 2 signedNeil can draft this record; it cannot sign it.

By hand, and with Neil.

Neil’s side is one full-size test lot: a measurement, not yet a rate.

By handPublished studies and records

30 days
of batch record review lead time is common.BioPhorum, in BioPharm International, 2012
1 in 10
errors missed by a person checking written material.US NRC human reliability handbook
22%
of errors still missed with an independent double check.Randomised trial, BMJ Quality & Safety, 2026
236
FDA observations in a year on production record review.FDA inspection observations, FY2025, 21 CFR 211.192

With NeilTest lot 24-0917, October 2026

Overnight
272 pages and 653 messages read for one lot.Every page, result, line event and message
3 of 3
planted problems found.Built into the lot for Neil to find
0 of 3
decoys raised: things that look like problems but aren’t.Built into the lot for Neil to set aside
23 of 52
checks settled by calculation in code, not by the model.Times, durations, limits and every-page rules

Neil prepares. People decide.

Numbers are calculated in code, every quote is matched to its page, and handwriting Neil is unsure of goes to a person. Authorised people make every decision and sign it. Under Seal’s agreements, your data is not used to train the underlying AI models.

How Neil fits the EU’s draft Annex 22

Summary

The problem
Release waits for the end of the batch. QA then reads every page of the record and reconstructs the case from separate laboratory, line and quality records.
Seal’s approach
Neil reviews each lot overnight against its release plan and leaves a brief: what is met and where, what is open, and what happened that the record doesn’t show. The release case gives each requirement an owner, a source and a recorded outcome.
What changes
QA records exactly what it decided and on what evidence, and the decision carries into inventory status, market eligibility and certificates.
Where to start
Lots your team has already released. Neil reviews them, and QA judges its briefs against what they found. Book a demo.

1Build the release case before the batch is finished.

Release work starts with the requirements for this product, site and destination. Seal brings the executed batch record, material genealogy, laboratory evidence and quality reviews into one case. Each requirement has an owner, a source and a recorded outcome. Teams can see which work is complete, which evidence is missing and which decision is holding the batch.

Begin with your approved release procedure. Define the population, applicable specification, manufacturing instructions, sampling plan, review roles and market conditions. Keep the effective versions with the case. A reviewer should be able to explain why a requirement applies to this batch without reconstructing the plan from separate files.

Evidence

  • Manufacturing (met)Batch record and genealogy
  • QC laboratory (met)Approved results
  • Quality (met)Deviations and impact
Release › B-071
release recorded
  • Inventory (met)Released within scope
  • Certificate (met)From approved results
  • Market M2 (met)Eligible
  • Market M1 (not met)Awaiting acknowledgement
Figure 1. Evidence comes into one release case, and the decision carries into stock, the certificate and each market

1.1Why teams choose Seal for batch release

When release waits for the end of the batch, QA collects the batch record, laboratory results and quality events from separate systems, checks them page by page and records a disposition. Seal keeps the release requirements, their evidence and the open blockers on the platform where the batch, tests and investigations run, so the case assembles as the work happens. A revised release procedure applies to later decisions, and each earlier decision keeps the requirements and evidence it was made on.

2Give each blocker a source and an owner.

B-071 has three reviewed laboratory results and an unresolved hold-time exception. Its release case connects the 52-minute observation, the 45-minute instruction limit, the deviation and the required product-impact assessment. The quality reviewer can follow the issue to its source; the production reviewer can see the conclusion needed to complete manufacturing review.

The same approach applies to a missing signature, preliminary result, unapproved substitution or incomplete source-data review. Keep the reason, responsible role, linked evidence and next action together. A review queue should tell the team what to do next while keeping every required check visible, including those already complete.

3Review the evidence that was true at execution.

Manufacturing review needs the instruction version used, actual values, calculations, material lots, equipment, people, times, corrections and signatures. Each batch must be tested against its final specifications before release, so laboratory review needs sample identity, the applicable specification and method, suitability, reportable results and their approval.¹ A preliminary passing value does not satisfy a requirement for an approved result.

Equipment, cleaning and personnel checks concern the time and purpose of use. A balance being calibrated today does not establish its state when the batch ran. Keep the relevant eligibility evidence with the recorded use, and link any later investigation to the batches it may affect. Preserve original results and invalidation history when a replacement result is generated.

Balance calibration

Figure 2. A check uses the state of the equipment when the batch used it, not its state today

4Review as evidence arrives, with a clear path for changes.

Manufacturing, QC and QA can review completed evidence while later activities continue. Retain each review’s scope, source versions and outcome, so the final reviewer can distinguish work already assessed from new information. Configure which corrections, new results or linked deviations require reassessment, then verify that path before use.

For short-shelf-life products, include expected result availability, review handoffs and the latest decision time in the plan. The team can work on the actual critical path. Any conditional or exceptional release path still requires the applicable approved procedure, evidence and authorised decision; the schedule alone does not resolve a missing requirement.

Figure 3. Review starts while the batch is still running

5Record precisely what QA decided.

Once the impact assessment is approved and manufacturing review is complete, the case is ready for the authorised release role. The disposition records the defined batch population, quantity, presentation, evidence reviewed, rationale, conditions, signature meaning and effective time. Completing the preceding reviews does not make that decision; it remains with the quality unit.²

A release, rejection, restriction or further-evaluation outcome must carry its own scope. When an authorised amendment is needed, preserve the previous decision and the reason for the change. A reviewer returning later should be able to reconstruct the evidence considered and the decision made at that point, including any approved outstanding conditions.

B-071 › Disposition
release recorded
Decision
Release
Scope
Batch B-071, defined presentation
Evidence
Four requirements, reviewed versions
Condition
Market M1 awaits acknowledgement
Signed
QA, as the release decision
Figure 4. What the disposition records

6Carry the decision into stock, markets and certificates.

A manufacturer disposition and permission to distribute to a destination can differ. Once released, B-071 is eligible for Market M2 while Market M1 still awaits authority acknowledgement. Keep the market condition visible alongside the signed disposition. Configure inventory and distribution controls to apply the intended population and destination scope.

Prepare the certificate of analysis from the approved product, specification and reportable result versions. Retain certificate review, issue and replacement history. Reconcile the disposition, stock transition, applicable market gates, certificate and required notifications before closing the case. Each downstream record should lead back to the decision that supports it.

7Start with one difficult batch.

Bring an approved release procedure and a representative batch with a real review problem. Scope the source systems, release requirements and responsible teams. Use Neil to prepare the evidence index and proposed review work; have the team review the configuration and verify the release path against its intended use.

Prove the awkward cases as well as the completed case: a preliminary result, a changed reviewed record, an unresolved impact assessment, an unauthorised completion attempt and a destination that remains blocked after QA disposition. Agree which record owns each decision and how stock and certificates consume it. That gives the first workflow a concrete acceptance boundary.

Connect batch execution, QC laboratory work, deviation assessment, inventory and certificates of analysis around the same release case.

References

  1. 121 CFR 211.165, Testing and release for distribution: each batch must be tested for conformance to final specifications, including identity and strength of each active ingredient, prior to release. eCFR
  2. 221 CFR 211.22, Responsibilities of quality control unit: a quality control unit must have the responsibility and authority to approve or reject components, in-process materials, packaging, labelling and drug products, and to review production records. eCFR

AConnected across Seal

BCapabilities

CapabilityWhat it covers
Release requirement planningResolve execution, testing, quality, equipment, training, data-review, market, certificate and approval obligations from the effective product state.
Evidence and population resolutionLink each obligation to the reviewed version of its source record and to the batches, samples, events, people, assets and documents in scope.
Exception-based reviewRoute missing, failed, stale, changed or judgement-dependent requirements to reviewers while keeping the full review population visible.
Concurrent reviewReview completed evidence during execution with source-version snapshots. Configure and verify reassessment when relevant source data changes.
QA dispositionSign release, rejection, restriction, reprocessing or other decisions for a precise population with conditions, rationale, evidence and segregation of duties.
Market eligibilityKeep manufacturer disposition distinct from authority release, label, import testing, serialisation and other destination-specific distribution gates.
CoA provenancePopulate reviewed certificates from approved specifications and reportable results, with field-level source traceability and replacement history.
Release reconciliationClose only after obligations, exceptions, decisions, market gates, inventory transitions, certificates and approved open controls agree.

CConnected records

Entity
What it records
Kind
Batch Release Case
Accountable review and disposition record for a defined batch population, product state, site, presentation and market scope.
type
Standard Commercial Release
Post-execution review plan for a commercial lot under approved manufacturer and destination-market requirements.
template
REL-071
Illustrative release case for B-071, connecting material, QC, manufacturing and deviation reviews to disposition and two destination-market gates.
instance
Concurrent Short-Shelf-Life Review
Scheduled rolling review with stale-evidence controls, latest-decision time, handoffs, contingencies and final reconciliation.
template
Release Requirement
Versioned execution, testing, investigation, equipment, training, data-review, regulatory, document or approval obligation.
type
Executed Batch Record Review
Approved process version, completed operations, materials, calculations, corrections, exceptions, signatures and yields.
template
Release Testing Review
Applicable specification, samples, methods, suitability, raw-data review, OOS or OOT state, and approved reportable results.
template
Review Population
Governed set of batches, sublots, materials, samples, equipment uses, people, events, data and documents included in review.
type
Release Evidence
Source record and the reviewed version, with its meaning, status, provenance, reviewer and supersession history.
type
Review Exception
Failed, missing, stale, changed, excluded or judgement-dependent requirement with context, owner, assessment and resolution.
type
Release Review
Reviewer, assigned scope, source versions, exceptions, comments, outcome, signature, staleness and completion state.
type
REV-071-QA
QA review records population, source versions, extended-hold impact, result state, comments, signature and completion.
instance
QA Disposition
Signed decision for a precise population, quantity, product state, conditions, rationale, evidence snapshot and effective time.
type
DISP-071-01
Batch B-071 approved for specified presentations and markets; one authority-release market remains ineligible.
instance
Market Eligibility Gate
Destination-specific regulatory, authority-release, label, testing, serialisation, import or approval condition.
type
Authority Lot-Release Gate
The destination stays ineligible until the required regulator-facing protocol, samples, response and authorisation are complete.
template
GATE-071-M1
Market M1 distribution remains blocked pending external lot-release acknowledgement.
instance
Inventory Status Transition
Authorised quarantine, release, restriction, rejection, reprocess, return or destruction movement tied to the disposition scope.
type
Release Certificate
Controlled CoA or disposition document with field-level provenance, template, review, signature, delivery and replacement history.
type
Market Certificate of Analysis
Market- and customer-specific controlled certificate populated from approved product, specification, result and disposition sources.
template
COA-071-M2
Signed certificate uses approved reportable results and market template with field-level source traceability.
instance
Release Reconciliation
Final verification of obligations, populations, exceptions, decisions, market gates, inventory, certificates and open controls.
type

DQuestions and answers

Does Seal replace MES, LIMS and QMS for batch release?

Not necessarily. The release case can draw on records from existing validated systems or from Seal modules. It resolves source evidence to requirements and retains what QA reviewed, without making every connected system the same system.

What does review by exception mean?

Configured checks verify rule-based requirements and route unresolved items to reviewers. The full population stays visible: teams can see each rule run, included record, evidence version, exclusion, stale item and manual judgement, not only the flagged items.

Can QA review before manufacturing is complete?

Yes. Completed evidence can be reviewed during execution, with each review’s scope and source versions retained. Configure and verify which later changes require reassessment. Final disposition still requires the complete configured evidence set.

How are deviations and OOS results handled?

They remain linked to their operation, sample, result, evidence, investigation and product-impact decision. Closing an investigation does not itself release a batch; QA records how its approved conclusion affects the defined release population.

Does a QA-released batch become distributable everywhere?

Not necessarily. Market eligibility can also depend on authority lot release, local testing, the registered specification, approved labelling, import or serialisation requirements. These states stay distinct and can be configured as distribution gates.

How are equipment and training checked?

Eligibility is evaluated at the time and purpose of use against effective qualification, calibration, maintenance, cleaning, curriculum, practical qualification, expiration and restriction records. Today’s status is not used as retroactive proof.

Can Seal generate a CoA?

Yes, once the configured prerequisites are met. Product, batch, market, specification, reportable results, statements and disposition populate controlled fields with their provenance. Review, signature, delivery, correction and replacement follow the approved workflow.

What supports short-shelf-life products?

The release plan shows when evidence is expected, the latest decision time, handoffs, missing data and contingencies. Concurrent review reduces avoidable waiting, while conditional paths still follow approved product- and market-specific procedures.

Can a release decision be changed?

An authorised amendment or reversal creates a new signed decision linked to the prior one. It identifies the affected population and inventory, and starts the required notifications and controls, and the earlier decision is retained.

What should an implementation prove first?

Take one difficult lot from release planning through execution and testing evidence, including a deviation or OOS result. Continue through concurrent review, point-in-time equipment and training checks, QA disposition, a market-specific gate, the inventory transition, the CoA and final reconciliation.

See your process in Seal.

Bring a procedure or a recurring problem. See how your team configures it with Neil and improves the next run.