Skip to main content

Prepare a batch for review.

Check execution, LIMS and quality evidence against your batch-review requirements and prepare a source-linked brief with missing evidence requested.

Illustration of a seal reading a signed batch certificate marked Released beside a tray of finished cartons.
Neil reads
  • The batch execution record and review requirements
  • Linked QC results and deviation records
  • Recorded signatures and approval status
Neil drafts

A batch review brief with an evidence checklist and open items.

Your team decides

QA verifies the evidence and decides disposition; in the EU a QP certifies the batch.

Neil’s summary does not release it or replace signatures.

Example conversation

You

Can you get B-2407 ready for QA review?

Neil

Yes. I found a few gaps to sort out first.

The transfer-stop assessment is still open, and two QC reports aren’t attached. I’ll bring those into the review brief with the sources behind each finding.

See the five sources

This example uses selected execution, LIMS, quality and ERP snapshots, plus a controlled review-plan excerpt. In your environment, these can come from configured connections or supplied exports.

Example records; no live query or source changes.

You

But the batch is marked complete?

Neil

That’s the execution status, not a QA decision.

still shows a quality hold, and no QA disposition is recorded. I can prepare the review; I won’t change the stock status.

You

SEC purity passed. What’s missing?

Neil

The supplied plan names three reports. I have one.

The purity result and method match . I’d ask QC for the other two reports and their review status.

Missing from this package doesn’t mean the tests failed—or weren’t run.

You

Put that in a brief for Quality. Include who needs to follow up.

Neil

Here’s the draft. Each finding has its source version and a follow-up for QC, Quality or the batch reviewer.

B-2407 review brief · Draft 01Findings, source versions and follow-up work
B-2407Draft 01

Batch review brief

Execution is complete. Two review items need attention.

Pending in v03

Product-impact assessment

DEV-038 does not yet establish the product impact of the transfer interruption.

Two reports not supplied

Complete QC panel

QC-2407 supplies SEC purity. BR-012 also requires potency and host cell protein. Missing from this package does not mean the tests were not performed.

Review basis and selected versions

Checked against the supplied BR-012 v06 excerpt. This brief is not an exhaustive batch-release checklist.

Selected snapshots: 9 September 2026, 09:00 UTC. Original source versions stay attached to this brief.

Follow-up work by owner
QC reviewer
Supply the potency and host cell protein reports for B-2407. Confirm sample and batch identity, applicable methods and specifications, report review status and any exceptions.
Deviation owner
Complete the product-impact assessment in DEV-038 using the transfer pump log, line pressure trend and post-transfer bioburden result; route it to the authorised reviewer.
QA reviewer
Confirm the complete batch-review scope and assess the execution, analytical and deviation evidence. Refresh source statuses before recording any disposition; preserve required signatures and the stock restriction until the authorised process permits a change.

Send me the updated assessment when it arrives and I can refresh the brief.

This demo uses prewritten replies.

Bring the batch that’s waiting for review.

Give Neil the batch reference and your review requirements. Connect the relevant systems or supply the records. Get a brief with source versions, missing evidence and follow-up work your reviewers can act on.

Book a demo
Execution system / v07

B-2407

Batch execution record

Batch
B-2407
Product
mAb-24 drug substance
Execution
Complete
QC evidence
QC-2407 attached
Linked deviation
DEV-038
Review status
Awaiting QA review
Snapshot
9 September 2026, 09:00 UTC

Execution completion is the recorded workflow state, not a completed QA review. The underlying execution evidence and applicable review requirements still need verification.