Introduction
A complete response letter, or CRL, is one of the moments in a regulatory affairs career that tests everything at once: technical judgment, project management, and the ability to keep a team calm and focused when the news is bad. FDA issues a CRL at the end of a review cycle for an NDA, BLA, or ANDA when the agency determines it cannot approve the application in its current form. It is not a rejection of the product, and it is not the same as a Refuse to File decision made before review even begins. It is FDA's formal statement of what stands between the current submission and an approval, and how regulatory affairs responds to it shapes the rest of the product's path to market.
Companies do not talk about CRLs much publicly beyond a brief disclosure, but internally the response is one of the most cross-functional, high-stakes projects a regulatory team runs. Understanding the actual workflow behind it is useful both for regulatory professionals who will eventually own one and for anyone trying to understand what a CRL response lead role actually involves when they see it in a job posting.
Reading the Letter Before Doing Anything Else
The first job is not to react, it is to read carefully and categorize. A CRL lays out deficiencies, and those deficiencies typically fall into a handful of buckets: clinical (efficacy or safety data FDA found insufficient or in need of further analysis), CMC (chemistry, manufacturing, and controls issues, often tied to a facility inspection finding or a specification concern), facility (an unresolved inspection observation at a manufacturing site), and labeling (disagreements over how the product should be described for use). A single CRL can, and often does, combine several of these.
Regulatory affairs reads the letter line by line and builds a deficiency list, distinguishing issues that require new data or a new study from issues that can be resolved by better analysis of data the company already has, additional documentation, or a facility remediation. That distinction drives almost everything that follows, because it determines how long a response will realistically take and what a resubmission needs to contain.
Convening the Cross-Functional Response Team
Regulatory affairs leads the response, but it does not write the response alone. Clinical, CMC, quality, biostatistics, and often nonclinical and medical affairs all have to weigh in, because the deficiencies almost always touch more than one function. Regulatory's job in this phase is translation and project management: turning FDA's sometimes dense regulatory language into a concrete list of what each function needs to produce, setting a realistic internal timeline, and keeping the team from either underestimating the work (which leads to a second CRL) or overbuilding the response beyond what FDA actually asked for.
This is also where regulatory affairs earns its keep by managing up. Executive leadership wants a resubmission date immediately; regulatory has to hold the line on a timeline that reflects the actual deficiencies rather than a hoped-for one, which is not always a comfortable conversation to have the week a CRL arrives.
What the Deficiencies Actually Look Like in Practice
A clinical deficiency might mean FDA wants additional analysis of a subgroup, is not convinced the primary endpoint reflects a clinically meaningful benefit, or has a safety concern that needs a longer-term follow-up dataset the company does not yet have. A CMC deficiency is often narrower on paper but can be just as time-consuming in practice: a specification that needs tightening, a stability dataset that has to be extended, or a manufacturing process description that FDA felt was not adequately validated. Facility-related deficiencies are their own category entirely, since they depend on a separate inspection outcome and timeline that regulatory affairs does not fully control; if a manufacturing site received an unfavorable inspection classification, the CRL response may be waiting on that site's remediation and a reinspection before the company can even resubmit.
Labeling deficiencies are frequently the least technically demanding but can still stall a resubmission if they involve a genuine disagreement, for example over how a warning should be worded or which population the label should describe, that requires real back-and-forth with the review division rather than a one-sided fix. Regulatory affairs has to recognize early which category a given deficiency actually falls into, because treating a substantive clinical concern as if it were a simple labeling tweak is one of the more common ways a first resubmission turns into a second CRL.
Deciding on a Type A Meeting Request
Sponsors are generally entitled to request a Type A meeting with FDA after a CRL, and FDA aims to hold these meetings within 30 days of the request. This meeting is the chance to clarify exactly what the agency meant by a given deficiency, confirm whether the company's proposed approach to resolving it would be adequate, and, where the letter is ambiguous, avoid guessing wrong and resubmitting into a second CRL. Not every CRL response includes a Type A meeting, but for anything beyond a narrow, well-understood labeling fix, requesting one is close to standard practice, and regulatory affairs prepares the briefing package and drives the internal rehearsal for it.
Preparing for that meeting is its own regulatory writing exercise: a tight, specific set of questions for FDA, framed so the agency can give a direct answer rather than a noncommittal one, plus enough supporting data to make the company's proposed path credible without turning the meeting into a full data dump.
Building the Resubmission Strategy
FDA classifies resubmissions into two categories with different review clocks: a Class 1 resubmission, generally for narrower issues like labeling or a defined dataset addition, carries a shorter review goal of about two months, while a Class 2 resubmission, for more substantial issues such as new clinical data or a significant manufacturing change, carries a longer review goal of about six months. Regulatory affairs makes the classification call in coordination with FDA feedback (often from the Type A meeting) and builds the internal plan around whichever timeline applies, since that decision affects everything from clinical trial timelines to the company's public financial guidance.
Getting the classification right matters because submitting a resubmission and having FDA reclassify it, or reject the classification the company proposed, costs real time. Regulatory affairs is the function accountable for making sure the resubmission package actually matches the class it is being filed under.
Writing the Actual Resubmission
The resubmission itself is typically organized around a point-by-point response to each deficiency in the original CRL: what the deficiency was, what the company did to address it, and where in the new submission the supporting material can be found. This is exacting regulatory writing. It has to be complete enough that a reviewer does not have to hunt for the answer, precise enough that it does not overstate what the new data shows, and organized well enough that a reviewer working through a stack of resubmissions can follow the logic quickly.
Regulatory affairs also updates the proposed labeling if needed, prepares the cover letter that frames the resubmission for the review division, and coordinates the final quality check across every function that contributed, since a resubmission with a gap or an inconsistency risks the very same outcome the company is trying to avoid a second time.
Managing Communication Beyond the Agency
A CRL is also a disclosure event for a public company, and regulatory affairs typically has to brief investor relations, legal, and executive leadership on what the letter actually says well before any public statement goes out. This is a different kind of writing than the resubmission itself: a short, accurate public description of the deficiencies that does not overstate the company's confidence in a fast resolution or understate a genuinely serious finding, since either mistake can create problems ranging from investor litigation risk to a credibility loss with FDA if the company's public characterization does not match the letter it actually received. Regulatory affairs is rarely the one drafting the press release, but it is usually the function whose sign-off on the technical accuracy of that release matters most.
Internally, regulatory affairs also has to manage a workforce that may be anxious about what a CRL means for the program and, by extension, for their jobs. Clear, honest internal updates on what the deficiencies are, what the realistic timeline looks like, and what is being asked of each function go a long way toward keeping a cross-functional team functional through a stressful stretch rather than working at cross purposes.
What This Work Teaches You
Very few regulatory experiences build judgment as fast as owning a CRL response. It forces a level of precision about what a health authority actually said versus what a team assumed it said, and it puts a premium on being able to say no to internal pressure for an unrealistic timeline. People who have led a CRL response tend to be more comfortable making a hard regulatory call under uncertainty, and hiring managers recognize that experience specifically, not just generic submissions experience, when they see it on a resume.
Conclusion
A complete response letter is a setback, not an ending, and the way a regulatory affairs team handles the first few weeks after one arrives often determines whether the product gets to market in a reasonable timeframe or cycles through a second review. The work is demanding and unglamorous: careful reading, honest timelines, disciplined writing, and a lot of internal translation between what FDA said and what each function needs to do about it. It is also some of the most respected experience a regulatory professional can carry into the next role.