Regulatory Strategy Oversight: What the Board Owns and What It Doesn't
Regulatory strategy is where a biopharma company's scientific ambitions collide with the institution that ultimately decides whether any of it reaches a patient. It is, in a real sense, the interface between what the company wants to be true and what a regulator will accept as proven. And yet on most clinical-stage boards, it is the single most under-governed area of the entire enterprise.
The pattern is familiar. The board engages deeply with the science, because the science is exciting and the founders love to talk about it. It engages deeply with financing, because the runway is always a live concern. It engages, eventually, with commercial strategy. But when the head of regulatory affairs presents, the room goes quiet in a particular way — not the quiet of close attention, but the quiet of directors who feel they lack the standing to ask questions. Regulatory gets treated as a technical function, a specialist domain, something the board ratifies rather than governs.
This is a serious mistake, and it is worth being precise about why. The regulatory pathway a company chooses is not a downstream execution detail. It determines what trials must be run, what those trials cost, how long they take, what the eventual label can claim, and therefore what the asset is ultimately worth. A company can have excellent science and still destroy enormous value through a poorly governed regulatory strategy. The board's job is not to design that strategy. But it is emphatically the board's job to ensure the strategy exists, is coherent, is stress-tested, and is revisited when the facts change.
This article is about drawing that line correctly — what the board owns in regulatory oversight, and what it should leave to management.
The Distinction That Governs Everything
Start with the boundary, because getting it wrong in either direction causes damage.
Management owns regulatory tactics: which specific studies to run, how to design a given protocol, how to respond to a particular agency question, who to bring to a meeting with the FDA or EMA, what to say in a briefing document. These are matters of professional expertise and operational execution. A board that tries to co-manage them is a board that has lost its way — substituting the judgment of generalist directors for the judgment of the specialists the company hired precisely to make these calls.
The board owns regulatory strategy — meaning the small number of high-level choices that shape the entire development program and cannot be reversed cheaply. Which indication to pursue first. Whether to pursue an accelerated or expedited pathway and what that commits the company to. Whether the endpoint the company is building its program around is one the agency will actually accept. What the regulatory basis for eventual approval will be, and how much risk is embedded in that basis. Whether to seek early agency input or proceed and hope.
The test is simple. If a decision, once made, locks the company into a costly path that is expensive or impossible to reverse, it is a strategic decision and the board should engage with it. If a decision can be adjusted next quarter without material consequence, it is tactical and belongs to management.
The failure mode boards fall into most often is not over-management — it is under-engagement dressed up as respect for expertise. A board that "defers to the regulatory team" on the question of whether the pivotal endpoint will be accepted by the agency is not being appropriately humble. It is abdicating one of the few decisions that will most determine whether the company succeeds.
What the Board Should Actually Ask
Boards do not need regulatory credentials to govern regulatory strategy well. They need a small set of questions asked consistently and answered honestly. The questions below are the ones that most reliably surface trouble before it becomes irreversible.
What is the regulatory basis for approval, and how much of it is settled versus assumed?
Every development program rests on a theory of how the drug will eventually be approved — which endpoints, in which population, on the strength of what evidence. Some elements of that theory are grounded in explicit agency guidance or prior precedent. Others are the company's own interpretation of what the agency will accept. The board needs to know which is which. The most dangerous programs are the ones where management has quietly convinced itself that an assumption is a fact. When a regulatory lead says "the agency will accept this endpoint," the right follow-up is: on what basis do we believe that — guidance, precedent, a meeting, or hope?
Have we asked the agency, or are we guessing?
Regulators offer structured opportunities for input — pre-IND meetings, end-of-Phase-2 meetings, scientific advice procedures in Europe, and various expedited-pathway interactions. These meetings are not free; they take time and consume management attention, and companies sometimes avoid them out of a fear of hearing bad news. That avoidance is exactly the behavior a board should be alert to. It is almost always cheaper to learn that the agency disagrees with your endpoint before you have run the pivotal trial than after. The board should understand what agency interactions have occurred, what the agency actually said, and what interactions are planned before the next irreversible commitment.
What did the agency actually say — and are we reading the minutes or the summary?
There is a recurring governance hazard here worth naming directly. Management presents the outcome of an agency meeting, and the presentation is upbeat: the meeting "went well." But agency feedback is frequently more equivocal than an enthusiastic internal summary conveys. Official minutes, when they exist, often contain caveats, cautions, and areas of disagreement that get smoothed over in the retelling. A board does not need to read every meeting minute. But on the pivotal interactions — the ones the whole program depends on — directors should ask to see the actual agency feedback, not just management's characterization of it. The gap between the two is where unpleasant surprises live.
What happens to the program if the agency says no?
Good regulatory governance means understanding the downside branch, not just the base case. If the accelerated pathway is denied, what is the fallback, and how much time and money does it cost? If the agency rejects the chosen endpoint at the end-of-Phase-2 meeting, does the program survive, and in what form? Boards that only ever see the intended path are not equipped to weigh the risk they are carrying. The point is not pessimism; it is knowing the shape of the tree.
Is our regulatory strategy consistent across jurisdictions, and have we thought about sequencing?
Companies developing in parallel across the FDA and EMA — and increasingly other agencies — face genuine strategic choices about sequencing, about which agency's requirements drive trial design, and about whether a strategy optimized for one market compromises another. These are strategic questions with real value implications, and they are easy to leave un-owned because no single functional lead is responsible for the whole picture. That gap is where the board earns its seat.
The Recurring Traps
A few specific pitfalls recur often enough across clinical-stage companies that they deserve to be named as standing risks rather than one-off problems.
Confusing a designation with an approval. Expedited-pathway designations — breakthrough, fast track, PRIME, and their equivalents — are valuable, and management is right to pursue them and right to be pleased when they are granted. But a designation is a commitment to closer engagement and potentially faster review; it is not a lowering of the evidentiary bar for approval, and it is emphatically not approval itself. Boards sometimes absorb the enthusiasm around a designation and quietly recalibrate their sense of program risk as though a hurdle has been cleared. The scientific and evidentiary requirements are, in most respects, unchanged. A designation is a faster road, not a shorter one.
Endpoint drift. Over the course of a long development program, the endpoint the company is building toward can shift — sometimes for good scientific reasons, sometimes because the original endpoint is looking harder to hit than expected. Each individual shift may be defensible. But the cumulative drift can leave the company pursuing an approval basis that no one on the board consciously signed off on, and that the agency has never actually endorsed. The board should periodically ask whether the endpoint the company is running its pivotal program on is still the endpoint the agency agreed to, and still the endpoint that supports a commercially meaningful label.
Over-reliance on a single regulatory voice. In smaller companies, regulatory strategy often lives in the head of one experienced person — sometimes an internal lead, sometimes a consultant. That concentration is efficient, but it means the board is effectively taking one individual's judgment on trust, with no independent check. This does not require a large regulatory function. It does mean that on the pivotal calls, the board should have a mechanism — an independent advisor, a second opinion, a specialized committee member — to pressure-test the strategy against a second qualified view.
The label nobody modeled. The regulatory pathway determines the eventual label, and the label determines what the company can market and what payers will reimburse. It is possible to run a technically successful program that yields an approval with a label so narrow, or so hedged, that the commercial value is a fraction of what the founders imagined. Regulatory and commercial strategy are frequently governed in separate conversations, by separate committees, on separate agendas. The board is often the only body positioned to connect them — to ask whether the label the regulatory strategy is pointed at is a label the commercial strategy can actually build on.
How to Structure the Oversight
Governance of regulatory strategy does not require a standing regulatory committee at most clinical-stage companies, and creating heavy process where light process will do is its own error. What it requires is a deliberate cadence and a few structural habits.
At minimum, regulatory strategy should be a substantive, standalone board agenda item at defined inflection points — not folded into a general clinical-development update where it competes for attention with enrollment metrics and gets three minutes at the end. The natural cadence is to give it real time before each major agency interaction and after each one, and before any decision that locks in the pivotal program design.
The board should ensure it has access to genuine regulatory expertise that is not solely the management team it is meant to be overseeing. On some boards this is a director with regulatory depth. On others it is a named external advisor the board can consult independently. The specific mechanism matters less than the principle: the board should not be wholly dependent on the same people whose strategy it is evaluating for its understanding of whether that strategy is sound.
And the board should insist, on the pivotal interactions, on seeing primary agency feedback rather than only management's synthesis of it. This is not an expression of distrust in management. It is the same discipline a board applies everywhere else — reading the actual clinical data rather than the summary slide, seeing the actual contract rather than the deal summary. Regulatory feedback deserves the same treatment precisely because so much rides on it.
The Underlying Principle
Regulatory strategy sits in an awkward governance position. It is too technical for boards to feel confident engaging, and too consequential for them to responsibly ignore. The resolution is not for directors to become regulatory experts. It is for them to understand which regulatory questions are strategic — which ones shape the whole program and cannot be cheaply reversed — and to govern those with the same seriousness they bring to financing and scientific decisions.
The regulator is, in the end, the customer whose approval the entire enterprise is organized to earn. A board that engages closely with the science and the money but treats the pathway to approval as a technical afterthought is governing everything except the thing that determines whether any of it matters. The strategy belongs to management. Ensuring there is a coherent, tested, honestly-understood strategy belongs to the board.
Lawrence Fine is CEO of AGCP Farmacêuticos and has advised on licensing, regulatory, and partnership strategy across the pharmaceutical and advanced materials sectors.