Technology Transfer to a CDMO: The Readiness Checklist

The short answer: A technology transfer is ready when the receiving site could, in principle, make the product from the documents alone. That means a complete knowledge package (process description, critical quality attributes, critical process parameters and proven ranges, material and equipment specifications), an analytical method transfer plan with acceptance criteria, a written gap analysis between the sending and receiving sites, a transfer protocol with success criteria and governance, and signed quality and technical agreements. Most transfers that slip are missing one of those five things on day one, not failing at the engineering batch. If you want an independent check of the package before you commit to a site, that is exactly what a CMC and tech-transfer readiness review covers.

Technology transfer is the hand-over of a manufacturing process, its analytical methods and the knowledge behind them from one party or site to another: sponsor to CDMO, development to commercial scale, or one CDMO to another. ICH Q10 treats it as a stage of the product lifecycle with its own objectives; the ISPE Good Practice Guide: Technology Transfer and the WHO guideline on technology transfer in pharmaceutical manufacturing (TRS 1044, Annex 4, 2022) describe how to run one. This checklist distils what those documents expect into the order a small team actually meets it.

Start with the decision the transfer serves

A transfer exists to hit a milestone: a first GMP batch for Phase 1, scale-up for Phase 3, process performance qualification before a filing, or continuity after a CDMO change. Write that milestone, its date and the batch size it needs at the top of the protocol, because every later trade-off (how much development to repeat, how many engineering batches to run, whether to revalidate methods) is decided against it. Teams that skip this step argue about scope for months.

1. The knowledge package

The receiving site needs to understand the process, not just follow it. The package should contain, as documents the receiving site can read without a call:

1. Process description end to end, with a flow diagram, unit operations, in-process controls and hold times.
2. Quality target product profile and critical quality attributes (CQAs), with the rationale for each, in the sense of ICH Q8(R2).
3. Critical process parameters (CPPs) and their proven acceptable ranges, plus which parameters are scale-dependent and how they were derived.
4. Control strategy: which CQAs are controlled by which parameters, in-process tests, specifications and procedural controls (ICH Q11 for drug substance).
5. Material specifications for starting materials, intermediates, reagents, excipients and primary packaging, with approved suppliers and any single-source dependencies flagged.
6. Equipment list with principles of operation, critical settings and materials of construction, so equivalence at the receiving site can be judged.
7. Development and batch history: what was tried, what failed and why, deviations and their root causes. This is the part most often left out and most often needed.
8. Risk assessment of the process (the ICH Q9(R1) tools: FMEA or equivalent) carried forward, not re-started.

A quick test: hand the package to a scientist who has never seen the product and ask them to list the three things most likely to go wrong at the new site. If they cannot answer from the documents, the package is not ready.

2. The analytical method transfer plan

Methods move with the process, and they fail more often than the process does because they are assumed to "just work" on a different instrument with different analysts. USP <1224> Transfer of Analytical Procedures sets out four routes: comparative testing (both labs test the same samples), co-validation (the receiving lab takes part in the validation), revalidation at the receiving site, and a documented transfer waiver where justified. For each method the plan should state:

• which route applies and why;
• the samples, batches and number of replicates;
• the acceptance criteria, pre-agreed and numeric;
• the system suitability requirements and reference standards, with how the standards themselves will be qualified at the new site;
• the validation status of the method against ICH Q2(R2), and whether the new ICH Q14 development approach has been used to define the method's operating ranges.

Stability-indicating methods and any method used for release of the first GMP batch come first in the schedule, because nothing else can be released until they are in place.

3. The sending-vs-receiving gap analysis

Write down, line by line, every difference between the two sites and what will be done about it:

Area	Typical gaps	What closes them
Equipment	Different mixer geometry, dryer type, filter area, scale of reactor	Equivalence assessment; scale-down study; engineering batch
Scale	2× to 10× step changes in batch size	Identify scale-dependent parameters; adjust ranges with data, not by proportion
Materials	Different approved suppliers or grades at the receiving site	Supplier qualification; comparability of material attributes; update specifications
Utilities and environment	Water grade, compressed gas, humidity control, cleanroom classification (EU GMP Annex 1 for sterile products)	Site qualification evidence; environmental monitoring data
Analytical	Different instruments, columns, software, data-integrity controls	The method transfer plan above; instrument qualification
Quality system	Different deviation, change-control and OOS procedures and vocabularies	Quality agreement defines whose procedure governs each activity
People	Tacit knowledge held by one or two people at the sending site	Named knowledge holders, on-site presence for engineering batches, training records

