The question left unanswered

You asked the question you prepared for, got to the mic in the time the moderator allotted, and the answer that came back wasn't really an answer: “we're aware of that concern,” or “we'll take that back to the team,” or a pivot straight to the next hand in line. This happens often enough at public meetings and advisory committee sessions that it's worth planning for in advance, the same way you'd plan the question itself. A non-answer in the room isn't necessarily a dead end — it's a signal about where the real answer lives, and that's usually somewhere other than the microphone you were just standing at.

Write down exactly what you heard, not your summary of it

The first thing worth doing, before the next session starts and the exact wording blurs, is capturing what was actually said at the mic — the real phrase, not your paraphrase of it. “We're exploring that” and “we have no plans to pursue that” are both non-answers in the moment, but they're different non-answers, and the specific qualifier chosen usually isn't an accident. If the meeting is being transcribed or webcast — common at a formal advisory committee session — the exact wording will eventually be a matter of record; your own notes, taken immediately, are what you have before that record catches up.

Check whether the question belongs in the official record

At a formal federal meeting with a public comment period or an open docket, the mic exchange is often the informal version of a question you can also submit through the formal channel — and the formal channel is the one that actually requires a response on the record, where the hallway exchange doesn't. If the meeting you're at runs on a public docket, a written comment restating the question, with enough specificity that it can't be deflected the same way twice, is frequently a stronger path than trying again at next year's session. Even people who never approach the microphone can use this path; it doesn't require having asked the original question yourself.

A direct follow-up, addressed to a person, not a podium

Away from the formal docket, the most reliable path back to an unanswered question is often the least dramatic: a short, specific follow-up email addressed to someone by name, sent soon after the session while the exchange is still fresh for them too. This works better than it sounds, mostly because very few people in the room actually send it — most treat the deflection as the final word rather than the opening move it usually is. Keep it narrow: restate the specific question, note that it wasn't fully addressed at the mic, and ask for the answer in writing rather than relitigating the whole exchange.

When the honest answer is that it's genuinely too early

Not every deflection is evasive. Sometimes “we're still evaluating that” is the accurate answer, delivered at a moment when the agency or organization genuinely hasn't reached a position yet, and pressing harder in the room won't produce one. The useful move there isn't a sharper follow-up email; it's noting the date and checking back at the next natural point in that process — the next public meeting, the next guidance cycle, the next docket deadline — rather than assuming silence between now and then means the question was dropped.

Whichever path you take, confirm the mechanics — where the docket lives, whether comments are still open, when the next session on the same topic is scheduled — against the organizer's or agency's own page before you act on it. A deflected question is annoying; acting on stale instructions for how to follow it up is worse.