Pharma regulatory consulting: a practical decision guide for sponsors

Overview

Choosing whether, when, and how to engage external pharma regulatory consulting is a risk‑management decision. It materially affects program timelines and approval probability. This guide is written for regulatory affairs leads, regulatory operations managers, and program heads at small to mid‑size biotech and pharma companies evaluating that choice.

It does not catalog vendors or rank firms. Instead, it walks through the decisions that matter most before you engage anyone: submission pathway selection, expedited program eligibility, preparing for agency interactions, common eCTD failure modes, scoping post‑approval change work, and what a well‑structured consulting engagement looks like on paper.

Every practical claim here is bounded by regulator‑published guidance or primary‑source evidence; inline links point to those sources. Checklists and decision criteria are embedded so you can apply them directly without downloading separate documents.

---

What pharma regulatory consulting covers across the lifecycle

Regulatory failure—not scientific failure alone—is the defining risk in development. A molecule that meets biological endpoints can still be delayed months to years by preventable gaps in regulatory strategy, CMC documentation, or submission quality. Many Refuse to File and Complete Response Letter outcomes trace back to those avoidable issues rather than clinical data deficiencies.

Pharma regulatory consulting spans at least four distinct workstreams that map to different development phases and organizational gaps: strategy and health authority interactions, CMC and quality, submissions and eCTD operations, and safety plus post‑approval maintenance. Sponsors deciding whether to bring in a consultant—or what scope to assign—should identify which of these workstreams represents the actual gap, not which general label fits the firm.

Worked example — scoping a consulting engagement at Phase 2 entry:

A small oncology biotech has a first‑in‑class oral kinase inhibitor completing Phase 1 dose escalation. The team has two in‑house regulatory staff with NDA experience but no direct FDA meeting experience and no CMC consultant relationship. Preliminary activity in a rare indication raises the question of whether Breakthrough Therapy Designation is worth requesting before Phase 2 initiation.

A realistic consulting scope at this stage covers three integrated tasks: (1) a pre‑IND/Type B meeting request and briefing package to confirm Phase 2 acceptability and labeling direction; (2) a Breakthrough Therapy Designation request if preliminary evidence suggests substantial improvement over available therapy; and (3) an independent CMC readiness gap assessment focused on control strategy maturity and analytical method qualification.

Attempting to hand off only the meeting request while leaving the CMC gap and designation question unaddressed creates a false sense of preparation. Each task informs the others—the Phase 2 protocol design influences what CMC maturity is expected, and the designation request depends on what the briefing package establishes as unmet need. A consultant who integrates all three tasks produces more coherent output than separate engagements that do not coordinate across them.

Strategy and health authority interactions

The highest‑leverage moment for a regulatory consultant is often before the briefing package is written. Experienced consultants shape the questions a sponsor asks FDA or EMA, not just the quality of the answers provided.

A poorly framed question at a pre‑IND Type B meeting can lock in an unhelpful precedent that the program may spend years working around. Consultants who have managed many formal meetings bring pattern knowledge about which questions elicit useful written commitments, which questions produce non‑committal responses, and how to structure background to avoid triggering requests for additional data. That accumulated experience is difficult to replicate quickly inside a lean in‑house team.

FDA's Formal Meetings guidance defines four meeting types: Type A (dispute resolution and clinical holds), Type B (pre‑IND, pre‑NDA/BLA, end‑of‑Phase 2), Type C (all others), and Type D (informal). Type B meetings carry a 90‑day scheduling target from FDA receipt of the request. Sponsors have 30 days after meeting notification to submit a briefing document, and FDA will respond in writing even if no meeting is held.

EMA's Scientific Advice and Protocol Assistance runs through the Scientific Advice Working Party (SAWP) using a two‑round briefing document process with a SAWP rapporteur and a written opinion issued on an approximately 70‑day timeline for standard advice. Consultants familiar with SAWP can help calibrate what level of clinical and CMC data is needed before seeking advice and structure questions to maximize the operational value of the written response.

CMC and quality

