FDA Type C会议后行动追踪：CMC分歧、会议纪要和commitment log怎么衔接下一次submission

本文只解决什么 / 不解决什么

这篇文章只解决一个非常具体的问题：你刚完成了一次与CDER或CBER的Type C会议（CMC议题为主），FDA在30天内会发official meeting minutes，你的团队需要在分歧没扩大、commitment没漏掉、下一次amendment/IND submission没误期的前提下，把会议纪要、内部minutes、clarifying questions、commitment tracker串起来。

不解决：Type A/B/B(EOP)/D/INTERACT会议的策略和准备（见站内FDA Type A/B/C/D & INTERACT/Pre-IND会议指南）、IND/NDA整体submission流程、CMC综合策略。本文只覆盖一件事：Type C meeting结束当天到下一次正式submission之间这60-90天的执行细节。

为什么这个问题对中国创新药申办方特别重要

PDUFA VII（FY2023-2027）2023年9月修订的"Formal Meetings Between the FDA and Sponsors or Applicants of PDUFA Products" Draft Guidance Rev.1把Type C会议的几个关键时间窗口写得更明确：

• FDA响应meeting request：21天
• meeting package due：会议前47天（per Rev.1，比之前的早了18天）
• preliminary comments due：会议前5天
• sponsor对preliminary comments的回应：3天内
• 会议日期：FDA receipt of request后75天内
• official minutes：会议后30个日历日内
• clarifying questions（"Request for Clarification"）：minutes收到后20个日历日内提交
• FDA对clarifying questions的回应：收到后20个日历日内

中国申办方过去的典型问题：会议结束后没人专门负责跟踪、official minutes收到后没有及时review、20天的clarifying questions窗口被错过、commitment list在内部看不见，然后6-9个月后submission时发现问题。

下一次submission（无论是IND amendment、Pre-NDA briefing package还是IND/NDA本身）的成败往往不在科学层面，而在Type C会后这90天有没有把action items执行透。

Type C meeting后30天内的强制时间表

会议当天（Day 0）开始算：

为什么sponsor要在24-48小时内把自己的版本发给FDA？因为official minutes会被sponsor minutes影响——FDA project manager在写minutes时会review sponsor的版本，如果某条agreement在sponsor minutes中写得清楚而双方理解一致，FDA往往直接采纳那段措辞；如果sponsor minutes晚发，FDA已经按自己的笔记发出initial draft，再修就难得多。

实务做法：sponsor minutes不要超过3-5页，按FDA的风格用项目符号（不要transcript式），分agreements / disagreements / action items / open issues四个bucket，结尾说明"sponsor will submit a Request for Clarification within 20 days of receipt of FDA's official minutes if needed"。

official minutes收到当天到20天的关键决策

FDA official minutes收到的那天，sponsor应该立即触发review流程：

按照PDUFA VII guidance的明确说法，clarifying questions只能是confirming或clarifying性质——不能引入新议题、新proposal。如果有新数据或新方案，应该走新的meeting request或者直接放进amendment/submission中。

中国申办方常见误区：把clarifying questions窗口当成"再讨论一次"的机会，提交了一份重新论辩CMC决议的pseudo-clarification——FDA会回复"this question raises new issues; please submit a new meeting request"，浪费20天宝贵窗口。

怎么决定"agreement"还是"disagreement"

会议中FDA的发言往往不是绝对结论。Type C minutes的agreement/disagreement分类有讲究：

中国申办方在写sponsor minutes时最容易过度解读"FDA does not object"——把它当成"agreement"或"approved"。FDA很可能在official minutes里把同一句话改写成"FDA's lack of objection at this stage does not constitute approval; the proposal will be reviewed in the context of the eventual submission"。如果sponsor提前在内部把这条按"approved"传播，submission时碰壁就很被动。

CMC commitment log的标准结构

Type C meeting的核心产出是一份commitment log——把会议中的agreements、action items、disagreements、open issues全部按owner、deadline、output、状态跟踪。中国创新药团队普遍的commitment log做法是Excel / SharePoint / Smartsheet，关键字段：

这个log应该每两周（或每月）由RA Lead召集walk-through——而不是放在某个员工的笔记本里。

CMC议题的commitment特别处理

Type C会议如果以CMC为主（典型场景：late-phase IND转NDA、生物制品major process change、ADC的comparability、biosimilar的analytical similarity），CMC类commitment有几个特点：

