The Company's Voice to Regulators: Managing Meetings and Commitments as a Liaison

Introduction

Most descriptions of regulatory affairs jobs focus on writing: putting together a submission, drafting a response to a deficiency letter, building the argument for why a product should be approved. Less attention goes to a role that sits closer to the relationship itself — the person whose job is to manage how the company actually interacts with FDA, EMA, or another health authority as an ongoing, structured relationship rather than a series of one-off documents. At many companies that person carries the title Regulatory Affairs Liaison, or Health Authority Liaison, or the responsibility is folded into a senior strategist's role without a distinct title at all. Whatever it is called, the work is real, it is distinct from pure submission writing, and it is worth understanding on its own terms.

This is not a beginner role. It tends to go to people who already understand the submission process cold and have developed judgment about how regulators think, because the liaison function is fundamentally about managing a relationship under scrutiny, not producing a single deliverable. Getting it right builds trust that pays off across years of interactions with the same review division; getting it wrong can create friction that outlasts any one submission.

What the Title Actually Covers

The liaison function shows up under different labels depending on the company. Large pharmaceutical companies with dedicated global regulatory affairs organizations sometimes have a named Health Authority Liaison role, distinct from the regulatory strategist who owns the overall program plan. At mid-size and smaller companies, the same responsibilities usually sit inside a regulatory affairs manager or director's broader portfolio, handled alongside strategy and submission work rather than as a separate job. In either case, the core responsibility is the same: owning the mechanics of how the company requests, prepares for, conducts, and follows up on interactions with a health authority.

It is useful to distinguish this from the regulatory strategist role, which focuses on deciding what the company's regulatory position and pathway should be. The liaison function is more operational and relational — it is less about deciding what to say and more about making sure the right people say it, at the right meeting, with the right supporting material, and that everything the agency asked for afterward actually gets tracked down and delivered.

The Core Job: Owning the Health Authority Relationship

The center of the role is managing meeting requests and the flow of formal correspondence with a health authority. In the US, this means understanding the different meeting types available under FDA's formal meeting framework — Type A, B, C, and other more specialized designations depending on the program — and knowing which one fits a given need, what information the request has to include, and what timeline to expect. In the EU, the equivalent might be a scientific advice request to EMA or a national competent authority, each with its own procedural requirements. Getting a meeting request wrong, or filing it late relative to a submission timeline, can cost a program months.

Once a meeting is granted, the liaison typically owns the logistics and the document package: coordinating internal subject matter experts to draft briefing materials, making sure the package goes out within whatever window the agency requires, and managing the internal review and sign-off process so the final package actually reflects what the company wants to say. None of this is glamorous, but a late or incomplete briefing package can cause a meeting to be rescheduled or narrowed in scope, which is a real cost to a development timeline.

Meeting Prep Is Where the Real Work Happens

Getting the logistics right is necessary but not sufficient. The more demanding part of the job is preparing the internal team for the meeting itself: running mock sessions where subject matter experts practice answering the kinds of questions a reviewer is likely to ask, tightening presentation materials so they lead with the point rather than burying it, and making sure the company walks in with a clear, prioritized list of what it actually needs from the meeting. A liaison who has sat across from a given review division before brings pattern recognition that a first-timer doesn't have: which reviewers push hardest on a particular kind of data gap, which topics tend to eat the clock, what tone lands well versus what reads as evasive.

During the meeting itself, the liaison is often the person managing the room — making sure the agenda stays on track, that questions get routed to the right internal expert, and that someone is capturing accurate notes on commitments and action items, because what gets agreed to verbally in that room becomes the basis for a formal meeting minutes exchange afterward, and any mismatch between the company's understanding and the agency's official minutes has to be caught and resolved quickly.

Tracking Commitments and Correspondence

