Analytical method transfer is the documented process by which a validated analytical procedure is moved from one laboratory to another while demonstrating that the receiving laboratory can run the method and get results equivalent to the sending laboratory. It happens during technology transfer from development to commercial QC, when outsourcing testing to a contract laboratory, when opening a new site, or when a primary testing laboratory is closed.

The regulatory expectation is clear: USP Chapter <1224> and ICH Q10 address method transfer. EU GMP Chapter 1.7 addresses technology transfer. FDA’s 2015 analytical procedures and method validation guidance, while not solely focused on transfer, implies equivalence requirements for methods used across multiple sites.

When Method Transfer Is Required

Transfer is required when:

  • An analytical method validated at one laboratory will be used for testing at another laboratory (development to commercial, sponsor lab to contract lab)
  • A method is being relocated to a new facility
  • A significant change in analytical equipment at the receiving lab requires demonstrating equivalence (moving from one HPLC platform to another)

Transfer is not required when:

  • The same method is being used within the same validated environment (same lab, same validated equipment, same qualified analysts)
  • A compendial method is being introduced (verification is required, not full transfer)
  • An identical validated copy of a method is used with identical equipment at the same site

Roles: Sending Unit and Receiving Unit

Sending unit (SU): The laboratory that has the validated method and is transferring it. Responsible for: providing complete method documentation, providing reference standards and training materials, participating in the transfer execution (running parallel samples or providing oversight), and reviewing the transfer results.

Receiving unit (RU): The laboratory receiving the method. Responsible for: demonstrating it can run the method and obtain equivalent results, establishing its own system suitability qualification, training its analysts, and maintaining the method after transfer.

Both units must have QA oversight of the transfer. The method transfer report must be approved by QA at both the sending and receiving sites.

Transfer Protocol

The transfer protocol is a controlled document, approved by QA before the transfer begins, that defines:

Scope and objective: Which method(s) are being transferred, from which laboratory to which laboratory, and why.

Reference documents: Method document number and version, validation report, any relevant SOPs for sample preparation and analysis.

Transfer approach: Which of the three standard approaches will be used (see below).

Sample and material plan: What samples will be used for the transfer, how they will be prepared, how they will be shipped (if the SU and RU are in different locations), and how storage conditions during transfer will be controlled and documented.

Analytical plan: Which parameters will be assessed during the transfer, the number of replicates, the order of testing.

Acceptance criteria: The statistical criteria that must be met for the transfer to be declared successful. These must be predefined, setting acceptance criteria after seeing the data is not acceptable.

Deviation handling: What happens if acceptance criteria are not met.

Transfer Approaches

Approach 1: Comparative Testing

The most common approach. Both the SU and the RU analyze the same set of samples under the same conditions. Results are compared statistically. If the results from both laboratories are equivalent within the predefined acceptance criteria, the transfer is successful.

This approach requires the SU to run the method concurrently with the RU. It provides the most direct evidence of equivalence because the same samples are analyzed by both labs under controlled conditions.

Sample design: Typically three or more samples (independent preparations) per laboratory, at the concentrations of interest (100% nominal for assay; near the specification limit for impurity methods; at the LOQ for trace impurities). If the method is for stability testing, samples at multiple stability levels may be used.

Approach 2: Revalidation

The RU revalidates the method in its own laboratory. If the RU’s revalidation results meet the original validation acceptance criteria (from the SU’s validation), the transfer is considered successful.

This approach is used when the SU cannot run samples concurrently (e.g., the SU laboratory is closing). It provides less direct comparison to the SU but shows that the method performs adequately at the RU. The revalidation scope is typically the same as the original validation, or a subset if some characteristics don’t need to be re-established.

Approach 3: Co-validation

Both laboratories participate in the original validation simultaneously. Used when a method is being developed for multi-site use and both sites will be validating simultaneously. Less commonly used in post-development transfers.

Acceptance Criteria: Statistical Approaches

For assay methods (quantitative comparison between SU and RU):

The most commonly used statistical framework for comparative transfer acceptance is a two one-sided tests (TOST) equivalence test, with an acceptance range of ±X% from the SU results.

TOST approach:

  • Define the equivalence limit: the maximum acceptable difference between SU and RU results (e.g., ±2.0% for assay, ±10% for impurities)
  • Set the significance level (typically α = 0.05)
  • Run the equivalence test: both one-sided 90% confidence intervals must fall within the equivalence limit for the transfer to pass
  • This is more statistically rigorous than simply comparing means; it tests that the two laboratories are close enough to be interchangeable

