Features
September / October 2026

CMC Platform Technologies: Regulatory Considerations and Case Studies - Part 1

Celeste Frankenfeld Lamm, PhD
Shermeen Abbas
Nina Cauchon, PhD
Stuart Finnie
Jessica Lo Surdo, PhD
Jessica Hale
Laura Muehlbauer, PhD
Christopher Potter, PhD
Dennis Powers
Lisa Wright
Yan Yang, PhD
CMC-PLATFORM-TECHNOLOGIES-1900px.jpg

Platform technology is gaining importance as regulators and industry seek tools to streamline regulatory approaches. In this article, we discuss how organizations might use platform technology in regulatory submissions to improve process efficiency for regulators and industry.

Platform technology has emerged as a valuable tool for achieving a shared goal for regulators and the biopharmaceutical industry: expediting global delivery of new and improved medicines to patients safely and efficiently. There is agreement that platform technology rests upon a foundation of prior knowledge. However, there are diverse perspectives, questions, and concerns about what comprises prior knowledge, and how it might contribute to platform use. Although “platform technology” has been used broadly, the term’s regulatory definitions diverge in scope and applicability. This hinders industry’s ability to adopt global platform strategies, especially for streamlining the review, approval, and postapproval processes for regulatory submissions.

To effectively implement platforms, there is a need to ensure all parties have a shared understanding of the platform definition, as well as when, and how, it can be utilized. This can enable the appropriate application of risk management to the platforms during product development, provide confidence to industry to incentivize adoption, and facilitate collaboration across agencies when a platform is used in applications that are submitted using collaborative pathways (e.g., International Coalition of Medicines Regulatory Authorities [ICMRA] pilots, Access, Project ORBIS) or regulatory pathways where reliance is a tool. If we want to benefit from platform technology and prior knowledge, we need to agree on what a platform is, how much prior knowledge should be included in a submission versus available upon request, and how it should be included.

This article reviews the divergent regulatory definitions of “platform,” describes benefits of a harmonized definition, and closes with examples of such definitions.

Regulatory Landscape of Platform Technology

Next, we discuss divergent platform technology definitions and expectations for leveraging prior knowledge.

US Food and Drug Administration (FDA)

In May 2024, the US FDA issued draft guidance referring to Federal Food, Drug, and Cosmetic Act (FD&C Act) Section 506K(h)(1), which defined platform technology as a well-understood, reproducible technology (e.g., nucleic acid sequence, molecular structure, mechanism, delivery method, vector, or combinations) that:

  • Is essential to a drug’s structure or function
  • Can be adapted across multiple drugs with shared structural elements
  • Facilitates development or manufacture via standardized processes1, 2

This definition focuses primarily on molecular and advanced therapy technologies rather than manufacturing or analytical procedures and is broader than typical chemistry, manufacturing, and controls (CMC) usage. However, the US FDA adds that the term has other uses:

“Some technologies that industry and FDA have historically considered to be platform technologies might not meet the statutory definition and statutory eligibility factors and, if not, would not be eligible for the designation program. Ineligibility for des-ignation does not preclude a sponsor from leveraging prior knowledge across applications. FDA has allowed sponsors to leverage prior knowledge from previously submitted applications when authorizing or approving drugs in an application submitted by the same sponsor.”1

Finally, the guideline defines prior knowledge as expertise built over time, including experience with similar compounds, products, or processes, and established scientific principles.

For pharmaceutical devices, there are no well-established rules for platforms. The US FDA’s current thinking in the draft guidance is that drug delivery devices and autoinjectors may be out of scope for securing a platform designation.1 However, a US Congressionally–charged commission has challenged the US FDA to expand the platform technology designation’s scope.3, 4, 5, 6 Globally, device regulation is less defined, though device and combination-product components often rely on prior knowledge in practice.

The US FDA’s 510(k) pathway for devices operationalizes prior knowledge via predicates (marketed devices that are used as points of comparison). These are the basis for follow-on device approval when companies supply supporting data, demonstrating the equivalence between the two devices. Aspects of such new devices may have been changed or modified; however, the data from the initial application’s unchanged aspects remains useful and reliable.

