Batch releaseEvidence first, then signature

Batch release software where the evidence decides.

The batch release software in Swat iQua Suite assembles one release dossier per batch from the records themselves — batch record, QC results, CoA, deviations, packaging and sterile checks. QA batch release is possible only when every critical item is satisfied, and the person who ran the batch can never release it.

  • Versioned release checklist
  • Critical items cannot be marked N/A
  • Blockers derived from open records
  • Certificate of Batch Release PDF
Swat iQua Suite batch release dossier with checklist items, named reviewers and status
100K+
batches released
25
modules enforce segregation of duties
3
e-signature levels
1–3
months to go-live

2-minute product tour

Real screens, real records. See a release decision in action.

  1. Batch release dossier with department sign-offs and critical review items marked satisfactory by a named reviewer

    Step 1 of 4Satisfactory

    One dossier per batch

    Production, QC, packaging and QA review sit in one release dossier. Every critical item is signed off by a named reviewer before QA can decide.

    1. Department sign-offs
    2. Critical review items
    3. Release certificate PDF
  2. Batch release with three open critical blockers and a rejection recorded in the activity timeline

    Step 2 of 4Rejected

    Blockers stop a release

    An unsatisfactory critical item raises a blocker. This batch was rejected — yield below limit, no QC release testing and no Certificate of Analysis — with the reason on record.

    1. Critical blockers
    2. Override only by request
    3. Rejected, with the reason
  3. Shipment with its finished-goods lot, quantity and status, and an activity timeline of the dispatch

    Step 3 of 4Dispatched

    Only released stock ships

    A shipment carries released finished-goods lots only, and every status change — created, dispatched, delivered — is logged with the user and time.

    1. Customer & status
    2. Finished-goods lot
    3. Every change logged
  4. Traceability screen tracing a batch forward to bulk batches, packaging orders, finished-goods lots and shipments

    Step 4 of 4Forward trace

    Traced forward in one view

    Pick a batch and see its bulk, packaging orders, finished-goods lots and shipments to each customer — or trace a finished-goods lot back to its batch.

    1. Pick a batch
    2. Finished-goods lots
    3. Shipments & customers

Real product footage

Watch a release decided on the evidence.

QA batch disposition

How batch release software should protect the QA signature.

A QA release signature says the batch was made, tested and investigated as required. Collecting that proof by hand is where time is lost and mistakes slip in.

One dossier, built from the records

Each batch gets one release dossier, created from a versioned checklist template that is itself approved with segregation of duties and an e-signature. The checklist is filtered by batch category and sterility, so a sterile injectable sees sterility, endotoxin and media-fill items and a tablet batch does not. Typical items include:

  • Batch manufacturing record complete and signed
  • Yield reconciled
  • QC testing complete and within specification
  • Certificate of Analysis approved
  • Deviations, OOS investigations and CAPAs closed
  • Material genealogy traced
  • Packaging reconciliation complete
  • Sterility, endotoxin and media fill satisfactory (sterile batches)
  • QA final review

Review by exception — with rules the system enforces

Critical items cannot be marked not applicable. The “QC complete” and “deviations closed” items cannot be attested while linked QC, deviation, OOS or CAPA records are still open — the status is derived from system data, not typed in. An unsatisfactory critical item raises a release blocker, and sterile failures (BI/CI, filter integrity, CCIT, visual inspection, media fill) raise blockers automatically. QA’s attention goes to the exceptions instead of re-checking every page.

Overrides are documented exceptions

Where a blocker must be overridden, it becomes a documented risk-acceptance exception: requested, then approved independently with segregation of duties and an e-signature. Evidence exceptions approved under QA authority expire, and once expired the item is blocked again automatically. Even an administrator cannot bypass a critical evidence gap.

The decision

The reviewer cannot be the dossier creator, and completing the review freezes the checklist. The release decision is e-signed by QA, and the person who executed the batch cannot be the releaser. Release automatically moves the batch’s finished-goods lots from quarantine to released; reject, hold, lift hold and close are recorded the same way. A Certificate of Batch Release PDF is generated on release.

QP release: where an EU or UK Qualified Person certifies batches, certification remains the QP’s own responsibility. Swat iQua Suite gives the QP or QA head the assembled evidence and an e-signed release record — it does not replace QP certification.

Evidence to decision

From batch record to released lot.

  1. BMRSITE-01/26/0002

    Batch record closed

    E-signed close, with yield classified against the formula’s window.

    Closed
  2. QCCoA

    QC complete, CoA approved

    Results reviewed and approved by different people; the CoA is generated.

    Approved
  3. Dossier26BREL0002

    Checklist reviewed

    Blockers cleared or covered by approved exceptions; review freezes the checklist.

    Pending decision
  4. ReleaseFG lots

    QA releases

    E-signed; finished-goods lots move from quarantine to released.

    Released

Shipments accept only released lots — the release decision flows straight into distribution.

Evidence sources