Simpler acceptance criteria (for lower-risk methods):

  • Mean difference between SU and RU results is within ±X%
  • RU method precision (%RSD) is within specification from the validation
  • Not appropriate for methods where statistical equivalence is critical

For impurity/purity methods:

  • RU results for known impurities must be within ±Y% of SU results (where Y is defined based on the impurity level and the specification)
  • RU LOQ must be at or below the established LOQ
  • RU method precision at the specification level must be within validated precision limits

For system suitability:

At the completion of the transfer, the RU must show that its system suitability criteria (retention time, peak symmetry, column efficiency, standard response precision) are met with its equipment under the method conditions. System suitability criteria defined in the validated method must be achievable at the RU.

Transfer of Reference Standards and Reagents

Reference standards don’t travel automatically with a method. The RU must:

  • Obtain certified reference standards from the same source as the SU, or demonstrate equivalence of its reference standards against those used during validation
  • Prepare reagents per the method specification and verify their quality
  • Qualify its reference standard storage and handling procedures

For biologically derived reference standards (antibody standards, cell-based assay references, activity standards), the characterization requirements are more extensive and the transfer of the reference standard itself may require comparability testing.

Transfer Execution and Documentation

Pre-transfer qualification: Before the transfer, verify that the RU has:

  • The qualified instruments (calibrated, within specification, any required qualification records complete)
  • Qualified analysts (trained on the method, competency demonstrated)
  • Appropriate reagents and reference standards
  • The current controlled document

Execution documentation: Record each step as it is performed. Who ran what, on which instrument, on which date, using which reference standard lot. This is the raw data of the transfer exercise. Chain of custody for samples must be documented.

Data package: Compile all raw data from both labs, the statistical analysis, the system suitability data from each run, and any deviations from the protocol.

Handling Transfer Failures

If acceptance criteria are not met, the transfer is not declared successful. Options:

Investigate before re-testing. Identify whether the failure is attributable to a specific cause: a reagent difference between sites, a column chemistry difference, a sample preparation difference, an instrument configuration difference. The same structured investigation approach as an OOS applies here: look for a specific assignable cause before deciding on the path forward.

Address the root cause and repeat the exercise. If a specific difference is identified and corrected (e.g., the RU was using a different grade of mobile phase solvent), repeat the affected portion of the transfer after the correction.

Conduct additional optimization at the RU. For some methods, slight modifications may be needed at the RU (column length, gradient adjustment) to achieve equivalent performance with different instrumentation. These modifications require evaluation against the method’s validation scope and may require partial revalidation or a documented method suitability assessment.

Escalate to SU method review. Occasionally, a transfer failure reveals a weakness in the original method, the method is not robust across different equipment or column lots. This requires the SU to review the method and potentially improve it before transfer proceeds.

What’s not acceptable: adjusting acceptance criteria after seeing the data to make the transfer “pass.” If the predefined criteria weren’t met, the transfer didn’t pass. Setting acceptance criteria wide enough to guarantee success regardless of data quality is equally unacceptable.

Regulatory Filing Requirements

For NDA/BLA submissions: Analytical method transfer is typically documented in Module 3 as part of the manufacturing process transfer summary. The transfer report (summarizing the approach, samples, results, and conclusion) may be included or referenced. FDA reviewers may request the full transfer data package.

For post-approval changes: If the method is transferred after approval (e.g., to a new contract lab), the transfer is a post-approval change. Depending on the product and the significance of the change, it may require a Prior Approval Supplement, CBE-30, or Annual Report. The transfer report is submitted as part of the supplement.

For global submissions (CTD): The same transfer data package is submitted in Module 3 for all ICH markets. EMA reviewers and PMDA reviewers may have specific requirements for the statistical analysis or the number of batches tested.

Common Method Transfer Mistakes

Acceptance criteria defined after data review. This invalidates the statistical basis of the transfer. Criteria must be predefined in the protocol.

Inadequate sample design. Using only one sample at one concentration doesn’t provide adequate information about the method’s performance at the RU. Include samples across the relevant concentration range.

Different sample lots at SU and RU. If the SU and RU test different batches of material, you’re not doing a comparative transfer, you’re doing two separate method suitability checks. The power of comparative testing depends on using the same samples.

No documentation of sample chain of custody during shipping. Samples shipped between sites without controlled shipping conditions documentation. A temperature excursion during shipping can explain a transfer failure that has nothing to do with the method.

Transfer declared complete before all documentation is approved. The receiving lab begins using the method for release testing before the transfer report is signed by QA at both sites. Any data generated before the transfer is formally complete is potentially not defensible.