Every medicine that reaches a patient carries a promise: it is safe, it works, and it was made exactly as intended. Quality assurance is the function that stands behind that promise. In pharma, QA gives patients, regulators, and the business confidence that every batch meets its specification, and that the systems used to make it are designed, controlled, and documented to deliver the same result every time.

This guide sets out what quality assurance in pharma covers, how it differs from quality control, and the core functions a pharmaceutical QA team owns. It also looks at the pressures reshaping QA today, and why knowing what has changed in the regulations is now as important as following them.

What is quality assurance in pharma?

Quality assurance in pharma is the planned, systematic set of activities that ensures medicines are consistently developed, manufactured, tested, stored, and distributed to the quality required for their intended use. QA is the oversight layer of the pharmaceutical quality system. It does not make or test the product itself. It makes sure the processes that do are fit for purpose, followed in practice, and properly documented.

QA spans the full product lifecycle and the GxP disciplines that govern it: good manufacturing practice (GMP), good clinical practice (GCP), good laboratory practice (GLP), and good distribution practice (GDP). For most QA teams, GMP is the standard they work against most often. Our guide to what GMP is in pharma and why it matters covers it in more detail.

Why does quality assurance matter? Three reasons stand out:

  • Patient safety. Contaminated, sub-potent, or mislabeled products can cause direct harm. QA controls are designed to prevent those failures before a batch is ever released.
  • Regulatory standing. Manufacturing licenses, marketing authorizations, and the right to supply depend on demonstrable compliance. Weak quality systems lead to inspection findings, FDA Form 483 observations, warning letters, import alerts, and, in the EU and UK, statements of GMP non-compliance.
  • Commercial impact. Recalls, rejected batches, supply interruptions, and delayed approvals all carry significant cost. A robust quality system protects revenue, reputation, and the trust of partners and customers.

QA does not operate against a single rulebook. Several overlapping frameworks shape what a compliant quality system looks like:

  • ICH guidelines. The International Council for Harmonisation sets globally harmonized expectations adopted by regulators in its member regions. For QA, the most important are ICH Q10 (pharmaceutical quality system), ICH Q9(R1) (quality risk management), ICH Q7 (GMP for active pharmaceutical ingredients), and ICH E6(R3) for clinical trials.
  • eCFR (US). Title 21 of the Electronic Code of Federal Regulations contains the FDA’s binding requirements, including Parts 210 and 211 (current GMP for finished pharmaceuticals), Part 11 (electronic records and electronic signatures), and Parts 600 to 680 for biologics.
  • EudraLex (EU). Volume 4 of EudraLex holds the EU GMP guidelines: Part I for medicinal products, Part II for active substances, and a set of annexes covering topics such as sterile manufacturing (Annex 1), computerized systems (Annex 11), and certification by a Qualified Person and batch release (Annex 16).
  • MHRA (UK). The Medicines and Healthcare products Regulatory Agency licenses and inspects UK manufacturers. UK GMP and GDP requirements and guidance are brought together in its “Orange Guide”, underpinned by the Human Medicines Regulations 2012.
  • PIC/S. The Pharmaceutical Inspection Co-operation Scheme brings together more than 50 regulatory inspectorates, including the FDA and MHRA. Its GMP guide is closely aligned with EU GMP and helps harmonize inspection standards across member authorities.

The difference between QA vs QC in pharma

Quality assurance and quality control are often used interchangeably, but they do different jobs. Both sit within the quality unit and depend on each other.

  • QA is process-oriented and preventive. It builds and maintains the systems that stop defects from happening: procedures, training, change control, validation, supplier oversight, and batch release. The question QA asks is: ‘Are we set up to get this right every time?’
  • QC is product-oriented and detective. It samples and tests raw materials, intermediates, finished products, and the manufacturing environment against approved specifications. The question QC asks is: ‘Did this batch meet its specification?’
