Batch certification is often described as the final step in manufacturing. Operationally it is the last step in a chain of information transfers, most of which cross a company boundary. The Qualified Person signs on the basis of records produced by manufacturing sites, testing laboratories and packaging operations that frequently belong to other organisations.
That makes release a contract problem as much as a quality one, and it explains why quality operations teams spend so much of their time chasing documents rather than assessing them. Every input the Qualified Person relies on is an obligation somebody owes under an agreement, with a scope, a timeframe and an escalation path. Where those obligations are written clearly and tracked, release runs on schedule. Where they are implied by practice, the chain holds until the first unusual batch and then stops. The chain is also longer than most release timelines assume, because a single finished pack can involve an active ingredient supplier, a drug product site, a packaging operation, two laboratories and an importer, each with its own agreement and its own interpretation of what it owes.
The gap tends to open in the same place each time. The quality agreement describes responsibilities in prose, the supply agreement describes delivery in commercial terms, and neither produces a dated record anyone can monitor. It is the same drift described in managing CDMO quality agreements, where the document is sound and the follow-through is not.
The four obligation groups behind a release
Reading a typical quality agreement against an actual release decision produces four clusters of obligation. Each should be recorded with an owning party, a timeframe and a defined closing artifact.
- Batch documentation, covering executed manufacturing and packaging records, certificates of analysis and reconciliation data within a stated number of working days.
- Deviation and investigation status, requiring closure or a documented interim assessment before the batch can be considered for certification.
- Change notification, listing the change categories that require advance notice, the notice period and the approval right the receiving party holds.
- Compliance state confirmation, covering inspection outcomes, licence status and any regulatory action affecting the manufacturing or testing site.
- Import testing or exemption basis, recording whether testing is repeated in the receiving territory and, if not, the legal instrument relied on.
Change notification is the group that causes most retrospective difficulty. A change implemented without notice is a clear breach and is usually identified quickly. The more common failure is subtler: the notice arrives, it is filed, and nobody records a decision. Months later the release history shows a change that was notified and never assessed, which is harder to explain than a change that was missed outright, because the company plainly had the information and did nothing with it. A notification record that cannot close without a recorded decision removes the possibility entirely, and costs nothing to implement.
A responsibility matrix written at company level breaks down as soon as a second manufacturing site or a separate packaging operation joins the chain. Write the matrix per site and per activity, and reissue it when the network changes rather than at the next scheduled review.
What belongs on the release obligation record
Treating each obligation as a record rather than a paragraph requires a small, fixed field set. Resist the temptation to model everything the agreement says; the objective is a register that a quality operations team will actually maintain between inspections. These five fields carry almost all of the operational value.
- Owning party and site. The legal entity and the specific facility, since duties differ between sites operated by the same supplier.
- Trigger and timeframe. What starts the clock, such as batch completion or a change decision, and how many working days follow.
- Closing artifact. The named document that satisfies the obligation, so completion is evidenced rather than asserted.
- Escalation path. Who is notified on the supplier side and internally when the timeframe lapses, with the step after that.
- Retention period. How long the artifact must be held and who holds it, including rights of access after the agreement ends.
A five-step implementation roadmap
Step 1, Map the physical chain
List every site that manufactures, tests, packages, stores or imports the product, with the legal entity behind each. The map is the base layer for everything else, and in multi-product portfolios it is usually less complete than the quality function assumes.
Step 2, Abstract obligations from the quality agreements
Work through each agreement and extract the obligations into the five-field structure above. Where a responsibility is described without a timeframe, flag it; an obligation with no clock cannot be monitored and will be the one that slips during a busy period.
Step 3, Reconcile against the supply agreement
Compare the quality agreement against the commercial terms for the same activities. Conflicts between delivery timeframes and documentation timeframes are common and are best resolved by amendment rather than by a working assumption held in one team.
Step 4, Instrument change notification
Create a record type for incoming change notifications with a decision field and a due date. Require an assessment outcome before the record can close, and report open notifications by age so the backlog is visible before an inspection surfaces it.
Step 5, Review the import basis annually
Where testing is not repeated on import, re-verify the instrument relied on, the sites it covers and the product categories in scope. Record the review with a date and an owner, because the arrangements change and the reliance is otherwise invisible until challenged.
Put the release chain on one register
Site-level responsibilities, notification clocks and closing evidence, managed as live obligations.
Why release delays are usually data delays
When a release slips, the explanation offered is normally an open deviation or a late certificate of analysis. Both are real, but they are symptoms. The underlying cause is that the supplier obligation producing that document had no tracked due date, so nobody chased it until the Qualified Person asked. Making the obligation visible days earlier moves the chase forward and takes the pressure off the final step. The effect compounds across a portfolio, and it is the same mechanism that makes a quality agreement management programme worth running at all.
Obligations by party and closing evidence
The table summarises a representative release chain. Timeframes are illustrative and should be replaced with those in the governing quality agreement for each site.
| Obligation | Owing party | Typical trigger | Closing evidence |
|---|---|---|---|
| Executed batch records supplied | Manufacturing site | Batch completion | Reviewed batch record package |
| Finished product certificate of analysis | Testing laboratory | Completion of testing | Signed certificate of analysis |
| Deviation closed or assessed | Site owning the deviation | Deviation raised | Investigation report with impact statement |
| Change notification and decision | Party making the change | Change proposed | Notification record with assessment outcome |
| Import testing or exemption basis | Importer | Receipt in territory | Test results or documented legal basis |
The practical test is whether a Qualified Person can see, before a batch arrives at the release queue, which supporting obligations are complete and which are outstanding with an owner against each. Where that view exists, certification becomes a decision. Where it does not, it becomes a search, and the search happens under time pressure with product waiting. The difference rarely shows up in a single batch. It shows up across a quarter, in the proportion of releases that complete on the planned date and in how often the quality function has to ask a supplier for something the agreement already required them to send.
For related guidance, see GxP supplier qualification, contract controls that hold, Quality agreement obligations pharma teams keep missing and The sponsor’s guide to CRO master service agreements.
