How to document an IND transfer of obligations to a CRO

What must a written transfer of IND obligations to a CRO identify?

Under 21 CFR 312.52, a transfer must be described in writing. A partial transfer identifies each obligation assumed; a transfer of all obligations may use a general statement to that effect. Obligations outside the written scope remain untransferred. Connect that scope to named operational owners so the allocation works in practice.

Before you begin

Written sponsor-to-CRO transfers under 21 CFR 312.52. Contract scope, sponsor identity and regulatory responsibility are related but distinct.

What you will prepare: A reviewable obligation matrix and written transfer with no unassigned duties.

Start with the obligation, not the service description

Section 312.52 permits a sponsor to transfer any or all Part 312 obligations to a CRO. The transfer must be described in writing. If only some obligations transfer, describe each; an obligation absent from the writing is deemed not transferred. If all transfer, the regulation permits a general statement covering all obligations.

“Clinical operations support” does not, by itself, identify which regulatory duties the CRO assumes. Ask the sponsor’s regulatory and legal owners to map the agreement to the applicable obligations. The CRO is subject to the relevant regulations and regulatory action for obligations it assumes. Keep ordinary vendor tasks separate from regulatory transfers.

Build a matrix that survives a real incident

Use columns for obligation/provision, affected IND and studies, sponsor-retained duties, CRO-assumed duties, effective period, operational owner, handoff interface and supporting agreement. Describe boundaries where two parties contribute to one process: who detects a safety issue, who evaluates it and who performs the sponsor’s reporting obligation.

The writing should identify both parties, the scope, effective date and the obligations assumed. Have authorized owners reconcile the final text with the executed agreement and the IND submission. Where the scope changes, update the written allocation and affected operational instructions. Do not silently replace a named obligation with a broad new contract title.

Worked check: the safety duty is missing

Fictional exercise: a CRO agreement transfers monitoring and investigator selection but says nothing about sponsor safety reporting. Under §312.52, an omitted obligation is not transferred. The sponsor therefore cannot use the agreement’s general reference to “trial management” as evidence that the reporting duty moved.

Change the scenario to a proposed transfer of all obligations: authorized reviewers must confirm that the writing actually states that scope and that the CRO can perform it. Remove the executed writing altogether: disposition becomes undetermined, not “transferred because the CRO has started work.”

Test the agreement at the points where work changes hands

Use this worksheet alongside the actual written allocation. Contract titles and service descriptions are inputs to review, not substitutes for the obligations the writing transfers.

Take one real process and walk it across organizations. For example, monitoring identifies a potential safety issue. Locate the written monitoring allocation, then separately establish who evaluates and reports the issue. Ask each owner to identify the record they receive and the action they perform. A complete vendor task list can still conceal a missing responsibility at the interface.

Agreement exercise: a service order adds data processing but leaves the written regulatory allocation unchanged. Do not infer that the CRO now assumes an additional sponsor obligation. Ask the accountable reviewers to reconcile the service change with the transfer’s scope and update the controlling writing if that scope is changing. Retain the old and new effective periods so open work is not assigned to neither party.

This exercise helps review an allocation; it does not supply legal transfer language. Use the sponsor-change guide if the sponsor itself changes, and the contact-change guide for consequential updates to regulatory and technical contacts.

Frequently asked questions

Sources and revisions

Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.

Related guides