Technology Transfer
Technology transfer is the documented process of transferring product and process knowledge between development and manufacturing, or between manufacturing sites, so the receiving unit can reproduce the process in a state of control. It is where knowledge management meets process validation — and where quality is most often quietly lost.
What an explainer is not
A topic explainer is SPEQ’s synthesis of what a practice involves, cited to the standards that govern it. It does not reproduce their text, and it does not determine which of them apply to your product or process.
[ POSITION IN THE FRAMEWORK ]
7 DIMENSIONS · 24 LINKSTechnology transfer is where the GMP and quality-system disciplines hand a process between organizations: sending and receiving units prove comparability, and the knowledge package — not the batch record — is the real payload.
06 · QUALITY MATURITY — TECHNOLOGY TRANSFER, REACTIVE TO ADAPTIVE
Transfer means emailing batch records; the receiving site rediscovers the process through deviations.
A transfer protocol and report exist, but the package carries parameters without the rationale behind them.
A defined sending/receiving model moves the full knowledge package; comparability meets predefined criteria, methods transfer formally.
Transfer risk is assessed up front and post-transfer monitoring compares site performance against the sending baseline.
Knowledge management makes transfers routine: rationale, models, and development history travel with every process.
SPEQ’s shared five-stage progression, labelled synthesis — not the FDA QMM rating scale. Where does your organization sit? Score your quality system →
07 · REGULATORY & EVIDENCE
GOVERNING STANDARDS · 4
Derived from the 4 standards SPEQ maps to this subject, across 2 regulatory bodies: EMA, ICH.
RECORDS & OBJECTIVE EVIDENCE
- A transfer protocol and closure report with predefined acceptance criteria
- A knowledge package covering CQAs, CPPs, and control-strategy rationale
- Analytical method transfer protocols and results between sites
- Receiving-site qualification and process validation (PPQ) evidence
- Change control records and regulatory filings for the site change
COMMON INSPECTION FINDINGS
- Transfers executed without a protocol or predefined criteria
- Receiving sites holding parameters with no development rationale
- Analytical methods never formally transferred — two sites, two answers
- Post-transfer deviations rooted in knowledge that did not travel
- Distribution from the receiving site before required regulatory approval
The sending and receiving unit model
Technology transfer is framed as a controlled handover between a Sending Unit (which holds the validated process and its knowledge) and a Receiving Unit (which must reproduce it). It runs on a transfer protocol that defines scope, responsibilities, acceptance criteria, and the tests that will demonstrate success, closed out by a transfer report. Without that structure, a transfer becomes an uncontrolled experiment on a commercial product.
Knowledge transfer is the real payload
What actually moves is not just a batch record — it is understanding. The CQAs, CPPs, design space, control strategy, development history, and the reasons behind each parameter all have to travel with the process. ICH Q10 names knowledge management as a lifecycle enabler precisely because a receiving site that inherits parameters without the rationale cannot troubleshoot, and cannot safely improve.
Demonstrating comparability
A transfer is not complete when the equipment is installed — it is complete when the receiving site demonstrates the process performs equivalently. That means qualification of facilities and equipment, process validation / process performance qualification at the receiving site, and analytical method transfer so both sites test the same way and get the same answer. Comparability is the evidence, not the assumption.
Managing the change
A site change is a regulated change: it runs through change control, is assessed with quality risk management (ICH Q9), and — depending on scope — may require regulatory filings and approval before distribution. For APIs, ICH Q7 sets the GMP baseline the receiving site must meet. Technology transfer done well is a controlled, evidenced change; done badly, it is the root cause behind a surprising number of post-transfer deviations and shortages.
WORKED EXAMPLE — SPEQ SYNTHESIS
A hypothetical sponsor is transferring a commercial oral product from its own site to a contract manufacturer in another region. Both sites are GMP-licensed. The receiving site proposes to begin with three demonstration batches and asks what it needs from the sending unit first.
Establish what is being transferred, which is knowledge before it is a process
Batch records transfer easily; the reasoning behind them does not. Development history, the basis for each critical parameter, the failures the sending unit already had and what it learned from them — that is the asset, and omitting it is why transfers fail at the receiving site rather than at the sending one.
Compare the two facilities on equipment train and scale, in detail
Nominally equivalent equipment is routinely not equivalent in the ways that matter — geometry, shear, heat transfer, hold capability. The comparison has to be specific enough that a difference becomes a question rather than a surprise in the first batch.
Agree the acceptance criteria for the transfer before any batch is made
What result will be treated as a successful transfer, and on what attributes. Criteria written after data exists are an inspection finding, and the temptation to write them that way is strongest precisely here, because both parties want the transfer to succeed.
Transfer the analytical methods as a distinct exercise
A process transfer resting on an untransferred method is measuring the receiving site with the sending site’s assumptions. Method transfer has its own protocol, its own acceptance criteria and often its own timeline, and collapsing it into the process transfer is a common and expensive shortcut.
Write the responsibilities down in a quality agreement, including notification
Who decides, who is told, and within what time. The clause that matters in practice is change notification: a receiving site that changes a supplier or a parameter without telling the sending unit has broken the transfer without either party noticing.
Define what the demonstration batches must show, and what happens if they do not
Three batches that meet specification do not by themselves demonstrate a transferred process; they demonstrate three batches. The protocol should say what comparability means here and what the route is if the data does not support it.
A transfer package holding the knowledge as well as the documents, a specific facility comparison, pre-agreed acceptance criteria, a separate method transfer, a quality agreement with real notification triggers, and a stated route for an unsuccessful outcome. Whether the transfer succeeded is determined by the data against those criteria, by both quality units.
WHAT WOULD CHANGE THIS
- If the receiving site is in a different regulatory jurisdiction, the filing consequences may dominate the technical ones, and the sequence above runs alongside a regulatory strategy rather than ahead of it.
- A transfer of a sterile product adds the whole contamination control and aseptic qualification layer, which is not a variation on this sequence but an additional one.
- If the sending unit no longer employs the people who developed the process, the knowledge transfer step becomes reconstruction from records, and the transfer should be planned around that limitation rather than despite it.
FREQUENTLY ASKED
What is technology transfer?
The documented transfer of product and process knowledge between development and manufacturing, or between sites, so the receiving unit can reproduce the process in a validated state of control.
What are the sending and receiving units?
The Sending Unit holds the established, validated process and its knowledge; the Receiving Unit must reproduce it. The handover is governed by a transfer protocol and closed out by a transfer report with predefined acceptance criteria.
What actually gets transferred?
More than the batch record: the critical quality attributes, critical process parameters, design space, control strategy, and the development rationale behind them. This knowledge transfer — an ICH Q10 lifecycle enabler — is what lets the receiving site run and troubleshoot the process.
How is a technology transfer verified?
By demonstrating comparable performance at the receiving site — equipment/facility qualification, process validation (PPQ), and analytical method transfer — all managed under change control and quality risk management, with regulatory filings where required.