In the pharmaceutical industry, when stability testing is outsourced to Contract Research Organizations (CROs) or external labs, the sponsor retains full responsibility for regulatory compliance. A well-crafted Quality Agreement is not only a best practice—it’s a requirement under FDA, EMA, and ICH Q10 expectations. This tutorial explains how to structure an effective Quality Agreement that ensures GMP compliance and defines clear roles between the sponsor and testing partner.

📜 What is a Quality Agreement?

A Quality Agreement is a legally binding document that defines the responsibilities, procedures, and expectations between two parties—typically the marketing authorization holder (sponsor) and the contract testing lab (CRO). It is not the same as a commercial contract and must focus solely on quality systems and compliance.

According to FDA guidance (Nov 2016) and EU GMP Part I Chapter 7, sponsors must ensure that these agreements are in place for all outsourced GMP activities, including stability testing.

📝 Core Components of a Quality Agreement

Every Quality Agreement for outsourced stability work should cover the following key sections:

• ✅ Scope of Work: Define what testing or storage is covered
• ✅ Roles and Responsibilities: Detailed split between sponsor and CRO QA units
• ✅ Document Control: SOP sharing, version management, and approval requirements
• ✅ Deviation Management: Reporting timelines, investigation responsibilities, and CAPA
• ✅ Change Control: What requires notification or prior approval
• ✅ Audit Rights: Sponsor’s right to audit, frequency, and scope
• ✅ Record Retention and Data Access: How long data is stored and who owns it
• ✅ Communication and Escalation: Contact points and urgent notification paths

📃 Scope of Stability Testing and Storage

This section should clearly define the nature of testing to be performed:

• ✅ Real-time and accelerated studies
• ✅ Photostability, humidity-controlled, and refrigerated conditions
• ✅ Sample pull schedules and notification expectations
• ✅ Reference to stability protocols and product-specific test methods

It should also include a list of products or study codes, if possible, as annexures for clarity and traceability.

📝 Defining QA Roles and Responsibilities

This is the heart of the agreement. Clearly assign:

• ✅ Who approves protocols and methods
• ✅ Who handles sample receipt, storage, and tracking
• ✅ Who signs off on raw data, test reports, and trend charts
• ✅ Who conducts deviation investigations and implements CAPA
• ✅ Who retains and archives the data, and for how long

Use RACI charts (Responsible, Accountable, Consulted, Informed) if necessary for clarity.

⚙️ Change Control and Deviation Management

Include specific clauses that outline:

• ✅ What type of changes (methods, equipment, storage conditions) require sponsor review
• ✅ Notification timelines (e.g., 10 days before implementation)
• ✅ Handling of planned vs. unplanned deviations
• ✅ Root cause analysis and CAPA workflows for deviations affecting data

Ensure language matches the sponsor’s internal deviation SOPs for consistency.

💻 Documentation, Record Retention, and Data Ownership

This section of the Quality Agreement must define:

• ✅ Raw data retention period (typically 5–10 years based on market requirements)
• ✅ Formats for sharing raw data and summary reports (electronic and/or paper)
• ✅ Access rights to LIMS systems, chamber logs, and trending databases
• ✅ Ownership of the data—generally belongs to the sponsor by default

Also address requirements for data backup, disaster recovery plans, and compliance with 21 CFR Part 11 or EU Annex 11 where applicable.

🛠 Audit Rights and Regulatory Readiness

To ensure oversight, the agreement should guarantee:

• ✅ Sponsor’s right to perform scheduled and for-cause audits
• ✅ Cooperation in regulatory inspections (FDA, EMA, CDSCO, etc.)
• ✅ Immediate notification of regulatory audits or findings related to sponsor projects
• ✅ Access to audit trails and QA review logs during inspections

It’s also wise to define mutual expectations for audit report timelines and CAPA implementation by the vendor.

📞 Communication, Contacts, and Escalation

To avoid delays or miscommunication, include:

• ✅ Designated QA points of contact at both organizations
• ✅ Email, phone, and escalation contacts for urgent issues (e.g., chamber excursions)
• ✅ Agreed response timeframes (e.g., 24 hours for critical issues, 5 days for non-critical)
• ✅ Regular review meetings or teleconferences for active projects

These provisions streamline issue resolution and maintain project continuity.

📑 Annexes and Supporting Documents

A robust Quality Agreement may include annexes such as:

• ✅ Product-wise scope table or test matrix
• ✅ Reference SOPs with version numbers
• ✅ Contact list for functional teams
• ✅ Stability protocol templates or linked documents

This allows the agreement to remain concise while keeping supporting material available for future reference.

🏆 Conclusion: A Living Document for Long-Term Partnership

The Quality Agreement is not a one-time formality—it is a living document that should evolve with the relationship between the sponsor and the contract lab. As regulations change, new stability protocols are added, or audit findings surface, the agreement must be updated accordingly.

Creating a clear, enforceable, and collaborative Quality Agreement ensures data integrity, reduces audit risks, and enhances the transparency between both parties. In the eyes of regulators, it’s a reflection of your quality culture and commitment to GMP compliance.

Download editable Quality Agreement templates and sponsor-CRO role mapping tools at StabilityStudies.in and PharmaGMP.in.