Delegation Playbook for Pharma CEO Regulatory Submissions

Regulatory submissions are the commercial lifeline of any pharmaceutical company. An NDA or BLA approval unlocks years of revenue and validates the science and capital deployed to reach that milestone. They are also extraordinarily complex, technically specialized, and governed by federal requirements that make individual accountability a legal matter, not just an organizational preference.

This combination creates a specific delegation challenge for pharma CEOs. You cannot manage regulatory submissions personally. You do not have the technical expertise, the bandwidth, or the organizational structure to lead NDA or BLA submissions alongside everything else the CEO role requires. But the stakes, the regulatory exposure, and the board scrutiny around these submissions mean you cannot simply hand them off and check in at approval.

This playbook defines how to delegate regulatory submission processes to your VP of Regulatory Affairs in a way that gives that leader genuine authority, keeps the CEO accountable at the governance level, and establishes clear escalation criteria for the FDA interactions that require CEO-level engagement.

The VP Regulatory Affairs Authority Framework

Effective regulatory delegation starts with a clear authority framework for your VP Regulatory Affairs (VP RA). Without this, you will either under-delegate (creating a bottleneck on your calendar) or over-delegate (losing visibility on material regulatory risks).

Full VP RA Authority

The VP RA should have unambiguous authority over:

Submission strategy. Which regulatory pathway to pursue (e.g., 505(b)(1) versus 505(b)(2) for small molecules), what priority designation to seek (Breakthrough, Fast Track, Priority Review), and the timing strategy for submission filing.

Submission content. The technical content of all regulatory documents, including the CTD structure, clinical summaries, non-clinical overviews, and quality sections. The CEO should not be reviewing these documents.

Agency communication management. Pre-IND meetings, Type A/B/C meeting requests, and responses to FDA information requests (CIRs) are VP RA-owned activities. The VP RA maintains a log of all agency communications for CEO visibility.

Regulatory operations team. Hiring, managing, and structuring the regulatory affairs team, including any contract regulatory support, is the VP RA’s responsibility. The CEO approves headcount budgets but does not manage individual regulatory staff.

CMC and labeling coordination. Working with manufacturing and medical affairs teams to ensure submission-ready documentation is VP RA-led.

CEO Involvement Criteria

The CEO should be involved in regulatory matters only when specific conditions are met. Document these criteria explicitly so neither you nor the VP RA has to make judgment calls in the moment.

CEO involvement is triggered when:

The FDA requests a meeting at which the agency expects sponsor executive presence (uncommon, but occurs during certain dispute resolution processes)
A complete response letter (CRL) is received, triggering a board notification requirement
A clinical hold is imposed on any active IND
The VP RA identifies a risk that could materially delay approval by more than two regulatory review cycles
A regulatory strategy decision requires a change to approved clinical or commercial plans that has been board-authorized

Outside these triggers, the CEO’s role is to receive the VP RA’s regular updates and ask strategic questions, not to manage the process.

Building the Regulatory Governance Structure

Compliance governance in pharmaceutical regulation is not optional. Federal law creates individual accountability for pharmaceutical executives in ways that require the CEO to maintain genuine oversight even when delegating execution authority. The FDA’s use of Warning Letters, consent decrees, and 483 observations means a CEO cannot credibly claim ignorance of systemic regulatory failures.

The governance structure that bridges delegation and accountability has three components.

Regulatory Steering Committee

A cross-functional Regulatory Steering Committee (RSC), chaired by the VP RA and including the CMO, CSO, Head of Quality, and General Counsel, provides the institutional governance layer. The RSC:

Reviews submission strategy at key milestones (pre-IND, end-of-Phase 2, pre-NDA)
Approves major changes to regulatory strategy
Escalates material risks to the CEO and board

The CEO should not chair the RSC. CEO participation in RSC meetings should be limited to the pre-NDA strategy review and any meeting where a material risk is on the agenda. Routine RSC governance belongs to the VP RA.

CEO Regulatory Dashboard

The VP RA maintains a one-page regulatory dashboard updated monthly and presented quarterly to the CEO and board. The dashboard covers:

Status of all active INDs and NDAs/BLAs by program
Open FDA commitments and their due dates
Material risks flagged by the RSC
Post-market regulatory commitments (REMS, post-approval studies) and their completion status

This dashboard gives the CEO genuine oversight without requiring the CEO to attend weekly regulatory team meetings.

Board Regulatory Reporting

The board receives an annual regulatory update from the VP RA, typically presented to the science and technology committee or equivalent. The CEO’s role in this update is framing the strategic significance of the regulatory portfolio in the context of the company’s growth plans, not presenting the technical detail.

When a material regulatory event occurs (CRL, clinical hold, advisory committee meeting), the VP RA and CEO present jointly to the board within 30 days of the event.

FDA Interactions: The Escalation Matrix

The most nuanced part of regulatory delegation is defining which FDA interactions require CEO involvement. The answer is almost never “routine FDA interactions” and almost always “disputes or high-visibility proceedings.”

Routine FDA Interactions: VP RA Owned

Pre-submission meeting requests and meeting minutes
Response to information requests and deficiency letters
NDA/BLA rolling submission coordination
Post-approval supplement submissions
Annual report filings
Labeling negotiations (unless a dispute triggers escalation)

Escalation to CEO

Advisory Committee (AdCom) meetings. When the FDA schedules an advisory committee review of a pending application, the CEO should be informed and should participate in the company’s pre-AdCom preparation at a strategic level. The CEO does not present at AdCom, but the board and investors expect CEO visibility into this process.

