Tech TransferTechnology Transfer

Technology transfer is the structured movement of a manufacturing process from one site (the Sending Unit, SU) to another (the Receiving Unit, RU). The process can be a clinical-to-commercial transfer, a site-to-site transfer within a sponsor's network, or — most commonly today — a sponsor-to-CMO transfer. ICH Q10 §2.3 frames it as a PQS responsibility; WHO TRS 961 Annex 7 provides the operational playbook.

A tech transfer that ships only the MMR and assumes the receiving site will figure it out is the most common cause of post-transfer failure. Process knowledge (the why behind every set-point) does not live in the MMR; it lives in the development reports, the failed-batch investigations and the operator know-how at the sending site.

1. Initiation — feasibility, business case, regulatory strategy. Determines whether the transfer is even worth doing.
2. Planning — transfer plan, project team (SU + RU + QA + RA), timeline, deliverables, acceptance criteria.
3. Knowledge transfer — development reports, batch records, deviation history, complaint history, stability data, validation reports, training material, process know-how.
4. Gap analysis — RU equipment vs SU equipment, RU SOPs vs SU procedures, RU analytical methods vs SU methods. The output drives the engineering plan.
5. Engineering / demonstration batches — RU runs the process at scale to demonstrate operability, identify gaps, debug.
6. Comparability — side-by-side analytical comparison of SU and RU batches against the established product profile (ICH Q5E framework for biologics, similar discipline for small molecules).
7. PPQ at the RU — receiving site runs its own PPQ under its own protocol against its own acceptance criteria.
8. Regulatory filings — depending on jurisdiction, prior approval supplement (FDA CBE-30, PAS, AR), Type IA/IB/II variation (EU), Lifecycle Management under ICH Q12.
9. Close-out — transfer report, lessons learned, retention plan for SU records, decommissioning if applicable.

The MMR is the tip of the iceberg. A complete knowledge package includes: every development report (Stage 1 of FDA PV); every PPQ report from the SU; every Stage 3 CPV report; every deviation, OOS and OOT investigation since launch; every CAPA effectiveness review; every change control; every complaint trended; every stability shelf-life extension; every recall; every annual product quality review.

Beyond documents, the SU must transfer process know-how: the operator tricks (the order of additions that prevents foaming, the impeller speed at which the granulation breaks), the equipment quirks (the heat exchanger that runs 2 °C high on the inlet), the supplier nuances (the polymer grade from supplier A behaves differently than the same grade from supplier B). This is best done by on-site secondments — SU operators at the RU, RU operators at the SU.

Comparability is the formal demonstration that the RU-made product is the same as the SU-made product within the established product profile. For small molecules: assay, related substances, dissolution, content uniformity, physical attributes — typically compared on 3+ RU batches against the SU's historical performance with statistical testing (two-one-sided t-tests, equivalence margins per the ICH Q12 framework).

For biologics, ICH Q5E codifies the comparability exercise: structural characterisation (peptide map, glycan profile, charge variants), functional characterisation (potency, binding), purity (HCP, HCD, aggregates), stability. Biologics comparability is more rigorous than small-molecule because the process IS the product — minor process differences can produce structurally different molecules.

ICH Q12 introduced the Established Conditions framework, which allows the sponsor to define in the dossier which conditions require which filing class — reducing the regulatory burden of routine post-approval changes including tech transfers. Adoption varies by region (FDA and EMA explicit, others slower).

1. Transfer plan written after the work started — no pre-defined acceptance criteria.
2. Knowledge package is the MMR only — no development reports, no investigation history.
3. Gap analysis missing or completed pro forma — equipment differences glossed over.
4. Engineering batches skipped — first RU batch was PPQ #1.
5. Comparability acceptance criteria invented after the SU/RU data was in hand.
6. PPQ acceptance criteria at the RU looser than at the SU without justification.
7. Regulatory filing classification wrong — major change filed as minor, exposed at inspection.
8. SU records destroyed prematurely after transfer — investigation history lost.

• Tech-transfer project objects link the SU and RU tenants (or sites within a multi-site tenant) with the shared knowledge package.
• MMR replication is version-locked — the RU's MMR is forked from the SU's, with a documented diff for every deviation.
• Engineering batches, demonstration batches and PPQ batches are tagged with their transfer-phase classification so reports group correctly.
• Comparability templates run side-by-side analytical comparisons with the established statistical tests; acceptance criteria pre-locked in the protocol.
• Regulatory filing tracker maps each change to FDA/EMA/MHRA/Health Canada/PMDA/NMPA expectations and tracks submission status.
• Knowledge-transfer checklist enforces the document set (dev reports, validation, CPV, deviations, stability) before PPQ can start.