CMC deficiencies are a leading cause of regulatory delays for complex molecules—particularly biologics, complex injectables, and products manufactured at CMOs where process understanding documentation is often less mature than the sponsor's internal assets.

The ICH Q series frames expectations across the development lifecycle: Q8 covers pharmaceutical development and design space, Q9 covers quality risk management, Q10 covers the pharmaceutical quality system, Q11 covers drug substance development and manufacture, and Q13 addresses continuous manufacturing. These guidelines define what regulators expect at each stage but do not prescribe how to meet those expectations—that is where a consultant's judgment matters.

Phase‑appropriate expectations are critical. A Phase 1 IND requires a less mature control strategy than a Phase 3 NDA but must still demonstrate process control sufficient to protect trial participants. Over‑specifying controls at Phase 1 wastes resources and can create unnecessary comparability obligations later; under‑specifying creates clinical hold risk. The right balance depends on molecule class, manufacturing platform, and prior agency interactions—exactly the kind of trade‑off advice experienced CMC consultants provide.

Submissions and eCTD

Submissions consulting covers planning, content authoring, Module 1 regional localization, publishing, and pre‑submission quality review. eCTD is mandatory for most NDA, BLA, ANDA, and IND submissions to FDA and required by EMA for centralized applications.

Effective publishing and validation require both regulatory knowledge and technical publishing fluency—skills that rarely reside in a single person. Sponsors therefore often engage separate authoring and publishing consultants or use platform tools to bridge the gap. Teams running recurring submission programs increasingly combine consultant expertise with purpose-built eCTD workspace tools that validate structure and metadata continuously during drafting rather than as a final pre-submission step, catching defects when they are still easy to fix.

Module 1 is the most regionally variable module: FDA and EMA require different cover letters, administrative forms, and folder conventions. A document set that validates cleanly for FDA will often trigger technical rejections when submitted to EMA without regional adaptation. Good submissions consulting anticipates those differences and prepares region‑specific Module 1 content in parallel with global dossier development.

Safety and post-approval

The safety and post‑approval workstream encompasses two distinct areas often bundled too loosely: pharmacovigilance (PV) system setup and post‑approval change management.

Sponsors entering the EU must establish a QPPV and maintain a PSMF per EMA's Good Pharmacovigilance Practice (GVP) Module I. This is an organizational and documentation obligation, not simply a database vendor selection—and it must be in place at time of authorization, not after.

Post‑approval change management is a classification exercise: every change to an approved product must be classified under the applicable framework (US supplements or EU variations) and submitted accordingly. Consultants bring institutional knowledge of what triggers prior approval versus notification‑only categories and practical experience with how specific FDA divisions or EMA national authorities apply those rules in practice.

---

When to engage a consultant vs build in-house

The right choice depends on the actual capability gap, not merely program stage. Two early‑stage programs can have radically different needs depending on prior modality experience, expedited pathway eligibility, and the first target market.

The case for external engagement is strongest when the program requires regulatory expertise the in‑house team has not previously exercised—for example, a small‑molecule team approaching its first biologic. It is also warranted when submission load peaks in a compressed window that cannot be absorbed by existing headcount, or when a specific agency interaction requires pattern knowledge gained only through repetition.

The case for building in‑house is strongest when the company has a sustained pipeline in a defined therapeutic area and modality. In that scenario, internal capability investment pays back over a multi-year horizon in ways episodic consulting cannot match.

Two governance models are common. An embedded model places the consultant within the sponsor's team structure—attending internal program meetings, participating in cross‑functional decision‑making, and maintaining continuity across projects. This suits strategic gaps and programs where institutional familiarity is needed over many months. A project‑based model engages a consultant for a defined deliverable—a strategy memo, briefing package, or gap assessment—and ends when the deliverable is complete. This works for discrete tasks with well‑specified knowledge needs and a clear handoff point.

Beware over‑reliance on external consultants. It can slow internal capability building and leave sponsors exposed when the consulting relationship ends. The best engagements include explicit knowledge transfer: joint briefing package development or structured debrief sessions after agency interactions so internal staff build durable competence alongside the consultant.

---

