Technology Transfer
Technology transfer moves a product and everything known about it from a sending unit to a receiving unit: development to first commercial site, site to site within a network, sponsor to contract manufacturer. ICH Q10 names it as a distinct lifecycle stage with a specific goal — to transfer product and process knowledge sufficient for the receiving unit to manufacture and control the product — and that framing is the whole discipline. What transfers is not a recipe but a body of knowledge: the control strategy and its rationale, critical quality attributes and process parameters with their ranges and their history, analytical methods with their validation evidence, known failure modes, and the accumulated "why" behind every number that a bare batch record omits.
What this page does not claim
Phases are an organising device, not a regulatory mandate — real programmes overlap them, and a medical device, a food product and a small-molecule drug traverse them differently. Each page says where the differences bite.
What happens in this phase
Technology transfer moves a product and everything known about it from a sending unit to a receiving unit: development to first commercial site, site to site within a network, sponsor to contract manufacturer. ICH Q10 names it as a distinct lifecycle stage with a specific goal — to transfer product and process knowledge sufficient for the receiving unit to manufacture and control the product — and that framing is the whole discipline. What transfers is not a recipe but a body of knowledge: the control strategy and its rationale, critical quality attributes and process parameters with their ranges and their history, analytical methods with their validation evidence, known failure modes, and the accumulated "why" behind every number that a bare batch record omits.
The work is protocol-driven. A transfer plan defines scope, responsibilities, success criteria, and the gap assessment between sending and receiving capability — equipment differences, scale differences, utility and environmental differences, personnel experience. Analytical methods transfer first, because nothing else can be judged until the receiving laboratory can measure reliably: comparative testing or co-validation demonstrates the receiving lab gets the right answer, with method performance managed across the lifecycle per ICH Q14 and USP <1220> thinking. Process transfer then proceeds through engineering and demonstration batches toward the qualification and validation activities of the next phases, with comparability of product quality between sites as the standing question.
Where the transfer touches a marketed product, the regulatory dimension binds: a new site or a changed process may require variation, notification, or prior approval depending on what was registered — which is where the ICH Q12 vocabulary of established conditions earns its keep. Quality owns the transfer's honesty: gap assessments that record inconvenient differences rather than smoothing them, acceptance criteria set before the batches are made, and a transfer report that states what was and was not demonstrated. A transfer declared successful because the timeline needed it — with differences parked as "equivalent" on assertion — is the origin story of a disproportionate share of later validation failures and market complaints.
- A defined process at the sending unit with documented control strategy, CQAs, CPPs, and their development history.
- A receiving unit assessed as capable — equipment, utilities, personnel, and quality-system readiness — with gaps identified and dispositioned.
- An approved transfer protocol with responsibilities, success criteria, and comparability acceptance criteria agreed by both units.
- Analytical methods with validation evidence available for transfer or co-validation at the receiving laboratory.
- Analytical methods demonstrated at the receiving laboratory against pre-set acceptance criteria.
- Demonstration or engineering batches meeting the comparability criteria, with differences investigated and dispositioned.
- An approved transfer report stating what was demonstrated, what remains open, and the basis for proceeding.
- Regulatory impact assessed and any required variations or notifications identified and planned.
- The receiving unit ready to enter qualification and validation with a complete knowledge package.
SPEQ synthesis. Phase boundaries and gate criteria are an organising device for planning and review, not a regulatory mandate. Real programmes overlap phases and re-enter them; treat these as the questions worth answering, not a compliance checklist.
- Approve the transfer protocol and hold both units to acceptance criteria set before, not after, the results exist.
- Own the gap assessment's integrity — differences between sites recorded and risk-assessed, never waved through as equivalent by assertion.
- Oversee analytical method transfer, the precondition for every other judgement in the transfer.
- Assess regulatory impact against the registered details, engaging the variation process where the transfer touches established conditions.
- Approve the transfer report and the decision that the receiving unit may proceed.
- The transfer protocol — scope, responsibilities, success criteria, comparability plan
- Gap and risk assessments between sending and receiving units
- Analytical method transfer protocols and reports
- Engineering / demonstration batch records and their comparability data
- The knowledge package: control strategy, parameter history, known failure modes, development rationale
- The approved transfer report and regulatory impact assessment
- Transferring the batch record without the knowledge — the receiving site can execute the recipe but cannot recognise or diagnose an excursion.
- Declaring equipment "equivalent" on nameplate data, discovering at validation that mixing, heat transfer, or environment differ in ways that matter.
- Compressing method transfer to protect the timeline, so every subsequent comparability judgement rests on a measurement no one fully trusts.
- Success criteria negotiated after the batches are made, converting the protocol from a test into a rationalisation.
- Regulatory impact assessed last, so a technically successful transfer stalls unmarketable while variations catch up.
Derived from the 7 standards SPEQ maps to this phase, across 4 regulatory bodies: FDA, EMA, ICH, USP.
FREQUENTLY ASKED
Is technology transfer a regulatory requirement or just good practice?
Both, depending on where you look. ICH Q10 makes technology transfer one of the four pharmaceutical lifecycle stages a quality system must cover, and EU GMP expects transferred processes to be shown suitable at the receiving site before commercial use — the qualification and validation framework of Annex 15 picks the transfer up directly. Where a marketed product moves site, the change almost always engages the registered details, making it a regulatory transaction as well as a technical project. The discipline of protocols, acceptance criteria, and transfer reports is how firms make all three obligations demonstrable.
Why do analytical methods transfer before the process?
Because every judgement about the process at the receiving site is made through the methods. If the receiving laboratory cannot demonstrate it obtains valid results — by comparative testing against the sending lab, co-validation, or another justified approach — then apparent process differences cannot be distinguished from measurement differences, and comparability data is uninterpretable. Method transfer failing quietly is worse than it failing loudly: a bias that goes undetected shifts every subsequent result, and can surface later as a cluster of out-of-specification results that the process did not cause.
What belongs in the knowledge package beyond the batch record?
The "why" that the batch record deliberately omits. The control strategy and the rationale for each control; critical process parameters with their proven ranges and what happens outside them; the development history that explains why the process is shaped as it is; known failure modes and near-misses; analytical method quirks and their history; stability behaviour; and raw-material sensitivities. A receiving site holding only the recipe can make product until something drifts — then it lacks the understanding to investigate. The measure of a good transfer is whether the receiving unit can troubleshoot, not merely execute.