Bridging studies in combination products similarly leverage prior knowledge, using established drug attributes or device systems to streamline development. Bridging studies’ designs include identifying established like-drug attributes and/or delivery-device systems, in which prior product experience and knowledge can be leveraged without needing new studies. The US FDA’s 2019 draft guidance Bridging for Drug-Device and Biologic-Device Combination Products proposes a framework to rely on prior knowledge, but practical application details remain limited and acceptance has been inconsistent7

For combination-product submissions using bridging, sponsors typically:

  • Repeat device content from prior applications, updating as needed
  • Use a Type V Drug Master File (DMF) with device content referenced across applications

Both approaches have drawbacks. The first leads to redundant reviews by the US FDA, which wastes time and resources if the device components or specifications don’t change significantly. With the second approach, DMFs are reviewed only during application submissions and do not receive US FDA approval, which creates uncertainty about whether the included information will be deemed adequate. Additionally, every new application that cites the same DMF may prompt repeated reviews of the same information. For biologics license applications (BLAs), using DMFs presents additional challenges, as explained in the US FDA’s Final Rule on DMFs and BLAs.8

Bridging studies’ designs include identifying established like-drug attributes and/or delivery-device systems, in which prior product experience and knowledge can be leveraged without needing new studies.

Including combination products under the platform technology designation program—especially drug delivery devices such as autoinjectors and prefilled syringes—could solve this problem. Applicants could then refer to drug-agnostic information they consider “platform” from the original New Drug Application or BLA in subsequent submissions and include only product-specific data in new applications. This would reduce the regulatory burden for both the US FDA and industry.

The legislative definition includes the following:

“(A) well-understood and reproducible technology, which can include a nucleic acid sequence, molecular structure, mecha-nism of action, delivery method, vector, or a combination of any such technologies that the Secretary determines to be appropri-ate” (emphasis added).

Given this language, we argue that it is overly restrictive for the US FDA to exclude delivery methods/systems from the designation program, as the legislation neither defines nor expressly limits scope for a “delivery method.” Broadening the current interpretation could improve the program’s utility across industry. To date, only two designations have been granted. One was later withdrawn for safety issues; one remains active. This low number of designations further suggests that the current interpretation may be too narrow.

European Medicines Agency (EMA)

The EMA has not formally defined platform technology in regulation or guidance for human medicines, but it has convened workshops to clarify prior knowledge and platforms. The draft EU Pharmaceutical Legislation is likely to provide definitions and pathways when final.9 The joint Biologics Working Party/Quality Working Party (BWP/QWP) workshop in 2017 reached broad agreement that prior knowledge includes internal company experience, external literature, and common scientific principles. All forms of prior knowledge are usable to justify platform approaches (e.g., classifying parameters as noncritical process parameters).10

In 2024, the Quality Innovation Group (QIG) held a Listen and Learn Focus Group meeting on using prior knowledge and platform technologies.11 The group reiterated that “prior knowledge” includes a company’s knowledge and data from development and manufacturing (e.g., experience based on similar compounds, products, and processes) and reference to scientific and technical publications or application of established scientific principles. However, definitions of “platform” varied. Some attendees defined platforms as mathematical models applicable to different products; other attendees said “platforms” and “prior knowledge” are interchangeable terms.

The focus group also addressed platform technology definitions and regulatory approaches for vaccine Platform Technology Master Files (vPTMF) for veterinary products.12 However, the definition is limited to “a collection of technologies that have in common the use of a ‘backbone’ carrier or vector that is modified with a different antigen or set of antigens for each vaccine derived from the platform.”13 This definition is narrow and not broadly applicable. Despite the varying perspectives, attendees agreed that platform approaches can streamline development and validation to speed products to patients. The EMA continues to refine the concept.

International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH)

“Prior knowledge” is integral in later ICH Q guidelines. It is recognized as a source of information that supports development, risk assessment, identification of Critical Quality Attributes (CQAs), and alternative validation approaches in ICH Q8 to Q14. 14 ICH Q8 refers to prior knowledge in six contexts, though it provides no definition.15 ICH Q11 specifically defines prior knowledge in relation to platform approaches (i.e., established biological, chemical and engineering principles, technical literature, and applied manufacturing experience) and supports leveraging platform manufacturing to expedite understanding. 16 Additionally, Q11 defines platform manufacturing as “the approach of developing a production strategy for a new drug starting from manufacturing processes similar to those used by the same applicant to manufacture other drugs of the same type (e.g., as in the production of monoclonal antibodies [mAbs] using predefined host cell, cell culture, and purification processes, for which there already exists considerable experience).”16