FDA dispute resolution. If the company files a formal dispute resolution request (under 21 CFR 312.48 or equivalent), that process involves direct engagement between executive leadership and FDA division directors or the Office of New Drugs. The CEO may need to participate.

Meeting requests by FDA leadership. If the FDA’s Center Director, Deputy Center Director, or equivalent requests a meeting with sponsor leadership, the CEO attends.

Public health crises involving company products. If a marketed product is implicated in a public health signal requiring immediate FDA engagement, the CEO leads the company’s regulatory response in coordination with the VP RA and General Counsel.

Consent decree risk. If the VP RA assesses that FDA inspectional activity creates consent decree risk, the CEO and board must be informed immediately.

For pharmaceutical companies building delegation structures across multiple clinical programs, the pharma CEO delegation framework for clinical development teams addresses how to apply similar authority structures to clinical operations alongside regulatory functions.

The Pre-NDA Strategy Review: CEO’s Highest-Value Regulatory Moment

If there is one regulatory event where CEO active participation delivers the most value, it is the pre-NDA strategy review. This typically occurs six to twelve months before a planned submission, when the regulatory strategy is being finalized and the clinical data package is being assembled.

At the pre-NDA review, the CEO should be engaged on:

Label ambitions. What the company is seeking in the product label (indication, population, safety language) determines the commercial potential of the asset. This is a business strategy decision as much as a regulatory one.

Advisory committee strategy. Whether to request an AdCom, how to frame the benefit-risk narrative, and how to prepare for potential FDA questions are decisions that benefit from CEO perspective.

Timeline risk tolerance. The company’s willingness to accept a standard 10-month review versus pursuing strategies that might accelerate or risk delaying the review timeline involves business tradeoffs the CEO should weigh.

Parallel approval strategies. If seeking simultaneous US and ex-US approvals (EMA, Health Canada), the resource and timeline implications require CEO-level alignment.

This engagement should be structured, time-bounded, and prepared by the VP RA. The CEO should not be navigating technical submission questions. The pre-NDA review is a strategic session, not a document review.

Post-Approval Regulatory Delegation

Once a product is approved, the regulatory relationship shifts but does not diminish. Post-approval commitments, REMS programs, manufacturing changes, and labeling updates require ongoing regulatory management. The VP RA owns all of this.

The CEO’s post-approval regulatory responsibilities are governance-level:

Ensuring post-approval commitments are resourced adequately
Receiving annual updates on commitment completion status
Being informed of any 483 observations or Warning Letter risks in post-approval inspections
Approving any label changes that have material commercial implications

Post-approval regulatory work often becomes invisible to CEOs because it lacks the drama of initial approval. The risk is that under-resourced post-approval functions accumulate compliance gaps that become material FDA issues years later. The governance structure described above should extend into the post-approval phase, not terminate at approval.

Working with Contract Regulatory Organizations

Many pharmaceutical companies, particularly mid-size and specialty pharma, use Contract Research Organizations (CROs) and contract regulatory consultants to supplement internal regulatory capabilities. Delegation to the VP RA must include clear authority over these external relationships.

The VP RA should own:

CRO selection for regulatory services
Contract scope and deliverable accountability for regulatory CRO work
Integration of CRO work product into company submissions

The CEO’s involvement in CRO relationships should be limited to approving material contract values and being informed of any CRO performance issues that could affect submission timelines.

Common CEO Mistakes in Regulatory Delegation

Attending regulatory team meetings without a strategic purpose. CEO presence in operational regulatory meetings creates confusion about authority and slows decision-making. If the CEO attends, there should be a specific agenda item requiring CEO input.

Responding directly to FDA inquiries. CEOs sometimes receive informal outreach from FDA staff or industry contacts with information about pending reviews. Any such contact should be routed through the VP RA immediately and documented.

Making informal timeline commitments. Investor relations pressure sometimes leads CEOs to make informal timeline statements about regulatory milestones that are not consistent with the VP RA’s assessment. This creates internal misalignment and can create securities disclosure issues.

Under-resourcing the regulatory function. Regulatory affairs is chronically under-resourced in companies that have not yet experienced a major FDA setback. The CEO’s job is to ensure the VP RA has adequate budget and headcount before a submission bottleneck emerges.

According to McKinsey research on biopharmaceutical organizational design, companies that build strong functional leadership in regulatory affairs and empower those leaders with clear decision authority consistently outperform in submission quality and approval timelines. See McKinsey’s perspective on biopharma operating models for additional context on building high-performing regulatory organizations.

The guide to CEO delegation in pharmaceutical and biotech organizations provides a broader framework for distributing authority across the full pharmaceutical C-suite, which contextualizes the regulatory delegation structure described here.

Conclusion: Governance Without Micromanagement

Pharmaceutical CEOs who delegate regulatory submissions effectively operate in a specific posture: fully accountable for regulatory outcomes at the governance level, genuinely removed from technical submission management at the operational level.

This posture requires investing in a VP RA who has both the technical credibility and the organizational authority to lead the regulatory function independently. It requires building the governance structures that give the CEO real visibility without creating a shadow review process that slows the VP RA down. And it requires the discipline to stay in your lane, asking strategic questions rather than reviewing CTD sections.

Your regulatory submission timeline is one of the most material variables in your company’s financial performance. That is precisely why it needs to be owned by your best regulatory professional, not managed as a CEO side project.

For further context, explore Delegation Playbook for Automotive CEO: Cost Reduction and Delegation Playbook for Automotive CEO: Crisis Management.