How to read an FDA advisory committee briefing

Days before an FDA advisory committee meets to discuss a drug or device, two documents usually appear on FDA’s website: one written by the review division, one written by the sponsor. Both describe the same data. They are worth reading as a pair, not separately, because the gaps between them — not either document alone — are often where the real disagreement about a product sits.

Two documents, not one

FDA’s briefing document is written by the review division and lays out its preliminary read of the data — efficacy and safety findings for a drug, or performance and bench/clinical data for a device — along with any concerns the reviewers want the committee to weigh in on. For many advisory committee meetings the sponsor also submits its own briefing document, covering the same underlying data from its own perspective. Reading only one is reading half the argument. The value is in the comparison: where do the two documents emphasize the same evidence differently, and where does one raise a concern the other doesn’t mention at all? That gap is usually a preview of what the committee’s discussion will actually turn on.

Read the questions before the narrative

Buried in FDA’s briefing document, usually toward the end, are the specific discussion and voting questions FDA is putting to the committee. These are worth reading first, not last, because they tell you exactly what FDA has and hasn’t already made up its mind about. A question asking the committee to weigh in on the overall benefit-risk balance signals a genuinely open call; a question narrowly scoped to one subgroup or one endpoint signals FDA has already reached a view on everything else. Advisory committee meetings typically include an open public hearing segment as well, the same public-comment mechanic covered in how to get value from an FDA public meeting — a chance for outside stakeholders to speak directly to the questions FDA has posed.

An advisory committee meeting is one of the few points in FDA’s review process that happens in public, with the underlying disagreement laid out on the page for anyone to read. That is worth taking advantage of, whether you are tracking a specific product or just trying to understand how FDA reasons through a hard call — the same kind of close reading that pays off with a De Novo classification order or a Complete Response Letter, except here you get to watch the reasoning happen before the outcome is decided.