CEO Executive AssistantIn pharmaceutical and biotech companies, regulatory affairs is not a compliance function at the margin of the business. It is the critical path. The timeline between a promising compound and a marketed product runs entirely through the FDA, and the quality of a company’s regulatory operations determines whether that timeline is measured in years or decades. The CEO who cannot maintain clear, current visibility into regulatory affairs is flying blind on the company’s most consequential work.
Executive assistant support for regulatory affairs coordination gives pharma CEOs the administrative infrastructure to stay fully informed and effectively engaged without displacing the regulatory team’s operational bandwidth. This article covers how that support works across meeting scheduling, submission tracking, team coordination, and board-level reporting.
The Regulatory Oversight Challenge for Pharma CEOs
Pharmaceutical CEOs typically oversee a regulatory affairs function that manages multiple simultaneous programs, each with its own FDA interaction history, submission timeline, and agency relationship. A large company may have dozens of programs in various regulatory stages. Even a focused specialty pharma company might have two or three IND-stage programs, a rolling NDA review, and several post-approval commitments running concurrently.
The CEO needs visibility across all of this without becoming a bottleneck in the regulatory process itself. That means having a coordination system that surfaces the right information at the right time, ensures the CEO is prepared for every regulatory touchpoint, and keeps the board informed at the appropriate level of detail.
An EA who understands the structure of pharmaceutical regulatory affairs, even at a high level, can build and maintain that coordination system. They do not need to be a regulatory scientist. They need to be a sophisticated project manager who understands why these interactions and deadlines matter.
Regulatory Affairs Meeting Scheduling
FDA Meeting Coordination
Meetings with the FDA are among the most strategically important events in a pharmaceutical company’s calendar. Type A meetings (dispute resolution, clinical holds) have a mandated 30-day response window. Type B meetings (pre-IND, end of Phase 2, pre-NDA) are scheduled within 70 days of FDA receipt. Type C meetings cover everything else and carry a 90-day target timeline.
Each of these meeting types involves a preparation process that is months of scientific and regulatory work in the making. The CEO’s role in most FDA meetings is to receive briefings, provide strategic direction, and in some cases participate directly in high-stakes interactions. The EA’s role is to ensure the CEO’s scheduling and preparation infrastructure around these meetings is flawless.
This starts with the EA maintaining a current FDA meeting schedule: all confirmed meetings, all pending meeting requests, and the associated preparation milestones. When an FDA meeting date is confirmed, the EA immediately blocks the CEO’s calendar for the meeting itself plus dedicated pre-meeting briefing time. For major meetings, the EA schedules a series of preparation sessions in the weeks leading up to the meeting, ensuring the regulatory affairs team has scheduled time with the CEO to align on strategy, messaging, and anticipated agency questions.
Internal Regulatory Review Meetings
Beyond FDA interactions, the pharma CEO regularly participates in internal regulatory review meetings: program-level regulatory strategy reviews, regulatory risk assessments, submission readiness reviews, and advisory committee preparation sessions. The EA coordinates these meetings by working with the regulatory affairs leadership to align scheduling, distribute pre-read materials, and ensure the CEO receives a concise briefing document before each session.
The briefing document the EA prepares for regulatory review meetings follows a consistent format: current program status, key regulatory risks and mitigation strategies, decisions the CEO needs to make, and any upcoming FDA milestones. This consistency means the CEO can orient quickly, regardless of which program is under review.
Cross-Functional Regulatory Coordination Meetings
Regulatory strategy intersects with clinical development, medical affairs, legal, and commercial at multiple points. The EA coordinates the cross-functional regulatory coordination meetings where these teams align: regulatory-clinical interface meetings, labeling strategy sessions, risk management program reviews, and pre-submission alignment meetings.
For these cross-functional sessions, the EA manages a more complex scheduling challenge: multiple senior leaders with competing priorities. The EA maintains visibility into the relevant stakeholders’ calendars, proposes meeting windows, manages the confirming communication, and ensures all parties have relevant pre-read materials distributed in advance.
FDA Submission Tracking Workflows
The Submission Registry
A pharmaceutical company’s regulatory submission history is a strategic asset. Every IND, NDA, BLA, sNDA, or ANDA represents a major investment of resources and a critical milestone in the company’s pipeline. The EA maintains a submission registry that captures the current status of every active regulatory submission, organized by program and submission type.
For each submission, the registry tracks the submission date, the FDA’s assigned review division, the target action date (PDUFA date for NDAs/BLAs), any information requests or complete response letters received, and the current stage in the review cycle. This registry is not a replacement for the detailed submission management systems the regulatory affairs team maintains; it is a CEO-level view that gives the CEO current, accurate information on every active submission without requiring a deep dive into regulatory databases.
Milestone Tracking and Alert Systems
The most time-sensitive regulatory milestones have fixed statutory deadlines that cannot slip. PDUFA dates are public commitments. Clinical hold response windows have regulatory requirements. The EA builds an alert system that flags all upcoming statutory and self-imposed regulatory milestones at 90, 60, and 30 days out, ensuring the CEO and regulatory leadership have advance visibility to prepare appropriately.
This alert system feeds directly into the CEO’s regular check-ins with the head of regulatory affairs. The EA prepares a standing agenda item for these check-ins that reviews the milestone tracker and identifies any items that need CEO attention or escalation.
Complete Response Letter Management
A Complete Response Letter (CRL) from the FDA is among the highest-stakes regulatory events a company can face. It represents a rejection of the current submission with requirements for additional data, labeling revisions, or facility corrections before approval can be granted. The CEO’s response to a CRL, including how it is communicated to the board, investors, and employees, is a test of organizational leadership.
The EA supports CRL management by ensuring the CEO has immediate access to a complete briefing when a CRL is received, coordinating the emergency review meetings required to assess the FDA’s concerns, and helping the CEO prepare communications for the board and, where applicable, for public disclosure. The EA also tracks the CRL response timeline, ensuring the regulatory team’s resubmission planning has adequate CEO visibility and support.
Regulatory Team Coordination
CEO-Regulatory Affairs Leadership Interface
The relationship between the CEO and the head of regulatory affairs is a critical operational partnership. In most pharma companies, this means a Chief Regulatory Officer, VP of Regulatory Affairs, or Head of Regulatory. The EA coordinates this partnership by scheduling regular one-on-one meetings (typically biweekly or monthly), preparing briefing materials, tracking follow-up items, and ensuring information flows consistently between the CEO’s office and regulatory leadership.
For pharma CEOs who want a deeper framework for how to delegate regulatory decision-making while maintaining strategic oversight, this regulatory affairs delegation guide provides a practical model for structuring the CEO-regulatory team relationship.
Regulatory Affairs Calendar Management
The regulatory affairs function operates on multiple overlapping timelines: FDA submission deadlines, agency meeting schedules, post-approval commitment reporting windows, and internal regulatory milestone plans. The EA maintains a regulatory affairs calendar at the CEO level that captures all of these timelines in a single, current view.
This calendar is distinct from the internal project management systems the regulatory team uses. It is a CEO-level governance tool: showing the most important upcoming milestones across all programs, flagging conflicts or resource constraints, and providing the temporal context the CEO needs to make informed decisions about priorities and resource allocation.
Advisory Committee Preparation Coordination
For NDAs and BLAs subject to advisory committee review, the preparation process is extensive and multi-month. The EA coordinates the CEO’s involvement in advisory committee preparation: scheduling preparation sessions with the regulatory and medical affairs teams, ensuring the CEO has access to draft presentations and briefing documents, coordinating mock panel preparation if the CEO is participating, and managing logistics for the advisory committee meeting itself.
Advisory committee meetings are public events with significant strategic stakes. The EA also monitors the public docket for competitor advisory committee meetings that may signal FDA thinking on shared regulatory issues, and briefs the CEO accordingly.
Compliance Reporting to the Board
Regulatory Affairs in the Board Reporting Structure
The pharmaceutical company board has fiduciary responsibility over the company’s regulatory compliance. Directors need to understand the state of the regulatory portfolio, major upcoming milestones, significant risks, and any material developments with the FDA. At the same time, regulatory information in the board context must be translated from operational detail to strategic summary.
The EA coordinates the regulatory affairs component of board reporting by working with the head of regulatory affairs to compile the regulatory summary section of the board materials. This section typically covers the current regulatory portfolio overview, upcoming PDUFA dates and major milestones, any significant FDA communications, and the status of any post-approval commitments.
The EA ensures this section is formatted to the board materials template, reviewed by the CEO before the packet is finalized, and presented in language that gives directors the strategic context they need without requiring a deep background in regulatory science.
Audit Committee and Compliance Committee Reporting
For pharma companies with audit or compliance committees on the board, regulatory compliance reporting may appear at the committee level before or instead of the full board. The EA coordinates these committee-level reporting cycles: scheduling committee meetings, ensuring regulatory leadership has adequate lead time to prepare committee reports, and supporting the CEO’s preparation for committee-level regulatory discussions.
This committee coordination requires the EA to maintain a clear picture of what has been reported to which governance body and when, preventing gaps or redundancies in the board’s regulatory information diet.
Supporting the Regulatory Intelligence Function
FDA Guidance and Policy Tracking
FDA guidance documents, proposed rules, and policy statements directly affect the regulatory strategy of every pharmaceutical company. The EA supports the CEO’s regulatory intelligence function by maintaining a tracker of major FDA guidances relevant to the company’s programs, flagging new guidance documents in relevant therapeutic areas, and ensuring the regulatory team’s analysis of new guidances is routed to the CEO’s briefing materials.
This is not a function the EA performs independently. It is a coordination function: ensuring the regulatory team’s intelligence work surfaces to the CEO in a timely, organized way, rather than being buried in email or internal reports.
Competitive Regulatory Intelligence
The FDA’s public databases (Drugs@FDA, the FDA calendar, 483 observation databases, approval history) provide meaningful intelligence about competitor programs and FDA agency behavior. The EA supports competitive regulatory intelligence by coordinating regular briefings from the regulatory affairs team on competitor submissions, approvals, and FDA interactions relevant to the company’s market position.
For the CEO preparing to present competitive regulatory context to the board or investors, the EA ensures the most current and complete picture is available. The EA may also coordinate subscriptions to regulatory intelligence services (Informa, FDA News, the Pink Sheet) and ensure relevant alerts are routed to the CEO’s attention.
Building the Regulatory Oversight System
The Regulatory Affairs Dashboard
The most effective regulatory oversight systems surface the right information to the CEO through a structured, recurring dashboard: a one-to-two page document updated before every regulatory check-in that shows the current state of every program, every active submission, every upcoming milestone, and any emerging risks.
The EA builds and maintains this dashboard, working with regulatory affairs leadership to ensure accuracy and completeness. Over time, the dashboard format evolves to reflect the company’s specific portfolio and the CEO’s most important oversight priorities. A well-designed dashboard transforms regulatory oversight from an information-gathering task to a decision-support tool.
Pharma CEOs overseeing both regulatory and clinical development pipelines will find the coordination frameworks in this clinical trial delegation guide useful for structuring parallel oversight systems across the development function.
Integrating Regulatory and Commercial Timelines
Regulatory approval timelines directly drive commercial planning: launch preparation, market access strategy, sales force hiring, and commercial supply chain all depend on regulatory timing assumptions. The EA supports the CEO’s cross-functional oversight by ensuring the regulatory affairs calendar is integrated with the commercial planning calendar, and that any changes to regulatory timelines are immediately visible to the commercial leadership team.
This integration is a coordination function the EA manages between the regulatory affairs team and the commercial team, ensuring the CEO is not the sole information conduit between the two functions.
Conclusion
Pharma CEOs who invest in dedicated regulatory affairs coordination support are not simply gaining administrative convenience. They are building the oversight infrastructure that allows them to provide effective governance over the company’s most critical function. A skilled EA who maintains the regulatory calendar, coordinates FDA meeting preparation, tracks submission milestones, supports team coordination, and manages board-level regulatory reporting gives the CEO the visibility and bandwidth to lead regulatory strategy rather than manage regulatory administration. In an industry where regulatory outcomes are existential, that oversight system is a direct competitive asset.