Analytical Method Transfer Protocol

Document type	Protocol
Topic area	Tech Transfer & NPI
Level	Advanced
Updated	September 2026

This is a ready-to-use protocol for transferring an analytical method from a sending lab to a receiving lab, covering comparative testing, co-validation, and the documentation basis for a transfer waiver, consistent with USP General Chapter <1224>, Transfer of Analytical Procedures. Replace every <<FILL: ...>> placeholder with your own specifics and route it through your normal document control, review, and approval before execution. A worked filled specimen follows. Verify each cited reference against the current source before you rely on it.

Approval page

Field	Entry
Protocol title	Analytical Method Transfer Protocol for `<<FILL: method name>>`
Protocol number	`<<FILL: e.g. AMT-2026-01>>`
Method identifier and version	`<<FILL>>`
Sending site / lab	`<<FILL>>`
Receiving site / lab	`<<FILL>>`
Linked technology transfer plan	`<<FILL: document number>>`

Role	Name	Signature	Date
Author (Analytical / QC lead)	`<<FILL>>`
Reviewer (Sending site method owner)	`<<FILL>>`
Reviewer (Receiving site lab lead)	`<<FILL>>`
Approver (Quality Assurance, both sites)	`<<FILL>>`

1. Objective

To demonstrate that <<FILL: receiving site / lab>> can execute <<FILL: method name>> with performance equivalent to <<FILL: sending site / lab>>, using the mechanism selected in Section 3, before the receiving lab is relied upon for release or characterization testing of <<FILL: product>>.

2. Scope

Dimension	Decision
Method(s) covered	`<<FILL>>`
Product / matrix tested	`<<FILL>>`
Sample source	`<<FILL: retained lots, split samples, spiked samples>>`
Out of scope	`<<FILL: e.g. a separate identity method covered under its own protocol>>`

3. Transfer mechanism selected

Mechanism	Selected	Basis
Comparative testing	`<<FILL: yes/no>>`	`<<FILL>>`
Co-validation	`<<FILL: yes/no>>`	`<<FILL>>`
Transfer waiver	`<<FILL: yes/no>>`	`<<FILL: state the documented equivalence basis; a waiver with no stated basis is not acceptable>>`

4. Prerequisites

Prerequisite	Status
Receiving lab equipment qualified (IQ/OQ)	`<<FILL>>`
Reference standards and critical reagents qualified at the receiving lab	`<<FILL>>`
Receiving lab analysts trained on the method	`<<FILL>>`
Method validation report available for reference	`<<FILL: reference number>>`
For a biological/potency assay: established method precision (percent RSD) documented	`<<FILL: value and source>>`

5. Roles and responsibilities

Role	Responsibility
Sending site method owner	Confirms the method document, supplies historical precision data, supports troubleshooting
Receiving site analyst(s)	Executes the protocol under the receiving site’s procedures
Analytical / QC lead	Owns the protocol, calculates the statistical comparison, drafts the summary report
Quality Assurance (both sites)	Approves the protocol and the final disposition

6. Acceptance criteria

Field	Entry
Statistic compared	`<<FILL: mean difference, percent recovery, RSD comparison, as appropriate to the method>>`
Acceptance criterion	`<<FILL: state the numeric limit and, for a biological assay, tie it explicitly to the method's own established precision, e.g. within 2x historical intermediate-precision RSD, rather than an arbitrary round number>>`
Number of lots / samples tested	`<<FILL: state count and justify against the method's variability>>`
Replicates per lab, per lot	`<<FILL>>`

A biological or potency assay’s acceptance criterion must be derived from the method’s own historical precision, not borrowed from a chemistry-method transfer template; an acceptance window tighter than the method’s own demonstrated variability will fail on ordinary assay noise regardless of whether the receiving lab is performing correctly.

7. Sample plan and test matrix

Sample / lot ID	Sending lab result(s)	Receiving lab result(s)	Difference	Pass/Fail vs. criterion
`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`	`<<FILL>>`

8. Deviation handling

Any deviation from this protocol during execution is documented in the site’s deviation system, referenced here by number, and assessed for impact on the transfer conclusion before the summary is written. A deviation is not resolved by omitting the affected data point from the comparison without a documented, QA-approved basis.

9. Summary and conclusion

Field	Entry
Overall result vs. acceptance criteria	`<<FILL>>`
Deviations and their disposition	`<<FILL>>`
Conclusion: transfer successful / successful with conditions / not successful	`<<FILL>>`
If conditional, the condition and its closure owner	`<<FILL>>`

10. Attachments

<<FILL: raw data, chromatograms/assay printouts, statistical calculation worksheet>>

11. Revision history

Version	Date	Author	Summary of change
`<<FILL: 1.0>>`	`<<FILL>>`	`<<FILL>>`	Initial issue.

Filled specimen

Extract for an example potency bioassay transfer supporting a CAR-T tech transfer to a CDMO. Company and numbers are illustrative.

Field	Entry
Method	Cell-killing potency bioassay, percent relative potency vs. reference standard
Mechanism selected	Comparative testing; method already validated at sending site, receiving lab has the same instrument platform and trained analysts
Established method precision (sending site)	12% RSD, intermediate precision, from 24 historical assay runs
Acceptance criterion	Mean absolute difference across tested lots within 2x established RSD (24%)
Lots tested	6 split lots, in duplicate at each lab

Sample plan extract:

Sample / lot ID	Sending lab result	Receiving lab result	Difference	Pass/Fail
Lot A	98%	91%	7%	Pass
Lot B	104%	96%	8%	Pass
Lot C	89%	97%	8%	Pass
Lot D	112%	101%	11%	Pass
Lot E	95%	104%	9%	Pass
Lot F	101%	111%	10%	Pass

Mean absolute difference across the six lots: 9%, within the 24% criterion. Conclusion: transfer successful. No deviations recorded.

Common inspection findings this protocol prevents

A method transfer “passed” with no predefined acceptance criterion on file, decided after the data was already in hand.
A potency assay acceptance criterion borrowed from a chemistry-method transfer, tighter than the assay’s own demonstrated precision, generating false failures.
A transfer waiver granted with no documented equivalence basis, just an assertion that the receiving lab is “qualified.”
Sample and lot selection not justified against the method’s known variability, so the comparison is underpowered to detect a real difference.

How to adapt this protocol

Pull the sending site’s historical method precision before setting the acceptance criterion in Section 6; do not set the criterion first and look for supporting data afterward.
Choose the mechanism in Section 3 honestly against the method’s actual state, not by habit; co-validation, not comparative testing, is often the right call for a method still being finalized when the CDMO is brought on.
Size the sample plan in Section 7 to the method’s variability, more lots for a highly variable biological assay, fewer for a tight, well-characterized chemistry method.
Route the completed protocol and summary through both sites’ quality systems before the receiving lab is relied upon for release testing.