Regulatory Support (IND/IMPD/BLA)

Regulatory Support (IND/IMPD/BLA) — CMC dossiers that match the plant

Dual hubs: San Diego, CA (Southern California) & Montréal, Canada
Scope: Strategy and authorship for IND/IMPD/CTA/BLA/NDA quality (CMC) sections; Module 2 QOS and Module 3 Quality; regional Module 1 content; gap assessments; pre-IND/Scientific Advice briefing packages; query/clock-stop management; comparability and post-approval change control; eCTD build & lifecycle management; PAI readiness; global alignment (US/EU/UK/CA; veterinary routes mapped separately).

A submission is credible only when the dossier, the process, and the plant tell the same story. We start with the control strategy you will actually run, then we write CMC to that reality—no placeholders, no folklore. We keep ranges operator-holdable, acceptance criteria defensible, and every table traceable to source data with audit trails (ALCOA+). The result is a file that reads cleanly in review and stands up in inspection.

Why teams choose MycoVista for regulatory CMC

  • Process-first authorship. We don’t write around gaps; we close them or document risk and mitigation. CMC tables tie directly to recipes, validation reports, and batch records (eBMR/eBR).
  • Cross-modal literacy. mAbs/biologics, microbial enzymes, AAV & pDNA, LNPs (mRNA/siRNA/DNA), fill–finish, and select small molecules—each with the right annexes (viral safety, dsRNA, empty/full, topology, residuals, cleaning).
  • Regulator-facing discipline. Pre-IND/IMPD Scientific Advice packages that ask targeted questions; RFI/IR management with signed owners, data sources, and response statistics plans.
  • Global pragmatism. US FDA (CDER/CBER/CVM), EMA/NCAs, MHRA, Health Canada; eCTD granularity, lifecycle, and validation handled in-house; veterinary biologics/drugs routed via USDA-CVB/FDA-CVM when applicable.
  • Inspection linkage. We write for PAI: site narratives, equipment/utilities tables, training and deviation/CAPA summaries, CPV dashboards—so reviewers see the same record QA will present onsite.

Where CMC files usually crack—and how we prevent it

  • Design ≠ dossier. Specs and ranges on paper that cannot be held on the line. We publish NOR/PAR that match eBMR recipes (with interlocks/alarms).
  • Method drift. Transfers that changed answers. We insert equivalence metrics and cross-site trending into the file.
  • Incomplete validation. Sterile filtration, viral safety, hold-time, cleaning, and E/L treated as “later.” We validate what the product needs and write the evidence.
  • Comparability on the fly. Site/scale/material changes without prespecified windows. We file comparability protocols before we move.
  • eCTD mechanics. Wrong granularity, broken bookmarks, lifecycle mistakes. We run technical validation and lifecycle plans up front.

Program spine: from first meeting to marketing application

  1. Regulatory mapping & risk register. Product class, jurisdiction(s), pathway, meetings to request, data you have vs. need, critical path risks.
  2. Pre-IND / Scientific Advice. Concise questions, proposed approaches (process, analytics, validation), and alternatives; meeting minutes folded back into the plan.
  3. Authoring plan. CTD structure, owners, source tables, statistics, and references; Module 3 outline frozen early so development produces the right artifacts.
  4. eCTD build & validation. Granularity, file naming, hyperlinks/bookmarks, regional M1, STF where applicable, lifecycle sequences.
  5. Submission & review. RFI/IR/clock-stop playbooks; data owners and statisticians assigned; audit trails & raw data linked.
  6. Inspection readiness. PAI/QAR binders, site narratives, validation/CPV summaries, deviation/CAPA packs; mock interviews and floor routes.
  7. Post-approval. Change-classification matrices (US supplements; EU Type IA/IB/II); comparability designs; PV and stability commitments; labeling and CBE timelines.

eCTD structure (what we actually write)

  • Module 2 (Quality Overall Summary, 2.3)
    • QOS narrative anchored to the control strategy: DS/DP overviews, process flow diagrams with CPPs, specs/justifications, validation synopsis, stability/shelf life logic, comparability summary.
  • Module 3 (Quality)
    • 3.2.S Drug Substance: manufacturer(s); controls of materials; description & flow; process controls (CPPs, in-process limits); process validation/verification plan; characterization (identity/impurities/variants); reference standards; container closure; stability.
    • 3.2.P Drug Product: composition; development pharmaceutics (e.g., high-conc SC or lyo rationale); manufacturing & controls (batch formula, descriptions with IPCs/interlocks); process validation (filtration, holds, lyo); specifications & justification; analytical methods & validation; container-closure; stability (including in-use).
    • 3.2.A Appendices: adventitious agents safety, viral safety (biologics), E/L risk summaries, facility & equipment where region requires.
    • 3.2.R Regional: site-specific elements; comparability protocols (when agreed); environmental assessments where applicable.

