WorkflowQuality Operations & CAPA

Client Batch Release Package

Batch release documentation for each client, built from the plant's records, checked as that client's reviewer would check it, and signed before it leaves.

See one client's release package built and sent ↓
Watch with transcript →
The problem

The client's reviewer finds what the release team missed

A contract manufacturer sends each client a different release package: certificates, the batch record summary, deviations, changes, monitoring, media fill and stability, in the order that client's quality agreement sets. Specialists assemble them by hand from five systems and keep each client's rules in their heads and in old emails.

The client's reviewer reads every page. A background-room excursion left out, a certificate naming a superseded specification, two documents that disagree: each one comes back as a send-back, and the client's own market release waits a full loop for the fix.

Built forQA release specialistsHeads of QAQC reviewersClient quality liaisons

The Problem Today

Each client asks for its own release package, and its reviewer returns whatever the plant left out.

21
points a QP must ensure before certifying a batch, Annex 16 published

Pulled by hand for each batch

  • Records
  • Lab results
  • Deviations
  • Monitoring
  • Each send-back costs a loopThe client's release waits for the fix to come back
  • Client rules kept in headsEach checklist lives in old emails and one specialist's memory

The Solution

  1. The agreement read as a checklistEach item the client asks for, with its clause and past lessons
  2. Gathered and ticked by pageRecords pulled from the plant systems; each tick cites its page
  3. The client's review rehearsedA challenger finds a missing excursion and the agents' own old revision
  4. Signed, sent, receiptedThe QP signs the certificate; the client portal confirms what arrived

Built-in controls

  • No item is ticked without a cited page
  • The client's own QP releases to market
  • Learned rules apply only after QA approves them

What You Get

Each package reaches the client already checked against that client's own rules, so its release review starts on a complete file.

  • A receipt in fields on arrivalThe client sees items, pages and checksum as the package lands
  • Each client's rules, keptSend-back lessons approved and applied for the next specialist
  • Evidence reused for auditsEach page traced to the system record it came from
Features

Batch release documentation features, from checklist to client receipt

The release specialist, the QC reviewer, the QP and the client quality liaison work one sterile injection batch through them, for a client whose agreement asks for sixteen items.

demoThe contract manufacturer, its client, the people, batch numbers and every figure shown are sample data.

  1. 01Assembly

    Batch release documentation assembled by agents from the plant's systems

    • Records pulled read-only from each system. Batch record summary, review exceptions, lab results, deviations, changes and monitoring data arrive without a specialist exporting from five screens.
    • No tick before a cited page. The checklist stays empty while records come in, so a tick always means a page someone can open.
  2. 02Binder

    The client's checklist, read from its quality agreement and ticked by page

    • One checklist per client, with its clause. Each item carries the agreement clause it comes from, so a new specialist builds a package the way that client asks for it.
    • Laid out as the client will receive it. Index, page numbers and order follow the client's agreement, so its reviewer finds each item where they expect it.
  3. 03Client reviewer

    A challenger that reads the package as the client's QA reviewer would

    • Send-backs found before the package leaves. Each point is written as the client's reviewer would write it, with clause and evidence, so gaps close in-house instead of in the client's queue.
    • The agents' own drafts attacked too. A certificate of analysis drafted against an old specification revision is caught by the same reviewer that checks the records.
    • Past send-backs turned into checks. A lesson from an earlier send-back becomes a question asked of each later package for that client, once QA leadership signs it off.
  4. 04Points answered

    Each reviewer point closed by an agent with a cite, or by a named person

    • Fixes the reviewer can see. A pulled excursion report adds its pages and re-ticks the item, and a redraft clears the earlier signature on that certificate.
    • Statements a person confirms. Where a record cannot settle a point, the release specialist opens the source and confirms it as themselves.
  5. 05Excursion report

    Environmental monitoring excursion report pulled into the release package

    • Background rooms beside Grade A. EU GMP Annex 1 expects monitoring and trend data for classified areas to be reviewed for release, so the background room travels with the Grade A results.
    • The deviation and its assessment together. The client's reviewer reads the excursion, its cause and the impact assessment without asking for a second package.
  6. 06Certificate of analysis

    Certificate of analysis drafted against the specification revision in force

    • Results from LIMS, limits from the specification. Each test line carries the limit of the revision in force, so the certificate matches what the client approved.
    • Signed by QC, never by an agent. The QC reviewer reads the results and signs, and any later redraft asks for that signature again.
  7. 07Sign and send

    Four signatures in order, then a structured receipt from the client portal

    • Preparer and certifier are different people. The release specialist marks the package checked and cannot also sign the certificate, which the QP signs as checker.
    • A receipt in fields. The client's portal returns the items received, the pages and a checksum, so both sides know the same package arrived.
    • Market release stays with the client. The receipt shows market release as the client's own decision, made by the client's QP in the client's own system.
  8. 08Client portal

    The client's QA reviewer accepts or sends back each item in its portal

    • Item-by-item acceptance. The client's reviewer accepts or returns each item with a reason code, and nobody untangles an email thread about the whole package.
    • A send-back reopens the package. A reason code clears the signatures, and the fixed version goes back through the reviewer and the signers before it is sent again.
  9. 09Client rules

    Client quality agreement requirements kept as checklists with learned rules

    • Each client's rules side by side. Three clients' different packages sit with their clauses, so a specialist can take on another client's batches without inheriting a folder of emails.
    • A learned rule waits for sign-off. A rule proposed from a send-back takes effect for that client's next package only after the QP signs it.

Four people put their names to a client's release package

Each signs a different thing, in a fixed order.

