'Femi Fajimi

Writing Briefing Documents for Scientific Advice Meetings: A Step-by-Step Guide Using Azidomyxin 

By Femi Fajimi | 08 August 2025 

(Educational content. Azidomyxin is a fictional investigational product.) 

Introduction: What Is a Briefing Document and Why Does It Matter? 

In the pharmaceutical development lifecycle, the path from laboratory discovery to patient access is highly regulated. At key decision points, companies engage in structured, early-stage dialogues with regulatory authorities, most notably the European Medicines Agency (EMA) and the US Food and Drug Administration (FDA), to align their development plans with regulatory expectations. 

These engagements occur through scientific advice meetings in the EU and through Type B and Type C meetings in the US. Under the FDA framework, Type B meetings include critical milestones such as the Pre-Investigational New Drug (Pre-IND) meeting, End-of-Phase 2 (EOP2) meeting, and Pre-New Drug Application (Pre-NDA) or Biologics License Application (Pre-BLA) meeting. These meetings allow sponsors to confirm that their planned approach to clinical trials, data generation, and regulatory submissions is robust and aligned with agency expectations. 

In all cases, these interactions are underpinned by a central document: the briefing document. Far more than a background dossier, a briefing document is a strategic communication tool. It presents the sponsor’s development rationale, summarises key data, and, most importantly, poses precise questions to obtain clear regulatory feedback. Whether the goal is to seek input on clinical trial design, request a Paediatric Investigation Plan (PIP) waiver, or clarify the acceptability of a proposed surrogate endpoint, the briefing document shapes the dialogue between sponsor and regulator and, by extension, the future of the product. 

In this Post, I’ll walk you through each section of a briefing document, using Azidomyxin, a fictional new antibiotic under development for drug-resistant hospital-acquired pneumonia, to illustrate how writers structure content, formulate questions, and ensure regulatory clarity. 

About the Case Study Drug: Azidomyxin (AZD-143) 

Azidomyxin (AZD-143) is a novel intravenous antibacterial agent designed to target multidrug-resistant (MDR) strains of Klebsiella pneumoniae and Acinetobacter baumannii. It is currently in Phase II development, and the sponsor is seeking scientific advice from the EMA, including: 

• A Paediatric Investigation Plan (PIP) waiver 

• Guidance on a planned Phase III study design 

• Suitability of a composite primary endpoint involving clinical cure and microbiological eradication 

The fictional scenario mirrors realistic needs in anti-infective drug development, making it suitable to demonstrate how a scientific advice briefing document is constructed. 

Key Regulatory Context 

Before we begin, it’s helpful to understand the types of meetings and agencies for which briefing documents are written: 

Agency	Meeting Type	Purpose
EMA	Scientific Advice	Early feedback on development plans, PIP requests, study designs
EMA (COMP)	Protocol Assistance	Specific to orphan drugs; includes incentives and scientific advice
FDA	Type B Meetings	Pre-IND, End-of-Phase 2, Pre-NDA/BLA meetings
FDA	Type C Meetings	Any other discussions needed during development
EMA PDCO	PIP Waiver Request	Justification to exclude paediatric population when not appropriate

Each requires a well-prepared briefing package, typically submitted 30+ days prior to the meeting, and must follow agency-specific templates and expectations. 

Sample Structure of a Scientific Advice Briefing Document (EMA Format) 

Let’s now explore the standard structure, section-by-section, with full explanations and examples from the Azidomyxin case. 

Cover Page 

Purpose: 

Sets the administrative details- product name, procedure type, sponsor, submission date, and intended Agency. 

Example: 

Product Name: Azidomyxin (AZD-143) 

Applicant: NovaXen Pharmaceuticals Ltd 

Meeting Type: EMA Scientific Advice + PIP Waiver 

Regulatory Authority: (e.g. EMA or FDA) 

Submission Date: 10 August 2025 

Proposed Meeting Date: 20 September 2025 

Tip: Always check the latest EMA pre-submission guidance for required formatting. 

Table of Contents 

Purpose: 

Ensures clarity and easy navigation. Include all annexes. 

• Page numbers 

• Main headings and subheadings 

• Annexes and appendices are listed separately 

