Regulatory submissions, including New Drug Applications (NDAs), Biologics License Applications (BLAs), Investigational New Drug applications (INDs), and their international equivalents, represent the formal interface between a pharmaceutical company’s science and the regulatory agencies that grant market access. These submissions are among the most complex documents in any industry: an NDA can contain millions of pages of data, analysis, and clinical documentation organized according to strict regulatory format requirements.
Pharma CEOs who try to stay closely involved in regulatory submission management quickly discover that the work is too specialized and too voluminous for meaningful executive engagement at the operational level. The submission process is managed by regulatory affairs professionals who understand the regulatory requirements, review strategies, and submission logistics that the CEO cannot and should not need to master.
At the same time, regulatory submissions carry significant strategic and investor implications that require genuine CEO engagement at the right moments. This article describes how pharma CEOs delegate regulatory submissions effectively while maintaining the strategic oversight the function requires.
The Head of Regulatory Affairs as Primary Submission Delegate
The Chief Regulatory Officer or Head of Regulatory Affairs is the CEO’s primary delegate for all regulatory submission activities. This person should be a regulatory affairs professional with deep experience in the relevant regulatory jurisdiction (FDA, EMA, or international) and the specific regulatory pathway for the company’s product types.
The regulatory affairs leader’s mandate for submissions includes: developing and executing the regulatory strategy for each program, managing the submission team and regulatory consultants, coordinating with R&D and Medical Affairs for the scientific content of submissions, managing the FDA (or equivalent) relationship for each program, and tracking submission timelines and PDUFA dates.
The CEO should not be reviewing submission documents, attending submission team meetings, or managing the FDA liaison relationship at the operational level. These are regulatory affairs responsibilities.
What the CEO Delegates in Regulatory Submissions
The following activities should be fully delegated to the regulatory affairs function:
Submission strategy development: The regulatory team develops the strategy for each program, including the regulatory pathway (standard review vs. priority review, breakthrough therapy designation, etc.), the anticipated review timeline, and the approach to each section of the submission. The CEO reviews and approves the strategy at a high level; the regulatory team develops it.
Submission team management: Organizing and managing the cross-functional team (clinical, preclinical, statistical, manufacturing, labeling) that generates the submission content. This is a major project management undertaking that belongs to regulatory affairs, often with a dedicated Regulatory Project Manager.
Dossier preparation and quality review: The actual writing, compiling, and quality-checking of submission documents. These are regulatory and technical functions that require specialized expertise.
FDA correspondence and meeting management: Day-to-day FDA communications, meeting requests, meeting preparation, and meeting follow-up belong to regulatory affairs, with the CMO co-leading on clinical matters. The CEO does not manage FDA correspondence.
Electronic submission logistics: The technical process of assembling and submitting the electronic common technical document (eCTD). This is a regulatory technology function.
What the CEO Retains in Regulatory Submissions
Despite the extensive delegation above, the CEO retains meaningful roles in regulatory submissions:
Regulatory strategy approval: The CEO should formally review and approve the regulatory strategy for major programs, particularly the pathway decisions that affect timeline, investment, and risk. A strategy decision to pursue accelerated approval versus standard approval, for example, has significant investor and commercial implications that warrant CEO review.
Major FDA meeting participation: Certain FDA meetings, particularly Type B meetings before NDA submission and end-of-Phase 2 meetings, may benefit from CEO attendance to signal organizational commitment. The regulatory team prepares for these meetings and manages the content; the CEO attends as the organizational principal. Not every FDA meeting requires CEO presence; the regulatory lead determines which meetings benefit from CEO participation.
Approval milestone management: When a PDUFA date is approaching, the CEO should be receiving regular milestone briefings from the regulatory lead and should be prepared to manage the investor communications, internal communications, and external stakeholder engagement around the approval decision. The communication plan for both approval and for potential rejection (Complete Response Letter) should be prepared with CEO input.
CRL response strategy: If FDA issues a Complete Response Letter rather than approving a submission, the CEO is immediately informed and should be involved in the strategic response decision: how to respond, at what timeline, and how to communicate with investors and the board.
For context on how regulatory submission delegation connects to the broader clinical operations oversight structure, see pharma CEO clinical ops, which addresses how pharma CEOs can maintain strategic oversight of the full clinical development process that feeds regulatory submissions.
Building the Reporting System for Regulatory Oversight
The CEO’s regulatory submission oversight should operate through a structured reporting system:
Monthly regulatory update: A brief summary from the Head of Regulatory Affairs covering: submission timeline status for each active program (on track, at risk, or delayed), FDA correspondence received or sent in the prior month, any significant regulatory developments in the relevant therapeutic areas, and any emerging regulatory issues requiring CEO awareness.
Quarterly regulatory strategy review: A 60-minute meeting with the Head of Regulatory Affairs covering: strategic regulatory decisions upcoming in the next quarter, update on any advisory committee planning, and any regulatory strategy adjustments based on FDA feedback.
PDUFA date briefings: In the 90 days before a major PDUFA date, the CEO should receive weekly briefings on the submission status, any FDA information requests, and the communication plan for the approval decision.
This reporting structure keeps the CEO strategically informed without pulling the CEO into operational submission management.
The FDA Relationship at the CEO Level
The CEO’s relationship with the FDA exists primarily at the organizational level, not the submission level. The CEO may engage with FDA leadership at industry events, during congressional hearings on pharmaceutical policy, or in the context of significant organizational developments (a major partnership, a therapeutic area strategy, a significant post-marketing commitment). This is different from the program-specific FDA relationship that regulatory affairs manages.
The CEO should not be building personal relationships with the FDA reviewers assigned to specific programs. This is the regulatory lead’s relationship. When the FDA requests a meeting with company leadership beyond the regulatory and clinical teams, the CEO’s participation is coordinated through regulatory affairs based on the FDA’s specific request.
Managing International Regulatory Submissions
For pharmaceutical companies with global programs, regulatory submissions extend beyond FDA to EMA, PMDA (Japan), NMPA (China), Health Canada, and other agencies. International submission management follows the same delegation principles as FDA submissions, but with additional complexity from multi-jurisdictional strategy coordination.
The Head of Regulatory Affairs should have international regulatory expertise or access to international regulatory consultants. The CEO’s international regulatory engagement is limited to: approving the global regulatory strategy and submission sequence, participating in any senior-level regulatory agency meetings that genuinely benefit from CEO presence, and managing investor communications about international approval milestones.
International regulatory submissions should not be managed differently from FDA submissions from a delegation perspective. The regulatory affairs team owns the execution; the CEO maintains strategic oversight.
Preparing for Potential Submission Failures
Every regulatory submission carries the possibility of rejection. The Complete Response Letter (CRL) from FDA, or a negative opinion from EMA’s Committee for Medicinal Products for Human Use, is a high-stress organizational event with significant investor and strategic implications.
The CEO should invest time in advance of any major submission decision in preparing for this possibility:
- Work with the regulatory lead to understand the most likely issues FDA might raise in a CRL
- Prepare a CRL response strategy in advance, including the resources that would be needed
- Work with the Head of IR and General Counsel on the investor communication approach for a CRL scenario
- Brief the board on the submission status and the possibility of a CRL as part of normal board governance
According to Forbes analysis of pharmaceutical regulatory strategy, pharmaceutical companies that prepare rigorously for submission failure scenarios manage the organizational and investor consequences more effectively than those that assume approval. This preparation is a CEO-level governance responsibility, not a regulatory operations task.
See pharma CEO delegation guide for a comprehensive framework on how regulatory submission delegation fits within the full range of pharma CEO delegation responsibilities, including how submission timelines connect to commercial launch planning and investor communications.
Effective Delegation as a Regulatory Advantage
Regulatory submissions that are prepared by expert regulatory affairs teams, with appropriate CEO strategic oversight and without operational CEO involvement, are typically better submissions than those where CEO involvement creates confusion about authority or disrupts the systematic preparation process.
The CEO who trusts the regulatory affairs team to execute excellently, provides clear strategic direction on regulatory strategy, and engages at the right moments (strategy review, key FDA meetings, approval/CRL response) creates the conditions for regulatory excellence. That excellence is a competitive advantage that translates directly into faster approvals, better labels, and more successful commercialization of the company’s scientific investment.
Related Reading
For further context, explore How Pharma CEOs Delegate Business Development and Licensing and How Pharma CEOs Delegate Clinical Trial Operations.