Quality by Design (QbD) in Pharma

What is Quality by Design (QbD) in pharma?

Quality by Design is a systematic, science- and risk-based approach to pharmaceutical development defined in ICH Q8(R2). It builds quality into a product from the earliest development stages — through a Quality Target Product Profile, Critical Quality Attributes, and a scientifically justified design space — rather than relying on end-stage testing to catch problems after the fact.

Most QbD programs produce a risk assessment, a fishbone diagram, and the same fixed process ranges a traditional approach would have produced anyway. That's not Quality by Design — it's paperwork wearing its name.

The QbD Framework: QTPP to Control Strategy

ICH Q8(R2) defines QbD as a chain of four linked elements, each building on the one before it. Skip a step, or treat it as a formality, and everything downstream is weaker for it.

Element	What It Establishes
Quality Target Product Profile (QTPP)	The prospective summary of the product's intended quality characteristics — the target everything else is designed against
Critical Quality Attributes (CQAs)	Physical, chemical, or biological properties that must stay within an appropriate range to meet the QTPP
Critical Process Parameters & Material Attributes	The process and material variables shown, through risk assessment and experimentation, to affect the CQAs
Design Space	The multidimensional combination of those variables demonstrated to assure quality — the deliverable that unlocks regulatory flexibility
Control Strategy	The planned set of controls, derived from product and process understanding, that ensures ongoing performance within the design space

The Core Principles of Quality by Design

Some QbD explainers substitute a memorable five-step mnemonic for the actual regulatory framework. It's worth being precise here, because the substitution is where a lot of implementations quietly go wrong. The principles below come directly from ICH Q8(R2), Q9, and Q10 — not a paraphrase of them.

Build quality in through design, not through testing it in afterward. Quality is a property of the process and formulation, established before manufacturing begins — not a filter applied to finished product.
Define the QTPP before any process decision is made. Every downstream choice — CQAs, CPPs, design space boundaries — is only defensible if it traces back to a documented target profile.
Quality risk management (ICH Q9) is the connective framework, not a separate exercise — it's what links the QTPP, CQAs, CMAs, CPPs, and control strategy into one coherent chain rather than five disconnected documents.
Process understanding comes from systematic experimentation — Design of Experiments across multiple variables simultaneously — not from assumption, prior product experience, or a handful of confirmatory runs.
Control strategy is proportional to risk and maintained as a continuous lifecycle activity (ICH Q10), not fixed at approval and revisited only when something goes wrong.

QbD is frequently paired with Process Analytical Technology (PAT) — in-line, on-line, or at-line measurement tools that monitor critical attributes during manufacturing rather than only at the end. PAT is what makes real-time release testing possible: instead of testing the finished batch, the process itself generates continuous evidence that it's operating inside the validated design space. Without PAT, a design space still works — it just relies more heavily on periodic sampling to confirm the process stayed within bounds.

The Real Payoff: Design Space, Not Just "Better Quality"

QbD is often sold on "deeper process understanding" and "better quality," which undersells the actual commercial incentive. Under ICH Q8(R2), movement within an approved design space is not treated as a post-approval regulatory change. A manufacturer can adjust compression force, blend time, or another parameter within the established boundaries without filing a supplement — something a traditionally validated process cannot do, since any shift outside its registered ranges triggers the standard change process. That regulatory flexibility, not an abstract quality improvement, is what justifies the extra development investment.

Design space vs. Proven Acceptable Range — the distinction most teams miss: A Proven Acceptable Range (PAR) tests one parameter at a time and holds everything else constant. A genuine design space captures interactions between parameters, established through Design of Experiments, not sequential single-variable studies. Many companies build a set of PARs, label it a design space in the submission, and never realize they haven't actually earned the regulatory flexibility they're claiming.

Where QbD Programs Fail: "Checkbox QbD"

The most common failure isn't skipping QbD — it's doing the visible parts without the substance underneath. A team runs a risk assessment, builds a fishbone diagram, writes a QTPP document, and still submits fixed, narrow operating ranges because the DoE work needed to characterize parameter interactions was never actually done. The submission reads like QbD. The underlying data supports a traditional filing. The company pays for the extra documentation effort and never collects the regulatory flexibility it was meant to buy.

QbD vs. Traditional Development