工艺变更与comparability类commitment

中国创新药NDA filing前的最大风险：FDA Type C时agreed的comparability scope，到NDA filing时CMC团队跑完发现某个method没validate，整个package无法submit。预防做法：commitment log中的每条item都标"upstream dependency"——比如"comparability lot 3"依赖"clinical batch released"，"stability data 6mo"依赖"clinical batch released + 6mo elapsed"。倒推规划。

设施变更commitment

如果Type C讨论了从中国厂出口到美国的facility add-on，FDA典型的commitment：

• pre-approval inspection（PAI）会被schedule，但不是commitment——是FDA的discretion
• supplier qualification documentation按时update
• batch release records ready for inspection
• 工艺validation报告按pre-NDA timeline（通常NDA filing前60天）

中国厂常忽略的：FDA要求facility的"manufacturing readiness"包括data integrity、supplier qualification和change control的完整evidence——不只是工艺本身的validation。Type C会上FDA可能口头说"we'll evaluate this at PAI"，sponsor要把这条写进commitment log，预备PAI evidence pack。

clarifying questions的写法（什么算"clarifying"）

按2023年9月的guidance Rev.1，"Request for Clarification"的scope限制非常严：

可以问的：

• "FDA's minutes state 'X is acceptable'. To confirm, does this mean X is acceptable for submission [in the context of the proposed NDA] or only for Phase 3 advancement?"
• "FDA's minutes state 'sponsor should provide additional Y data'. To clarify, is this required at NDA filing or could it be a postmarketing commitment?"
• "FDA's minutes state '3 batches minimum'. To clarify, does this refer to clinical batches or process performance batches?"

不能问的：

• "We propose using 2 batches instead of 3. Is this acceptable?"（提出新proposal）
• "We have new data showing X. Does FDA agree?"（引入新数据）
• "Could FDA reconsider the Statistical Analysis Plan in light of [new proposal]?"（重新议论）

如果有新proposal，正确做法是写新meeting request（typically Type C、Type D或INTERACT），或在下次submission中提交。clarifying question窗口被FDA很严格执行——一旦判定为out of scope，FDA可能给out-of-scope advice（discretionary）但更常见是建议sponsor走new meeting。

实务的clarifying question示例（CMC场景）：

TO: [Project Manager Name], FDA Office of [X]
FROM: [Sponsor Name], [Application Number]

RE: Request for Clarification on Official Meeting Minutes (Type C Meeting Date
2026-04-15)

Pursuant to FDA's Formal Meetings Guidance for PDUFA Products (September
2023, Rev.1), the sponsor respectfully submits the following clarifying
questions on FDA's official meeting minutes received on [date]:

Question 1 (Section 2.1, Page 4): FDA's minutes state "FDA agrees that
3 lots of process performance qualification (PPQ) using Process B is
sufficient for inclusion in the NDA". To clarify, does FDA's agreement
extend to 3 PPQ lots conducted at the proposed manufacturing site (中国
工厂A) only, or does it also include any required complementary lots at
the U.S. fill-finish site?

Question 2 (Section 3.2, Page 7): FDA's minutes note that "the proposed
specification for impurity X (NMT 0.5%) is acceptable". To clarify, does
this acceptance apply to release specification, stability shelf-life
specification, or both?

Question 3 (Section 4.1, Page 10): FDA's minutes recommend that "sponsor
provide a side-by-side comparability table including biological
characterization data". To clarify, does FDA expect this table to be
included in Module 3.2.S.2.6 of the NDA, or as a standalone supplement
to be submitted prior to the NDA filing?

These clarifying questions are submitted within 20 calendar days of
receipt of the official meeting minutes per the Formal Meetings
Guidance.

每条question一定要reference具体的section/page；FDA review division同时review数十份application，clarification request越具体回得越快。

与FDA project manager的非正式沟通

Type C会议后到下次submission之间，sponsor和FDA project manager的email沟通有讲究：

中国申办方经常碰到的情况：US consultant CC sponsor团队和FDA PM大量邮件讨论技术细节——这些邮件不进入official IND record。FDA如果想官方回应必须走correspondence。所有可能影响submission decision的信息都应submitted into IND/BLA via formal channel（IND amendment、general correspondence）。

minutes有重大错误（disagreement about minutes）的处理