Quality assurance (QA) Quality control (QC)
Focus Processes and systems Products and materials
Approach Preventive Detective
Timing Across the full lifecycle, before, during and after manufacture At defined points: incoming materials, in-process, and finished product
Typical activities SOPs, change control, deviations and CAPA, audits, supplier qualification, batch record review and release Analytical testing, sampling, stability studies, environmental monitoring, method validation
Key output Evidence that the quality system is working Data showing whether a product meets specification

 

The two are complementary. QC generates the data. QA makes sure that data is generated, reviewed, and acted on within a controlled system. An out-of-specification QC result, for example, triggers QA processes such as a deviation investigation and corrective and preventive action.

The core functions of a pharmaceutical QA team

The scope of QA varies with company size, modality and operating model. A virtual biotech that outsources all manufacturing will run QA very differently from a large multi-site manufacturer. Most QA teams, however, own or oversee the nine functions below. Together, they form the quality system that inspectors evaluate.

Document control and SOPs

Controlled documents are the operating instructions of a GxP organization. They include standard operating procedures (SOPs), work instructions, specifications, master batch records, validation protocols, and forms. QA manages their lifecycle: drafting, review, approval, issue, periodic review, and retirement. The aim is simple: only the current approved version is in use, and superseded versions are withdrawn from use but retained.

The records those documents generate must meet data integrity expectations, usually summarized as ALCOA+. Data should be attributable, legible, contemporaneous, original, and accurate, as well as complete, consistent, enduring and available. These principles apply equally to paper and electronic records, and data integrity remains one of the most frequently cited areas at inspection. Our article on GxP audit and inspection readiness explains how inspectors test them in practice.

Expectations are rising. In July 2025, the European Commission published draft revisions of EU GMP Chapter 4 (documentation) and Annex 11 (computerized systems), together with a new Annex 22 on artificial intelligence. The drafts place greater emphasis on data governance, audit trails, electronic signatures, and system security.

Change control

Change is constant in pharmaceutical operations: new equipment, alternative suppliers, process improvements, revised specifications, system upgrades, and updated SOPs. Change control makes sure no change is implemented until its impact on product quality and regulatory compliance has been assessed and approved.

A typical change control process includes a documented proposal, an impact assessment covering product quality, validation status, stability, and regulatory filings, a risk assessment, approval by QA and relevant subject matter experts, controlled implementation, and a post-implementation effectiveness check.

The regulatory dimension is easy to underestimate. Some changes require a variation in the EU and UK, or a post-approval supplement in the US, before they can be implemented. Missing that step can mean supplying product that no longer matches the approved dossier.

Deviations and CAPA

A deviation is any departure from an approved procedure, instruction, or specification. QA makes sure deviations are recorded promptly, classified by risk (typically minor, major, or critical), and investigated in proportion to that risk.

Investigations should identify the true root cause, using structured techniques such as the 5 whys, fishbone (Ishikawa) diagrams, or fault tree analysis. Attributing a deviation to “human error” without asking why the error was possible is a common weakness that inspectors look for.

Corrective and preventive action (CAPA) closes the loop. Corrective actions address the problem that occurred. Preventive actions stop it from recurring, or from happening elsewhere. Every CAPA should have an owner, a due date, and an effectiveness check, because inspectors increasingly ask for evidence that a CAPA worked, not just that it was closed.

Audits and self-inspections

Audits give QA an independent view of whether the quality system works in practice. Internal audits, or self-inspections, review compliance across all GxP areas on a risk-based schedule. Supplier audits assess the vendors, contract manufacturers, and laboratories the business depends on.

QA also leads preparation for regulatory inspections. These include pre-approval, routine surveillance, and for-cause inspections by the FDA, inspections carried out by the national competent authorities of EU member states (coordinated by the EMA for centrally authorized products), and inspections by the MHRA in the UK.

The timing of inspections is becoming less predictable. In May 2025, the FDA announced the expanded use of unannounced inspections at foreign manufacturing facilities. For QA teams, inspection readiness is a continuous state, not a project that starts when an inspection is scheduled.

Supplier and CDMO qualification