Aspect	Traditional Approach	QbD Approach
Process parameters	Fixed ranges from a handful of validation batches	Multidimensional design space from systematic DoE
Quality assurance	Relies heavily on end-product testing	Built in through process understanding and control strategy
Post-approval changes	Require a regulatory supplement outside registered ranges	Permitted within design space without resubmission
Development investment	Lower upfront, higher lifecycle regulatory burden	Higher upfront, lower lifecycle regulatory burden

How GoVal Supports a QbD-Based Control Strategy

Earning design space flexibility doesn't remove documentation obligations — it shifts them. Every parameter change still needs to be assessed against the approved design space and shown to stay within its boundaries, and that assessment has to be as defensible at inspection as a regulatory filing would be. GoVal ties risk assessments, critical parameter documentation, and change control directly to each product's defined design space and control strategy, so a proposed process change generates the same audit-trailed evidence a QTPP-to-control-strategy chain requires, without a spreadsheet reconstruction the day an inspector asks for it.

Frequently Asked Questions

What is Quality by Design (QbD) in pharma? +

Quality by Design is a systematic, science- and risk-based approach to pharmaceutical development defined in ICH Q8(R2), which builds quality into a product from the earliest development stages rather than testing it in at the end. It centers on a Quality Target Product Profile (QTPP), Critical Quality Attributes (CQAs), understanding of how variables affect them, and a scientifically justified design space supported by an integrated control strategy.

What is a design space in QbD, and how is it different from a Proven Acceptable Range? +

A design space is the multidimensional combination of input variables demonstrated, through structured experimentation, to provide assurance of quality — critically, it captures interactions between parameters. A Proven Acceptable Range (PAR) tests one parameter at a time and doesn't account for interactions. Many teams build PARs and call the result a design space, but only a genuine multivariate design space, established via Design of Experiments, earns ICH Q8's regulatory flexibility.

Do you need FDA approval to change a process within an approved design space? +

No. Under ICH Q8(R2), movement of process parameters within an approved design space isn't treated as a post-approval change requiring regulatory resubmission — this is the central regulatory incentive for QbD development. Moving outside the design space boundaries is treated as a change and normally triggers the standard post-approval change process, so the boundaries themselves must be scientifically justified and clearly documented.

What is "checkbox QbD" and why does it fail? +

Checkbox QbD is completing the visible artifacts — risk assessments, fishbone diagrams, a QTPP document — without the Design of Experiments work needed to establish a genuine multivariate design space. The result is QbD-style documentation over PAR-style ranges, meaning the team spent the extra development effort without earning the regulatory flexibility that effort was meant to unlock.

What's the difference between QbD and traditional pharmaceutical development? +

Traditional development relies on empirical, often one-factor-at-a-time testing, fixed parameters from a handful of validation batches, and end-stage testing to catch problems. QbD front-loads systematic experimentation and risk assessment to understand variable interactions, resulting in a defined design space, real-time release testing potential, and a control strategy that catches problems through process understanding rather than final testing alone.

What are the core principles of Quality by Design? +

QbD's core principles, grounded in ICH Q8(R2), Q9, and Q10: build quality in through design rather than testing it in afterward; define a Quality Target Product Profile before making process decisions; use quality risk management as the connective framework linking every element; establish process understanding through systematic experimentation rather than assumption; and apply a control strategy proportional to risk, maintained continuously across the lifecycle rather than fixed at approval.

What are the biggest challenges in implementing QbD? +

The most common challenge is completing QbD's visible documentation — risk assessments, QTPP documents — without the Design of Experiments work needed to build a genuine design space, delivering none of the regulatory benefit for the added cost. Teams also struggle with cross-functional buy-in, since QbD requires R&D, manufacturing, quality, and regulatory affairs to share process understanding early, and with navigating how regulators evaluate QbD-based submissions differently from traditional fixed-range filings.

How does GoVal support a QbD-based control strategy? +

GoVal ties risk assessments, critical process parameter documentation, and change control directly to each product's defined design space boundaries. When a process parameter change is proposed, GoVal's change control workflow assesses it against the documented design space and control strategy, generating the audit-trailed evidence needed to demonstrate that operation stayed within approved boundaries.

Keep every process change inside its approved design space — and prove it

Risk assessments, critical parameter documentation, and change control tied to your control strategy — in GoVal.

Book a Free Demo →