Interacting with the FDA involves a set of formal processes that carry real consequences for a drug development timeline. A poorly prepared pre-IND meeting request, a slow or incomplete response to an information request, or an unpolished advisory committee presentation can each add months to a program. Because of this, many sponsors — particularly smaller biotechs without an in-house regulatory affairs department — bring in outside expertise at specific points in the review process.
This article looks at three of those points: preparing a pre-IND package, responding to FDA deficiencies, and preparing for an advisory committee meeting. In each case, the underlying challenge is similar — assembling the right data, in the right format, on a schedule set largely by the agency rather than the sponsor.
The Pre-IND Meeting: A Narrow Window to Get Right
Before filing an Investigational New Drug (IND) application, sponsors can request what FDA classifies as a Type B meeting under its formal meeting-management framework, grounded in 21 CFR 312.82 for early consultation. A sponsor is generally granted one pre-IND meeting per investigational product and indication, which makes the request itself worth preparing carefully.
A complete meeting request typically needs the proposed meeting type, a brief development history, a specific list of questions grouped by discipline, and a list of proposed attendees from the sponsor’s team and any consultants involved. FDA’s formal meeting procedures generally call for Type B meetings to be scheduled within 60 days of receiving the written request, while the meeting package is typically due separately in advance of the meeting. Sponsors should therefore build sufficient lead time into their submission schedule. Consultants experienced with this process can help sponsors consolidate nonclinical, CMC, and clinical-development questions into a focused multidisciplinary meeting request and prepare the supporting meeting package, rather than pursuing separate discipline-specific meetings.
Where Regulatory Affairs Consulting Fits Into This Process
Because pre-IND packages, deficiency responses, and advisory committee materials each draw on overlapping regulatory, scientific, and operational knowledge, sponsors often look for regulatory affairs consulting support that spans more than one of these moments rather than hiring separately for each.
Tigermed’s regulatory affairs group reports more than 4200 drug registration projects and over 1000 global drug registratio customers, with a team of nearly 60 regulatory experts working across submissions to NMPA, FDA, and EMA. According to the company, this includes IND and NDA submission support, submission dossier preparation, gap analysis, and regulatory strategy development. In 2025, the company reported 50 new US FDA IND projects, compared with 29 new US FDA IND projects in 2023, providing evidence of ongoing FDA-related registration activit.
Responding to FDA Deficiencies and Information Requests
Once an application is under FDA review, sponsors can expect to receive information requests at various points in the process. For standard NDA reviews, FDA typically holds an internal mid-cycle meeting around month five (month three for priority reviews), during which the agency identifies issues that could affect an approval decision and confirms whether an advisory committee meeting will be needed. For certain NDA and BLA reviews, an early filing communication, often referred to as the 74-day letter, may identify filing issues or deficiencies that the sponsor needs to address during the review process.
Responding to these requests generally requires pulling together data and explanations from multiple functions — clinical, nonclinical, CMC, and biostatistics — within a limited window, since the pace of an FDA review cycle does not pause indefinitely for a sponsor’s internal coordination. Experienced regulatory consultants are typically used at this stage to help organize a response that directly addresses each point raised, rather than providing broader context the reviewer did not request.
Preparing for an Advisory Committee Meeting
Not every application goes before an FDA advisory committee, but for those that do, the meeting is a significant event. An advisory committee brings together outside experts to review a sponsor’s data publicly and offer a recommendation to FDA, which the agency considers, though it is not bound to follow. Whether an advisory committee meeting is convened at all is typically decided internally by FDA around the mid-cycle point of the review, giving sponsors a limited window to prepare once notified.
Preparing for this kind of meeting generally involves building a detailed briefing document that anticipates the specific questions FDA and the committee are likely to raise, along with rehearsing the sponsor’s presentation and question-and-response approach ahead of the actual session. Because advisory committee outcomes can shape both the immediate review decision and how a product’s data is perceived publicly afterward, sponsors often value input from consultants who have supported comparable meetings before, since the format and areas of scrutiny can vary depending on the therapeutic area and the specific safety or efficacy questions involved.
Choosing Support That Matches the Submission Stage
Pre-IND preparation, deficiency response, and advisory committee readiness each call for a slightly different mix of regulatory, scientific, and communication skills, even though all three fall under the broader umbrella of regulatory affairs work. Sponsors evaluating fda regulatory consulting support are generally better served by confirming a consultant’s specific experience with the stage they are approaching, rather than assuming broad regulatory experience automatically covers each of these distinct moments equally well.
Companies such as Tigermed, which report sustained FDA submission volume alongside multi-agency regulatory experience, illustrate one example of how CROs have structured this kind of support. As with any regulatory engagement, sponsors are advised to request references tied to comparable product types and to confirm a consultant’s current, specific experience before relying on it for a time-sensitive submission. Given how much a single missed detail can cost in review time, this kind of upfront diligence is generally viewed as a reasonable investment rather than an unnecessary delay.
