Not the one your company sent this year

Most regulatory teams get one seat at the conference everyone actually wants to attend, and most years the arithmetic that decides who fills it has nothing to do with a ranking of who deserves it most. It has to do with whose project is at the stage where the agenda matters most right now, who covered the equivalent trip last year, and who has a submission deadline the week after that makes travel impossible regardless of merit. None of that is visible from the outside. What is visible is the outcome: the seat went to someone else, and you are reading their trip report instead of writing one. The feeling is real. The useful response to it is a different question than the one the feeling suggests.

What the decision was probably weighing

The one-page business case that got this year's trip approved almost certainly named a specific project question and a specific person positioned to act on the answer — that is what a signable case actually looks like, and it rarely doubles as a ranking of everyone who might have gotten something out of the room. If your project was between milestones, or your submission deadline landed inside the conference week, you were a weaker case this cycle on pure logistics, independent of standing or performance. Worth confirming before assuming otherwise: ask whoever decided what the case for this year actually was. The answer is frequently more boring, and less personal, than the version that forms on its own when nobody explains it.

What's still recoverable from a trip you didn't take

A surprising share of a conference's value travels secondhand if someone asks for it deliberately instead of waiting for a casual summary. Ask the colleague who went for a structured version of what they brought back, not just a hallway “it was good” — a real readout built around decisions rather than a chronological trip diary, and their actual notes, which usually contain more than made it into the summary they gave everyone else. If the event offers recorded sessions or a webinar companion to its flagship program, that is a second, independent path into the same content, worth checking on the organizer's own page rather than assuming it doesn't exist. None of this fully substitutes for the room. Most of it is still worth more than nothing, and almost nobody asks for it this specifically.

The ask that actually changes next year

Resenting this year's decision rarely changes next year's; naming a specific future case usually does. Rather than raising it as a grievance, raise it as a plan: the conference year is usually planned as a whole, which means the window to argue for a specific seat is months before the registration deadline, not after someone else's badge has already arrived. Name the project question this seat would answer for you, specifically, the way any other business case has to, and ask what would need to be true by registration time for that to be the stronger case next cycle. A manager who can see a concrete argument coming has an easier time building next year's budget around it than one fielding a vague request to be “considered more.”

When it's a pattern, not a year

One cycle going to someone else is logistics. The same person getting every seat for several cycles running, independent of whose project actually needs the room, is a different and more honest conversation to have directly with whoever is making the call — not a grievance filed at a conference, but a straightforward question about how the rotation is supposed to work and whether it's working that way in practice. Most managers would rather hear that question plainly than have it simmer unasked for another year.

One habit either way

Whether the seat is yours this year or someone else's, the date and venue worth building any of the above around should come from the organizer's own page, checked close to when it matters — not from last year's dates, a sponsor's save-the-date email, or a colleague's memory of when it usually runs.