Batch release process flowchart (QP certification to despatch)
Batch release process flowchart for GMP manufacture: batch record review, analytical testing, OOS and deviation closure, QA review, QP certification, disposition, certificate of analysis and stock unblocking.
How it works
Rename the lanes to your own organisation
Replace Production, Quality control lab, QA, Qualified person and Supply chain with the functions you actually have. Contract sites usually split the lab into in-house and contract laboratory lanes; virtual manufacturers replace Production entirely with a contract manufacturer lane and keep the QP in-house. If you hold no marketing authorisation, rename the Qualified person lane to whoever your quality manual gives release authority to, and say so explicitly rather than deleting the lane and losing the separation between reviewing a batch and releasing it.
Write down what the record review must cover
"Close and review the batch record" and "QA review of the batch record" are only as good as the checklist behind them. List what is verified: every signature present, dated and in sequence; in-process results recorded as figures inside their limits; materials traceable to approved suppliers and released lots; equipment in calibration and within its qualification period; label reconciliation complete; yield inside the expected range; and every attached deviation cross-referenced. Decide which of those QA verifies itself and which it takes on trust from Production, and write that split into the procedure so it is not renegotiated batch by batch.
Set the investigation closure rule
"All investigations closed?" needs a written definition or it becomes negotiable at the worst moment. State that closed means the investigation reached a supported conclusion and issued an impact statement naming this batch, and that a linked CAPA may still be open. Say which shared events pull other batches in — a common bulk, a shared cleaning cycle, a failed media fill, an environmental excursion in the same room and shift. Name who may declare closure, and record the closure date separately from the CAPA date.
Make the disposition decision three-way in your SOP too
Most procedures describe release and rejection and leave hold to custom. Write it down: who applies a hold, what the batch's ERP status becomes, who owns it while it is held, when it is reviewed, and how remaining shelf life is recalculated so nobody releases a batch with four weeks left on it. Say who may lift a hold, and keep that with the person who certifies rather than with whoever is chasing the shipment.
Control the moment stock becomes sellable
"Update batch status and unblock stock" is where a good paper process meets an indifferent system one. Certification means nothing commercially until the ERP moves the batch from quarantine to unrestricted, and on many sites that transition is open to anyone with a warehouse role. Restrict it to the release record, log the user and timestamp, and reconcile the quantity unblocked against the quantity certified so reference samples, retains and rejected sub-lots are not quietly sold with the rest.
Walk it through with the people who run it, then publish a version
Sit down with a production supervisor, the QA reviewer who actually reads the records, an analyst and the QP, and walk the chart end to end against the last three batches you released. You will find steps that happen in a different order, a query loop nobody records, and at least one hand-off that runs on a phone call. Correct the chart to what is really done, agree the changes you want, then publish that revision with its approval and keep the earlier ones, so anyone opening it later can tell which version they are reading.
Frequently asked questions
What are the steps in a batch release process?
Close the executed batch record and reconcile the yield; review it for completeness and correct any gaps so that the original entry stays legible and the reason and date of the correction are recorded; complete the analytical testing and have the results reviewed by a second person; review environmental monitoring, utilities data and equipment status for the manufacturing window; confirm every deviation and out-of-specification investigation raised against the batch is closed with an impact statement; have QA review the record line by line; certify the batch against the marketing authorisation and GMP; take the disposition decision of release, hold or reject; issue the certificate of analysis; change the status in the ERP and unblock the stock; ship it; and archive the records and retention samples for the required period. The order matters more than the list. Every gate before certification exists so that the person signing is answering a question that has already been closed rather than one still being argued about.
What is the difference between batch release and batch certification?
They are two acts that often happen minutes apart and are frequently confused. Certification is the Qualified Person's confirmation, recorded in a register, that the batch was manufactured and checked in accordance with GMP and the terms of its marketing authorisation. Release is the subsequent step that transfers the batch into saleable stock: the status changes in the ERP or inventory system, the quarantine block comes off and the batch becomes pickable. EU GMP Annex 16 treats them as distinct, and it is worth keeping them distinct in your own procedure, because the failure mode is specific and common — a batch certified on paper while the system status stays in quarantine, or, far worse, stock unblocked by a warehouse user before certification was signed. Draw them as separate boxes owned by separate lanes and the gap becomes visible.
What does the Qualified Person actually do before certifying a batch?
The QP confirms that the batch complies with GMP and with the terms of its marketing authorisation, and takes personal legal responsibility for that confirmation in the EU and the UK. In practice that means satisfying themselves that the manufacturing and packaging record is complete and reviewed, that testing was performed to registered specifications and methods, that all deviations and out-of-specification results affecting the batch are closed with an impact assessment, that the facilities, equipment and utilities were qualified and in control, and that any contract sites in the chain are approved and covered by a technical agreement. Annex 16 allows the QP to rely on the quality system and on other named people for the detail rather than repeating every check personally, but the reliance has to be documented and the responsibility does not transfer. Where manufacture, testing and importation sit at different sites, each contributor's part is written down.
How is this different from a deviation management process flowchart?
They intersect at exactly one point and are otherwise different processes. The deviation management process at /templates/deviation-management-process starts when someone departs from an approved procedure: contain it, record it inside the reporting window, classify it as minor, major or critical, assess the impact, investigate the cause, decide on the affected batch and raise a CAPA. It runs on the event. This page runs on the batch. It assumes deviations are being handled properly elsewhere and asks only one thing of them, at the "All investigations closed?" gate: is every investigation attached to this batch finished, with a documented conclusion and an impact statement? Use the deviation chart to define how an investigation is run and classified. Use this one to define how a batch gets from a closed record to unblocked stock, and where a batch has to wait. Most sites need both, and they should reference each other rather than duplicate each other.
Can a rejected batch be reprocessed or reworked?
Sometimes, and only on terms written down in advance. Reprocessing repeats a step that is already part of the registered manufacturing process, such as recrystallising or re-filtering material. Reworking subjects the batch to something the registered process does not describe. Neither is a routine recovery from a failing result: both are available only where the marketing authorisation and the quality system provide for them, with a protocol approved before the work starts, an assessment of the additional risks to quality, and the QP involved in the decision rather than told about it afterwards. A reprocessed or reworked batch is tested again in full and its history is carried in the batch record, so a regulator or a customer can see what happened to it. In this chart that is why "Reprocessing permitted by the MA?" sits on the not-released route and why the permitted branch loops back to "Complete analytical testing" rather than forward to release.