Briefing Books, Question Lists, and FDA-Facing Materials

6.1 The Role of the Briefing Book in FDA Decision-Making

The briefing book is not a data dump, a marketing document, or a compressed version of the full regulatory submission. It is a focused decision document. Its purpose is to provide FDA with the information needed to evaluate specific sponsor questions in the context of product development. The document should help reviewers understand what the sponsor is asking, why the issue matters, what evidence supports the sponsor’s position, and what decision will be made after the meeting.

Primary role: The briefing book should equip FDA reviewers to provide clear, actionable feedback on the sponsor’s defined questions before the next development or submission decision is made.

FDA reviewers typically have limited time to assess the meeting package. They may be reviewing multiple programs, handling formal submissions, responding to internal consultations, and preparing preliminary comments. The sponsor should therefore make the reviewer’s task easier. The briefing book should be organized, concise, transparent, and traceable. It should not force FDA to search through appendices to infer the sponsor’s position or reconstruct the logic behind a question.

The briefing book also shapes the tone of the interaction. When the package is clear, balanced, and credible, it signals that the sponsor is disciplined and prepared. When the package is vague, overly promotional, inconsistent, or poorly referenced, it signals risk. FDA may respond more cautiously if the evidence does not support the sponsor’s conclusion, if the question is not answerable, or if the package appears to avoid difficult issues.

The best briefing books are written from the reviewer’s perspective. They anticipate what the agency needs to know, what concerns the agency may have, and where the sponsor’s evidence may be vulnerable. They present the development program honestly, including limitations, uncertainties, and risk mitigations. This does not mean the sponsor should weaken its position. It means the sponsor should defend its position with evidence rather than rhetoric.

The document also serves an internal function. Preparing a briefing book forces the sponsor to align across clinical, nonclinical, CMC, regulatory, safety, statistics, quality, labeling, and executive leadership. If internal contradictions exist, the briefing book process will surface them. If questions are not tied to decisions, the writing process will expose that gap. If data are not ready, the package will become unstable. For this reason, briefing book development should be treated as a strategic workstream, not a medical writing task alone.

6.2 Structuring Background, Rationale, Data Summaries, and Sponsor Positions

A strong briefing book has a simple internal logic. It begins with context, narrows to the issue, presents relevant evidence, states the sponsor position, and asks a specific question. This sequence should be repeated across the package. Reviewers should never have to ask, “Why is this information here?” or “What does the sponsor want the FDA to conclude?”

Background: The background section should describe the product, indication, mechanism, development stage, prior FDA interactions, completed studies, planned next milestone, and reason for the meeting. It should be concise but sufficient. The goal is to orient the reviewer, not to retell the entire development history.

The background should include the target indication and patient population, current development status, key completed studies, relevant safety experience, and the decision that the meeting is intended to support. If the product has a novel modality, special designation, accelerated pathway consideration, combination-product feature, platform component, or unusual manufacturing issue, that context should be introduced early. The reviewer should understand why the meeting is being requested and why the questions matter now.

Rationale: The rationale section should explain why the sponsor’s proposed approach is scientifically, clinically, operationally, and regulatorily reasonable. It should connect data to decisions. For example, if the sponsor proposes a Phase 3 endpoint, the rationale should connect disease burden, mechanism, Phase 2 results, clinical meaningfulness, measurement reliability, and labeling implications. If the sponsor proposes a starting dose, the rationale should connect nonclinical findings, exposure margins, pharmacology, safety considerations, and clinical monitoring.

Rationale should not be confused with advocacy. Advocacy says, “This is the best path because we prefer it.” Rationale says, “This is the proposed path because the available evidence supports it, the alternatives have been considered, and the residual risks can be managed.” FDA-facing rationale should be precise, transparent, and supported by data.

Data summaries: Data should be summarized at the level needed to answer the question. A briefing book should not include every table from every study. It should include the analyses, figures, and summaries that directly support the sponsor’s position. Each data display should have a purpose. If a table does not help FDA evaluate a question, it belongs in an appendix or should be removed.

Data summaries should also be balanced. If a Phase 2 result is positive overall but inconsistent across subgroups, the package should acknowledge that. If safety follow-up is limited, the package should say so. If a CMC process change introduces comparability risk, the package should explain the risk and the mitigation plan. Selective presentation may seem useful in the short term, but it reduces credibility and can lead FDA to question the entire package.

Sponsor positions: Every major question should include a clear sponsor position. The position should state what the sponsor proposes to do and why. It should be placed close to the question, not buried several pages earlier. FDA should be able to see the question, the sponsor’s proposed approach, and the supporting logic without having to assemble the argument independently.

A practical structure for each major issue is as follows:

• Issue: The specific development, clinical, nonclinical, CMC, safety, statistical, or submission question requiring FDA feedback.
• Context: The minimum background FDA needs to understand the issue.
• Evidence: The relevant data, analyses, precedents, guidance considerations, or prior FDA advice.
• Sponsor position: The proposed approach and the reason the sponsor believes it is justified.
• Question: The specific request for FDA agreement, comment, or clarification.

This structure creates discipline. It prevents the package from becoming a collection of disconnected sections and helps every reviewer understand the decision logic. It also supports the live meeting because the sponsor can use the same issue-context-evidence-position-question sequence when answering FDA follow-up questions.

6.3 Writing Clear, Answerable, and Strategically Sequenced Questions

The question list is the spine of the briefing book. If the questions are weak, the package will struggle no matter how polished the writing is. A strong question is specific, answerable, decision-linked, and supported by a clear sponsor position. It tells the FDA what feedback is needed and why that feedback matters.

Clear question: A clear question asks one primary thing, uses precise language, identifies the sponsor’s proposed approach, and avoids ambiguity about the requested FDA response.

Questions should avoid broad formulations such as “Does FDA have any comments on our program?” or “Does the FDA agree with our overall approach?” These questions may produce general comments, but they rarely produce decision-quality feedback. Better questions focus on a specific element of the plan. For example, the sponsor may ask whether the proposed 12-week primary endpoint assessment is acceptable to support the intended indication, whether the planned safety database is adequate for the proposed chronic-use population, or whether the proposed comparability strategy is sufficient to bridge clinical and commercial material.

Answerable question: An answerable question gives FDA enough context and evidence to respond. If the sponsor asks FDA to agree with a plan but does not provide the data or rationale needed to evaluate it, the likely response will be conditional, cautious, or noncommittal.

Each question should be tested before submission. Can the FDA answer this question based on the package? Does the question ask for feedback FDA can reasonably provide at this stage? Is the sponsor’s position clear? Would an agreement, disagreement, or request for additional information change the development plan? If not, the question should be rewritten or removed.

Question sequencing also matters. The list should follow the logic of the decision. Foundational questions should come before dependent questions. For example, in an End-of-Phase 2 meeting, the indication and population question may need to come before the endpoint question, which may come before the statistical analysis and safety database questions. In a Pre-NDA meeting, the submission content question may come before integrated summaries, labeling, REMS, and advisory committee topics. Good sequencing helps FDA reviewers see the architecture of the sponsor’s strategy.

Strategic sequence: Questions should be ordered so that FDA can follow the decision logic from the development objective to the specific design, evidence, safety, CMC, or submission issue.

The sponsor should also manage the number of questions. A long question list often signals a lack of prioritization. FDA meeting time is limited, and preliminary responses may be more useful when the questions are focused. The sponsor should distinguish between questions that are essential for the next decision, questions that can be handled through other channels, and questions that can wait for a later interaction.

Sub-questions require caution. A question with six subparts may appear to be one question, but it behaves like six. It may overload the package and make it difficult for FDA to provide complete feedback. If multiple subparts are necessary, they should be tightly related and organized in a way that allows FDA to respond efficiently. The sponsor should avoid hiding unrelated issues under one umbrella question.

The best question lists are written through multiple rounds. The first draft captures issues. The second draft ties issues to decisions. The third draft sharpens sponsor positions. The final draft removes anything that is not necessary. This process requires regulatory leadership and cross-functional discipline. It should not be delegated entirely to writing support or assembled at the end of package development.

6.4 Managing Appendices, References, Tables, and Cross-Functional Review

Supporting materials can strengthen a briefing book or bury it. Appendices, references, tables, figures, and listings are useful when they improve traceability and allow the main text to remain concise. They become a problem when they are used to avoid making decisions about what matters. FDA should not need to search the appendix to understand the sponsor’s argument.

Appendices: Appendices should contain supporting detail, not the core argument. If information is essential to answer a question, the main text should summarize it clearly and direct FDA to the appendix for additional detail. If information is merely background, it should be included only if it helps reviewers understand the issue.

Appendices should be carefully labeled and cross-referenced. Each appendix should have a clear purpose, and the main text should point to it precisely. Generic references such as “see appendix” are less useful than specific references to a particular appendix, table, or figure. Poor cross-referencing creates a reviewer burden and can undermine confidence in the package.

References: References should support the sponsor’s rationale without overwhelming the package. Relevant FDA guidance, scientific literature, precedent, and prior agency advice can be valuable, but they should be used selectively. A long reference list does not compensate for weak reasoning. The sponsor should explain how the reference supports the position rather than simply attaching citations.

