Introduction
Regulatory affairs is a field where the work is visible to the people directly downstream of it—your manager, your project team, maybe a health authority reviewer—but often invisible to whoever actually approves a title change or a salary band adjustment. That gap is why so many regulatory professionals wait for a promotion to be offered rather than asking for one, and why so many of those same professionals end up leaving for a title bump elsewhere instead of getting it where they are. Asking for a promotion is a skill, and like most skills in this field, it rewards preparation over instinct. This is a working guide to building that case: what to document along the way, how to frame the conversation, and what typically happens on the other side of the table.
Why Promotions in Regulatory Affairs Move Slower Than You'd Like
Regulatory teams tend to be lean relative to the scope of what they cover, and promotions usually require more than a manager's enthusiasm—they require a budget line, a leveling review, sometimes HR calibration against other functions, and in larger companies a business case that gets discussed above your manager's head. None of that means the promotion isn't deserved; it means the timeline is often longer and less transparent than in functions with faster headcount cycles. Understanding this up front changes how you approach the ask. You are not persuading one person in one conversation. You are giving your manager the ammunition they need to make your case in rooms you are not in.
Start With the Job Description of the Role Above You
Before you build any kind of case, get specific about what the next level actually requires. If your company has a formal leveling framework or career ladder, read it closely—not the marketing language, the actual competencies listed for the next title. If no formal framework exists, look at internal postings for that level, or ask your manager directly what separates a Senior Regulatory Affairs Specialist from a Regulatory Affairs Manager, or an Associate from a Specialist, in your organization specifically. Titles are not standardized across companies, so the gap between your current role and the next one is a local question, not an industry one. Once you know the actual bar, you can evaluate honestly whether you are already clearing it, close to it, or building toward it.
Document Impact, Not Just Activity
The single most common mistake in a promotion case is listing what you did instead of what changed because you did it. "Managed the 510(k) submission for Project X" is activity. "Led the 510(k) submission for Project X, which cleared FDA review without an additional information request, keeping the launch on the original timeline" is impact. Keep a running record—a simple document you update monthly, not something you reconstruct from memory the week before your review—of submissions you owned, timelines you protected or recovered, cross-functional problems you solved, and instances where you operated above your current title: mentoring someone more junior, representing regulatory in a meeting your manager would normally attend, catching a labeling or CMC issue before it became expensive. Specificity is what turns a self-assessment from a list of duties into evidence. A tracking document doesn't need to be elaborate—a running list with a date, a two-line description, and the outcome is enough to be useful a year later, when memory has flattened three different submissions into a vague sense that the year was busy. The habit matters more than the format: reconstructing a year of impact from scratch in the days before a review almost always undersells the work, because the details that made something genuinely hard—the shortened timeline, the reviewer question that required a same-day turnaround, the labeling discrepancy caught before it shipped—are exactly the details that fade first from memory.
Build Your Case Before You Need It
The strongest promotion cases are built over two or three performance cycles, not assembled in the two weeks before a compensation review. If your company has a mid-year check-in, use it to flag the trajectory explicitly: tell your manager you are working toward the next level and ask what they would need to see from you to support that case when the time comes. This does two things. It puts the conversation on the calendar rather than making it a surprise, and it gives your manager a chance to tell you about gaps you might not see—maybe you're strong on submission execution but haven't yet led a health authority interaction solo, or you haven't had visibility with a particular product line. Better to learn that a year out than in the meeting where you expected an answer.
Timing the Conversation
Formal promotions are usually tied to a company's compensation cycle, which most life sciences companies run annually and some run twice a year. Raising the topic cold in the middle of an unrelated week rarely lands well, not because the ask is wrong but because your manager has no budget conversation to attach it to yet. The better move is to raise it early enough that it can be built into the cycle—typically several months ahead of the review period, not the week before. If you are not sure when that cycle happens, ask HR or your manager directly; it is a reasonable question, not a presumptuous one.
What to Actually Say
When the conversation happens, lead with the evidence, not the ask. A useful structure: state clearly that you'd like to talk about your growth toward the next level, walk through two or three concrete examples of impact at that level, ask directly what your manager sees as the gap between where you are and where you're asking to be, and listen more than you talk in response. Avoid comparing yourself to specific peers by name—it puts your manager in an awkward position and shifts the conversation away from your own case. Avoid leading with a competing offer as leverage unless it is real and you are genuinely prepared to take it; using a bluff here damages trust in a field where reputations travel between a small number of companies.
If the Answer Is Not Yet
A "not yet" is not a rejection if it comes with specifics. Ask directly: what would need to be true in six months, or at the next cycle, for this to be a yes? Get it in writing if you can, even informally in a follow-up email summarizing what was discussed. If the answer is vague—"just keep doing good work"—push gently for something more concrete; vague feedback is often a sign the case genuinely isn't there yet rather than a sign your manager is withholding information. If you get a clear, specific answer and you meet it and are still told no, that is meaningful information about whether this company will ever level you the way you deserve, and it is reasonable to start looking outward at that point.
What Managers Are Weighing on Their Side
It helps to understand the constraints your manager is operating under. Promotion budgets are often capped as a percentage of the team, meaning your manager may be choosing between advocating for you or for a colleague in the same cycle. Leveling frameworks in larger pharma and device companies frequently require sign-off from HR business partners who have never met you and are calibrating your case against people in entirely different functions. None of this is a reason to stop asking. It is a reason to make your manager's job easier by giving them a case they can carry into those rooms without having to reconstruct it themselves.
Common Missteps That Undercut a Strong Case
A few patterns show up often enough to name directly. Framing the ask around tenure—"I've been here three years"—rather than around scope of impact tends to fall flat, because time served isn't what leveling frameworks measure. Asking in the same breath as a complaint about workload, even a legitimate one, muddies the message and makes it easy for a manager to address the workload issue instead of the promotion. Going over your manager's head to skip-level without giving your manager a chance to advocate for you first usually backfires, even when the skip-level conversation feels productive in the moment; it signals you don't trust the person who will have to defend the case in rooms you can't see. And treating a single strong project as the entire case, rather than a pattern of performance at the next level sustained across several months, tends to read as one good quarter rather than readiness for a permanent step up.
Conclusion
A promotion in regulatory affairs is rarely handed out for tenure alone, and it rarely arrives without someone asking. The professionals who move up fastest tend to be the ones who treat the case-building as ongoing work: they track impact as it happens, understand the actual bar for the next level in their specific organization, and raise the conversation early enough that it can be planned for rather than reacted to. None of that guarantees a yes on the first ask. It does mean that when the answer eventually comes, it will be based on evidence you controlled rather than visibility you hoped for.