Submission pathway decisions: US/EU/JP at a glance

Choosing the wrong submission pathway is expensive to reverse. An NDA submitted under an incorrect regulatory basis can be refused to file or require mid‑review restructuring, resetting review timelines with real commercial consequences. Pathway selection should be locked before the Phase 3 protocol is finalized, because evidence package requirements differ meaningfully across pathways and protocol design needs to be aligned with the chosen regulatory basis from the start.

US pathway decisions center on three questions: is the drug a new molecular entity with no prior approval, a modification of an approved drug, or a generic of an approved reference? Is the developer relying on its own clinical data, on a reference product's data, or demonstrating bioequivalence? And for biologics, is the product seeking original licensure or biosimilar designation?

For EU pathways, the initial question is whether the product is eligible or mandatory for the centralized procedure. If not, assess whether national routes (DCP or MRP) are appropriate given the target market footprint.

505(b)(2) vs ANDA vs BLA vs 351(k): choosing the right US path

An NDA under 21 CFR 314.50(b)(1) requires a complete proprietary data package. A 505(b)(2) NDA allows reliance on published literature or FDA's prior findings for a reference drug while typically requiring bridging studies. An ANDA under 21 CFR 314.94 requires demonstration of pharmaceutical equivalence and bioequivalence to a reference listed drug. ANDAs are only available when the proposed product matches the reference's active ingredient, dosage form, strength, route, and labeling.

505(b)(2) is not a shortcut but a flexible pathway for modifications of approved drugs—new formulations, routes, dosage forms, indications, or combinations—where reliance on existing data is scientifically justified. The clinical burden under 505(b)(2) is product‑specific. FDA may require bridging PK studies, comparative safety studies, or in some cases full efficacy studies. Sponsors should budget for this variability when projecting development timelines.

For biologics, 42 U.S.C. 262(a) (351(a)) covers original BLA licensure, while 42 U.S.C. 262(k) (351(k)) covers biosimilars and interchangeables. A 351(k) applicant must demonstrate biosimilarity to a licensed reference through a stepwise analytical, nonclinical, and clinical program. Sponsors evaluating biosimilar programs should check originator exclusivity dates and the queue of existing biosimilar applications for the target reference product. The FDA Purple Book provides searchable access to licensed biologics, biosimilars, and interchangeables, including exclusivity dates and patent-list records.

Quick decision cues for US pathway selection:

• New molecular entity with full proprietary data: 505(b)(1) NDA
• Modified form of an approved drug with some reliance on existing data: 505(b)(2) NDA
• Same active ingredient, dosage form, and route as RLD: ANDA
• Novel biologic with no approved reference product: 351(a) BLA
• Biologic referencing an approved 351(a) product with an analytical and clinical biosimilarity package: 351(k) BLA

EU centralized vs DCP/MRP vs national procedures

The EU centralized procedure is mandatory for certain categories (new active substances for HIV, cancer, diabetes, neurodegenerative disease, autoimmune disease, and rare diseases) and for all biotech‑derived medicines. It is optional for products representing a significant therapeutic innovation.

Centralized approval yields a single EU‑wide marketing authorization valid in all member states plus EEA countries. The decentralized procedure (DCP) allows simultaneous authorization in multiple member states with a Reference Member State driving the assessment. The mutual recognition procedure (MRP) applies where a product already authorized in one member state is subsequently sought in others. Both DCP and MRP result in national authorizations, creating a more complex variation landscape if the product later expands into additional markets.

Practically, centralized is administratively heavier upfront but simpler to maintain post‑approval since one variation filing can cover all markets. DCP or MRP can move faster for smaller initial footprints but accumulate variation complexity over time. Sponsors should weigh initial administrative cost against long‑term maintenance burden when the choice is discretionary.

---

Expedited and reliance options you should consider

Not every asset qualifies for an expedited pathway, and not every qualifying program should pursue one. The post‑marketing commitment burden associated with accelerated approvals and conditional marketing authorizations can be substantial, and additional evidence requirements sometimes outweigh time‑to‑market gains for assets with modest unmet need. For programs addressing serious conditions with genuine unmet need, however, bypassing an applicable expedited program can be a missed de‑risking opportunity worth examining with counsel early.

