These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Pharma ERP
- Features
- Batch release and stability
Batch release and stability
Connect batch review decisions with certificate, expiry and stability evidence.
OverviewPending batch release reviews×
Pharma ERP · Batch release and stability
New
Pending batch release reviews
Approval conditions
| Batch | QA reviewer | Certificate number | Expiry date | Status | |
|---|---|---|---|---|---|
| LTS-77972 | BRR-70718 | 08 Oct | Pending | ||
| LTS-86385 | BRR-54620 | 17 Oct | Pending | ||
| LTS-68332 | BRR-75361 | 14 Oct | Pending | ||
| LTS-63072 | BRR-23354 | 10 Oct | Pending | ||
| LTS-93891 | BRR-96951 | 26 Oct | Pending |
6 of 6 records
LTS-77972Batch release reviews · BRR-70718
PendingExpiry date08 Oct
What you can do
Bring the evidence to the batch decision
A completed production run still needs a quality decision about its batch. Each batch release review connects that decision to lots and a quality reviewer in the person record, with certificate number, expiry date and status visible on the review. The Batch Release Reviews screen presents a queue, status distribution, certificate and expiry evidence, and the selected record’s review history. The team can examine the recorded batch context before deciding which evidence needs attention. Industry Reviewer bases the release decision on the recorded quality evidence.
How the work is organized
- Review ownership. The reviewer record carries the reviewer identity through its user reference. Agree who may be selected as quality reviewer and how that person receives the Industry Reviewer responsibility. A displayed name must resolve to the correct account before any decision route is enabled.
- Decision progress. Pending and Testing identify work still under review; Approved and Rejected retain the outcome. Move the review from Pending through Testing to Approved after the relevant evidence is checked. Agree how the quality owner records an adverse decision and rehearse that route.
- Stability evidence. Each stability study links the batch to storage condition, pull date, result and disposition. Pending, Accept and Investigate distinguish a pull awaiting evaluation from an accepted result or an investigation. The pull date describes the evidence event and should survive a later correction.
What to agree during setup
Agree which certificate evidence is sufficient for your review and how certificate number is checked against certificates where applicable. Match the certificate number to the supporting certificate and selected lot during review. Resolve a changed number or inconsistent expiry with the quality owner before release. Decide how storage conditions are described consistently and who follows an Investigate disposition. External laboratory results and controlled documents need agreed import and access rules.
Check the handoff on an actual case
Take a batch whose production output has been accepted but whose review is still Testing. Industry Reviewer checks the linked lot record, the attributed quality reviewer and the certificate evidence shown on the screen. An acceptable production quantity cannot substitute for the batch decision. If certificate evidence refers to another lot, retain the discrepancy for investigation and do not record an unsupported approval.
Next, record a stability pull for the same batch and correct the reported result after review. The correction rehearsal must retain the original evidence and attribution through the configured successor-evidence route. Replaying the original capture must fail as a duplicate. Specialty review must not create another stock movement or financial posting. Rehearse these actions with the actual reviewer account. Require the named quality decision and confirm that ordinary capture cannot approve the batch.
What your team sees
- Batch review queue — Follow Pending and Testing work with its batch, reviewer, certificate number and expiry.
- Pending batch release reviews — Review records awaiting the configured decision route.
- Stability pull schedule — Follow dated pulls and Investigate evidence alongside the recorded result.
Follow the work through
Review batch and stability evidence and rehearse quality holds. Agree the account mapping through roles.
What it keeps track of
Data model- Batch release reviews
- Batch Release Reviews for ERP for Pharma.
- Stability studies
- Stability Studies for ERP for Pharma.
- Lots
- A quantity received or made together: supplier lot, receipt date and expiry, traced through issue, production and shipment.
- People
- People for ERP for Pharma.
- Users
- Users
- Certificates
- Certificates of conformance, material test reports and calibration certificates, attached to a supplier lot or an instrument.
Who uses it
Permissions- Industry Reviewer
- , Industry Specialist, Quality Inspector.
- Industry Specialist
- Maintains stability studies; Industry Reviewer reviews specialty evidence.
- Quality Inspector
- Owns supporting certificate and inspection work.
- Keep evidence preparation separate from the release decision.
Set up Pharma ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.