Adding a Rescue Site: What the Sponsor Handoff Needs to Include

Give the new team the current problem

A rescue site may receive the protocol and an urgent recruitment target while the reasons for that target remain scattered across earlier conversations. The new team then has to rediscover what the study has already learned. A focused handoff shares the current problem, the relevant evidence, and the assumptions that still need testing.

Begin with a short description of the study’s position. Explain which enrollment milestone needs support, the time available, the population that has been hardest to reach, and any operational issues that affected other sites. Share useful context without turning one location’s experience into an assumption about every other practice.

Separate current requirements from past versions

The proposed investigator and operational team need a reliable starting set of study information. Identify the current protocol, key supporting documents, relevant amendments, and any sponsor decisions that affect feasibility. If the study has changed, summarize the operational consequences so the new team knows what requires particular attention.

A version label alone may not explain the work. A changed visit can affect appointments, samples, staffing, budgets, and participant communication at the same time. Ask the receiving team to describe the requirements back in its own workflow. This is a practical way to discover uncertainty before a startup commitment is made.

WCR's discussion of turning study documents into a usable visit workflow offers further context for this document-to-operations handoff.

Share the enrollment lessons that matter

Useful lessons explain where the pathway became difficult. Examples might include records that took longer to obtain than expected, a narrow treatment-history requirement, appointments that were hard to schedule, or a mismatch between outreach and the eligible population. The receiving site should understand the observation and the limits of the evidence.

Provide stage-level information where available and agree on common definitions. A count called “screened” may mean something different to central recruitment, a sponsor dashboard, and a local coordinator. A clear handoff reduces the chance that the new site’s forecast repeats an earlier misunderstanding.

• Explain the specific recruitment or execution constraint the site is being asked to address.
• Identify current documents and decisions that affect startup or screening.
• Share known procedural, vendor, supply, and system dependencies.
• Clarify the expected reporting stages, owners, and review points.

Agree on who resolves the open items

A handoff should end with a short list of questions and named routes for resolving them. Clinical interpretation belongs with the appropriate clinical reviewers. Contract, system, supply, and procedure questions need their own owners. Asking the site to “move quickly” is less useful than making the next dependency easy to resolve.

The sponsor, CRO, central operations team, and local practice should know which decisions are pending and when the next update is expected. WGR’s site-management approach connects these workstreams so local teams receive usable direction rather than several unrelated requests.

Test the handoff against the first screening

Before declaring the handoff complete, walk through a representative first screening visit. Ask what the team needs to know, which resources it needs to use, what the investigator must review, and how an unresolved question would be escalated. The exercise can expose omissions that were not obvious in a document list.

An informed rescue decision depends on both the study information and the receiving team’s ability to act on it. Explore WGR’s trial rescue review and feasibility and startup process for that combined assessment. The strongest handoff gives the site enough context to explain its proposed contribution and the conditions behind it.

End with a receiving-team summary

Ask the receiving team to summarize the opportunity in its own terms: the patient group being assessed, the contribution requested, the first visit being prepared, and the items that could prevent progress. This is more useful than asking whether everyone has received the documents. It shows whether the information has become a shared understanding of the work.

Use differences in that summary to identify clarification needs. The sponsor may consider a procedure routine while the local team needs to confirm access; the site may interpret a recruitment stage differently from the central dashboard. Resolve those differences in the handoff record so the next person joining the study can understand the decisions without reconstructing the conversation.