A small biotech evaluating an overseas clinical asset may receive a polished study report well before it understands how the underlying records can be accessed. The report lets the team examine the results. Whether FDA could verify the study is a separate diligence question, and it shapes the regulatory argument the buyer plans to make.
In an FDA Voices post in early September, the heads of CDER, CBER, CDRH and the Oncology Center of Excellence said the agency is adding resources for foreign inspections, "including through inspecting more phase 1 and early-stage trials," and is giving priority to a more rigorous review of foreign studies not conducted under an IND or IDE. FDA frames this as the application of existing law. Foreign studies not run under an IND can still be accepted, provided GCP was met and FDA can validate the data. Where it cannot, including where inspection access was denied or restricted, FDA says its regulations allow it to refuse the evidence.
We have written before about in-licensed Chinese assets and the IND-bridging problem and about trial-site provenance after the House China probe. FDA's post brings the same question into the diligence room: what supports the submission's account of how the study was conducted?
A GCP statement needs a record behind it
For a well-designed and well-conducted foreign drug study performed outside an IND, 21 CFR 312.120 sets conditions for acceptance as support for an IND or marketing application, including GCP and FDA's ability to validate the data through an on-site inspection if necessary. Its supporting-information provisions cover ethics review, consent, monitoring, investigator qualifications and training, and it allows cross-references to information elsewhere in the submission instead of duplication. 21 CFR 312.120
Those provisions make a generic compliance paragraph a poor starting point. A better one is the evidence available to whoever is responsible for that paragraph.
In practice, we would ask the writer and the relevant clinical and quality leads to assemble the proposed statements with references to their support. Where a record is held by another organisation, name the custodian and how access will be arranged. Where something has not been verified, keep that status visible in the working draft.
This does not make regulatory writing responsible for inspecting sites or certifying conduct. It lets the writing process surface questions that belong with clinical operations, quality assurance, legal counsel or the original sponsor while there is still time to address them.
What an acquiring biotech should ask for
Consider a hypothetical asset transfer. The buyer has the final CSR, but the original CRO holds the monitoring records and the sites hold the source records. The report says the trial followed GCP, and the buyer wants to rely on the study in its US development plan.
Access for the buyer and access for FDA are separate questions. An agreement to deliver documents to the buyer does not establish that FDA can inspect the site and the relevant records. A data-room index may list the files delivered to the buyer and say much less about the records that stayed where they were.
This will not wait until the marketing application. FDA says it will discuss the provenance and IND status of foreign clinical data with sponsors early, including at pre-IND and Type B meetings. A buyer planning its first FDA meeting on an in-licensed asset should expect the question and have a concrete account of what can be obtained or made available, by whom and under which arrangements.
We would give this issue an owner during diligence and carry the unresolved items into the development plan. An entry such as "confirm records access with original CRO" needs a named person and a date. Otherwise it survives the transaction as an assumption and comes back as a submission problem.
For management, the decision is whether uncertainty about the supporting records changes how the evidence can be used, the work needed before submission or the transaction timetable. Clear drafting helps expose that decision, but more confident language cannot settle it.
Scope the CRO's contribution before the report is rewritten
A CRO asked to adapt an inherited report for a new sponsor should agree the scope of verification at the outset. Editorial revision, reconciliation against supplied documents and an assessment of missing records are different assignments.
The scope should state which materials will be reviewed, which conclusions need sponsor confirmation and how unresolved discrepancies will be reported. If the work reveals a gap, there should be a route to the person who can investigate it, rather than an expectation that the writer will close the comment alone.
That boundary keeps the deliverable useful. The sponsor should be able to tell which statements were checked against records, which reflect an accountable expert's assessment and which still need an answer.
Follow the evidence into the claims
An access or integrity concern can reach beyond the report where it is first noticed. As an internal planning exercise, we would trace where the affected evidence is used, perhaps in a dose rationale, an investigator's brochure or a briefing package, to understand which conclusions need reassessment if the concern stays open.
That is a question for the scientific and regulatory team, with the writer helping to locate the relevant claims. It is not a reason to write the study out of the programme's story; it is a reason to know which conclusions rest on it.
Before commissioning the next submission draft, a sponsor relying on inherited foreign clinical evidence should be able to explain what it has reviewed, what remains accessible elsewhere and what is still uncertain. That account gives the writer a defensible basis for the text and gives leadership a clearer view of the work ahead.