Module 04G · Lesson 03

Health Authority Interaction Preparation — Strategic Regulatory Work

Reading time: 18 minutes Track: Role Path — Regulatory Affairs Prerequisites: Module 04G · Lessons 01 and 02

What this lesson does

Health authority interactions — pre-IND meetings, end-of-Phase-2 meetings, Type C meetings, advisory committees, scientific advice — are where regulatory strategy meets the agency face-to-face. The preparation work is intense, the stakes are high, and AI can be a meaningful force multiplier when used well.

This lesson addresses the specific AI workflow for agency interaction preparation.

By the end of this lesson, you'll be able to:

Use AI to accelerate meeting preparation without compromising rigor
Anticipate agency questions more comprehensively than you would alone
Build mock Q&A processes that improve actual meeting performance
Recognize the failure modes specific to agency-interaction preparation

01 · The structure of agency-interaction prep

Most significant agency interactions follow a similar prep arc:

Strategic framing — what we're trying to accomplish, what we need from the agency
Briefing document drafting — formal pre-meeting submission
Question anticipation — what will the agency ask
Mock Q&A — internal rehearsal
Final preparation — materials, presenter assignments, day-of logistics

AI helps significantly in steps 1, 2, 3, and 4.

02 · Strategic framing

Before drafting any document, you need clarity on what you're trying to accomplish.

AI for strategic framing

Senior regulatory strategist preparing for [meeting type] with FDA on [topic]. Help me clarify strategy:

1. What outcome am I optimizing for from this meeting?
2. What does success look like in agency response?
3. What are the secondary objectives?
4. What questions, if answered well by the agency, would unlock our program?
5. What's the worst-case agency response and how do I mitigate?
6. What's the question I most don't want to ask but need to?

Context: [program details, recent history, current situation]

Be challenging. Push back on weak framing.

This pre-drafting conversation often reshapes the briefing document fundamentally. The reframing is worth the time.

The mistake to avoid

Drafting a briefing document before strategy is clear. Many briefing documents are essentially comprehensive data dumps in search of a strategic ask. They get less useful agency feedback.

The reframe: a briefing document is a question to the agency, supported by data. The question should be sharp before the support is built.

03 · Briefing document drafting

Module 04G Lesson 02 covered submission section drafting. Briefing documents follow similar patterns with specific additions.

Briefing-specific structure

Senior regulatory strategist drafting briefing document for [meeting type].

Standard structure:
1. Introduction (purpose of meeting)
2. Background (program status, prior interactions)
3. Specific issues for agency discussion
4. Proposed approach (what we plan to do)
5. Supporting rationale (evidence and reasoning)
6. Specific questions to agency

For each issue:
- Clear articulation of the problem or decision
- Your proposed approach
- Specific question to the agency
- Supporting data

Conventions: 
- Sharp questions (specific, answerable)
- Honest assessment of uncertainties
- Don't bury the ask
- Anticipate likely agency concerns

Iterate the structure before drafting content. A weak structure can't be redeemed by good content.

The questions section

The most important part of any briefing document is the questions. Sharp questions get sharp feedback; vague questions get vague responses.

Senior regulatory strategist refining questions for FDA. My current draft questions are:

[List]

For each:
1. Is this question specific enough to get an actionable answer?
2. Is the question phrased to surface FDA's view, not lead them to ours?
3. Are there better ways to phrase it?
4. What follow-up questions should I prepare in case FDA asks back?
5. What's a worse version of this question I should make sure I'm not asking?

Question refinement is high-leverage. Spending 30 minutes on it can change meeting outcomes.

04 · Question anticipation

What will the agency ask? Predicting this well makes you more effective in the meeting.

The structured anticipation prompt

Senior FDA reviewer in [division] with experience in [therapeutic area, modality]. I'm sharing a briefing document for an upcoming Type [X] meeting. As an experienced reviewer:

1. What questions would you ask during this meeting?
2. What positions would you push back on?
3. What additional data would you request?
4. What concerns would you raise that aren't directly addressed?
5. What precedents would you cite?
6. What would you find weak in our proposal?

Be specific. Don't be soft. Reviewers have seen many programs; reviewers are skeptical by default.

[Briefing document attached]

This produces a structured list of anticipated questions. Some will be on target; some will be reaches. Triage.

The mock-reviewer roles

Different reviewer personas surface different questions. For a comprehensive prep:

Lead clinical reviewer — efficacy and safety scrutiny
Statistical reviewer — design and analysis scrutiny
CMC reviewer — manufacturing and quality scrutiny
Pharmacology/toxicology reviewer — nonclinical scrutiny
Division director / supervisor — strategic and precedential view

For an important meeting, run the anticipation prompt with multiple reviewer personas. Aggregate the questions.

The "what should they ask but might not" check

A specific addition: AI may also surface questions the agency should ask but might miss.

Beyond what FDA is likely to ask, what should they be asking that they might miss? What weaknesses in our proposal could a less experienced reviewer overlook?