Regulatory bodies’ varied descriptions of “platform technology” reflect diverse perspectives and the term’s complex implications for regulatory practices.

ICH Q2(R2) and ICH Q14 formalize application of prior knowledge and platform concepts to the development, validation, and life cycle of analytical procedures.17 Pharmaceutical and biotechnology companies have increasingly employed platform analytical procedures during drug development and have begun integrating them into commercial products, facilitated by adoption of ICH Q2(R2) and ICH Q14.17, 18 ICH Q2(R2) defines a platform analytical procedure as “suitable to test quality attributes of different products without significant change to its operational conditions, system suitability and reporting structure.” ICH Q14 allows, in certain cases, abbreviated development and selective omission of validation tests with science- and risk-based justification. This formal acknowledgment lets companies leverage platform procedures to make validation and transfer more efficient and ensure method robustness by building on prior knowledge with the platform procedure.

World Health Organization (WHO)

The WHO limits a platform technology’s scope to monoclonal antibodies (mAbs), defining the technology as unchanged technology elements (e.g., manufacturing methods/processes, mAb scaffold, Good Manufacturing Practice [GMP] compliance) that allow reuse of experience, data, and validations to accelerate development.

“The experience and knowledge gained, data generated (on manufacturing, control and stability), and the validation of un-changed method can all be used as supportive data for the more rapid assessment and development of a new mAb product candidate that fits within the boundary of the platform.”19

The WHO highlights that development time for establishing and validating product process and quality control methods is reduced when using mAbs-related platform technologies. However, the WHO acknowledges that although platform technology may provide product safety confidence, it may not reduce the nonclinical and clinical expectations for new marketing applications.

Landscape Summary

Regulatory bodies’ varied descriptions of “platform technology” reflect diverse perspectives and the term’s complex implications for regulatory practices.

The US FDA defines platform technology as a well-understood and reproducible technology that encompasses molecular and delivery methods and figures in drug development and manufacturing. The EMA has not formally defined platform technology for human medicines but has led discussions highlighting internal and external prior knowledge’s importance in justifying platform technologies. The ICH recognizes prior knowledge as critical for supporting development and risk assessment, linking it to platform approaches in drug manufacturing. Meanwhile, the WHO limits its definition of platform technology specifically to mAbs, focusing on manufacturing method and process consistency.

These varying definitions illustrate the complexity of what might be termed “platform technology,” though the broad use of the terminology across regulatory bodies underscores stakeholders’ shared goal to streamline processes and expedite patient access to new therapies. However, for industry to adopt platforms and effectively communicate the concepts in regulatory submissions, all parties will need a shared understanding.

Establishing a Common Definition of Platform Technologies

At their core, platform technologies are systems that enable standardized processes, creating predictable, reusable point-A-to-point-B pathways. However, the definition needs more nuance to capture complexities.

As we seek to define platform technology, several critical questions arise:

  • Applicability: How broadly applicable must a process be to qualify as a platform?
  • Experience: What level of experience is required to classify a process as a platform? Is an “n” of 2 sufficient, or is more needed?
  • Scope: To what extent do process details constitute the platform? Does the platform encompass specific unit operations and process parameters, and does it require shared structure between products?
  • Roles and documentation: How do we approach ownership and access to platform knowledge across two entities (e.g., a contract development and manufacturing organization [CDMO] and an applicant) or two companies in partnership to develop and commercialize a product?
  • Life cycle: If platforms need updates, how can we ensure that those updates are assessed and applied across all products that depend upon them?

Applicability

Many technologies could be classified as platforms under the CMC context: elements of manufacturing processes and lines; facility design; analytical procedures; and drug delivery devices.

Manufacturing lines and processes

Manufacturing lines and processes often include multiple unit operations that can be applied across a wide range of products, making them prime candidates for platform classification. Established prior knowledge underpins many of these processes, helping identify critical processing parameters that require control. Examples include tableting, encapsulation, spray-drying, freeze-drying, vector technology, and downstream biologics purification. Although certain parameters may be specific to individual products, equipment-related parameters apply generally across the platform.