Every input to release, already in the system.

  • In-House QC Testing

    QC results classified against limits frozen at assignment — a later spec change never rewrites a verdict.

    QC testing
  • Deviation Management

    Open deviations, OOS investigations and CAPAs block the “deviations closed” item.

    Deviation management
  • Packaging & Reconciliation

    Printed-component reconciliation must balance before the finished lot exists.

    Packaging
  • Environmental Monitoring

    Excursions dispositioned with sterile impact become critical release blockers.

    Environmental monitoring
  • Inspection Readiness

    The same evidence framework assembles inspection dossiers with a checksum manifest.

    Inspection readiness
  • Distribution, Traceability & Recall

    Ship only released lots; trace and recall from one view.

    Traceability & recall

After release

Ship, trace and recall from the same records.

Shipments refuse any finished-goods lot that is not QA-released. Dispatch records a genealogy link, so any lot traces backwards to its raw-material lots and forwards to every customer that received it.

  • One-click traceability — material lots → dispensing → batch → bulk → packaging → finished lot → shipment → customer.
  • Recall — affected lots and customers resolved automatically.
  • Recall records — notification per customer, returns, recovery % and an effectiveness check.
  • E-signed closure — with a SHA-256 checksum evidence manifest.
Distribution, traceability & recall
Pharmaceutical capsules on a production line

What regulators expect

One release record for every market.

The wording differs between regulators, but the expectation is the same: the quality unit reviews the complete record, and nothing unexplained is released.

US FDA

21 CFR 211.192 requires production and control records to be reviewed and approved by the quality control unit before a batch is released, and any unexplained discrepancy or failure to meet specifications to be thoroughly investigated. The release dossier makes that review explicit: each linked record, its status and the investigation behind it.

EU and UK

In the EU and UK, batch certification by a Qualified Person rests on confirming that the batch was manufactured and checked in line with its marketing authorisation and GMP. The dossier gives the QP the evidence in one place, with every input traceable to its signed source record.

India, WHO and other markets

Revised Schedule M and WHO GMP both expect the quality unit to review batch records and investigations before release. The same dossier, audit trail and e-signatures serve FDA, MHRA, EMA, CDSCO and WHO inspections from one set of records.

Built into the release

The controls behind every release decision.

  • The person who ran the batch cannot release it

    Segregation of duties between batch executor, dossier creator, reviewer and QA releaser — enforced by the server.

  • E-signed decisions

    Release, reject, hold and exception approvals re-authenticate the signer.

  • Full audit trail

    Every checklist entry, blocker and decision with user, time and reason.

  • Certificate of Batch Release

    An A4 PDF generated on release.

  • Expiring exceptions

    Approved evidence exceptions expire and re-block automatically.

Customer stories

Ten years on, they would choose Swat iQua Suite again.

“Ten years on, we would choose it again.”

We moved our QC LIMS onto SwatTech in 2016 and have never looked back. Every specification, result and calibration is one search away, and every change explains itself. When inspectors arrive, we don’t prepare — we simply open the system.

ARC Pharma UK LimitedUnited Kingdom · QC laboratory, since 2016

“Audits are something we welcome now.”

In contract testing, our reputation rides on every result we sign. A second-person review on every result, a complete audit trail and a client portal that delivers reports and CoAs on time have turned audits from something we braced for into something we welcome.

Lunar Labs LimitedUnited Kingdom · QC laboratory

“Any batch, traced in one click.”

In API manufacturing, traceability is everything. Today we follow any batch back to its raw-material lots and forward to every shipment in seconds. Revised Schedule M no longer feels like a deadline — it feels like the way we already work.

Norvium Healthcare Pvt. Ltd.India · API manufacturing

FAQ

Frequently asked questions

Can’t find your answer? Talk to our team — we reply within one business day.

What is batch release software?

Software that assembles the evidence for a batch disposition — batch record, QC results, CoA, deviations, packaging and other checks — and records the QA decision with an e-signature. In Swat iQua Suite the evidence comes from the same platform, so the status of each item is derived from the records rather than typed in.

Can a batch be released with an open deviation or CAPA?

Not without a trace. The “deviations closed” item cannot be attested while a linked deviation, OOS or CAPA is open. If a blocker must be overridden, it goes through a documented risk-acceptance exception, approved independently with an e-signature.

Does it support QP release?

It gives the Qualified Person or QA head one dossier with all the evidence and an e-signed release record. QP certification itself remains the QP’s own responsibility; Swat iQua Suite does not replace it.

Is a Certificate of Batch Release generated?

Yes. A Certificate of Batch Release PDF is generated on release, and the finished-product CoA is generated from the approved QC results.

What happens to finished goods after release?

Release moves the batch’s finished-goods lots from quarantine to released. Only released lots can be added to a shipment, and each shipment is linked for forward and backward traceability.

Does it handle sterile batches?

Yes. The checklist adds sterility, endotoxin and media-fill items for sterile batches, and failed sterilisation, filter integrity, CCIT, visual inspection or media fill results raise release blockers automatically.

Ready to see Swat iQua Suite in action?

Book a free, personalised demo and see how Swat iQua Suite takes your plants, labs and quality teams from paper to inspection-ready.

Download the brochure →