This is a ready-to-use protocol for transferring a validated analytical procedure from a sending unit (SU) to a receiving unit (RU). Acceptance criteria must be set here, before any testing, and never revised after the data is reviewed. Replace every <<FILL: ...>> placeholder, route it through dual-site QA approval, and confirm every cited regulation against the current source before you rely on it. This content is educational reference, not legal or regulatory advice.
Approval page
| Field | Entry |
|---|---|
| Protocol title | Analytical Method Transfer, <<FILL: method name>> |
| Protocol number | <<FILL: PROTOCOL-ID>> |
| Version | <<FILL>> |
| Sending unit (SU) | <<FILL: site / lab>> |
| Receiving unit (RU) | <<FILL: site / lab>> |
| Product / specification | <<FILL>> |
1. Objective
To demonstrate, through a predefined and dual-site-approved comparison, that <<FILL: RU name>> can execute <<FILL: method name and number>> and obtain results equivalent to <<FILL: SU name>>, so that the RU can be authorized to use the method for its intended GxP purpose.
2. Scope
This protocol applies to <<FILL: method name, number, version>> for <<FILL: product / specification>>, transferring from <<FILL: SU>> to <<FILL: RU>>. It does not cover other methods or other receiving sites; each requires its own protocol or a documented extension.
3. System description / method summary
Briefly describe the method (technique, what it measures, key instrumentation) and reference the controlling method document and validation report.
| Field | Entry |
|---|---|
| Method document number and version | <<FILL>> |
| Validation report reference | <<FILL>> |
| Method type | <<FILL: assay / related substances / dissolution / bioassay / microbiological / other>> |
4. Prerequisites
- Current, controlled method document issued to the RU (not a draft or marked-up copy).
- RU instruments qualified and within calibration.
- RU analysts trained on the method with documented competency.
- Reference standards and reagents of the correct grade, lot, and in-date status available at the RU.
- Sample material identified, with a plan for splitting and shipping if sites are in different locations.
See the paired readiness checklist for the pre-transfer gate.
5. Roles
| Role | Responsibility |
|---|---|
| Protocol author | <<FILL: name/role>>, defines approach, sample plan, and acceptance criteria |
| SU technical lead | Supplies method documentation, standards, and technical oversight |
| RU technical lead | Executes RU testing, confirms readiness, owns the method after transfer |
| SU Quality Assurance | Approves protocol and report at the sending site |
| RU Quality Assurance | Approves protocol and report at the receiving site; gates start of routine release testing |
| Statistician / numerate reviewer | Sets or reviews the equivalence limit and statistical test |
6. Transfer approach
| Field | Entry |
|---|---|
| Approach selected | <<FILL: Comparative testing / Co-validation / Revalidation at RU / Transfer waiver>> |
| Justification | <<FILL: why this approach fits the situation>> |
7. Sample and analytical plan
| Field | Entry |
|---|---|
| Sample material / lot(s) | <<FILL>> |
| Number of independent preparations per lab | <<FILL>> |
| Concentrations / levels tested | <<FILL: e.g. 100% nominal; near specification; near LOQ>> |
| Number of analysts at RU | <<FILL: minimum 2 recommended>> |
| Number of instruments at RU | <<FILL>> |
| Shipping / chain of custody plan (if applicable) | <<FILL>> |
8. Predefined acceptance criteria
State every criterion as a number, decided before testing. Do not leave any cell as a qualitative aspiration.
| Parameter | Test | Acceptance criterion (predefined) |
|---|---|---|
<<FILL: e.g. Assay accuracy/equivalence>> | <<FILL: e.g. n preps per lab, same lot>> | <<FILL: e.g. 90% CI of (RU mean minus SU mean) entirely within +/- X% (TOST)>> |
<<FILL: e.g. RU precision>> | <<FILL>> | <<FILL: e.g. %RSD <= validated repeatability limit>> |
<<FILL: e.g. related substances>> | <<FILL>> | <<FILL>> |
<<FILL: e.g. system suitability>> | <<FILL: every run, both labs>> | <<FILL>> |
9. Deviation and failure handling
- Any criterion not met is a transfer failure, investigated per section 10, not retested informally.
- Any deviation from the protocol (a substitution, a timing change, a missed step) is documented at the time it occurs, assessed for impact, and approved by both QA units before the affected data is used in the conclusion.
- Acceptance criteria are never revised after data review. A failed criterion is addressed by investigation and, where justified, a repeat of the affected portion under the same or an amended, re-approved protocol.
10. Acceptance criteria for the transfer overall
- Every predefined criterion in section 8 is met, or the deviation is investigated to a documented assignable cause and the affected portion repeated and passed.
- All system suitability requirements are met on the RU’s own equipment.
- Raw data, calculations, and instrument outputs are complete and reconstructable by a reviewer who was not present.
- The protocol was approved by both QA units before testing began.
11. References
USP General Chapter <1224>, Transfer of Analytical Procedures. USP General Chapter <1226>, Verification of Compendial Procedures (if a compendial method is involved). ICH Q2(R2), Validation of Analytical Procedures. FDA, Analytical Procedures and Methods Validation for Drugs and Biologics (2015). EU GMP Part I, Chapter 6 (Quality Control).
Confirm the current version and clause numbers of each reference before issue.
12. Approvals (before testing)
| Role | Name | Signature | Date |
|---|---|---|---|
| Protocol author | <<FILL>> | ||
| SU Quality Assurance | <<FILL>> | ||
| RU Quality Assurance | <<FILL>> |
Filled specimen
Excerpt of a completed protocol for an example small-molecule assay transfer. Illustrative only.
| Field | Entry |
|---|---|
| Method | HPLC assay and related substances, tablet, method TM-0042 v2.0 |
| SU / RU | Development QC Lab / Commercial QC Lab, Site B |
| Transfer approach | Comparative testing (Approach 1); both labs operational concurrently, same lot available |
| Parameter | Test | Acceptance criterion (predefined) |
|---|---|---|
| Assay accuracy/equivalence | 6 independent preps per lab, same lot | 90% CI of (RU mean - SU mean) entirely within +/-3.0% of label claim (TOST) |
| Assay precision (RU) | 6 preps, RU only | %RSD <= 2.0% |
| Related substances | Spiked sample at specification level | RU within +/-25% relative of SU (or +/-0.05% absolute, whichever larger) |
| System suitability | Every run, both labs | Resolution >= 2.0; tailing <= 2.0; standard %RSD <= 1.0% (n=5) |
Result: RU mean 100.8%, SU mean 99.6%, 90% CI of the difference 0.26% to 2.14%, entirely inside +/-3.0%. Assay criterion met. All other criteria met on first execution. Conclusion: transferred, no conditions.
Common inspection findings this protocol prevents
- Acceptance criteria written as qualitative statements (“results should be comparable”) rather than predefined numbers.
- A protocol approved after testing began, or approved by only one site’s QA.
- The transfer approach selected with no documented justification for why it fits the situation.
- No named minimum number of analysts or instruments at the RU, so the study proves the method works once, not that it works in the RU’s real operation.
How to adapt this protocol
- Set the method, sites, and product in the header.
- Select and justify the transfer approach in section 6 based on your actual situation (concurrent testing possible or not, multi-site design, waiver basis).
- Fill section 8 with real numeric criteria derived from the method’s validated repeatability and a stated equivalence limit; do not leave any criterion qualitative.
- Point section 9’s investigation process to your real deviation and OOS procedures.
- Confirm every regulation in section 11 against the current published version before issue.