Drug Quality Agreement: Meaning and Responsibilities
A quality agreement defines how a drug manufacturer and its contract facility divide quality-related work, exchange evidence and make decisions. It does not transfer either party’s CGMP obligations.

On this page · 8 sections
- 1What a quality agreement means
- 2Law, FDA guidance and site practice are different
- 3What the agreement should cover
- 4A fictional responsibility matrix and exercise
- 5Operational approval, owner disposition and shipment
- 6Changes and investigations need defined handoffs
- 7Records, complaints and returns remain part of the interface
- 8Use the definition without turning it into a universal template
How does Quality Agreement apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What a quality agreement means
FDA’s November 2016 guidance defines the term directly: “A quality agreement is a comprehensive written agreement between parties involved in the contract manufacturing of drugs that defines and establishes each party’s manufacturing activities in terms of how each will comply with CGMP.” CGMP means current good manufacturing practice.
In practical terms, the agreement describes the quality interface between an owner and a contract facility, such as a manufacturer, packager or analytical laboratory. It explains who performs the work, who reviews its evidence, who makes each decision and how information crosses the organizational boundary. It is not a substitute for the procedures used to perform that work.
FDA explains the allocation this way: “In general, the quality agreement should clearly state which party — the owner or the contract facility or both — carries out specific CGMP activities.” The phrase “or both” matters: allocating a task to one party does not necessarily eliminate the other party’s review or oversight role.
People may informally call this a “pharmaceutical quality agreement” or “technical agreement.” Those labels do not establish its scope; the actual activities, products, sites and responsibilities need to be stated.
02Law, FDA guidance and site practice are different
Law: 21 CFR 211.22(a) states, “The quality control unit shall be responsible for approving or rejecting drug products manufactured, processed, packed, or held under contract by another company.” Section 211.22(d) also requires written quality control unit responsibilities and procedures that are followed. These are regulatory requirements, not optional recommendations.
The regulatory context also recognizes outsourcing explicitly. Under §200.10(b), FDA regards extramural contract facilities as an extension of the manufacturer’s own facility. Outsourcing therefore should not be treated as moving the activity outside the manufacturer’s quality oversight.
FDA guidance: the November 2016 document recommends written quality agreements, but its recommendations are nonbinding. It states, “It does not establish any rights for any person and is not binding on FDA or the public.” Distinguish that recommendation from the underlying CGMP requirements it discusses.
Site practice: contact lists, escalation routes and agreed notification targets make the arrangement usable. Their specific design is not a universal FDA timetable. The Part 211 examples here concern finished drug products, not every product category addressed by the guidance.
03What the agreement should cover
FDA’s nonbinding guidance describes purpose and scope, definitions, resolution of disagreements, manufacturing activities, and the agreement’s life cycle and revisions. It also recommends clear communication expectations, named contacts and identification of who has final approval for particular activities.
- Scope and locations: identify the products or services, manufacturing operations and sites included.
- Manufacturing responsibilities: address quality unit activities, facilities and equipment, materials management, laboratory controls and documentation relevant to the contracted work.
- Exceptions and changes: explain deviation reporting, investigation responsibilities, change notification and approval arrangements.
- Oversight and communication: address audits, inspections, communication of findings and resolution of disagreements.
- Document life cycle: explain how the agreement and referenced documents are reviewed and revised.
As a drafting practice, make each allocation answer a real handoff question. “Contractor handles testing” leaves unresolved who receives an initial failing result, who investigates it and what evidence the owner reviews. Naming those separate actions is more useful than assigning a broad heading such as “quality.”
FDA recommends keeping the quality agreement separate from, or at least severable from, commercial contracts. Its guidance says general business terms such as pricing, delivery terms and limits on liability should not be included. Quality responsibilities for storage and transport are different from commercial delivery terms.
04A fictional responsibility matrix and exercise
The following small matrix is fictional site practice for an owner outsourcing finished-drug bottling. It illustrates separate decisions, not a complete agreement or a regulatory template. Each party’s applicable CGMP obligations remain in place.
| Activity | Contract facility | Owner | Evidence exchanged |
|---|---|---|---|
| Batch documentation and discrepancy investigation | Prepares records and leads the site investigation | Reviews product impact and requests further evidence | Batch record and investigation |
| Contractor operational approval | Quality unit approves or rejects its output | Receives the decision and supporting records | Contractor approval or rejection |
| Owner disposition | Provides agreed supporting evidence | Quality unit approves or rejects the batch for final release | Recorded owner decision |
| Shipment for distribution | Checks authorization before dispatch | Communicates approved status and authorization | Status check and dispatch record |
Exercise: 12,000 bottles enter reconciliation. Of these, 11,820 remain on hold, 120 are recorded rejects and 60 are assigned to sampling. These categories do not overlap. The unexplained quantity is 12,000 − 11,820 − 120 − 60 = 0 bottles.
That arithmetic reconciles the quantity; it does not establish product acceptability. Ask both parties who investigates the reason for the rejects, which records support the investigation and who decides the held stock’s disposition. A zero quantity difference cannot replace that assessment or authorize shipment.
05Operational approval, owner disposition and shipment
FDA’s guidance distinguishes the contractor’s approval or rejection of the product or results of its operations from the owner’s approval or rejection of the drug, including final release. A contractor’s completed work package is therefore not automatically the owner’s final disposition decision.
For finished-drug distribution, §211.165 establishes laboratory testing and specification-conformance requirements. Section 211.192 requires quality control unit review and approval of production and control records before a batch is released or distributed. A passing certificate of analysis does not replace that record review.
- Work and evidenceManufacturing, testing and investigation records describe what happened.
- Batch identity and status
- Contractor Operational DecisionThe contractor’s quality unit approves or rejects its operational output.
- Decision and supporting evidence
- Owner DispositionThe owner’s quality unit makes its approval or rejection decision for final release.
- Recorded disposition
- Authorized ShipmentDistribution follows the agreed status checks and shipping controls.
- Dispatch authorization and record
As site practice, define “release” wherever it appears: release of test results, approval of a manufacturing stage and release for distribution are not interchangeable. Distinguish a controlled transfer for further processing from shipment of finished product for distribution.
06Changes and investigations need defined handoffs
Law: §211.100 requires production and process-control procedures, including changes, to receive the specified organizational and quality control unit review and approval. It also requires execution to be documented at the time of performance and deviations from written procedures to be recorded and justified.
FDA guidance recommends explaining how changes are managed between the parties. It recognizes that some changes need owner review and approval before implementation, while others may be implemented without notifying the owner. The agreement should distinguish those categories rather than treating every change identically.
For investigations, §211.192 requires thorough investigation of unexplained discrepancies and failures to meet specifications, whether or not the batch has been distributed. The investigation must extend to other potentially associated batches and products, with written conclusions and followup.
In practice, define the notification trigger, recipient, supporting information and escalation route for a deviation or out-of-specification result. Separate initial notification from the completed investigation report. Agree response targets appropriate to the situation; do not present a convenient number of hours or days as a universal regulatory deadline.
07Records, complaints and returns remain part of the interface
FDA guidance recommends defining document review and approval, responsibility for original records or true copies, and availability for inspection. As site practice, specify which records the owner receives routinely and how it can obtain underlying data when a summary raises questions. Also address access after the commercial relationship ends.
Law: §211.180(a) generally requires batch-specific production, control and distribution records to be retained for at least one year after batch expiry. For the specified expiration-dating-exempt OTC products, the period is three years after distribution. This is not a single retention rule for every document: identify the applicable record category rather than assigning one blanket period.
Under §211.198, written procedures must cover written and oral drug-product complaints. Possible specification failures require quality control unit review and a determination about investigation. When an investigation under §211.192 is not conducted, the complaint record must include the reason and the responsible person’s name. The agreement can define how complaints received by either party reach that process.
Section 211.204 states, “Returned drug products shall be identified as such and held.” The practical interface should identify who receives returns, assesses their condition, investigates and records disposition. A commercial return authorization is not a quality decision permitting reuse.
08Use the definition without turning it into a universal template
A useful first check is to walk one actual handoff through the agreement: can both parties identify the decision-maker, required evidence and route for unresolved questions? Review the agreement when scope, sites, methods or responsibilities change, and choose a justified periodic review approach. There is no universal review or audit cycle proposed here.
Medical devices, dietary supplements, food and positron emission tomography (PET) drugs have their own applicable rules. Do not assume this drug quality agreement framework applies unchanged. FDA’s 2016 guidance expressly excludes medical devices and dietary supplements; this definition does not interpret those sectors’ requirements.
For the full operational treatment of contractor oversight and quality-system evaluation, continue to the CMO/CDMO quality systems buyer’s guide. This definition explains the document’s purpose and boundaries rather than duplicating that broader guide.
Frequently asked questions
Q.Is a quality agreement itself required by FDA regulation?+
The November 2016 FDA guidance recommends a written quality agreement; that recommendation is nonbinding. Underlying CGMP obligations remain binding. For example, §211.22(d) requires written quality control unit responsibilities and procedures, and requires those procedures to be followed.
Q.Does this framework include a contract testing laboratory?+
Yes. FDA’s guidance includes analytical testing and other laboratory activities. It recommends defining result communication, investigation responsibilities and laboratory controls. The agreement should not reduce the relationship to receipt of a pass/fail certificate.
Q.Can the contractor make the owner’s final release decision?+
Contractor operational approval is distinct from owner disposition. FDA describes contractors as approving or rejecting their operational output and owners as approving or rejecting the drug, including final release. A contractual allocation does not remove applicable CGMP responsibilities.
Q.How is it different from a supply agreement?+
The quality agreement addresses CGMP-related activities and responsibilities. A supply agreement addresses the commercial relationship. FDA recommends separate or severable documents and keeping general business terms, such as pricing and liability limits, out of the quality agreement.
Q.How often should the agreement be reviewed?+
Choose and document a review approach suited to the arrangement, with revision triggers for relevant changes. Do not copy an assumed annual or two-to-three-year cycle as a universal requirement. Check whether the responsibilities and contacts still match the actual work.
Q.Is a technical agreement the same thing?+
“Technical agreement” is sometimes used informally for a quality agreement, as is “pharmaceutical quality agreement.” Check the document’s content: the title alone does not show that it covers the necessary activities, evidence exchanges and decisions.
Primary sources
- FDA — Contract Manufacturing Arrangements for Drugs: Quality Agreements, November 2016
- eCFR — 21 CFR 200.10: Contract facilities
- eCFR — 21 CFR 211.22: Responsibilities of quality control unit
- eCFR — 21 CFR 211.100: Written procedures; deviations
- eCFR — 21 CFR 211.165: Testing and release for distribution
- eCFR — 21 CFR 211.180: General record requirements
- eCFR — 21 CFR 211.192: Production record review
- eCFR — 21 CFR 211.198: Complaint files
- eCFR — 21 CFR 211.204: Returned drug products
Further reading
- CMO/CDMO Quality Systems Buyer’s GuideContinue from the definition to operational contractor oversight and quality-system evaluation.
- Disposition and Distribution WalkthroughFollow how the quality disposition decision stays distinct from operational completion and physical dispatch in the GMP batch-record and release guide.
Want to see how Quality Agreement could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