We maintain trace tables that cite source documents (method reports, validation studies, stability stats, batch records) for every statement.

Modality annotations (what reviewers expect to see)

mAbs / complex biologics

  • CQAs: glycan window, charge profile, aggregate limits, potency model.
  • Validation: Protein A loading & cleanability data; ion-exchange/HIC selectivity evidence; low-pH inactivation kinetics; viral filtration pressure–time; UF/DF shear/aggregation thresholds.
  • DP: high-concentration viscosity & filter recovery (PFS) or lyo cycle physics with residual-moisture & reconstitution data.

Microbial proteins / enzymes

  • USP physics: oxygen transfer & carbon uptake limits at scale; induction temperature/pH windows.
  • DSP: endotoxin control strategy; IB/refold kinetics if used; impurity clearance maps.
  • Specs: activity as primary potency; residual DNA/protein & lysis agents; stability at use pH/temperature.

AAV & other vectors

  • Attributes: vg titer (qPCR/ddPCR with inhibition controls), capsid, empty/full methodology & acceptance, potency, residuals (DNA/protein/nuclease/detergents), sterility/endotoxin/mycoplasma.
  • Separation: charge-based e/f with orthogonal confirmation; lot-to-lot stability narrative.
  • Plasmids: topology, residuals, endotoxin; linkage to vector production.

Plasmid DNA (pDNA)

  • Topology: SC/OC/L as release and stability attributes; filtration feasibility.
  • Process: alkaline lysis & clarification parameters; AEX capture & polish; QC with residual RNA/protein/gDNA and endotoxin.

LNPs (mRNA/siRNA/DNA)

  • Attributes: size/PDI, Enc%, nucleic-acid integrity and dsRNA (mRNA), residual solvent, osmolality/pH, potency, sterility/endotoxin.
  • Process: FRR/TFR/N:P ranges; TFF recipe with TMP/cross-flow limits; filtration feasibility (or aseptic justification).
  • Stability: Enc%/potency retention, size drift, dsRNA trend, in-use rules.

Fill–Finish / DP

  • Sterile filtration: feasibility on real bulk, recovery, integrity (pre/post; PUPSIT if applicable).
  • Inspection/CCIT: method & acceptance; visual inspection capability; label/pack/ship lane validation.
  • Lyo: collapse/eutectic; primary/secondary drying; residual moisture targets; reconstitution.

Small molecules (select)

  • Chemistry: control of stereochemistry/impurities; solid form & PSD; residual solvents (HS-GC); elemental impurities; cleaning validation (MACO/PDE).
  • DMF/ASMF: Type II DMF or ASMF referencing; LOA management; closed/open part discipline.

(Veterinary biologics/drugs are authored against USDA-CVB/FDA-CVM or EU CVMP frameworks; we build separate templates when those routes apply.)

Specifications & justification (how we defend the numbers)

  • Link to clinical & platform data. Justifications cite development distributions, clinical batches, and safety margins.
  • Tight where it protects risk, wide where it’s meaningless. E.g., charge tails with stability impact get limits; cosmetic attributes do not.
  • Statistic-aware. Capability, guardbanding, OOT rules, and sampling plans explained; for one-sided limits (e.g., endotoxin), appropriate confidence logic applied.

Comparability (planned, not improvised)

  • Protocols pre-filed for site/scale/material changes with equivalence windows and orthogonal confirmations.
  • Designs include side-by-side lots or matched historical controls; we declare analysis plans (e.g., TOST) before data lock.
  • Narratives show sameness or managed difference with risk assessment and mitigation.

Query & clock-stop management (how we keep tempo)

  • Triage. Categorize by theme (process, methods, validation, stability, facilities); assign owner & statistician.
  • Evidence. Pull source data with audit trails; if new analyses are required, protocolize them.
  • Response. Direct answers with tables/figures; cross-references to modules and appendices; commit only what the system can deliver.
  • Governance. Single editor; QA signoff; version control; deadline tracking; quality of service metrics kept.

