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
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 ↓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
Each client asks for its own release package, and its reviewer returns whatever the plant left out.
Pulled by hand for each batch
Built-in controls
Each package reaches the client already checked against that client's own rules, so its release review starts on a complete file.
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.
Each signs a different thing, in a fixed order.
Build and check each client package, and confirm what records cannot settle
Review release results and sign the certificate of analysis
Sign the certificate of manufacture as QP, and approve learned rules
Send signed packages and own what each client writes back
Around the one batch: the queue across clients and plants, the record of send-backs and the settings each client's agreement drives.
demoSample data, from the working solution.
The chain runs from the client's agreement to the portal, and it stops at each signer.
Reads the client's rule pack, plans the package and assembles the documents in the client's order and format.
Pulls the batch record summary, review exceptions, lots, filter tests, results, deviations, changes, monitoring data and storage temperatures.
Drafts the certificate of analysis against the specification in force, and the certificate of manufacture and GMP compliance.
Ticks each checklist item only with a cited page.
Plays the client's QA reviewer from the agreement and past send-backs, and lists what that reviewer would return.
Sends the signed package to the client portal and reads the structured receipt and answers.
Turns each send-back into a proposed rule for that client.
Each signer opens the document first, signs as themselves with a meaning, and cannot sign their own work.
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.
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.
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.
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.
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.
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.
Every report heard in the operator's own words, contained at once, classified by QA the same day.
1-min demoDeviation Impact AssessmentEvery batch that shares a cause is found, held or cleared the same day, and the client hears first.
1-min demoHuman Error Investigation"Human error" is earned, not assumed, and the fix lands on the design of every line.
1-min demoBring 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.