FDA administers several expedited programs. Fast Track supports drugs for serious conditions that show potential to address unmet need, offering more frequent communication and rolling review eligibility. Breakthrough Therapy Designation requires preliminary clinical evidence of substantial improvement over existing therapies and provides intensive FDA guidance and organizational commitment. RMAT designation applies to regenerative medicine therapies and combines Breakthrough benefits with eligibility for expedited CMC interactions.

Accelerated Approval allows approval based on a surrogate or intermediate clinical endpoint reasonably likely to predict clinical benefit, with confirmatory post‑marketing studies required. Priority Review shortens FDA's review clock from 12 to 6 months for drugs offering major advances or addressing areas with no available therapy.

EMA's PRIME scheme is the nearest EU analog to Breakthrough Therapy. It is available for medicines addressing unmet medical need with early clinical evidence (or promising preclinical data for ATMPs). PRIME provides an appointed rapporteur, enhanced interactions, and eligibility for accelerated assessment.

Project Orbis enables concurrent submission and review of oncology applications across multiple health authorities. Sponsors submit to FDA and request participation, enabling coordinated review across participating agencies. ACCESS Consortium provides a separate collaboration among several regulators for parallel assessment and work‑sharing to reduce duplicate review burden. Sponsors seeking simultaneous entry into multiple mid‑size English‑speaking markets should evaluate ACCESS eligibility early in planning.

---

Make your first agency interaction count

The risk in a pre‑submission meeting without adequate preparation is not just a non‑committal answer. It is receiving a written position that constrains the program operationally. Agency positions expressed during formal meetings are not legally binding but establish a reference point that reviewers consult and that applicants subsequently cite. A poorly framed question can produce a response that is technically accurate but operationally unhelpful—or one that forecloses a design option the sponsor had not yet ruled out.

Consultants who have managed repeated Type B meetings or EMA Scientific Advice requests add value by knowing which questions generate useful written commitments and which preserve regulatory flexibility. This pattern knowledge accumulates through repetition that most small in‑house teams cannot achieve rapidly on their own.

Pre-IND/Type B-C and EMA Scientific Advice/SAWP essentials

For FDA pre‑IND meetings, FDA's Formal Meetings guidance specifies that the meeting request should include the proposed agenda, a list of specific questions, the preferred meeting format, and background information. FDA will confirm a meeting date or provide a written response within 21 days of a Type B meeting request. The briefing document is due 30 days before the scheduled meeting.

For EMA Scientific Advice, sponsors submit a two‑stage briefing document. The procedure opens with rapporteur appointment, and a final Scientific Advice letter is issued within approximately 70 days for standard advice. Sponsors seeking both clinical and CMC advice typically coordinate a single request rather than sequential procedures, which avoids scheduling gaps and keeps the written response coherent across modules.

If Japan is in the global plan, PMDA's Pre‑Consultation and Consultation systems operate differently in document structure and meeting expectations from FDA and EMA. Aligning PMDA timelines early avoids conflicting commitments between markets. See the PMDA consultation information for current procedures.

Briefing package core components

A well‑constructed briefing package increases the probability that FDA or EMA's written response addresses the sponsor's strategic question rather than a peripheral technical point.

Core components for a pre‑IND/Type B package include, in sequence: cover letter with meeting type and preferred format; product description covering indication, mechanism, and target population with unmet‑need context; nonclinical summary including key toxicology and safety signals; prior clinical data (Phase 1 findings or published data if evaluating a 505(b)(2) pathway); proposed Phase 2 design with endpoints, dose rationale, and statistical approach; CMC overview appropriate to meeting stage (for pre‑IND, drug substance and product characterization and manufacturing description at current maturity); and a numbered regulatory question list grouped by topic.

Consultants tailor the depth of each section to meeting type and prior agency interactions so the package builds on earlier positions rather than re‑litigating resolved questions. A section that is too thin invites a request for more information; a section that is too detailed on settled points wastes the reviewer's attention.

