Cell Bank Documentation That Actually Holds Up in an IND Filing

IND filings are full of documentation surprises. One of the most common — and most avoidable — is a cell bank package that looks complete until a reviewer asks for something that wasn't recorded during development. That missing document usually doesn't exist because no one made a deliberate decision to skip it; it just wasn't on anyone's list at the time. By the time you need it, the cells are three passages away from where the question applies, and reconstructing the answer is either expensive or impossible.

This post covers the cell bank documentation elements that FDA reviewers look for in a biologics IND and the gaps that most early-stage programs discover late. It is not regulatory advice — if you're filing an IND, you need a regulatory consultant reviewing your specific CMC package. What this is: a practical orientation for founding scientists who want to understand what "IND-quality documentation" actually means before they start generating it.

The Regulatory Framework: What Module 3 Expects

Cell bank documentation in an IND lives in Module 3 of the Common Technical Document (CTD), specifically under 3.2.A.1 (Facilities and Equipment) for GMP context and 3.2.S.2.3 (Control of Materials) for the biological source and characterization of the cell substrate. For phase 1 INDs, FDA expects less than for later phases, but the expectations are still non-trivial. The records you don't generate in phase 1 become the records you have to reconstruct for phase 2 — when you're under more pressure, not less.

The key documents the agency expects to see include:

• Master Cell Bank (MCB) and Working Cell Bank (WCB) characterization reports, documenting identity, viability, sterility, and mycoplasma test results
• Passage history from the parental cell line through MCB establishment and WCB preparation
• Genetic identity confirmation — sequence verification of the expression construct including the transgene coding sequence, promoter, selection marker, and regulatory elements
• Integration site characterization for stably transfected lines (required for phase 2/3; advisable to establish at phase 1)
• Stability data — documented expression consistency across the relevant number of passages for the intended production run
• Certificate of Analysis (CoA) for each cell bank lot

The Five Most Common Documentation Gaps

1. Incomplete Passage History

FDA expects to trace the cell line lineage from the original parental source through every manipulation that resulted in your MCB. This means documented passage numbers, media formulations at each stage, the date and purpose of each banking event, and the operator who performed each step. Most early programs maintain informal records in an ELN that capture enough to reconstruct the science — but not the chain of custody in the format that a technical review requires. The gap appears when the ELN notes say "expanded from vial in -80 freezer, passage ~15" and the reviewer asks what "~15" means and who verified it.

2. Missing Mycoplasma Testing Documentation

Mycoplasma testing is required for the MCB. Most programs do test for mycoplasma, but the test report is sometimes filed separately from the cell bank package, or is an informal PDF from a contract lab that doesn't include the SOP version, lot number of the testing reagents, and GLP compliance statement that make it technically acceptable. The test itself costs $300–$800. The documentation audit takes three days to reconstruct if the original report is incomplete.

3. Absent or Informal Genetic Identity Records

Sequence verification of the expression construct is not optional, and "we sequenced it when we cloned it" is not documentation. What FDA expects is a formal sequence confirmation report that includes the full sequenced region, alignment to the intended construct map, identification of any sequencing artifacts, and a clear statement that the identity-confirmed construct is the same construct used to establish the cell bank. Sanger sequencing results saved as .ab1 files on a lab computer are not that report. They're the raw data. The report is the document that interprets and certifies those results.

4. Stability Data Gaps at Key Passage Points

For a phase 1 IND, FDA accepts limited stability data — typically expression consistency across the passage range that encompasses your intended production run. If your bioreactor process runs to passage 40, stability data through passage 40 is expected. We've seen programs that characterized expression through passage 20 and then ran their actual process at passage 38, with no data connecting those two points. The gap creates a question reviewers will ask and that you can't answer retroactively with the original material.

5. CMO Transfer Documentation Not Established at Bank Creation

If you're planning to transfer your cell bank to a CMO for process development or GMP manufacturing, the technical transfer dossier needs to be in a format the CMO can use without reconstruction. Programs that create documentation purely for FDA review often discover that their CMO needs additional detail — induction protocol, recommended media formulation, freezing protocol, outgrowth kinetics — that wasn't systematically recorded during development. Generating that information retroactively from informal lab notes is slow and sometimes impossible if the originating scientist has left the team.

Building Documentation at the Right Time

The right time to establish IND-quality documentation discipline is when you're setting up your cell bank generation workflow — not six months before you file. The marginal time cost of documenting correctly from the start is small. The cost of reconstructing incomplete records is large.

A practical checklist for programs entering MCB establishment:

1. Assign a single custodian responsible for the cell bank documentation package — not the science generally, but the documentation specifically.
2. Establish a formal SOP for each step: transfection, selection, single-cell cloning, clone screening, MCB expansion, cryopreservation, and WCB preparation. These don't need to be GMP SOPs for phase 1, but they need to exist in a controlled format with version numbers.
3. Record all passage numbers formally, with dates, operators, and vial inventory at each passage.
4. Commission mycoplasma testing from a lab that issues GLP-compliant reports, and file the original report in your cell bank package.
5. Perform formal sequence confirmation of the expression construct post-selection and document it as a report, not just a raw file.
6. Define the passage range for your intended production runs before you start stability passaging, and design the stability screen to cover that range plus a 20% margin.
7. Start building the technical transfer dossier format during development, not at the point of CMO handoff. Use the CMO's preferred format if you know who they are, or use an FDA CTD-aligned format if not.

What "Audit-Ready" Actually Means in Practice

Audit-ready documentation doesn't mean every document is perfect — it means every document has been reviewed, dated, signed by the responsible operator, and filed in a location you can retrieve within one hour if asked. For early programs, this is often a well-organized shared drive with a clear naming convention and an index document that maps every document to the CTD section it supports. That's minimal, but it works.

The most useful test of your documentation package: can someone who wasn't involved in generating the cell bank reconstruct the full development history from your records alone, without asking you a single question? If the answer is no, your package has gaps.

We include a complete technical transfer dossier — formatted to align with FDA and EMA CTD expectations — in every cell bank we deliver. This isn't because we expect all our partners to file INDs immediately; it's because the cost of producing that documentation during development is essentially zero relative to the cost of producing it after the fact. For the partners who do reach IND-enabling work, having a clean documentation chain from the start of the program is worth months of prep time saved.