This is for your team's awareness, not for the meeting. If FDA doesn't catch a weakness, you may need to address it preemptively in the briefing or in your presentation.

05 · Mock Q&A development

The internal rehearsal where you simulate the meeting. AI helps build the mock Q&A document and run practice rounds.

The mock Q&A document

Senior regulatory strategist preparing mock Q&A for [meeting]. Based on the briefing document and anticipated agency questions, build a Q&A document with:

For each anticipated question:
1. The question (as the agency might ask it)
2. Our proposed response (with key data points and framing)
3. Likely follow-up questions
4. Risk assessment (what makes this question difficult)
5. Alternative framings if our first response doesn't land

Cover at least [N] questions. Be specific about responses, not generic.

[Briefing document and anticipated questions attached]

This produces a structured document that your team uses to prepare. Refine through internal review.

Running mock Q&A

The actual rehearsal is human-to-human. But AI can support:

Generating additional probing questions during practice
Critiquing presenter responses (with structured framework)
Identifying weak responses or framing
Suggesting better responses

Use AI between mock sessions to refine. The mocks themselves are human work.

06 · The "challenger" workflow

A specific technique: use AI to challenge your strategy hard before the agency does.

Senior regulatory strategist with deep experience and tendency to be skeptical. Review our strategy for the upcoming [meeting]:

[Strategy summary, briefing document, mock Q&A]

Be a challenger:
1. What's the weakest part of our strategy?
2. Where are we overconfident?
3. What's the most likely scenario where the meeting goes badly?
4. What could we do in the next [week / month] to strengthen our position?
5. What if the agency takes the worst-case position — what's our recovery plan?

Don't soften the critique.

This is uncomfortable but useful. The agency will be a challenger; better to face the challenge internally first.

Acting on the challenger output

Triage the AI's challenges:

Real weaknesses you can address before the meeting → address them
Weaknesses you can't address but should be prepared for → develop contingency responses
Reaches that aren't actually weaknesses → note and dismiss

The discipline: don't dismiss critiques because they're uncomfortable. Dismiss them because they're not actually right.

07 · A worked example

A realistic scenario: preparing for an end-of-Phase-2 meeting with FDA.

Setting: Your Phase 2 results are positive but not unambiguous. You need agency feedback on Phase 3 design — sample size, endpoints, comparator, regulatory pathway. The meeting is in 6 weeks.

Week 1 — Strategic framing

Run the strategic framing prompt. Refine the meeting objectives.

Realization from the framing conversation: the most important question isn't sample size (you can run scenarios) — it's whether the agency will accept the proposed primary endpoint given the Phase 2 results. Reorient the briefing around that.

Weeks 2-3 — Briefing document drafting

Following the workflow from Module 04G Lesson 02. Heavy verification.

Week 4 — Question anticipation

Run the structured anticipation across multiple reviewer personas. Generate ~40 anticipated questions. Triage to ~25 most likely.

Week 4-5 — Mock Q&A development

Build the Q&A document. Internal review by senior team.

Week 5 — Mock sessions

Run two mock meetings. Use AI between sessions to refine responses.

Week 5-6 — Challenger workflow

Run challenger session 1 week before meeting. Identify two weak spots; develop contingency responses.

Day of meeting

You're prepared. AI's role is done; the meeting is human.

Outcome: Better prepared than you would have been without AI; agency feedback is more useful because your questions are sharper.

08 · Documentation after the meeting

After the meeting, AI helps with:

Drafting meeting minutes (from your notes)
Comparing official FDA minutes (when they arrive) to your understanding
Drafting communications about meeting outcomes (internal, to program team)
Updating regulatory strategy based on agency feedback
Drafting follow-up correspondence if needed

The post-meeting workflow has its own cadence. AI helps throughout.

09 · Knowledge check

Three questions.

Q1. Why does this lesson recommend doing strategic framing before briefing document drafting?

a) It's required by FDA b) Without clear strategy, briefing documents become comprehensive data dumps in search of an ask — drafting before strategy is clear produces less useful agency feedback c) Briefing documents are optional d) Strategy is the responsibility of management, not regulatory

Q2. What's the recommended approach for question anticipation?

a) Generate a list of generic questions b) Run multiple AI reviewer personas (clinical, statistical, CMC, supervisor) and aggregate questions; triage to most likely; also ask what FDA should ask but might miss c) Wait for FDA to ask d) Anticipate only the easy questions

Q3. Why is the "challenger" workflow described as uncomfortable but useful?

a) Challengers are always wrong b) Better to face hard critiques internally than have the agency surface them in the meeting — discomfort is appropriate; dismiss critiques because they're not right, not because they're uncomfortable c) Challengers slow down preparation d) Challengers are AI-only

Answers: Q1: b · Q2: b · Q3: b

10 · What's next

Lesson 04: Regulatory intelligence and comparative analysis.

End of Lesson 03.