Pre-Approval Inspection (PAI) readiness

  • Binders. Site master narrative, process description, validation dossiers (filtration/viral/holds/cleaning), training matrices, deviation/CAPA trend reports, EM/utilities CPV, stability trends.
  • Floor plan & routes. Gowning, flows, closed processing, materials segregation.
  • Mock interviews. Role-specific Q&A; document retrieval drills; eBMR/eBR navigation practice; alarm/interlock demonstration scripts.
  • Issue closure. Known deviations with CAPA & effectiveness; change-control histories; supplier/CMO coordination.

eCTD production & lifecycle (mechanics done right)

  • Granularity & naming per region; valid bookmarks/hyperlinks; technical validation before sequence build.
  • Lifecycle sequences. Initial, amendments, supplements/variations; linkages preserved; obsolete files retired correctly.
  • Publishing QA. Automated checks + human review against a defect checklist (broken links, wrong region, missing leaf titles).
  • Archival. Immutable storage with retrieval SLAs; sequence maps maintained.

Program Onboarding (first 30 days)

  1. Regulatory map & meeting plan. Jurisdictions, pathways, meetings to request, timelines.
  2. Gap assessment. Against CTD 3.2.S/3.2.P basics: control strategy, validation studies (filtration/viral/holds/cleaning), method quals/vals, stability design, specs rationale, CPV.
  3. Authoring outline & RACI. Module owners, tables/figures list, source data locations, statisticians assigned.
  4. Comparability & change matrix. Likely changes, protocol skeletons, acceptance windows.
  5. eCTD plan. Granularity map, lifecycle intent, technical validation tools, sequence naming.
  6. PAI plan (preview). Binder index, mock schedule, document requests list.

You provide: current control strategy, latest validation/method/stability files, batch records, and target filing windows.
We deliver: a signed plan with document numbers, owners, dates, and a risk register aligned to your milestones.

Indicative timelines (program-dependent)

  • Weeks 0–2: Mapping, gaps, pre-IND/SA question set, Module 3 outline frozen.
  • Weeks 3–6: Draft QOS and 3.2.S/P shells; validations/stability/comparability plans finalized; eCTD build harness tested.
  • Weeks 6–12+: Populate with executed studies & stats; internal QA review; technical validation; sequence build & submission.
  • During review: RFI/IR playbook active; responses tracked; PAI prep drills.
  • Post-decision: Label & post-approval commitments filed; change-classification matrix activated.

Deliverables (what you receive)

  • QOS (Module 2.3) and Module 3 ready for submission (word & publishable format).
  • Regional Module 1 content packages (forms/cover letters/certifications).
  • Validation & stability reports (filtration/viral/hold/cleaning/E/L; regression & shelf-life rationale).
  • Specifications & justifications with capability/guardband tables.
  • Comparability protocol(s) and executed reports (when changes occur).
  • PAI playbook (binders, mock Q&A, retrieval drills).
  • eCTD sequences (validated) and lifecycle plan.
  • Query responses with references and statistics; archive and trace tables.

FAQs (direct, practical)

Will you adopt our sponsor templates? Yes, if they support traceability and eCTD compliance; otherwise we adapt with change-tracked rationale.
Can you be the publisher of record? Yes—authoring, publishing, lifecycle, and archive.
How do you justify three PPQ lots? Risk-based narrative tied to Stage-1 maturity, process complexity, and market scope; capability and boundary evidence included.
Do you handle post-approval changes? Yes—US PAS/CBE-30/CBE-0; EU IA/IB/II; CA SNDS/NDS; comparability and re-validation plans included.
What about gene therapy extras (shedding/RCL)? We coordinate across modules; CMC references potency, vector identity, adventitious agent testing, and release/stability; nonclinical/clinical authors cover shedding/RCL.

Conclusion

Regulatory success is alignment: a control strategy operators can hold, validation that reflects real risk, analytics that read the truth, and a dossier that mirrors all three. We write to that standard—table by table, range by range—so review is predictable and inspection is a confirmation, not a discovery.

MycoVista | San Diego, CA & Montréal, Canada
Start Program Onboarding → Share your control strategy, executed studies, and target filing window. We’ll return a gap assessment, an authoring plan with owners/dates, and an eCTD map that carries you from submission through PAI and post-approval.

EN / FR support available.