A health authority relationship generates an ongoing paper trail: meeting minutes, information requests, commitments the company made during a review, post-marketing requirements, and periodic correspondence that has nothing to do with a specific submission event. Someone has to own tracking all of it — what was promised, what the deadline is, and who internally is accountable for delivering it. In larger organizations this tracking often lives in a dedicated regulatory information system; in smaller ones it may be a carefully maintained spreadsheet. Either way, losing track of an open commitment is one of the more damaging things that can happen to a company's standing with a review division, because it signals that the company isn't managing its own regulatory obligations carefully.

Cross-Functional Coordination

Because health authority meetings and correspondence touch nearly every functional area of a development program, the liaison spends much of the job coordinating across teams: clinical for data interpretation and study design questions, CMC for manufacturing and quality topics, biostatistics for analysis plans, and often legal or corporate communications when a topic has commercial or public sensitivity. The liaison is rarely the technical expert in the room on any one of these topics, but is usually the person who has to translate between functions, keep the internal team aligned on a single message, and make sure a technical disagreement between two departments doesn't surface for the first time in front of the regulator.

Regulatory Intelligence as Ongoing Input

A good liaison also functions as an intelligence source for the rest of the organization, staying current on how a particular review division's expectations are evolving — through public guidance documents, published meeting minutes from other companies' programs where available, conference presentations by agency staff, and patterns noticed across the company's own recent interactions. That intelligence feeds back into how future meeting requests and briefing packages get framed, and it is part of what makes an experienced liaison more valuable over time than someone new to a given therapeutic area or device category.

A Realistic Day in the Life

A typical day might start with tracking down an internal expert who owes input on a briefing package due to the agency in a week, followed by a status call with a cross-functional team to confirm who is presenting which section at an upcoming meeting. Midday often includes drafting or reviewing correspondence — a response to an information request, or a formal meeting request letter that needs to go out within a specific window relative to a submission date. Afternoons frequently bring a mock meeting rehearsal, or a debrief call after a real one, capturing action items while they are still fresh and routing them to the right owners. Woven through all of it is the quieter administrative work of keeping the commitment tracker current, which is unglamorous but is exactly the kind of work that prevents expensive surprises later.

Skills That Matter

Strong liaisons combine a solid grounding in regulatory procedure with skills that are more about people than paperwork: the ability to read a room and adjust in real time, patience for detailed administrative tracking, and enough credibility across clinical, CMC, and quality functions that subject matter experts trust the liaison's read on how to frame something for a regulator. Composure under pressure matters too — health authority meetings can surface unexpected pushback, and the liaison is often the person who has to keep the room from getting defensive or derailed.

Common Misconceptions

People sometimes assume this is an entry-level coordination job, essentially scheduling meetings. In practice, the judgment calls involved — how to frame a request, when to push back on an internal team's proposed messaging, how to read whether a meeting is going well or badly in real time — require real regulatory experience, which is why the role usually goes to someone several years into a regulatory affairs career rather than someone just starting out. Another misconception is that the job is the same across companies; a liaison at a large pharmaceutical company with a mature, dedicated function looks quite different from someone doing the same work as one part of a broader regulatory affairs role at a smaller biotech, where the scope is similar but the resources and internal support are much thinner.

Where the Role Leads

Time spent as a liaison builds a specific kind of judgment that transfers well into regulatory affairs leadership: a working sense of how regulators actually think and respond, not just what the guidance documents say, plus strong cross-functional relationships across a development organization. People who spend a few years in this work often move into regulatory strategy leadership, program-level regulatory affairs management, or head of regulatory affairs roles where that relationship judgment becomes a core part of the job rather than a specialized piece of it.

Conclusion

The regulatory affairs liaison role rarely gets its own line in an org chart at smaller companies, and even where it does, it is easy to underestimate from the outside. But the quality of a company's relationship with its health authority — whether meetings run smoothly, whether commitments get tracked and delivered, whether the agency sees a company as organized and straightforward to work with — often comes down to how well this function is being done. For anyone who enjoys the operational and relational side of regulatory work as much as the technical writing, it is a role worth understanding and, for the right person, worth pursuing.