The volunteer job inside the conference

Somewhere between accepting the invitation and packing the bag, a board seat, a chapter office, or a standing-committee assignment quietly turns one trip into two. The society scheduled its governance business for the same week as the flagship conference on purpose — it's the one week a geographically scattered group of volunteers is reliably in the same building — and that business rarely shows up on the public agenda you registered against. If you've said yes to one of these roles, the itinerary your employer approved and the actual week ahead of you are not quite the same document.

The meeting isn't on the public agenda

A society's board or chapter-leadership meeting is organizational business, not programming, so it typically doesn't appear in the same published schedule as the sessions everyone else is choosing between. It shows up instead as a separate calendar invite from the society itself, often timed for the morning before the exhibit hall opens or folded into the first evening, competing directly with the welcome reception you'd otherwise be working. The only reliable fix is checking that invite against the actual conference dates as soon as it arrives, the same discipline this site applies to every listed event: confirm the specific time against the organizer's own communication, close to the date, rather than assuming it slots neatly around a public program built for a different audience. A flagship week like RAPS Convergence or the ISPE Annual Meeting runs enough parallel governance activity alongside its public sessions that assuming the two schedules won't collide is usually wrong.

Two jobs, one week

Once the governance meeting has a confirmed slot, the honest next step is deciding on purpose what it's replacing, rather than discovering the trade-off in real time. A three-hour committee session on a conference's second morning is a real cost measured in sessions you won't sit in and hallway conversations you won't have — and it's a cost worth paying deliberately for a role you value, not one that quietly erodes the trip your employer thought they were funding. Program-committee reviewing is a lighter version of the same tension, mostly absorbed in the weeks before the conference rather than during it; board and chapter governance is heavier precisely because it competes for the same days you're also supposed to be attending.

What your employer is actually paying for

The business case that got this trip approved almost certainly described a conference, not a volunteer governance commitment layered on top of one — and most managers are perfectly reasonable about the difference once it's named instead of assumed. If the role adds a travel day, an extra night's hotel, or meaningfully reduces the session-hours the trip was justified on, say so before you book anything, the same way a good approval conversation already asks you to name what the trip is actually buying. Societies vary widely in what they cover for volunteer leadership — some offset travel for board members, most do not — and that's worth a direct question to the society, not a guess folded into your own expense report.

Deciding whether to say yes again

A volunteer role that felt like an honor the first year can start to feel like an obligation by the third, especially once it's quietly costing you the parts of the conference you originally valued the trip for. That's worth an honest annual check, the same one worth applying to any standing commitment on the calendar: is the role still worth what it's trading away, or has it become the reason the week no longer feels like the event you signed up to attend? Neither answer is wrong, but only one of them is a decision instead of an accident.