Introduction and Background 

Purpose: 

This section introduces the product and sets the strategic and regulatory context for the briefing document. It outlines why the meeting is being requested and what type of guidance the sponsor seeks from the regulatory Authority. It helps the reviewers understand the stage of development, the regulatory objective, and the specific decisions that the Agency’s feedback will inform. 

This section is typically brief but must be clear, focused, and informative as it shapes how the Agency approaches your questions and prepares internally for the meeting. 

What to include: 

• The development stage of Azidomyxin (e.g. entering Phase II) 

• The purpose of the meeting (e.g. confirm primary endpoint, request PIP waiver) 

• What decisions or guidance does the sponsor need to proceed 

• Therapeutic area and unmet need 

• Mechanism of action 

• Summary of clinical and non-clinical data to date 

• Orphan designation or fast-track status (if applicable) 

Example from Azidomyxin: 

Azidomyxin (AZD-143) is a novel, narrow-spectrum antibacterial compound under development by NovaXen Biotherapeutics for the treatment of hospital-acquired pneumonia (HAP) caused by multidrug-resistant (MDR) Gram-negative pathogens, including Pseudomonas aeruginosa and Klebsiella pneumoniae. 

The molecule inhibits lipopolysaccharide biosynthesis, resulting in potent bactericidal activity. To date, Phase I studies have demonstrated acceptable safety and tolerability in healthy volunteers, while a Phase IIa proof-of-concept study in ventilated patients with HAP has shown preliminary signals of efficacy in bacterial clearance and clinical improvement. 

NovaXen is preparing to initiate a pivotal Phase III trial and requests a scientific advice meeting with the EMA to obtain guidance on the proposed composite primary endpoint, statistical assumptions, and safety monitoring strategy. In parallel, NovaXen seeks confirmation of eligibility for a Paediatric Investigation Plan (PIP) waiver, based on a well-justified argument that paediatric HAP due to the target pathogens is extremely rare, with limited clinical relevance for the studied indication. 

Why This Matters 

This section ensures that agency reviewers understand the strategic intent behind the meeting and the scope of the advice sought. It allows regulatory teams to assign appropriate expertise in preparation for the meeting and enables focused responses to sponsor questions. 

A weak or vague Purpose section can lead to misaligned expectations or unnecessary clarification requests. A strong one fosters clarity, alignment, and regulatory rapport. 

Summary of Questions for Regulatory Advice 

Purpose: 

It is one of the most essential sections. Offers a concise but thorough description of the product and its development history. 

How to frame questions: 

• Be focused, unambiguous, and directly related to decision-making. 

• Use numbering (e.g. Q1, Q2). 

• Support each question with a brief rationale. 

Includes: 

• Drug class and mechanism of action (e.g. Azidomyxin is a synthetic lipopeptide targeting MDR Gram-negative bacteria) 

• Therapeutic indication (e.g. complicated urinary tract infections) 

• Summary of pharmacology, nonclinical findings, and prior clinical data (e.g. Phase I safety, PK) 

• Regulatory milestones achieved to date (e.g. orphan status, scientific advice history) 

This is not a full IB – keep it brief, strategic, and relevant to the questions being asked. 

Summary of Clinical and Nonclinical Data 

Purpose: Presents key data that support the sponsor’s development strategy and inform the questions posed. 

Includes: 

• Nonclinical data (e.g. toxicity profile, NOAELs, in vivo efficacy) 

• Clinical pharmacology (PK/PD findings, bioavailability) 

• Phase I/II results (e.g. safety signals, tolerability, preliminary efficacy) 

• Special populations or unmet medical need (if applicable) 

Use summary tables and bullet points. Ensure all data supports the development rationale. 

Regulatory Status and Development Plan 

Purpose: Clarifies the intended regulatory path and plans for upcoming submissions. 

Includes: 

• Planned Phase II/III trials (design, endpoints, comparators) 

• PIP waiver or deferral plan (if paediatric requirements apply) 

• Global development considerations (e.g. US–EU alignment) 

• Future regulatory interactions (Pre-NDA, MAA timelines) 

It helps the Agency contextualise your questions. Be transparent about uncertainties. 