---

eCTD pitfalls sponsors still trip on

A technically rejected eCTD submission cannot be reviewed until the technical issue is corrected and the sequence resubmitted. In many cases a technical rejection resets the review clock. A defect that takes a few days to correct can still cost weeks of actual review time if the PDUFA schedule is tight and the submission window has closed. The categories of errors that generate technical rejections are well documented by FDA and are, in most cases, avoidable with adequate pre‑submission checks.

Module 1 differences and technical rejection triggers

Module 1 is administrative and entirely region‑specific. FDA's Module 1 requires specific forms (Form 356h for NDAs/BLAs, Form 1571 for INDs), a defined cover letter format, and a folder structure under FDA's eCTD Technical Conformance Guide. EMA's Module 1 requires the European application form, a contact details section, and a different folder hierarchy under the EU eCTD Specification. A document set that validates cleanly for FDA will often need regional adaptation for EMA.

Common technical rejection triggers at FDA include broken hyperlinks, checksum mismatches between md5 manifests and files, lifecycle operation errors (particularly incorrect "replace" operations), metadata errors in backbone XML (incorrect document type codes or language attributes), and non‑bookmarked PDFs in sections that require bookmarks. EMA applies additional validation criteria specific to the EU backbone and Module 1.

Running a structural check before sequence transmission is the minimum quality step. Browser‑based validators that run ICH, FDA TRC, and regional checks locally—without moving dossier content off the submitter's machine—can surface lifecycle, hyperlink, metadata, and checksum issues before transmission. For example, Assyro's free eCTD validator runs 358 CFR, ICH, and FDA TRC structural checks across Modules 1–5, with lifecycle XML and checksum manifests validated locally in the browser. For teams managing recurring submission programs, platforms that validate structure and metadata continuously during authoring catch defects when they are still easy to remediate rather than in the final publishing sprint.

---

CMC control strategy: phase-appropriate expectations

A CMC control strategy is the integrated set of analytical procedures, specifications, manufacturing controls, and process monitoring approaches that together assure product quality. ICH Q8 introduced design space and Quality by Design; ICH Q10 aligned the pharmaceutical quality system to QbD; ICH Q11 extended the approach to drug substances; and ICH Q13 addressed continuous manufacturing. These guidelines define what "phase‑appropriate" means at each stage but leave documentation and presentation choices to sponsor judgment—where experienced consultants provide practical trade‑off advice.

At IND/Phase 1, regulators expect basic characterization, preliminary specifications with justification, and a manufacturing process description controlled enough to protect participants. They do not expect a fully developed design space or validated analytical methods. Overfiling a mature control strategy at Phase 1 is not harmful by itself, but it creates comparability and lifecycle obligations that can complicate later changes.

At Phase 3 and filing, expectations rise: process validation or performance qualification data should align with FDA's Process Validation guidance. Analytical method validation should meet ICH Q2(R1). Comparability data bridging clinical to commercial material is expected and must be analytically comprehensive.

Avoidable CMC deficiency themes

Many CMC deficiency letters trace back to recurring issues that sponsors and their consultants can address proactively:

• Insufficient specification justification: acceptance criteria not linked to clinical batch data, stability data, or clinical safety and efficacy findings.
• Process understanding gaps: parameters described without evidence that critical parameters and acceptable ranges are established and controlled.
• Stability protocol deficiencies: studies that fail to bracket commercial container sizes or use non‑representative clinical batches.
• Method validation gaps: insufficient demonstration of specificity, robustness, or cross‑validation between development and commercial methods.
• Comparability package incompleteness: bridging between development phases without a complete analytical comparability assessment.

Addressing these issues requires scientific judgment plus knowledge of how specific FDA divisions and EMA product teams historically apply guidelines. This experience-based knowledge is what seasoned CMC consultants supply that general documentation checklists cannot.

---

Post-approval changes: US supplements vs EU variations

Post‑approval, every change to the approved dossier must be managed under the applicable change control framework. Misclassifying a change—filing at a lower level than required or over‑filing—has real consequences. Under‑filing can expose the sponsor to enforcement exposure. Over‑filing (treating a minor change as a PAS, for example) creates unnecessary delays and resource drain without a corresponding regulatory benefit.