Outsourcing an activity does not outsource the responsibility for it. The manufacturer or marketing authorization holder remains accountable for the quality of materials and services provided by third parties, from raw material suppliers to contract development and manufacturing organizations (CDMOs) and contract testing labs.

Supplier qualification is risk-based. It typically includes an initial assessment or questionnaire, an on-site or remote audit for critical suppliers, formal approval, and ongoing monitoring of performance through deviations, complaints, change notifications, and periodic re-audits.

Quality agreements define who is responsible for what: batch release, deviation handling, change notification, testing, data access, record retention, and audit rights. A clear agreement prevents gaps in accountability that can surface at inspection. Monitoring the regulatory status of key suppliers matters too. A warning letter or import alert issued to a CDMO is an early signal that your own supply and compliance position may be at risk.

Batch record review and release

Before a batch can be released, QA reviews the executed batch record to confirm it was made according to the approved process. The review checks that every step and entry is complete and correct, in-process results are within limits, any deviations have been investigated and assessed, QC results meet specification, and labeling and materials reconcile.

In the EU and UK, a Qualified Person must certify each batch before release, as set out in EU GMP Annex 16. In the US, 21 CFR 211.22 gives the quality control unit responsibility for approving or rejecting drug products. Electronic batch records allow review by exception, focusing QA attention on the entries and events that need it, but only when the underlying system is validated and its audit trails are reviewed.

Training and quality culture

People make quality systems work. QA ensures staff receive GMP training at induction and on an ongoing basis, and are trained on the current version of every SOP relevant to their role. Training records need to show competency, not just attendance.

Quality culture goes further than training. ICH Q10 places responsibility for the pharmaceutical quality system with senior management. Leaders set priorities, allocate resources, and decide whether people feel able to raise a deviation or concern without blame. Inspectors interview staff at every level, and how people talk about quality reveals a great deal about whether the system works day to day.

Quality risk management

ICH Q9(R1), revised in 2023, sets out the principles for risk-based decision-making across the quality system. The revision clarified that the formality of a risk assessment should be proportionate to the level of risk, addressed subjectivity in risk scoring, and highlighted the link between quality risk management and product availability.

In practice, quality risk management shapes many of the functions above: how deviations are classified, which suppliers are audited and how often, how much validation a change requires, and where internal audits focus. Common tools include failure mode and effects analysis (FMEA), hazard analysis and critical control points (HACCP), and risk ranking and filtering. The goal is to focus effort where the risk to patients and product quality is highest.

Regulatory surveillance and impact assessment

Most descriptions of QA stop at the internal quality system. Yet the requirements that system is built to meet keep moving. Regulatory surveillance is the structured monitoring of new and revised guidance, regulations, health authority updates, and inspection findings, such as Form 483 observations, warning letters, and non-compliance reports, across every market where the business operates.

Surveillance alone is not enough. Each relevant change needs an impact assessment: what does this mean for our SOPs, specifications, validation, training, and regulatory filings? Who needs to provide input? What will we change, by when, and who owns it? The outcome should be documented and traceable, because inspectors can ask how a site became aware of revised guidance and what it did in response.

This is where many quality systems are weakest, and where a structured approach makes the clearest difference. Infodesk supports QA and GxP teams with exactly this process, from surveillance through to documented action.

The challenges QA teams are facing