Facility design

Current discussions about standardizing facilities for decentralized or distributed manufacturing align closely with the platform concept. This standardization can enhance efficiency and adaptability in manufacturing operations.

Analytical procedures

For analytical procedures, compendial methods can be considered a form of platform technology because they apply universally across numerous products. Using more complex procedures across multiple products offers the promise of additional regulatory flexibilities during development, validation, and transfers. Per ICH Q14, it is essential to recognize that analytical procedures, much like manufacturing processes, are developed based on prior knowledge, yielding predictable outcomes and reusable pathways.17

Drug delivery devices

Device delivery technologies typically fall outside the US FDA’s platform designation criteria because the agency doesn’t deem them integral to drug or biological product structure or function and doesn’t think they significantly enhance manufacturing efficiency or review.1 Nevertheless, combination-product sponsors are increasingly developing device platforms that can work across multiple therapies.

For example, prefilled syringes are available in “standard” forms and are used similarly for many different products. These manufacturers leverage prior knowledge about real-world safety, effectiveness, and usability to inform the development of new combination-product platforms. A European Federation of Pharmaceutical Industries and Associations (EFPIA) reflection paper highlights how device constituent parts are used in medicinal products and discusses how a platform device approach can streamline review for these products.20

Experience

How many product experiences are needed to establish a platform for regulatory submission? At a minimum, one might need only two if an approved submission includes directly relevant prior knowledge. Iterative development can offer valuable insights, letting developers tap their experience to adapt to new products more effectively. How well people understand the product and platform matters more than how many products use the technology. A platform’s defining feature is its applicability across products.

Scope

Varying definitions for “platform” in different contexts create confusion. The main question to answer here is, how much of the process constitutes the platform? It should be asked:

  • Should the platform include specific unit operations and process parameters?
  • Can the process parameters encompass slight differences across products and still maintain the platform approach?
  • Is a shared structure between products essential for the platform to be applicable?

Master files can solve the incomplete knowledge problem, giving regulatory authorities detailed information to support the platform.

Trying to answer these questions definitively may inadvertently, and unintentionally, constrain platform opportunities. It’s more effective, then, for a sponsor to propose the scope of a platform case by case for agreement with regulators, drawing on the aspects of prior knowledge that can be leveraged to support the platform’s development.

Roles and Documentation

Challenges arise when more than one party develops or uses a single platform throughout its life cycle. For example, if a CDMO is using all of its development experience to support a platform, it will need to exclude some, or even all, of this information from a marketing application. Yet, how can an applicant maintain product quality control when it lacks access to all the relevant information? The CDMO has valuable operational knowledge, but the applicant will struggle to evaluate how changes might affect manufacturing or final product quality. The same issue can arise when two companies work together to commercialize a new drug. Each partner may have important information that isn’t fully shared, yet both partners must maintain product quality.

Master files can solve the incomplete knowledge problem, giving regulatory authorities detailed information to support the platform. The two partners can use quality agreements to outline how to communicate and manage impacts to a platform technology within quality systems. Besides helping manage information shared across multiple parties, master files can also support prior knowledge’s use across multiple products or submissions.

Sponsors may find a layered submission strategy useful, in which the core prior knowledge is maintained in a master file and referenced in later submissions. Those submissions can then explain why the prior knowledge applies to the new product and can provide any necessary product-specific bridging information. Using cross-references this way can reduce duplicative writing and regulatory review, lowering the risk that platform-related communication raises unnecessary questions for other approved products.

Life Cycle

Platforms, like most other technologies, may eventually need updates. Because platforms extend across multiple products, it is critical to assess how changes could affect each product and consider how to best manage documentation throughout a quality system and regulatory submissions. This is why master files are critical for platforms; they provide a centralized location for communicating updates. When the update doesn’t affect the product beyond the platform, submissions and subsequent review can be minimized.

Proposed Definition of CMC Platform Technology

