Plan: Complete Response Letter (CRL) Resubmission Plan

This is a ready-to-use plan for the period between receiving a Complete Response Letter (CRL) and filing a resubmission. It turns “read the CRL and fix everything” into a governed effort: a deficiency log, a documented resubmission-class decision, an owner and an evidence requirement for every deliverable, and a single acceptance gate before the package goes out. Replace every <<FILL: ...>> placeholder. Read it alongside managing health authority interactions for the reasoning behind the CRL classification rules and the Type A meeting decision this plan schedules. A filled specimen follows.

Document control header

1. Purpose

This plan governs the path from a Complete Response Letter to a filed resubmission for <<FILL: PRODUCT>>, so that every deficiency FDA cited is closed with verified evidence, the resubmission is classified and scheduled correctly, and nothing is filed that a reviewer or, where a facility deficiency is involved, an inspector cannot verify. A CRL is not the end of the program; it is a defined list of what has to be true before approval, and this plan is how the organization proves each item on that list.

2. Scope

This plan covers everything from the day the CRL is received to the day the resubmission is filed: reading and categorizing every deficiency, deciding whether to request a pre-resubmission Type A meeting, executing and verifying each deliverable, making and documenting the resubmission-class decision, and confirming completeness before the package goes out. It does not replace the CAPA procedure that closes a manufacturing, quality-system, or data-integrity deficiency (<<FILL: SOP-ID for CAPA>>; see what is a CAPA and CAPA effectiveness verification), which this plan schedules and tracks to completion rather than performs. It also does not replace the meeting-management procedure that governs the Type A meeting itself (see the health authority meeting management SOP).

3. Governance and roles

4. Approach: deficiency-by-deficiency categorization

1. Log every deficiency in the CRL exactly as written, do not paraphrase or combine two deficiencies into one line.
2. Assign each a discipline (clinical, CMC, facility/quality system, labeling, statistics) and a severity (major or minor, using your internal criticality scheme).
3. For each deficiency, state in plain language what FDA actually needs to see, not just what the letter says; a facility citation about audit trail review needs a working CAPA an inspector can verify, not an explanation letter.
4. Confirm no deficiency is being read narrower than it was written; a deficiency framed as a data point is sometimes really a systemic finding, and treating it as the narrower reading is a common source of a second CRL.

5. Risk basis and the resubmission-class decision

The resubmission class is not a preference; FDA determines it against a defined list (see the Class 1 vs Class 2 comparison). Plan against the class the evidence supports, not the class you would prefer, and document the rationale before the Type A meeting so the meeting can confirm or correct it rather than introduce it cold.

6. Deliverables per deficiency, with owners

A deliverable is not complete because a document was written; it is complete when the stated evidence exists and has been reviewed. For a CAPA deliverable, “evidence required” means an effectiveness check with a defined monitoring period, not just a closed action item.

7. Pre-resubmission Type A meeting decision

Default to requesting a Type A meeting unless every deficiency is unambiguous and the response is a straightforward Class 1 matter. Request the meeting when any of the following apply:

• A deficiency’s remediation approach is open to more than one reasonable reading.
• Any deficiency is likely to drive a Class 2 classification, so the team confirms the scope of “complete” before committing six months of work to it.
• A facility or data-integrity deficiency is involved, so the team can align on what evidence of CAPA effectiveness the agency expects to see.

Decision and date requested: <<FILL>>. Meeting outcome and action items: <<FILL>> (track in the health authority interaction and commitment log).

8. Schedule

9. Acceptance: what “complete” means before submission

A resubmission is ready to file only when all of the following are true:

• Every deficiency in the CRL has a closed deliverable with the stated evidence in hand, not a plan to produce it.
• Any CAPA claimed complete has a documented effectiveness check, not just a completed action.
• The resubmission-class assessment is documented with rationale and has QA and regulatory concurrence.
• No new, unaddressed issue has been introduced into the package that was not part of the CRL or the agreed Type A meeting scope.
• The cover letter states plainly that the submission is a complete response to every deficiency in the CRL.
• Senior quality and the executive sponsor have signed the go decision.

10. References

21 CFR 314.110, Complete response letter to the applicant, and the parallel biologics provisions. FDA guidance for industry, Classifying Resubmissions in Response to Action Letters (CDER/CBER), and CDER’s internal manual of policies and procedures MAPP 6020.4 for the current Class 1/Class 2 criteria. FDA guidance, Formal Meetings Between the FDA and Sponsors or Applicants of PDUFA Products (for the pre-resubmission Type A meeting).

Confirm the current version of each reference before issue.

11. Revision history

12. Approvals

Filled specimen

An illustrative CRL response for an example recombinant therapeutic protein BLA, with two deficiencies of different character. Company, product, and dates are illustrative; replace with your own.

Deficiency categorization

Resubmission-class decision

Rationale and documented class assessment: Deficiency 1 is a facility/quality-system finding that will require FDA to verify the CAPA’s effectiveness, which the team expects to include a re-inspection; this alone drives Class 2 regardless of how quickly deficiency 2 closes. Class 2 (6 month review clock) assessed and confirmed with QA and Regulatory, 14 July 2026.

Schedule (excerpt)

At the Type A meeting the agency confirmed the retrospective review population for deficiency 1 should cover twelve months of batches, not the six the team had proposed, and agreed the method re-validation approach for deficiency 2 was acceptable without additional discussion. Getting that population question answered in July, rather than discovering it after building a six-month retrospective review, is the entire value of requesting the meeting before building anything.

Common inspection findings this plan prevents

• A resubmission that addressed the letter of a CRL deficiency but not what an inspector actually needed to see, drawing a second CRL.
• A facility CAPA claimed complete with no effectiveness check, so the same gap reappears at the next inspection.
• A resubmission filed as Class 1 when a facility or data-integrity element should have driven a Class 2 classification, creating a credibility problem when FDA reclassifies it.
• A retrospective review scoped narrower than the deficiency actually required, discovered only after the resubmission was already built.

How to adapt this plan

1. Set your product, application number, and CRL date in the header.
2. Size section 4’s deficiency table to the actual CRL; a single-deficiency CRL still benefits from the same discipline, a multi-deficiency CRL needs it more.
3. Point the CAPA cross-reference in section 2 to your real procedure, and confirm the effectiveness-check requirement in section 9 matches it.
4. Use the Class 1 vs Class 2 comparison in the parent article to pressure-test your own classification rationale in section 5 before the Type A meeting.
5. Confirm every regulation and guidance reference in section 10 against the current published version before issue.