An FDA advisory committee’s vote gets the headline. The transcript is where the real signal is — the specific concerns individual panelists raised, the way FDA worded its voting questions, and the parts of the discussion that never make it into a press release.

What’s actually in the transcript

An advisory committee meeting follows a fairly fixed order, and the transcript records all of it: conflict-of-interest disclosures, FDA’s own presentation of the data and its questions for the panel, a sponsor presentation where one applies, an open public hearing, committee discussion, and finally the voting questions and the vote itself. The meeting page on FDA’s advisory committee calendar hosts the transcript alongside the roster and the briefing document — read the briefing first for the technical background, then the transcript for what the panel actually did with it.

On a first pass, the disclosures and administrative housekeeping are safe to skim. What isn’t safe to skim is the committee discussion that happens after the presentations and before the vote — that’s where individual members raise the specific concerns the vote count alone won’t show you. A panel can vote fifteen to two in favor and still spend twenty minutes on a subgroup FDA ends up asking more questions about later.

Read the voting questions like a specification

FDA staff write the voting questions, and the wording is deliberate. A question scoped to a specific subpopulation, a specific claim, or a specific comparator tells you where FDA thinks the evidence is genuinely uncertain; a broad, single up-or-down question suggests the agency sees fewer open issues. Compare the question’s scope against the sponsor’s original proposed indications — a question narrower than what was proposed is often the earliest public signal of where a restriction or a request for more data is headed.

This is the same primary-source habit that pays off when you’re reading a complete response letter or a De Novo order months later: the transcript is where the agency’s specific concerns get spoken out loud, before they get written into a letter in far more compressed language.

Where this goes wrong

Reading only the topline vote and skipping the discussion

The count tells you what happened; the discussion tells you why, and why is what predicts the next letter.

Treating open public hearing testimony as expert evidence

It’s public comment, often from patients and advocacy groups, and it’s valuable context — but it doesn’t carry the same evidentiary weight as the committee’s own technical deliberation.

Assuming FDA will follow the panel’s recommendation

Advisory committees are advisory. FDA has cleared or approved products after a negative vote and issued complete response letters after a positive one; plan around the substance of the discussion, not just the count.

None of this is difficult to find — every word of it is posted for free on FDA’s own site. The skill isn’t access, it’s the habit of reading the primary transcript instead of somebody else’s summary of it, the same discipline that separates reading a regulation from reading a plain-language explainer someone wrote about it.

Sources & further reading

  1. 21 CFR Part 14 — Public Hearing Before a Public Advisory Committee ecfr.gov
  2. FDA — Advisory Committees fda.gov
  3. Regulatory Academy — How to Read an FDA Advisory Committee Briefing regulatoryacademy.com
  4. Regulatory Academy — How to Get Value from an FDA Public Meeting 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.