How to work a regulatory conference

The difference between attending a conference and working one is invisible on the expense report and unmistakable a month later. Two colleagues go to the same event: one comes home with a tote bag and a vague sense of having been busy; the other comes home with three answers their program needed, five contacts who reply to their emails, and a one-page brief the whole team reads. Same registration fee. The difference was decided mostly before the flight, and the rest of it in the hallway.

Before the flight: triage like an editor

Print the agenda — or open it properly, once, with a pen mentality — and sort every session into three piles. Must: it speaks directly to the program question that justified this trip; you will sit front-third and take notes. Should: useful if nothing better happens, including the better thing being a conversation. Skip: everything you already know, everything you can read later in slides, and every panel whose title promises a fireside chat. Be ruthless: at a good conference the musts are four or five sessions a day at most.

Then do the counterintuitive part: leave a third of each day empty. An agenda packed wall-to-wall guarantees you will be walking into a room while the most useful conversation of the week is happening outside it. The empty third is not slack; it is inventory you will spend on people.

Book the two or three meetings that matter before you go. The consultant you have been meaning to evaluate, the counterpart at the company one year ahead of yours on the same pathway, the organizer of the working group you keep almost joining — all of them are easier to secure two weeks out than by badge-spotting in a crowd of thousands.

In the room

Sit where you can leave politely — aisle, back half — because the correct response to a session that turns out to be a sales pitch is to leave and spend the hour better. Take decision notes, not transcription: the slides will be published, so the only notes worth taking are the ones the slides will not contain — what the speaker said under questioning, what they declined to say, and the sentence that changes something at work on Monday. One page per day, three headings: changes our work, changes our dates, people to follow up. That page is the trip report writing itself.

When a regulator is at the podium, the questions are the session. Ask something specific and answerable — a named guidance, a named scenario, a genuine fork in interpretation — and you will get thinking on the record that is not written anywhere. Ask “what keeps you up at night” and you will get the same answer the last three conferences got. If your question is really about your own submission, it is a meeting request, not a question; agency staff at conferences are usually generous about pointing you at the right process, and never going to review your file from the floor.

The hallway is the conference

The sessions are the excuse; the concentration of your professional world in one building is the product. Working the hallway does not require charisma — regulatory affairs is not a profession of natural card-spammers, and the good news is that card-spamming does not work anyway. What works is specificity. The opening line is the session you are both walking out of: “did you buy their timeline?” beats any introduction that starts with your job title. Coffee queues, lunch tables with one open seat, the ten minutes before a session starts — these outperform receptions, where the acoustics and the alcohol both work against a substantive sentence.

Keep the arithmetic humane: five real conversations a day beat forty exchanged cards. A real conversation ends with a specific reason to follow up — a document one of you will send, an introduction one of you will make, a question one of you will chase. Write the reason on the back of the card or in your phone in the moment; by Thursday the cards are archaeology.

The evening events are optional, and the mornings are not. Skip the third reception without guilt; do not skip breakfast, which is the same room at a tenth of the volume.

The expo floor, used correctly

The exhibition floor is market research that someone else paid to assemble. Walk it once, deliberately, with a question — who are the three credible vendors for the capability we will need next year? — and collect the shortlist, not the merchandise. Every scanned badge is a sales sequence you are opting into, so scan where you mean it. Fifteen focused minutes at the right three booths is due diligence; two aimless hours is how the tote bag fills.

The 48-hour rule

Conference value has a half-life measured in days. Within 48 hours of landing — while the notes still mean something — two things ship. The trip report: one page, from the daily decision-notes, sent to the team you promised it to; what changes our work, what changes our dates, who we now know. And the follow-ups: one line each, referencing the actual conversation and doing the specific thing you promised — the document, the introduction, the answer. A follow-up that could have been sent by anyone lands like it was sent by no one; the one that quotes Tuesday’s hallway lands.

Then the last habit, the one this site exists for: before you close the laptop, put next year’s edition on the calendar — from the organizer’s own dates, not the banner in the expo hall. Dates move. Checking them at source is a two-minute discipline that has saved more flights than any tip above.