The quality leader’s guide to the CDMO quality agreement

The quality agreement is usually the most operationally detailed document a pharmaceutical company signs with a contract manufacturer, and the least connected to any system. It is negotiated by quality, signed alongside a supply agreement negotiated by procurement and legal, and then filed. The obligations inside it are real, dated and auditable, and almost nobody tracks them as such.

Drift begins immediately. The supply agreement is amended for pricing or volume, the quality agreement is not. A site transfer happens and the responsibility matrix still names the original facility. A subcontractor change is raised verbally in an operations meeting rather than through the consent path the agreement requires. None of this surfaces until an inspection does.

Regulators expect the split of cGMP responsibilities between a sponsor and a contract facility to be defined in writing. FDA guidance on contract manufacturing arrangements sets that expectation for quality agreements, and the electronic systems holding the resulting records fall under 21 CFR Part 11 expectations for electronic records and signatures.

Start with the responsibility matrix

The core of a quality agreement is the allocation of cGMP responsibilities between sponsor and CDMO. Prose invites interpretation. A line by line matrix does not. For each activity, state who performs it, who approves it, who is notified, and within what period. Where an activity is shared, define what shared means operationally, because shared without definition means neither party owns it.

• Change control, which changes need prior written approval, which need notification only, and the notice period for each, separated by class so a raw material substitution is not treated like a label revision.
• Deviations and investigations, the window for notifying the sponsor of a deviation affecting sponsor product, who owns the investigation, who approves the root cause conclusion, and how effectiveness checks are evidenced.
• Out of specification results, the reporting timeline, whether the contract facility may release conditionally, and the escalation path when sponsor and CDMO disagree on the disposition of a batch.
• Audit and inspection rights, routine audit frequency, notice required, for cause audit terms, and the duty to tell the sponsor when an authority inspects the site or issues observations touching sponsor product.
• Records and data retention, which party retains batch records, executed protocols and stability data, for how long, in what format, and how the sponsor obtains access on request or on termination.

Two clauses deserve more attention than they usually get. Subcontracting consent, because a CDMO that outsources testing or packaging without written consent moves work outside the audited chain you approved. And data retention on termination, because access to batch records is hardest to obtain exactly when a relationship ends and most likely to be needed.

Turning clauses into tracked obligations

Most quality agreement failures are not disagreements about the text. They are missed clocks. A notification window elapses, an annual audit is not scheduled, a retention period passes with nobody confirming the records exist. Clauses that contain a period, a frequency or a trigger are obligations, and obligations need an owner, a due date and evidence that they were met.

• Extract every clause that contains a clock. Notification windows, reporting timelines, audit frequencies, retention periods and renewal dates. Each becomes a tracked record with an owner in quality, supply chain or regulatory, not a paragraph someone must remember.
• Give every obligation a named owner. Not the quality department. A person, with a named backup. Ownership that sits with a function rather than a person is the most common reason an obligation is found unmet during inspection readiness.
• Attach the evidence to the obligation. A completed audit report, a change notification acknowledgement, a signed deviation closure. If evidence lives only in a mailbox, the obligation is untracked in practice, whatever the register says.
• Alert before the deadline, not after. A notification window that has already closed cannot be met. Lead time should reflect the work required, weeks for a supplier audit, days for acknowledging a change notification.
• Review the register whenever the agreement changes. A site transfer, a new subcontractor or a scope change should trigger re-extraction, because obligations added by amendment are least likely to reach the people who perform them.

A five step approach to managing quality agreements

Step 1, Inventory The Agreements

Build one list of every quality agreement in force, with the CDMO, the site, the products in scope and the linked supply agreement. Programs routinely find agreements covering sites that no longer manufacture for them, and products that moved to another facility years ago without a corresponding revision.

Step 2, Standardize The Responsibility Matrix

Create one template matrix and negotiate variations from it, rather than accepting each CDMO template as the starting point. Consistency across the network lets quality compare obligations between suppliers and spot sites where notification windows are materially weaker.

Step 3, Extract Obligations With Review

Apply the same clause extraction approach used for clinical trial agreements to pull every dated commitment into a register, then have quality confirm each one. Machines are fast at finding clauses containing periods and frequencies. A qualified reviewer decides what the obligation requires and who performs it.

Step 4, Assign Owners And Alerts

Load the register into a system that supports owners, due dates, recurring obligations and escalation. Recurring items such as annual audits and periodic product reviews should generate the next occurrence automatically. Alerts should reach the responsible individual, not a shared quality mailbox nobody owns after a reorganization.

Step 5, Rehearse The Inspection Question

Ask the register to answer the question an inspector will ask. Show the quality agreement in force for this product, the responsibility split it defines, and evidence that each dated commitment was met over two years. If assembling that takes days, the process is not ready.

What GxP and Part 11 expectations mean for the system holding this

The obligations are quality obligations, but the system recording them carries its own requirements. 21 CFR Part 11 governs electronic records and electronic signatures used to satisfy predicate rule requirements. In practice a system in scope needs validation appropriate to its use, secure and role based access control, and audit trails recording who changed what and when without obscuring the original entry. Signature manifestations must identify the signer, the date and the meaning of the signing. If approvals, obligation closures and evidence records live in a platform, that platform is in scope, so ask for validation documentation and an audit trail export. Obligation management built for life sciences should assume these controls rather than add them later.

A clause to obligation mapping you can reuse

The table below shows how recurring sections of a quality agreement translate into tracked records. It is deliberately generic, because the specific windows are negotiated per relationship. What should not vary is the discipline, every clause with a period or a frequency becomes an obligation with an owner, a due date and a place where evidence is filed.

A quality agreement is not a formality sitting behind the supply agreement. It is the operating manual for a manufacturing relationship, and most of it is written as dated commitments. Align it with the commercial agreement on a single review cycle, express the responsibility split as a matrix, not prose, and move every clause containing a clock into a register with an owner, a due date and filed evidence. Do that and inspection readiness becomes a report you run, not a project you launch.

For related guidance, see The quality leader’s guide to CMO quality agreements, The quality leader’s guide to pharma quality agreements and Quality agreement obligations, who tracks what in GxP.

Aavenir Life Sciences & Pharma PracticeAavenir editorial covers contract and obligation management practice for regulated life sciences, pharma and medical device organizations.