Nobody hands out a promotion for showing up reliably. In regulatory affairs, where most of the real work is a judgment call that happens out of anyone else’s sight, the case for your next title has to be made, not assumed — and the person best positioned to make it is you, because you were the only one in the room for all of it.
Track the evidence as it happens
The same running record that makes a regulatory decision log worth keeping is raw material for a promotion case, if you let it be. A call you made independently, a problem you caught before it became one, a program or submission you carried beyond what your title assumes, a junior colleague you trained, a moment you briefed someone senior directly instead of through your manager — each is a single dated line when it happens and a vague impression six months later if it isn’t written down. Keep both purposes in the same habit; the log doesn’t know which conversation it’s for yet.
Learn what the next level actually means
Ask your manager plainly what the next title means in scope, not adjectives. Does a senior or lead-level regulatory professional own submission strategy without a second set of eyes, manage a person, or represent the team in front of leadership unaccompanied? Get a concrete answer, then hold your tracked evidence against it directly rather than against a general sense that you’ve “been doing more.” The jump from doing the work to being accountable for someone else’s is its own transition, covered from the other side in moving from individual contributor to RA manager — worth reading before you ask, so you know what you’re actually asking for.
Where this goes wrong
Waiting to be noticed
Good regulatory work is often invisible on purpose — a clean submission looks uneventful precisely because someone caught the problems early. Nobody upstream is compiling your case for you.
Asking without evidence, in the middle of something else
A request dropped into an unrelated conversation, with nothing written down, is easy for a manager to defer and hard for you to follow up on specifically.
Treating a vague “not yet” as a final answer
If the reasons given aren’t specific, ask what would need to be true for the answer to change. That list, not the yes or no, is the actual output of the conversation.
None of this guarantees a yes. It does mean that when the conversation happens, it’s a decision made on the specifics instead of a guess made on how visible you managed to be that quarter — which is, not coincidentally, the same standard you’d want an FDA reviewer applying to your own submission.
Sources & further reading
- Regulatory Academy — The case for keeping a regulatory decision log regulatoryacademy.com
- Regulatory Academy — Moving from individual contributor to RA manager regulatoryacademy.com
- Regulatory Academy — The regulatory affairs career ladder, explained regulatoryacademy.com
- Regulatory Academy — Your first regulatory affairs performance review regulatoryacademy.com
This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.