Considering the previous discussion, a CMC platform technology can be defined as a system encompassing multiple elements, perhaps including manufacturing equipment, facility design, process operations, processing aids, analytical methods, or apparatuses (such as dose delivery devices). This system’s quality attributes are comparable and broadly relevant when applied across manufacturing, purification, or testing of multiple drug substances or products, including combination products. The technology’s broad applicability ensures that prior knowledge can be leveraged, speeding development and reducing review burden to expedite regulatory approvals. The sponsor should define the platform for regulatory submission case by case.

Value of Platforms

Many large pharmaceutical companies have accumulated decades of reliable, stress-tested systems and techniques, derived from testing and modifying systems across multiple products of a similar class. Much of this knowledge resides internally, but it has untapped value when it isn’t applied or recognized across products. Platforms can yield broad benefits for all if regulators can recognize them more broadly. A primary advantage of platform technology is its ability to streamline CMC product development. Each new product using the platform contributes to a growing body of knowledge, which helps standardize the development approach.

For instance, when pharmaceutical companies understand how excipient properties affect flow, or how active pharmaceutical ingredient (API) properties affect dissolution, less characterization is required. This spans from raw material selection to manufacturing processes and testing. Although each new process, method, or system typically necessitates extensive testing to ensure safety and quality, relying on prior knowledge and validated data means many testing aspects have already been completed. Consequently, instead of exhaustive testing, a focused risk assessment can be conducted to confirm the platform’s suitability for the new application, which will let characterization and qualification efforts focus on confirming and addressing identified risks.

Platform analytical procedures can streamline laboratory procedures and reduce validation, transfer, and training burdens. A recent publication highlights six case studies from different pharmaceutical companies that illustrate the development, application, and validation of platform analytical procedures across various drug modalities.21 Although different approaches exist for applying these procedures, they all rely on science- and risk-based justifications. Key elements include leveraging prior knowledge, defining measurement requirements in an analytical target profile (ATP), and conducting risk analyses to determine how much validation or how many transfer experiments are necessary. Given pressures on cost, speed, and product quality, platform analytical procedures present a significant opportunity that ultimately benefits industry stakeholders, regulators, and patients.

CMC submissions may be bolstered by additional data and experience from other products using the platform. However, this does not necessarily mean there will be more information to review. Robust technologies, built upon iterations from multiple products, can benefit from greater familiarity among reviewers. Products of a similar class developed using well-studied manufacturing processes and similar formulation components and tested with established analytical procedures are inherently lower risk and should achieve faster regulatory approvals. Cross-reference mechanisms, such as master files, are important for linking prior knowledge to new applications of a platform. When the information in a master file has been previously reviewed and approved, applying it to a new product requires less scrutiny, thereby reducing the regulatory review burden.

In some cases, only a subunit of the technology may apply broadly as a platform. However, segmenting the process into smaller, more manageable modules that focus on specific aspects can significantly streamline this effort. By using platform modules, pharmaceutical companies can enhance the efficiency of the regulatory review process. These standardized individual modules can be tested, validated, and designed to comply with regulatory requirements, ensuring reliable performance. This modular approach simplifies the application of platform technology.

Platform Technologies and Global Supply Resiliency Initiatives

As regulatory landscapes evolve, strengthening supply resiliency has become a top priority. These initiatives aim to ensure uninterrupted supply of medicines to patients. Platform technologies can build redundancy and support strategic onshoring. When these initiatives are coupled with effective regulatory execution measures, timeliness and accessibility of critical medicines for patients improves.

The ISPE Drug Shortages Prevention Model outlines successful regulatory execution. This includes compliance with reporting requirements and strategic interactions with health authorities to achieve optimal outcomes for drug shortage mitigation or prevention.22 The regulatory strategy employed to engage with health authorities may be pivotal in mitigating or preventing shortages. Proactive regulatory measures, such as using platforms to streamline technology transfer supported by efficient regulatory approvals, can ensure that manufacturers are well positioned to prevent or respond to supply chain disruptions.

The lead time to establish a new plant can be five to seven years; adding a single line within an existing plant can take three to five years.23, 24 However, employing a platform approach can significantly reduce the lead time for establishing a new manufacturing site by leveraging foundational qualification work and training and as mentioned, expedite timelines for regulatory authoring, review, and approval. Regulators’ acceptance of qualified platform technology can spur faster site transfers, further supporting initiatives such as onshoring to enhance supply chain resiliency. If a platform has been transferred multiple times, regulatory flexibilities may increase, such as reduced reporting categories for transfers, shorter review timelines, and decreased requirements for stability and process qualification. Leveraging robust historical data and proven experience can cut the time required to file and execute site transfers. This will ensure supply continuity and enhance resiliency for medically significant products by increasing production capacity and geographical supply chain diversity.