Questions for the Agency 

Purpose: The heart of the document. What guidance is being sought and why? 

For each question: 

1. Question: Clearly-worded, binary where possible (e.g. Does the CHMP agree that the proposed primary endpoint is acceptable?) 

2. Background: What the question relates to (e.g. target population, statistical design) 

3. Sponsor’s Position: The rationale for the approach taken 

4. Supporting Data: Any relevant results, tables, or evidence 

5. Impact on Development: How the answer will influence clinical or regulatory strategy 

Example: 

Q1: Does the EMA agree that the proposed primary endpoint of microbiological eradication at Day 7 is appropriate for the Phase III trial of Azidomyxin in cUTI? 

• Background: Standard endpoints in cUTI trials typically include microbiological and clinical response. 

• Position: The sponsor proposes eradication at Day 7 to capture early therapeutic success and reduce confounding by later antibiotic use. 

• Supporting Data: In Phase IIa, early eradication correlated strongly with symptom resolution (see Table 2). 

• Impact: Endpoint alignment is critical for powering and finalising the Phase III protocol. 

• Keep questions focused. Don’t include multiple issues in one question. Don’t ask “open” questions without justification. 

Paediatric Development (if applicable) 

Purpose: 

Required for EMA if requesting a waiver or deferral under the Paediatric Regulation. 

Content: 

• Justification for waiver 

• Epidemiological data 

• Lack of pharmacological rationale in children 

Example: 

MDR-HAP is extremely rare in the paediatric population and associated with different pathogens. No evidence supports extrapolation of adult data. NovaXen therefore requests a full PIP waiver under Article 11(1)(b). 

Appendices / Annexes 

Purpose: Supports the main document without crowding it with raw data. 

May include: 

• Protocol synopsis or draft protocol 

• Tables and figures referenced in the main text 

• Summary of product characteristics (if available) 

• PIP waiver request letter or form 

• Relevant literature or preclinical reports (if needed) 

Refer to these clearly in the body of the briefing document. Use headers like “Appendix A – Draft Protocol” 

Final Thoughts: What Makes a Strong Briefing Document? 

Crafting an effective briefing document means more than just compiling data. It requires: 

• Clarity: Questions must be specific and decision-focused. 

• Structure: Follow agency guidance precisely. 

• Balance: Provide enough data to justify positions without overwhelming reviewers. 

• Tone: Maintain a professional, objective, and concise narrative. 

• Traceability: Any data referenced should match CSR, IB, or protocol documents 

References 

1. ICH M4E(R2) – Common Technical Document for the Registration of Pharmaceuticals for Human Use: Efficacy – Structure and Content of Clinical Overview and Clinical Summary 

URL: https://database.ich.org/sites/default/files/M4E_R2__Guideline.pdf 

2. ICH E3 – Structure and Content of Clinical Study Reports 

URL: https://database.ich.org/sites/default/files/E3_Guideline.pdf 

3. EMA Scientific Advice Guidance – Scientific advice and protocol assistance for medicinal products 

URL: https://www.ema.europa.eu/en/human-regulatory/research-development/scientific-advice-protocol-assistance 

4. EMA Pre-submission Guidance for Scientific Advice 

5. EMA Guideline on the Evaluation of Medicinal Products Indicated for Treatment of Bacterial Infections (for anti-infective development context) 

6. EMA Guidance on Paediatric Investigation Plans (PIP) 

URL: https://www.ema.europa.eu/en/human-regulatory/research-development/paediatric-medicines/paediatric-investigation-plans 

7. FDA Guidance on Formal Meetings Between the FDA and Sponsors or Applicants of PDUFA Products (Type A, B, and C Meetings) 

URL: https://www.fda.gov/media/109951/download 

8. FDA Guidance – Briefing Package Content for Pre-IND, EOP2, and Pre-NDA/BLA Meetings 

9. ScienceDocs – Regulatory Briefing Documents Overview 

URL: https://www.sciencedocs.com/regulatory-briefing-documents 

⚠️ Disclaimer 

Azidomyxin is a fictional antibiotic created for educational purposes only. This post is intended to support learning among early-career regulatory writers and does not represent real data, company strategies, or regulatory interactions