Quality management maturity is useful as a buyer's decision lens only when it is converted into traceable audit questions. The practical task is to connect quality governance, investigations, change, transfer and supply decisions to the defined project and then record what is documented, demonstrated, managed or still unresolved.

1. Separate baseline compliance from operating maturity

FDA describes its Quality Management Maturity program as encouraging practices that go beyond current good manufacturing practice requirements, including a quality culture, continual improvement and resilience of supply. That does not create a new universal qualification standard for selecting a partner. It does, however, clarify why a sponsor should distinguish baseline compliance from the ability to manage quality decisions over time.

WHO’s fifty-ninth Expert Committee report brings together technical updates and adopted texts across pharmaceutical quality assurance, including quality-control specifications, good manufacturing and inspection practices, and regulatory frameworks. It is a useful horizon-scanning source when defining audit questions; it is not evidence that any individual site, product or project meets a defined requirement. [5]

For selection purposes, ask two separate questions: What regulatory and quality evidence is relevant to the defined project? and How are quality issues governed when the initial plan changes? The answers should be specific to the legal entity, manufacturing site, dosage form, product route, lifecycle stage and intended market.

2. Use quality metrics as audit questions, not a scorecard

FDA describes quality metrics as objective information used to measure, evaluate and monitor product and process lifecycle performance. Its public quality-metrics material notes that metrics can inform supplier selection and oversight of contract activities and material suppliers. [4] That makes metrics a useful route to better questions, not a public ranking or a conclusion that a CMO/CDMO is suitable for a defined project.

For an initial review, ask what a proposed metric means, which legal entity and site it covers, its period and denominator, who owns the data, how changes and investigations are reflected, and what limitations apply. Do not infer performance, capacity, regulatory status, supply continuity or project fit from a public narrative or a single metric. Those matters require product-, site-, target-market- and responsibility-specific evidence under an appropriate review process.

3. Ask five evidence-based questions

Question 1: How are quality issues escalated and reviewed?

Request a clear non-confidential explanation of the project governance model: quality-unit involvement, decision authorities, escalation path, management-review cadence and how a sponsor is informed. ICH Q10 describes management review and timely escalation as part of a pharmaceutical quality system. For a transfer or scale-up project, the practical issue is whether the right functions can make and document decisions at the right time.

Question 2: What does the investigation and CAPA route look like?

Do not ask only whether a CAPA procedure exists. Ask how deviations, complaints, non-conformances and audit observations move from detection to root-cause assessment, action, effectiveness review and sponsor communication. The evidence level should be proportionate to the project and handled under appropriate confidentiality controls.

Question 3: How is change control connected to the product and the filing?

A transfer frequently exposes differences in equipment, materials, analytical methods, utilities, scale or operating practice. ICH Q10 describes a risk-based change-management system that evaluates proposed changes against current product and process knowledge and, where relevant, the marketing authorisation. A useful due-diligence discussion therefore maps what may change, who evaluates it, what evidence is required, who approves it and how the regulatory impact is assessed.

Question 4: Is technology-transfer governance explicit?

Technology transfer is not only document receipt. It is the controlled movement and use of product and process knowledge. A receiving site should be able to explain the transfer plan, gap-assessment route, analytical-method readiness, issue log, responsibilities, decision gates and how knowledge from scale-up is fed back into the control strategy. If that route is vague, the project label may be concealing an unresolved development or governance gap.

Question 5: How is quality linked to reliable supply?

FDA’s QMM materials connect mature quality practices with resilience and reliable supply. A sponsor should not infer performance, capacity or continuity from that policy objective. Instead, ask concrete project questions: What are the agreed communication routes for quality-impacting events? How are materials, testing, release, storage and change decisions coordinated? What evidence would trigger a hold, escalation or re-planning decision?

4. Put the questions into the right sequence

  1. Public fit screen: legal entity and site, public dosage-form scope, intended market, lifecycle stage and a non-confidential project objective.
  2. Mutual confidentiality and scope: agree what may be exchanged and the purpose of the review before sharing detailed formulae, process parameters, dossiers, patient information or trade secrets.
  3. Project-specific due diligence: assess technical, analytical, quality, regulatory, capacity and commercial fit; a general quality-system discussion cannot replace this step.
  4. Written operating model: translate agreed responsibilities, change routes, communications and records into appropriate project and quality agreements.

Frequently asked questions

Is this checklist an FDA Quality Management Maturity assessment?

No. It is a public buyer decision aid, not an FDA QMM assessment, regulator rating, certification, approval, audit outcome or conclusion about a facility.

What evidence should a pharmaceutical CMO audit examine?

Examine source evidence for governance and escalation, investigations and CAPA, change control, technology transfer and quality-linked supply reliability, then confirm legal entity, site, product fit, data traceability and written responsibilities.

Does quality management maturity mean a CMO/CDMO is certified or approved?

No. It is a decision framework, not a certification, approval, inspection result or conclusion about a facility.

What can be shared before an NDA?

A first contact should normally be limited to non-confidential facts such as dosage form, presentation, project stage, target market, requested model, intended timing and the decision to be made. Use controlled disclosure after a mutual NDA and review plan are in place.

Can a quality agreement replace a CMO/CDMO audit?

No. A quality agreement documents responsibilities and communication routes; it does not replace assessment of the site, product, process, analytics, quality system and target-market fit.

Why is management review relevant to technology transfer?

Transfer creates cross-functional decisions and changes. Clear escalation, management review and change governance help determine how issues are assessed, documented and resolved through transfer and scale-up.

Can public quality metrics prove that a CMO/CDMO is suitable for my project?

No. FDA describes quality metrics as objective information that can inform supplier selection and oversight, but a public metric, policy page or narrative does not establish project fit. Definitions, period, scope, data governance, limitations, legal entity, site, product, target market and the project-specific evidence still need controlled review.

Authoritative sources

  1. U.S. FDA — CDER Quality Management Maturity
  2. U.S. FDA — Contract Manufacturing Arrangements for Drugs: Quality Agreements
  3. ICH Q10 — Pharmaceutical Quality System
  4. U.S. FDA — Quality Metrics for Drug Manufacturing
  5. WHO — Expert Committee on Specifications for Pharmaceutical Preparations: fifty-ninth report (TRS 1067, 2026)

This article is an industry perspective for general business discussion. It is not legal, regulatory or medical advice, an audit conclusion or a statement about any facility. Project requirements must be confirmed with the responsible parties and applicable authorities.