Platforms can streamline development, regulatory authoring, and regulatory review, and can benefit companies, regulators, and patients. Nevertheless, challenges remain. Differences in global regulatory expectations may hinder widespread acceptance of platform approaches to analytical procedures, manufacturing processes, or devices. Documentation concerns and change-management strategies for registered platform procedures must be addressed, particularly when modifications affect multiple products with global registrations. As we consider how to tackle these challenges, we’ll need to examine case studies to gauge how to apply platform technologies practically.

Several published case studies have demonstrated platform applications in which the molecular backbone is shared across programs, such as with siRNA therapeutics.25 In these instances, the platform approach aligns well with the US FDA’s designation programs, enabling streamlined development. The similarity in molecular structure allows for substantial leveraging of existing knowledge, including manufacturing processes, process controls, and stability data. However, platform technologies’ utility extends beyond cases with shared molecular backbones. Platforms can also be effectively applied in scenarios where molecular structures differ significantly across programs. In such contexts, detailed case studies are invaluable for illustrating how platform strategies can be adapted and applied for maximum benefit.

Conclusion

Platform technologies will look different depending on how they’re executed or which company uses them. Those who are submitting platforms will need to justify the proposed platform, associated reductions in process characterization or validation on prior knowledge, and experience with the technology. However, platforms offer a significant benefit of robust understanding, and the potential to reduce regulatory submission volume and review burden. Regulatory platforms can play a pivotal role in fostering continual improvement for biopharmaceutical manufacturing. By establishing standardized processes across multiple products or sites, these platforms promote consistency and help develop a large body of what becomes prior knowledge throughout the use of the platform.

Platforms can also encourage manufacturers to regularly evaluate and enhance their analytical methods and manufacturing processes, leading to iterative enhancements in assurance of product quality. Furthermore, regulatory platforms are collaborative, enabling knowledge sharing and allowing for the dissemination of best practices and innovations. Ultimately, this commitment to continual improvement streamlines operations and enhances patient access to high-quality medicines.

What remains then is to address the challenges that have hindered us from reaping the full benefits—aligning upon shared definitions across regulatory agencies and industry, identifying pathways that enable references of prior knowledge and life cycle management (like master files or in-company data repositories) and supporting greater familiarity and acceptance of platform approaches as justification for streamlining development, validation, and transfer of manufacturing activities. To keep pace with the speed of innovation, the regulatory framework must become more adaptive and define clearer pathways to enable the use of prior knowledge in making regulatory decisions.

Acknowledgments

The authors would like to acknowledge discussions, preliminary thinking, and advice on the topic offered by Timothy Graul, John Lepore, Roger Nosal, and Thomas Zimmer.

Not a Member Yet?

To continue reading this article and to take advantage of full access to Pharmaceutical Engineering magazine articles, technical reports, white papers and exclusive content on the latest pharmaceutical engineering news, join ISPE today. In addition to exclusive access to all of the content in Pharmaceutical Engineering magazine, you will get online access to 24 ISPE Good Practice Guides, exclusive networking events, regulatory resources, Communities of Practice, and more.

Learn more about the valuable benefits you'll receive with an ISPE membership.

Join Today


About Pharmaceutical Engineering

ISPE members receive an annual subscription to ISPE’s award-winning Pharmaceutical Engineering magazine as part of their membership benefits. Published six times yearly, each issue features contributions from expert authors and technical articles highlighting the latest industry trends and innovations.

Learn more

Join ISPE Today

Becoming a member of ISPE offers numerous benefits, including access to a vast network of professionals, exclusive training events, and valuable resources. As a member, you'll join more than 22,000 of your professional peers from over 120 countries in advancing solutions that lead to improved patient health. Membership provides access to 20+ complimentary ISPE Good Practice Guides, a robust library of on-demand training and e-learning resources, and much more. Learn more and consider joining today.

Become an ISPE member 

ISPE members: Get more involved by volunteering.