Under 21 CFR 312.52, a sponsor may transfer responsibility for any or all of its regulatory obligations to a contract research organization, but the transfer must be described in writing, and any obligation not covered is deemed not to have been transferred. A CRO that assumes sponsor obligations is subject to the same regulatory action as a sponsor for failing to meet them. What never moves is the sponsor's ultimate accountability for the trial.
What is a transfer of regulatory obligations?
It is a document, often an appendix to the contract or work order, listing which sponsor obligations the CRO assumes. Typical examples include monitoring, maintaining records, managing investigator selection and onboarding, and submitting safety reports. The IND application form asks whether obligations have been transferred and to whom, so the document has regulatory as well as contractual weight.
What never moves to the CRO?
Accountability. ICH E6(R3) is clear that the sponsor remains responsible for the trial and for overseeing every party it delegates to. In practice, the sponsor also retains decisions such as approving the protocol and its amendments, deciding whether to continue or stop the study, and judging how to respond to emerging safety information. A CRO can execute and advise. The sponsor decides and oversees.
What are the most common mistakes?
Vague language. "The CRO will perform all sponsor obligations" sounds comprehensive and is nearly useless.
Mismatch with the scope of work. The transfer lists obligations the work order doesn't fund, or the work order includes tasks the transfer doesn't mention.
No updates. Scope changes by amendment, but the transfer document stays frozen.
Gaps between vendors. When several vendors share the work, some obligations fall between them and others are claimed twice.
Poor filing. The document is signed but not filed where an inspector would expect to find it.
How do you write a good transfer of obligations?
Map each sponsor obligation to its regulatory basis. For each, record whether it is transferred fully, partially or retained, which vendor holds it, and how the sponsor will oversee it. Align the document line by line with the scope of work. Update it whenever scope changes. File it in the trial master file and make sure the IND reflects it.
Why does oversight matter even after a transfer?
Because a transfer moves the work, not the risk. If a CRO misses a safety reporting timeline, the consequences land on the sponsor's program and the participants in it. A transfer document is most useful when paired with an oversight plan that shows how the sponsor will know each transferred obligation is being met.
How should small sponsors approach this?
With extra care. Lean teams often transfer more obligations, which makes the clarity of the document and the strength of oversight more important, not less. A one-page summary of who holds each obligation, kept current, is one of the most practical tools a small sponsor can create.
Keep reading: Write the Exit Plan Before You Sign the CRO Contract