Under 21 CFR 314.70, FDA classifies NDA changes into three tiers. Prior Approval Supplements (PAS) require FDA approval before implementation for major changes such as new manufacturing sites for sterile products. Changes Being Effected (CBE‑30 and CBE‑0) cover changes with different pre‑implementation notification periods. Annual reports cover minor changes.

EU centralized procedure variations are governed by Commission Regulation (EC) No 1234/2008 and classified as Type IA (minor, notify after implementation), Type IB (moderate, notify before implementation with a 30‑day window), or Type II (major, full assessment required). ICH Q12 introduced the Post‑Approval Change Management Protocol (PACMP), allowing sponsors to define in advance how future changes will be managed and reducing per-change regulatory burden once the protocol is approved.

A practical illustration: changing a drug product manufacturing site from a clinical‑phase CMO to a commercial facility is almost always a PAS in the US for sterile parenterals and likely a Type II variation under EU centralized procedure. For dual‑market products, the more demanding requirement typically drives timelines. Consultants who have navigated simultaneous US/EU filings can prevent premature US submissions that create compliance gaps if EU assessment is still pending.

---

PV obligations at market entry: REMS vs RMP and QPPV basics

PV obligations at first approval are non‑negotiable and differ significantly between US and EU frameworks. Sponsors entering their first market should run PV system setup as a parallel workstream to the submission, not a post‑approval task—the obligations are assessed at time of authorization and gaps can delay approval.

In the US, FDA may require a Risk Evaluation and Mitigation Strategy (REMS) when necessary to ensure a drug's benefits outweigh its risks. REMS range from Medication Guides to ETASU (Elements to Assure Safe Use), which can include restricted distribution, prescriber certification, or required patient enrollment. Sponsors with known safety signals should model REMS scenarios before filing. See FDA REMS information for statutory and operational detail.

In the EU, a Risk Management Plan (RMP) is required for all new marketing authorization applications and must be submitted as part of Module 1.8.2. The RMP details safety specification, pharmacovigilance plan, and risk minimization measures; EMA's GVP Module V provides the template and content requirements. The QPPV role is a statutory EU requirement: every EU MA holder must designate a qualified person responsible for pharmacovigilance—a physician or pharmacist residing and operating in the EU—responsible for the PV system. The PSMF must be maintained at the QPPV's location and updated when system elements change. EudraVigilance registration and E2B(R3) adverse event reporting obligations begin at authorization. Sponsors should confirm their safety database vendor's registration and transmission capability before filing, not after.

---

Selecting and budgeting for a consulting partner

The decision‑useful question when choosing between firms is which one's capabilities and engagement model match the program's gap, timeline, and risk profile—not which firm has the longest client list in a broadly adjacent area. Technical tools—AI document intelligence, automated regulatory change tracking, and eCTD validation—are now widely available. When evaluating partners, ask how they use these tools operationally, not just whether they are aware of them.

Pricing models and scope drivers

Three pricing models dominate: project‑based fixed fees for defined deliverables (strategy memos, briefing packages), retainers for an agreed advisory availability, and Functional Service Provider (FSP) models where a dedicated consultant or team acts as a headcount extension on time‑and‑materials. Cost drivers include modality complexity (small molecule vs biologic vs ATMP), number of target markets, program stage (earlier stages tend to generate more iterative advisory work), and whether agency meeting participation is included in scope. Meeting‑facing consultants with extensive Type B or SAWP experience command different rates than those focused primarily on document preparation. Pricing details vary by firm and engagement scope; contact prospective partners directly for current rate structures.

SOW deliverables and KPIs that keep work accountable

A statement of work should define outputs, not inputs. Measurable outputs include: a regulatory strategy memo with pathway recommendation and milestone sequencing; a briefing package draft and sponsor‑approved question list; an agency response analysis memo; a CMC gap assessment with findings, severity classification, and remediation recommendations; and an eCTD readiness report covering structural validation, Module 1 completeness, and lifecycle status.