The core functions of QA have not changed much in principle. The environment around them has. These are the pressures QA, GxP and compliance teams describe most often:

  • Volume and pace of regulatory change. The FDA, EMA, MHRA, and other health authorities publish new guidance, Q&As, consultations and revisions continuously. The EU’s coordinated drafts of Chapter 4, Annex 11, and the new Annex 22 show how a single initiative can touch documentation, computerized systems, and data integrity at once. Multiply that across every market a company supplies, and keeping pace becomes a significant workload in its own right.
  • US and EU divergence. Where FDA and EU expectations differ, QA teams must maintain processes that satisfy both, and recognize when one authority moves while the other does not. Our analysis of where US and EU pharma regulations are diverging in 2026 explores the areas to watch.
  • Inspection pressure and shifting enforcement focus. Data integrity remains a recurring theme in inspection findings, and oversight of CDMOs and suppliers is under closer scrutiny. The FDA’s expanded use of unannounced foreign inspections reinforces the need to be ready at any time, at every site in the network, including those run by partners.
  • Manual tracking in spreadsheets and email. Many teams still manage surveillance and impact assessments through spreadsheets, shared drives and email threads. Decisions are hard to trace, ownership is unclear, and impact assessments are difficult to evidence during an inspection. Our guide to mastering regulatory impact assessment covers how to build a more defensible process.
  • Dispersed expertise. Impact assessments often depend on input from several subject matter experts across manufacturing, quality control, regulatory affairs, and IT. Without a consistent way to request, capture, and reconcile that input, assessments slow down and outcomes become inconsistent.
  • Digital transformation and AI. New systems and AI tools can reduce manual effort, but they bring their own validation and data integrity obligations. The draft EU Annex 22 points toward continuous oversight of AI models, including procedures for human review. QA has to assure the tools as well as the processes they support.

How regulatory intelligence supports quality assurance

QA can only assure compliance against requirements it knows about. If a revised guideline is missed, or noticed late, every downstream control built on the old requirement is out of date, however well it is executed. That is why structured regulatory surveillance and inspection intelligence are an important part of the quality system, not an optional extra.

Regulatory intelligence is the process of collecting, curating, validating, and interpreting regulatory and enforcement information so that it can drive decisions. For QA teams, it contributes in four ways:

  • Earlier awareness. Relevant new and revised guidance is identified quickly and routed to the right people, filtered by product, market, and site.
  • Inspection and enforcement insight. Form 483 observations, warning letters and inspection reports across the industry show what inspectors are citing now. QA teams can benchmark their own systems against those trends before an inspection, not after it.
  • Structured impact assessment. Each change is assessed with clear ownership, consistent subject matter expert input and a documented outcome, rather than a chain of emails.
  • A traceable record. When an inspector asks how you became aware of a change and what you did about it, the answer is evidence, not recollection.

Technology can make surveillance faster and more complete, but judgment about what a change means for a specific product, process or site stays with qualified people. The most effective approach treats regulatory surveillance as a controlled process within the quality system, with a defined scope, owners, procedures, and records, in the same way as change control or CAPA.

Build an end-to-end inspection-ready quality intelligence system with Infodesk

Infodesk helps QA and GxP teams turn regulatory updates into documented, auditable action, so nothing is missed and every decision can be evidenced at inspection.

Curated, validated regulatory intelligence is delivered directly into your workflows. Impact assessments are structured with clear ownership and consistent expert input. Inspection and enforcement intelligence brings inspection records and enforcement actions from seven health authorities into one place. The result is a complete, traceable record of what you knew, how you assessed it, and what you did. Find out more about how Infodesk supports quality assurance and GxP teams.

Infodesk’s regulatory intelligence platform

Infodesk’s regulatory intelligence platform is the surveillance layer that keeps QA and regulatory teams ahead of evolving documentation and data integrity guidance from the FDA, EMA, MHRA, PIC/S, and WHO.

Infodesk’s Workflow solution

Curated, validated intelligence is delivered directly into your workflows, so impact assessments can be easily managed and SOPs and training stay current.

Infodesk’s Inspection & Enforcement Intelligence solution

Infodesk’s Inspection & Enforcement Intelligence solution gives you a database of the inspector’s history, your site’s full record, and the findings escalating right now. Inspection and Enforcement Intelligence (I&E Intelligence) pulls every inspection record and enforcement action into one place across seven health authorities, then turns it into the profiles, briefs, and reports your team needs to prepare. This way inspection findings from elsewhere in the industry become early-warning signals rather than surprises and you can always be inspection-ready.

Infodesk gives you the clarity, confidence and proof to act, when action matters most. Ready to move from intelligence to action? Book a meeting with the Infodesk team.