The output is a list of actions with owners and dates. The gap analysis is also the honest basis for the budget: a transfer with a scale step, new suppliers and a method revalidation is a different project from a like-for-like site move.

4. The protocol and its success criteria

The transfer protocol is the single document that says what "done" means. It should contain the objective and milestone, the scope (which products, strengths, processes and methods), roles on both sides, the plan of engineering and demonstration batches, the acceptance criteria for each batch and each method, the comparability approach (how the receiving site's batches will be compared with the sending site's history), the change-control route, and the criteria for closing the transfer and moving into process validation under the FDA's 2011 Process Validation: General Principles and Practices stages or EU GMP Annex 15.

Success criteria must be numeric and agreed before the first batch is made. "Batch meets specification" is a minimum, not a success criterion; comparable yields, impurity profiles and in-process trends against the sending site's data are what show the process actually transferred.

5. Governance, people and the paperwork that binds it

• A quality agreement that assigns every GMP responsibility (release, deviations, change control, stability, complaints, audits) to one party, as the FDA's 2016 guidance on contract manufacturing arrangements expects.
• A technical agreement or statement of work covering batches, timelines, who pays for failed engineering batches, and ownership of data and intellectual property.
• A joint steering group with named decision makers and a cadence; a weekly technical call during batches.
• Knowledge holders on site. The people who developed the process should be present for the first engineering batch at the receiving site.
• Change control opened at the start, so every parameter adjustment during the transfer is recorded and assessed, not remembered.

Where transfers typically stall

The published guidance and the inspection record point at the same places. The knowledge package describes the process as validated rather than as developed, so the receiving site cannot tell which parameters matter. Analytical methods are transferred after the process rather than before, so the first batch cannot be released. Reference standards are not qualified at the new site. The quality agreement is signed after the engineering batch, so a deviation falls between two procedures. A single scientist at the sending site holds the "how", and leaves. None of these is a technical failure; all of them are readiness failures that a review of the documents would have found before any money was spent at the receiving site.

Choosing the receiving site is part of readiness

A transfer protocol cannot fix the wrong partner. Before committing, confirm the receiving site has made this dosage form at this scale before, holds a current GMP certificate and a clean recent inspection record (Form 483s, Warning Letters, recalls), has capacity in the window your milestone needs, and has analytical capability for your methods in-house rather than at a sub-contractor. The CDMO selection checklist covers the commercial and compliance screen; PharmaTek's directory links each site to its FDA enforcement record so that screen takes minutes rather than days. If you would rather have a team run the search, the Sourcing Desk does it for a fixed fee.

Frequently asked questions

What should a technology transfer package contain? A complete process description with flow diagram, the quality target product profile and critical quality attributes, critical process parameters with proven acceptable ranges and scale-dependence, the control strategy, material and equipment specifications, development and batch history including deviations, and the carried-forward risk assessment. The test is whether a scientist who has never seen the product could identify the main risks from the documents alone.

How is analytical method transfer done? USP <1224> describes four routes: comparative testing of the same samples by both laboratories, co-validation with the receiving laboratory taking part, revalidation at the receiving site, or a documented transfer waiver. Each method needs a stated route, samples and replicates, numeric acceptance criteria agreed in advance, and qualified reference standards at the receiving site. Release and stability-indicating methods go first.

What is the difference between technology transfer and process validation? Technology transfer moves the process and its knowledge to a new site and demonstrates, usually with engineering and demonstration batches, that the site can run it comparably. Process validation, in the FDA's three-stage model and EU GMP Annex 15, then shows the process consistently delivers quality at commercial scale through process performance qualification and continued verification. A transfer ends where validation begins.

How long does a technology transfer to a CDMO take? It depends on scale change, dosage form and how complete the package is; a like-for-like transfer of a simple oral solid is a different project from a sterile or biologic transfer with a scale step and method revalidation. The reliable way to shorten it is to finish the knowledge package, method transfer plan and gap analysis before the first site visit, because those three documents set the critical path.

When should you commission an independent readiness review? Before the transfer agreement is signed and before documents are shared with the receiving site. A review at that point finds the gaps in the package and plan while they are cheap to fix and while the scope of work with the CDMO can still be adjusted. PharmaTek's CMC and tech-transfer readiness review is a fixed-fee, vendor-neutral assessment built for small and virtual teams.

---

Preparing a transfer? Get an independent, fixed-fee read of your package and plan from the CMC and tech-transfer readiness review, or screen candidate receiving sites against their FDA records in the directory.