Tables and figures: Tables and figures should be designed for decision-making. A good table compares options, summarizes key results, explains exposure, shows safety events, or clarifies CMC readiness. A poor table copies excessive detail from a study report without explaining why it matters. Every table should have a clear title, appropriate footnotes, defined abbreviations, and a short interpretation in the text.

Cross-functional review is where many briefing books lose quality. Different functions may revise sections to emphasize their own priorities, leading to repetition, inconsistent terminology, conflicting numbers, or uneven tone. Medical writing can improve clarity, but it cannot resolve strategic disagreement. Regulatory strategy should own the integrated logic of the document and ensure that all sections support the meeting objective.

Cross-functional review: The review process should confirm scientific accuracy, regulatory consistency, data traceability, sponsor-position alignment, and readiness for FDA interpretation.

The review process should be staged. Early review should focus on the meeting objective, question list, and sponsor positions. Middle review should focus on evidence, section logic, and consistency across functions. Late review should focus on quality control, formatting, references, cross-links, and submission readiness. Late strategic rewrites should be avoided unless a material issue has been identified. If leadership waits until the final version to challenge the questions, the timeline and package quality will suffer.

Version control is essential. The team should maintain one master question list, one decision log, one comment-resolution process, and one accountable owner for final integration. Without this discipline, teams may continue debating old versions, numbers may drift across sections, and comments may be resolved inconsistently. FDA-facing materials require document control, not informal collaboration alone.

6.5 Briefing Book and Q-List Quality Checklist

The final quality review should test whether the package is ready for FDA, not merely whether it is formatted. The most important question is whether the FDA can understand the issue, evaluate the evidence, and answer the question efficiently. The following checklist can be used before final approval.

Strategic Quality

• Meeting objective: The purpose of the meeting is clear and linked to a specific development or submission decision.
• Decision relevance: Every question supports a decision, risk reduction, or material clarification needed before the next milestone.
• Sponsor position: Each question has a clear proposed approach that the sponsor is prepared to defend.
• Prior advice: The package reflects relevant prior FDA feedback and explains any change in sponsor direction.
• Scope discipline: The package does not include topics that are unrelated, premature, or unnecessary for the meeting objective.

Question List Quality

• Question clarity: Each question asks one primary issue and uses precise terminology.
• Answerability: FDA has enough information in the package to provide meaningful feedback.
• Strategic sequencing: Questions are ordered according to the logic of the decision and grouped by discipline where appropriate.
• Sub-question control: Sub-questions are limited, related, and not used to hide unrelated topics.
• Action implication: The team knows what it will do if FDA agrees, disagrees, or provides conditional feedback.

Evidence and Writing Quality

• Data relevance: Tables, figures, and summaries directly support the questions and sponsor positions.
• Balanced presentation: Limitations, uncertainties, and unfavorable findings are acknowledged where material.
• Traceability: Key claims can be traced to data, analyses, references, prior advice, or source documents.
• Consistency: Numbers, terminology, study names, endpoints, dosing language, and assumptions are consistent across sections.
• Reviewer usability: The package is organized so FDA can quickly locate the question, rationale, evidence, and sponsor position.

Operational Quality

• Appendix control: Appendices are relevant, labeled, cross-referenced, and not used as a substitute for clear main-text logic.
• Reference control: Guidance, literature, and precedent references are current, relevant, and accurately represented.
• Quality control: Formatting, hyperlinks, page numbers, abbreviations, tables, figures, and internal references have been checked.
• Approval record: Functional leads and leadership have approved the final questions and sponsor positions.
• Preliminary response plan: The team has a process to triage FDA preliminary comments and revise the live meeting agenda.

The briefing book and question list are the sponsor’s first opportunity to conduct the meeting well. In many cases, FDA’s preliminary comments will be shaped almost entirely by the written package. If the package is clear, focused, and evidence-based, the sponsor improves the likelihood of receiving useful feedback. If the package is diffuse or unsupported, the sponsor may receive responses that are cautious, conditional, or incomplete.

The discipline of briefing book development should therefore begin early. The team should align on the meeting objective, draft the question list, define sponsor positions, identify required evidence, and create a realistic review timeline before writing begins in earnest. The package should then be built around the questions, not around functional preferences or historical templates. A template can help with structure, but it cannot substitute for judgment.

The practical standard is not perfection. The standard is decision usefulness. A good briefing book enables FDA to understand the sponsor’s proposed path and provide feedback that can be acted on. It makes the sponsor’s logic visible, acknowledges uncertainty, and focuses discussion on the issues that matter most. In the FDA meeting strategy, writing quality is not cosmetic. It is strategic. The document determines what FDA sees, how FDA prepares, and what kind of conversation becomes possible.