Introduction
Attending a regulatory affairs conference builds knowledge and connections. Speaking at one builds a career. Presenters get remembered, get approached by recruiters and business development contacts who might otherwise never have found them, and get positioned, fairly or not, as a recognized voice in their area of the field. Yet most regulatory professionals never submit a speaking proposal, either because they assume selection is reserved for senior executives and agency officials, or because they simply do not know how the process works. Neither assumption holds up well on closer look.
Conference programming committees, whether at RAPS Convergence, DIA's global and regional meetings, TOPRA events, or the many smaller therapeutic-area and regional conferences that fill out the calendar, are chronically short on strong proposals that offer a specific, practical angle rather than a generic overview. That gap is an opportunity for regulatory professionals at any level who understand what these committees are actually looking for.
Who Actually Gets Selected
It is a persistent myth that conference speaking slots go almost exclusively to department heads, agency officials, and well-known consultants. Those speakers fill keynotes and panel discussions, but the bulk of a typical multi-track conference, breakout sessions, case study presentations, workshop tracks, is built from proposals submitted by working regulatory professionals at every level of seniority. A regulatory affairs manager or senior specialist with a genuinely specific project or lesson to share is often a stronger candidate for these sessions than a more senior executive offering broad, familiar commentary.
What programming committees are actually optimizing for is attendee value: will people who sit in this session leave knowing something they did not know before, ideally something they can apply. Seniority is a weak proxy for that. A specific, well-documented project, a novel submission strategy, a hard-won lesson from a difficult agency interaction, a first-of-its-kind approval, is a much stronger signal.
Programming committees are also typically made up of volunteer members of the professional association running the conference, often working regulatory professionals themselves rather than paid event staff. That matters for how proposals get evaluated: a committee reviewing submissions understands, from direct professional experience, when a proposal reflects real hands-on work versus when it has been dressed up to sound more substantial than it is. That same familiarity works in a submitter's favor when the proposal is genuinely grounded in real project experience, because it reads as credible to reviewers who know what that experience actually looks like from the inside.
What Makes a Proposal Get Picked
Most rejected proposals fail for the same handful of reasons, and most accepted ones share the same handful of strengths.
- Specificity beats scope. "An Overview of MDR Transition Strategy" is a weak proposal because it promises nothing the audience could not get from a guidance document. "How We Restructured Our Technical Documentation Process to Cut MDR Review Cycles by Six Weeks" is a strong one, because it promises a concrete, transferable lesson.
- A real case, not a hypothetical. Proposals built around an actual project, program, or submission, even a partial or anonymized one where confidentiality requires it, read as more credible and more useful than proposals built around general principles.
- A clear takeaway, stated early. Strong proposals tell the reviewer, in the first sentence or two, exactly what the audience will walk away able to do or understand. Committees reading dozens or hundreds of submissions reward proposals that make this easy to find.
- Fit with the specific conference and track. A proposal written generically and submitted to five different conferences tends to read as generic. Reviewers can usually tell when a submission was tailored to their event's actual themes and audience versus recycled from somewhere else.
- A realistic scope for the session length. Proposals that try to cover too much in a 30 or 45-minute slot read as unfocused. Committees favor proposals that clearly fit their time allotment with room for questions.
Where the Opportunities Actually Are
Large flagship conferences like RAPS Convergence and DIA's major annual meetings are the most visible targets, but they are also the most competitive, with the highest volume of submissions per available slot. Regional and therapeutic-area-specific conferences, smaller device-focused events, local RAPS chapter meetings, and niche therapeutic conferences, tend to have meaningfully better acceptance odds and are often a more realistic starting point for a first speaking credit. A well-received session at a smaller regional event is also a legitimate credential to reference in a future proposal to a larger conference.
Webinars hosted by professional associations or industry publications are a lower-stakes entry point still, often with a shorter proposal process and less competition, and they build the same core skill, structuring and delivering a session, without the pressure of a large in-person audience.
Internal company events, cross-functional lunch-and-learns, or a company's own regulatory training curriculum are worth considering too, even though they are not external speaking credits in the formal sense. Presenting a well-structured session internally first is a low-risk way to test a topic's clarity and pacing before adapting it into an external proposal, and it often surfaces gaps in the material, a step that seemed obvious to the presenter but confused the audience, before those gaps show up in front of a room of strangers at an actual conference.
Building the Track Record That Gets You In
Selection committees, especially at larger conferences, do weigh past speaking experience, which creates a real chicken-and-egg problem for first-time applicants. The practical way around it is to start smaller and build deliberately: a local RAPS chapter presentation, an internal company training turned into an external webinar, a co-presenting slot alongside a more established colleague or consultant who is already speaking regularly. Each of these builds both the track record a proposal can reference and, just as important, real practice at the mechanics of preparing and delivering a session.
It also helps to watch for calls for proposals well before they close. Most major conferences publish their call for proposals six to nine months ahead of the event, with submission windows that often run eight to twelve weeks. Missing that window because a proposal was not ready is one of the more avoidable reasons regulatory professionals miss out on opportunities they were genuinely qualified for.
Getting Your Employer's Support
Speaking at an external conference on company time, and sometimes representing content drawn from company projects, usually requires internal sign-off, and it is worth approaching that conversation deliberately rather than as an afterthought once a proposal is already accepted. Framing the request around what the company gets, visibility for the organization, professional development for the employee, and a credible external validation of the team's work, tends to land better than framing it purely as a personal opportunity. Legal and communications teams at larger companies often have an established review process for external speaking content; building in time for that review before a submission deadline, rather than scrambling afterward, avoids a common last-minute problem where an accepted proposal has to be withdrawn or significantly altered because the underlying content could not clear internal review in time.
Smaller companies without a formal review process still benefit from a quick conversation with a manager or the head of regulatory before submitting, both to confirm the specific project details are shareable and to make sure a manager is not blindsided by public visibility of a project they did not know was being presented externally. That conversation is also, in a quieter way, useful career signaling: it puts a manager on notice that this employee is actively building external visibility, which tends to help rather than hurt when promotion and development conversations happen later.
Preparing the Actual Session
Getting a proposal accepted is only the first step. Conference audiences, and reviewers evaluating speakers for future events, notice the difference between a session that is read from dense slides and one that is genuinely delivered as a conversation with the room. Building in real time for rehearsal, ideally in front of at least one honest colleague who will flag unclear sections or a pace that is too fast for the material, makes a measurable difference in how a session is received. It is also worth over-preparing for the question and answer portion specifically; audience questions at regulatory conferences are often sharper and more specific than the prepared content anticipates, and a speaker who can field them confidently leaves a stronger impression than one who covers the prepared material well but gets visibly thrown by questions.
Conclusion
Speaking at a regulatory affairs conference is far more accessible than most working professionals assume, and the selection process rewards specificity and real project experience more than seniority or title. A well-scoped proposal built around an actual case, submitted to the right conference and track, with a clear, upfront statement of what the audience will walk away with, has a genuinely competitive shot even from a first-time submitter. For regulatory professionals looking to build visibility in the field, tracking upcoming calls for proposals and drafting that first specific, well-scoped session idea is a concrete, achievable next step, not a distant career milestone reserved for someone more senior.