QA release specialists

Build and check each client package, and confirm what records cannot settle

  • The client's checklist with the clause behind it
  • The reviewer's points before anyone signs
  • Each tick tied to a page
QC reviewers

Review release results and sign the certificate of analysis

  • A certificate drafted against the revision in force
  • Each result beside its limit
  • A redraft that asks for a fresh signature
Heads of QA

Sign the certificate of manufacture as QP, and approve learned rules

  • The closed reviewer points beside the certificate
  • Nothing to sign before the package is checked
  • Send-back lessons offered as rules
Client quality liaisons

Send signed packages and own what each client writes back

  • A structured receipt for each package
  • Client notes held for them, unread by agents
  • Each client's clock in one queue

Records behind batch release documentation, system by system

Executed batch record and MESBatch record summary, review exceptions, component lots, filter integrity, sterilization and inspection records.
Release results in LIMSEach test result and its approval, set against the specification revision in force.
Deviations and change controlsEach deviation with its impact assessment, and each change effective in the batch period with the client's approval.
Environmental monitoringGrade A and background-room results for each fill day, with their excursion reports.
Warehouse temperaturesThe quarantine storage record from the cold room.
Quality agreements and past send-backsEach client's checklist, clause and clock, and what its reviewer has returned before.
More screens

The open packages, the agents' run and what each client returned

Around the one batch: the queue across clients and plants, the record of send-backs and the settings each client's agreement drives.

Before assembly: the checklist and its systemsThe package is due by the client's clock; until the agents assemble it, only the client's checklist and the systems they will read are shown.
Each agent's plan, sources and hand-offEach agent lists what it read, what it concluded and who it handed to, including the checklist checker's withdrawn tick on item 13.
Open packages and each client's clock37 packages across three clients and four plants, filtered by stage, with blocked, sent-back and to-sign rows each carrying its next action.
Why packages came backThe year's send-backs with reason code and the rule each one taught; missing items and wrong revisions lead the count.
Receipts and client answersEach receipt with items, pages, checksum and the client's answer; market release appears only as the client records it.
Clocks and signers, set per clientEach client's clock follows its agreement, the signer for each step is locked, and a change takes effect only with the QP's signature.

demoSample data, from the working solution.

One agent plays the client's reviewer against the other six

The chain runs from the client's agreement to the portal, and it stops at each signer.

Package coordinator

Reads the client's rule pack, plans the package and assembles the documents in the client's order and format.

  • Adds no requirement the agreement does not hold
  • Sends nothing
Records gatherer

Pulls the batch record summary, review exceptions, lots, filter tests, results, deviations, changes, monitoring data and storage temperatures.

  • Reads only, and edits no record
Certificate drafter

Drafts the certificate of analysis against the specification in force, and the certificate of manufacture and GMP compliance.

  • Signs nothing
  • States no market release
Checklist checker

Ticks each checklist item only with a cited page.

  • Relaxes no client rule
Client reviewer

Plays the client's QA reviewer from the agreement and past send-backs, and lists what that reviewer would return.

  • Fixes nothing and closes none of its own points
  • Speaks for no client
Portal messenger

Sends the signed package to the client portal and reads the structured receipt and answers.

  • Sends nothing the QP has not signed
  • Leaves client free text to the liaison
Rule keeper

Turns each send-back into a proposed rule for that client.

  • Proposes rules; the QP decides which take effect

Four signatures leave the CDMO; market release stays with the client's QP

Each signer opens the document first, signs as themselves with a meaning, and cannot sign their own work.

QC reviewer
Sees
Each result beside the limit of the revision in force
Signs
The certificate of analysis
QA release specialist
Sees
The checklist, the page behind each tick and the closed reviewer points
Signs
The package as prepared and checked, as maker
Head of QA and QP
Sees
The certificate, with the reviewer's points in the same view
Signs
The certificate of manufacture and GMP compliance, as checker
Client quality liaison
Sees
The signed package and the client's clock
Signs
The send, once the certificate is signed

What QA release teams ask about batch release documentation

What is batch release documentation?

Batch release documentation is the package a manufacturer sends with a batch: certificates of analysis and of manufacture, the batch record summary, deviations, changes, environmental monitoring, media fill and stability. Here agents build each client's batch release documentation from the plant's records and check it as that client's reviewer would.

Who releases a batch made by a contract manufacturer?

The contract manufacturer's quality unit approves what it made, and its head of QA and QP signs the certificate. The client's own quality unit, in the EU its QP, certifies the finished batch and releases it to market in the client's own system.

What is the difference between a certificate of analysis and a certificate of compliance?

The certificate of analysis lists each test result against the specification. The certificate of manufacture and GMP compliance states that the batch was made and tested under GMP and the quality agreement. QC signs the first; the head of QA and QP signs the second.

How does it know what each client wants?

Each client's quality agreement is read into a checklist with the clause behind each item, and each past send-back is proposed as a rule for the QP to approve. A rule applies only after approval.

What happens when a client sends a package back?

The client's reviewer picks a reason code in the portal. The package reopens and its signatures clear, the agents fix the item where the reviewer can see it and re-read the new version, and it is signed again before it goes back.

What is an executed batch record?

The batch record as the batch was actually made, with each step, component lot and signature filled in. Here the agents read it from the eBR and MES without editing it, and its summary, review exceptions, component lots, filter integrity, sterilization and inspection records go into the client's package where its agreement asks for them.

Send one package
a client sent back.

Bring one returned package with its batch records and the client's quality agreement, and the agents will rebuild it and show what the client's reviewer would have found.