按2023 guidance Rev.1 Section XI，如果sponsor认为FDA minutes有事实错误或遗漏关键内容（不是不同意FDA position本身——那要走standard appeal），应：

1. 第一步：联系FDA project manager（电话 + 后续邮件确认），说明具体哪条minute不准
2. 第二步：如果PM层面解决不了，向division director发函（cc PM），具体说明：(a) 哪一句minute和sponsor理解不符；(b) sponsor的版本是什么；(c) 期望FDA如何处理
3. 第三步：FDA review division评估后两种结果：
   • 如果minutes被认为足够准确：minutes维持原状，PM通知sponsor
   • 如果需要改：FDA发"addendum to official minutes"（不修改原文，新加附录）

"Addendum"会同时记录sponsor的concerns和FDA的最终立场——如果sponsor对FDA最终立场不满，要走formal dispute resolution（21 CFR 10.75 / 312.48 / 314.103），不是minutes addendum流程。

中国申办方实务建议：写disagreement letter时只列1-3条最关键的事实差异；列10条让review division直接判定为frivolous。聚焦于会直接影响submission的差异——如commitment scope、批次数量、specifications。

常见失败模式与补救

失败模式1：official minutes收到后没人review

补救：sponsor错过20天clarifying questions窗口。FDA可能仍受理（discretionary），但响应延后。预防：minutes收到日automatic trigger一个团队review流程（用RA tracker）。

失败模式2：sponsor minutes写得过度乐观

中国申办方常把"FDA does not object"写成"FDA approved"。补救：内部要有第二人reviewer（典型：US consultant + 内部RA Lead双审），或在internal communications把所有FDA措辞逐字quote（不paraphrase）。

失败模式3：commitment log丢失

会议结束后commitment list没人maintain，6个月后才发现某条agreed item漏做了。补救：commitment log在RA团队的核心文件，每月walk-through，触发function lead update。最好放在企业级SharePoint而不是某个员工的Excel。

失败模式4：clarifying question被判out-of-scope

补救：FDA回复时discretionary给一些response（"as a general matter..."），但不能reference at filing。需要走new meeting或在submission中处理。

失败模式5：commitment延期但没proactive通知FDA

补救：commitment若要延期（典型场景：比如comparability data完成时间从NDA filing前推迟到post-filing），sponsor要在原deadline前发一封正式letter说明：(a) 延期原因；(b) 新的timeline；(c) 不影响整体submission decision的rationale。等FDA在AI letter中发现再被动响应，对submission非常不利。

post-meeting commitment到下次submission的衔接

最后这一步是把commitment log接到下一份正式submission的具体section。三个核心衔接：

衔接到IND amendment

每条agreed action item应当在next IND amendment中明确reference："Per FDA's recommendation in the Type C meeting on 2026-04-15 (official minutes received 2026-05-15), the sponsor has updated [Section X.Y.Z] to include [specific content]." 这种reference让FDA reviewer快速对照meeting commitment和submission内容，减少second-cycle review concerns。

衔接到Pre-NDA briefing package

Pre-NDA meeting（typically B型）的background package中，sponsor通常引用之前的Type C agreement。引用时引用official minutes的具体page/section，并说明sponsor如何执行了那条agreement。

衔接到NDA filing

NDA Module 3 / Module 5的specific section要reference Type C agreement。例如Module 3.2.S.4.1（specifications）的rationale部分提"the proposed specification for impurity X (NMT 0.5%) was discussed in the Type C meeting on 2026-04-15 and FDA confirmed acceptance per official minutes Section 3.2 (Page 7)". 这种documented rationale是NDA review时FDA assessor最希望看到的。

60-90天commitment执行的内部memo示例

下面这段语言是说明性的，可作为sponsor内部上报CEO/CSO的commitment status memo参考：

TO: [Chief Scientific Officer]
FROM: Regulatory Affairs
DATE: 2026-06-15

RE: Type C Meeting (2026-04-15) — 60-Day Commitment Status

Following the Type C meeting on 2026-04-15 with [Division X], we received
FDA's official minutes on 2026-05-15. We submitted a Request for
Clarification on 2026-06-04 (within the 20-day window) addressing 3 specific
points related to Process B comparability scope. We expect FDA's response by
2026-06-24.

