💬 Pre-Submission Meeting Strategy
Strategic guide for engaging regulatory agencies before formal NAMs submissions to align expectations and identify data requirements
← Back to Qualification Pathways
Overview
Pre-submission meetings represent a critical early engagement with regulatory agencies before committing resources to full validation programs. For NAMs technologies, pre-submission meetings with FDA, EMA, and other regulators can significantly improve approval probability, reduce development timelines, and prevent costly misdirections. These meetings allow technology developers to present their methods, receive regulatory feedback on scientific approach, and obtain written guidance on data requirements—all before investing in expensive validation studies.
Strategic use of pre-submission meetings increases approval probability from 40-60% (case-by-case submissions without pre-submission) to 75-85% (FDA ISTAND with pre-submission). This represents the highest-ROI regulatory activity for companies developing NAMs technologies.
Types of Pre-Submission Meetings
FDA Type C Meetings (CDER Biomarker Qualification Team)
Focused meetings with FDA CDER specifically addressing novel methodologies and Drug Development Tools. Type C meetings are dedicated to discussing scientific approach and data strategy. FDA provides written responses within 14 days outlining recommendations, data requirements, and pathway guidance. Most valuable for FDA ISTAND or case-by-case qualification pathways.
EMA Scientific Advice Meetings
Formal scientific advice procedure (different from informal pre-submission) where EMA SAWP committee provides written opinion on proposed validation approach. Meetings are structured with formal agenda and documented advice. Available for organizations developing NAMs technologies for EU regulatory jurisdiction. Results in formal written guidance applicable to CTAs and MAAs.
ICH Pre-Submission Meetings
Coordinated meetings with multiple regulatory agencies (FDA, EMA, PMDA, others) simultaneously addressing novel methodologies and global regulatory strategies. Available for truly innovative NAMs technologies with global development scope. Provides harmonized regulatory feedback across jurisdictions.
Informal Pre-Submission Meetings
Preliminary meetings before formal Type C or Scientific Advice requests. Used to assess regulatory interest, obtain feedback on proposed approach, and determine optimal timing/pathway. Informal meetings do not generate official FDA/EMA written responses but provide valuable guidance for strategy refinement.
When to Request a Pre-Submission Meeting
Timing Consideration: Request pre-submission meeting when you have preliminary data on 20-50 compounds demonstrating proof-of-concept, but BEFORE investing $500K+ in large-scale validation. This allows regulatory guidance to shape validation strategy.
Too Early (Avoid): Don't request meetings with only 5-10 compound data or theoretical concepts. FDA requires sufficient preliminary evidence of method feasibility and biological relevance to provide meaningful feedback.
Too Late (Ineffective): Don't wait until you've completed full validation studies. By then, it's too late to implement regulatory feedback. Pre-submission feedback should actively shape validation design.
Pre-Submission Meeting Preparation Package
FDA and EMA expect comprehensive preparation packages of 30-50 pages containing:
Executive Summary (2-3 pages)
- Method name, technology platform, and intended use
- Unmet regulatory need being addressed
- Key preliminary data findings
- Proposed validation pathway and timeline
- Specific questions for FDA/EMA discussion
Scientific Rationale (8-12 pages)
- Biological relevance and mechanism of action
- Literature support for predictive value
- Comparison with existing testing approaches
- Advantages and limitations of method
- Target patient population and therapeutic areas
Preliminary Data (8-10 pages)
- Results from 20-50 reference compounds
- Method performance metrics and statistics
- Comparison with animal studies or human clinical data
- Reproducibility demonstration
- Quality control and standard operating procedures
Proposed Validation Strategy (10-15 pages)
- Detailed validation protocol design
- Reference compound selection strategy (100-500+ compounds)
- Inter-laboratory validation approach
- Statistical analysis plan and acceptance criteria
- Timeline with milestone projections
- Resource requirements and funding plan
Context of Use Statement (2-3 pages)
- Specific intended application of method
- Drug development phase and therapeutic indication
- Performance requirements and acceptance criteria
- Limitations and conditions of use
Strategic Questions to Ask FDA/EMA During Pre-Submission
Scientific & Validation Questions:
- Does FDA consider our proposed Context of Use appropriate and clearly defined?
- Are 100-500+ reference compounds sufficient for validation, or should we test more?
- Does FDA agree with our reference compound selection strategy (chemical diversity, toxicity classes)?
- Are 2-3 laboratories adequate for inter-laboratory validation, or does FDA expect 4+ sites?
- What acceptance criteria (sensitivity, specificity, predictive values) would FDA consider sufficient for qualification?
- Should we include mechanistic data alongside predictive performance data?
- Does FDA want specific comparison data with traditional animal studies or in vitro methods?
- What statistical analysis approaches does FDA recommend for our validation design?
- Should we pursue GLP compliance for validation studies, or is non-GLP acceptable?
- Does FDA have specific quality/characterization data requirements for biological reagents?
Regulatory Pathway Questions:
- Is ISTAND the appropriate pathway for our technology, or should we consider case-by-case approach?
- What is the realistic timeline for FDA review once we submit complete package?
- Would FDA recommend pursuing SAWP or OECD validation in parallel for global reach?
- What specific data should be included in IND submission to demonstrate method acceptability?
- Will method acceptability be formally addressed in IND review, or should we plan pre-IND meeting?
- What role should our preliminary/case-study clinical data play in NDA assessment of method?
- Does FDA expect post-approval monitoring or pharmacovigilance of method performance?
- Can we use method in multiple drug development programs once initially validated?
- Are there data requirements specific to our therapeutic indication?
- What would constitute a successful ISTAND Qualification Letter and when might we expect it?
Risk Mitigation Questions:
- What are FDA's primary concerns about our proposed validation approach?
- Are there known limitations of our technology platform that FDA has previously raised?
- What would cause FDA to reject or recommend against method use in NDAs?
- Should we plan contingency validation studies or backup methodologies?
- Does FDA have concerns about off-target effects or method artifacts?
Effective Pre-Submission Meeting Format
| Meeting Component |
Time (minutes) |
Presenter |
Key Deliverables |
| Opening & Introductions |
5 |
Sponsor Lead |
Clear objectives and questions |
| Scientific Rationale & Unmet Need |
15 |
Principal Scientist |
FDA understands biological relevance |
| Preliminary Data Presentation |
20 |
Data Lead |
FDA sees proof-of-concept evidence |
| Proposed Validation Strategy |
15 |
Regulatory Affairs |
FDA understands approach feasibility |
| Open Discussion & FDA Questions |
20 |
All participants |
Clarifications and FDA concerns addressed |
| Next Steps & Timeline |
5 |
Sponsor Lead |
Commitment to implement feedback |
Post-Meeting Implementation
Documentation and Follow-Up
- Within 5 days: Send thank-you letter and list of action items to FDA
- Within 2 weeks: Receive FDA written response summarizing meeting discussion and recommendations
- Within 4 weeks: Submit written responses to FDA questions/recommendations
- Track all FDA recommendations and ensure validation strategy reflects feedback
- Maintain detailed documentation of FDA guidance for regulatory submissions
- Plan follow-up informal meeting (3-6 months later) to update FDA on progress if major decisions made
Validation Strategy Refinement
- Incorporate FDA feedback directly into validation protocol
- Adjust reference compound list based on FDA comments
- Modify statistical analysis plan to align with FDA recommendations
- Add contingency studies if FDA identified high-risk areas
- Plan comparison studies if FDA wanted additional data
- Adjust timeline projections based on FDA guidance on complexity
Success Indicators: What FDA Written Response Should Say
Positive Response Indicators: "FDA finds the proposed approach to validation scientifically sound" and "The reference compound list appears adequate for demonstrating method relevance" and "FDA would expect to consider [method] for use in INDs and NDAs pending successful validation completion" and "The inter-laboratory validation design appears appropriate."
Concerning Response Indicators: "FDA has reservations about the biological relevance of the proposed system" or "The preliminary data are insufficient to justify the proposed validation scope" or "FDA would recommend additional mechanistic studies" or "FDA would not recommend proceeding with ISTAND pathway at this time."
Common Pre-Submission Meeting Mistakes to Avoid
- Insufficient Preliminary Data: Bringing only 5-10 compound results instead of 20-50. FDA needs evidence of feasibility.
- Vague Context of Use: Failing to precisely define intended application. COU ambiguity creates FDA uncertainty.
- No Specific Questions: Requesting generic guidance. Instead, ask specific questions requiring targeted responses.
- Overselling Preliminary Results: Claiming method superiority without sufficient evidence. FDA values scientific rigor over enthusiasm.
- Inadequate Preparation: Presenting materials developed hastily. FDA appreciates thorough, professional preparation.
- Wrong Regulatory Pathway: Requesting FDA ISTAND discussion for method more suited to case-by-case or OECD approach. Pre-meeting consultation helps clarify optimal pathway.
- Ignoring FDA Recommendations: Receiving feedback then proceeding with original plan regardless. This damages credibility and increases rejection risk.
- Late Problem Identification: Not bringing difficult/concerning data to pre-submission. Better to surface issues early.
Case Study: Successful Pre-Submission Strategy
Example: Organ-on-Chip Hepatotoxicity Platform
Initial Approach (Failed): Company submitted case-by-case NDA inclusion of organ-on-chip hepatotoxicity data without pre-submission meeting. FDA rejected method use citing insufficient validation, incomplete inter-laboratory reproducibility data, and unclear biological relevance mechanisms. Delayed approval by 18 months.
Revised Approach (Successful): Company conducted Type C pre-submission meeting with 45 compound preliminary dataset. During meeting, FDA provided specific guidance: (1) expand validation to 150+ compounds, (2) conduct testing at 3 independent laboratories, (3) include mechanistic data on metabolic pathway activation, (4) pursue ISTAND pathway for stronger regulatory endorsement. Company incorporated FDA feedback into 2-year validation program, then successfully achieved ISTAND qualification within 18 months. Method now accepted across multiple drug development programs.
Implementation Timeline
- Weeks 1-4: Prepare 30-50 page pre-submission package with preliminary data (20-50 compounds)
- Week 5: Submit meeting request to FDA (Type C) or EMA (Scientific Advice)
- Weeks 6-8: FDA/EMA scheduling and meeting confirmation
- Weeks 9-11: Prepare presentation materials and speaker practice
- Week 12: Conduct pre-submission meeting
- Weeks 13-14: Receive FDA written response
- Weeks 15-18: Refine validation strategy based on FDA feedback
- Weeks 19+: Initiate validation studies with revised protocol
Resources and Further Information
Critical Success Factor: Pre-submission meetings are the highest-ROI regulatory investment available to NAMs developers. Organizations that strategically use pre-submission engagement increase approval probability by 35-40% and reduce development timelines by 12-18 months. Companies should view pre-submission meetings not as optional compliance steps, but as essential strategic assets for NAMs commercialization.
← Back to Qualification Pathways