Governance cadence should include weekly or biweekly check‑ins, written status updates tied to milestones, and an escalation path for scope or timeline changes requiring sponsor leadership decisions. Engagements that lack defined milestone outputs drift most often, so this governance structure is worth building into the SOW before work begins rather than retrofitting it later.

Due-diligence questions and security checks

Before engaging a firm, cover these areas:

• Modality experience: request documented examples of submissions or agency interactions in the same molecule class.
• Regional footprint: confirm which agencies the lead consultant has direct experience with, distinguishing advisory familiarity from hands‑on submission management.
• Meeting experience: ask how many pre‑IND, Type B, or EMA Scientific Advice interactions the lead consultant has managed as the primary sponsor‑side point of contact.
• System controls: for consultants accessing sponsor systems, confirm 21 CFR Part 11 compliance posture and Annex 11 considerations for EU-facing work.
• Conflict checks: confirm no concurrent engagement with a competitor program in the same indication or with a competing applicant for the same reference product.
• Qualification markers: Regulatory Affairs Certification (RAC) is a recognized credential; prior regulator experience (ex‑FDA, ex‑EMA) in a relevant review division is a complementary signal worth probing for role and tenure.

---

On-page tools you can use now

The following assets are drawn directly from this guide and can be applied without downloads.

Pathway decision checklist (US)

• Is the molecule a new active moiety with no prior FDA approval? → 505(b)(1) NDA
• Is it a modification of an approved drug (new formulation, route, indication, or combination) with reference data? → 505(b)(2) NDA
• Is it chemically identical to a reference listed drug with the same dosage form and route? → ANDA
• Is it a novel biologic (protein, antibody, cell therapy, gene therapy) with no approved reference? → 351(a) BLA
• Is it a biologic referencing an approved 351(a) product with an analytical and clinical biosimilarity package? → 351(k) BLA

Pre-IND briefing package outline

A pre‑IND/Type B package for an early‑stage program should include, in sequence: cover letter with meeting type and preferred format; product description (indication, mechanism, target population); nonclinical summary (toxicology and safety signals); prior clinical data (dose escalation, PK/PD, safety); proposed Phase 2 protocol (design, endpoints, statistical approach, dose rationale); CMC overview (drug substance characterization, formulation, manufacturing description at current stage maturity); and a numbered regulatory question list grouped by topic.

Consultant evaluation scorecard (suggested weights)

• Modality‑specific submission experience (30%): prior submissions in the same molecule class with documented outcomes
• Regional meeting experience (25%): direct experience managing FDA Type B or EMA SAWP interactions
• CMC depth (15%): technical depth in the relevant manufacturing platform
• RIM and eCTD operations competency (15%): demonstrated publishing and validation experience
• System controls and data handling (10%): 21 CFR Part 11 and Annex 11 awareness and documented data handling practices
• Governance and communication (5%): SOW discipline, milestone tracking, and escalation protocol

Score each criterion 1–5, apply the weights, and total to compare shortlisted firms on a consistent basis rather than through competing narratives.

---

Making the final decision

If the checklists above surface a clear gap—a pathway choice that is not yet locked, a CMC control strategy that is under‑documented relative to phase expectations, or an agency meeting approaching without a structured briefing package—that is where to start. Match the specific gap to the relevant workstream (strategy, CMC, submissions, or PV), scope the engagement to the output that closes it, and apply the consultant scorecard to select the right partner for that task.

For sponsors unsure whether their eCTD sequences are structurally sound before engaging a submissions consultant, running a structural pre-check using a browser-based validator is a low-cost first step that surfaces issues without exposing dossier content. Assyro's free eCTD validator runs Modules 1–5 checks locally in the browser. Teams that want to model the operational and financial impact of submission workflow changes before committing to a platform or staffing decision can use Assyro's regulatory ROI calculator to configure a baseline and see the annualized impact in real time.

The narrower and more specific your scope definition going into any consulting engagement, the more accountable the SOW becomes—and the more precisely you can evaluate whether the engagement delivered what the program needed.