The current commitment log contains 14 items:
- 8 agreements requiring action prior to NDA filing
- 3 disagreements (we plan to provide additional rationale in NDA)
- 2 open issues (deferred to Pre-NDA Type B meeting)
- 1 explicit recommendation we have decided not to follow (with documented
  scientific rationale; will be addressed in NDA Module 3.2.P.5.4)

Critical path: Process B PPQ Lot #3 release date is now projected for
2026-09-15, on track for the 2026-12-15 NDA filing.

Risk: 1 commitment (extractables/leachables study) is currently 3 weeks
behind schedule. Recovery plan: parallel external CRO engagement; expected
catch-up by 2026-08-30.

Recommended next step: schedule Pre-NDA meeting (Type B EOP) by 2026-09-01.

一份post-meeting evidence binder示例

为Type C会议的commitment执行保留可审计证据，建议工厂在internal SharePoint维护：

/type-c-meeting-{date}-{topic}/
  ├── 01_Pre_Meeting/
  │   ├── meeting_request.pdf
  │   ├── meeting_package_v[##].pdf
  │   └── fda_preliminary_comments.pdf
  ├── 02_Meeting/
  │   ├── attendee_list.pdf
  │   ├── raw_notes_individual_attendees.zip
  │   ├── debrief_meeting_recording_or_minutes.pdf
  │   └── sponsor_summary_to_fda.pdf
  ├── 03_FDA_Official_Minutes/
  │   ├── fda_official_minutes.pdf
  │   ├── internal_review_log.xlsx
  │   └── disagreement_letter_to_division (if any).pdf
  ├── 04_Clarifying_Questions/
  │   ├── request_for_clarification.pdf
  │   └── fda_response.pdf
  ├── 05_Commitment_Log/
  │   ├── commitment_tracker_v[##].xlsx
  │   ├── monthly_walkthrough_minutes/
  │   └── escalation_log.pdf
  ├── 06_Submission_Cross_References/
  │   ├── ind_amendment_reference_table.xlsx
  │   ├── nda_filing_module_mapping.xlsx
  │   └── pre_nda_briefing_package_excerpts.pdf
  └── 07_Lessons_Learned/
      └── post_meeting_lessons_learned.pdf

这个binder的目的：当下一次FDA inspection或review cycle中FDA reference到Type C meeting，能在30分钟内调出所有相关材料；当sponsor团队成员变动时，新人能快速接管。

参考资源

• Formal Meetings Between the FDA and Sponsors or Applicants of PDUFA Products — Draft Guidance Rev.1（September 2023） — PDUFA VII下meeting类型、时间窗口、follow-up opportunity
• Best Practices for Communication Between IND Sponsors and FDA During Drug Development（December 2017） — IND期间sponsor-FDA沟通规范
• Formal Meetings Between the FDA and Sponsors or Applicants of BsUFA Products — 针对生物类似药的sponsor指南
• PDUFA VII Reauthorization Performance Goals and Procedures — meeting metrics和performance goals
• Good Review Management Principles and Practices for PDUFA Products — review division的操作原则
• 21 CFR 10.75（formal dispute resolution） — minutes之外的争议处理路径

本文为出海合规研究文章，所引用的FDA guidance、PDUFA goal letter内容截至发文日（2026-05-06），最新版本以FDA官网为准。涉及具体submission strategy和与FDA交互的判断，应结合各申办方的具体application、therapeutic area和review division背景；本文不构成法律或监管意见。

相关文章

文章

3D打印药物上市路径：FDA、EMA、NMPA监管框架与三迭纪出海实践

系统梳理3D打印药物在全球三大市场的监管框架：FDA新兴技术项目、EMA首份3DP GMP问答文件、NMPA审批现状，结合三迭纪T20G和D23的IND实战经验，为中国药企提供可操作的注册策略。

药品注册NDA2026-04-28

›

文章

FDA加速审批致幻剂药物：2026年突破性疗法认定、国家优先审评券与Right to Try全面解读

解读2026年4月FDA加速致幻剂（裸盖菇素、甲基酮等）审评的政策背景、监管路径和临床试验进展，分析其对创新药出海和全球精神健康药物开发的启示。

药品注册NDA2026-04-28

›

文章

FDA 一项关键临床试验即可获批新药：2026 单试验标准的战略影响

2026年2月FDA正式确认一项关键临床试验加确证性证据即可作为新药获批的默认标准，终结50年双试验传统。深度解读政策背景、确证性证据范围、对中国药企新药开发策略的影响。

药品注册NDA2026-04-26

›