The Marketplace
On May 15, 2026, the American Society of Gene and Cell Therapy and the Orphan Therapeutics Accelerator launched CGTxchange, a first-of-its-kind marketplace designed to help shelved cell and gene therapy programs find new sponsors. The platform went live with a demo at ASGCT 2026, and applications for qualified asset listings opened in May. Endpoints framed the mechanic in Zillow-like terms: a sponsor lists a program, prospective acquirers browse, and assets that would otherwise sit idle find a second path forward.
The timing matters. Biopharma dealmaking is also strengthening in 2026, with both large pharma and mid-sized companies actively looking for pipeline assets ahead of looming patent cliffs. Endpoints' companion piece asked whether megadeals are dead, with the answer being that deal volume is on pace for a strong year while the average deal size is migrating downward. More buyers, smaller checks, more programs changing hands.
For the regulatory writing function, this is the hard part: every program changing hands is also a regulatory file changing hands. And the file is only valuable if the next sponsor can understand not just what was submitted, but why each decision was made.
What an Acquirer Actually Buys
A regulatory file is rarely just a chronology.
From the outside, it looks like a sequence of documents: IND, protocol amendments, briefing books, agency minutes, information requests, responses, CSRs, annual reports, and CMC amendments. From the inside, it is a sequence of decisions. Why was this dose selected? Why was this endpoint retained? Why was this assay accepted as fit for purpose? What alternative manufacturing strategy was rejected? What agency feedback changed the clinical plan?
Those decisions often sit partly in documents and partly in team memory. When a program changes hands, the documents transfer more easily than the context. The acquiring team may inherit the file without the regulatory logic that made the file coherent.
That is the integration risk. The clinical dataset may be anchored in CRFs and databases. The CMC package may be anchored in batch records, methods, deviations, and comparability work. But the regulatory narrative depends on whether the rationale behind prior decisions was captured clearly enough for a new sponsor to reproduce. The asset is not only the molecule, vector, construct, data package, or manufacturing process. It is also the ability to continue the regulatory conversation without forcing the agency to re-litigate settled questions.
This is the integration risk that gets undercosted in deal modeling. The regulatory file is not the whole asset, but it determines how transferable the asset really is.
The Three Inheritance Risks
Programs that move between sponsors often run into three predictable regulatory-continuity risks.
Tacit alignment gets lost. The prior sponsor may have interpreted agency feedback in a specific way, but the nuance was not captured clearly in the minutes or internal decision records. What nuance from a Type B or Type C meeting shaped the team's interpretation of the formal language? What working understanding evolved over multiple interactions? The next sponsor then drafts from the document trail alone and accidentally contradicts the prior regulatory posture.
The narrative voice changes midstream. The acquiring sponsor continues drafting from the existing corpus, but terminology, cross-references, endpoint descriptions, safety language, and CMC rationale begin to drift. The agency reads the next package and sees inconsistency where the sponsor intended continuity. This is the most common failure and the most expensive to repair under deadline pressure.
Historical decisions get re-litigated internally. The acquirer reopens dose, population, endpoint, assay, or manufacturing decisions because the prior rationale is not visible. Some of that review is healthy. But if the next submission reflects a changed position without explaining why, the agency will ask whether the program itself has changed or whether the sponsor has lost control of its own history.
What a Defensible Hand-Off Looks Like
A defensible hand-off has three layers.
A decision log. Every load-bearing regulatory decision should have a short written entry: what was decided, why, who participated, what alternatives were considered, what agency feedback informed the decision, and what would trigger a revisit. The decision log does not replace the regulatory file. It makes the file readable. Programs that change hands without this log force the acquirer to rebuild the context from scratch, often incorrectly.
An agency-interaction map. Every FDA, EMA, or other agency interaction should be indexed by issue, not only by date. Dose selection, endpoint strategy, assay validation, vector design, comparability, safety monitoring, pediatric plans, and long-term follow-up should each trace back to the relevant meeting minutes, briefing document sections, commitments, and follow-up responses. The map is what lets the acquirer distinguish open commitments from settled ones without reading the entire correspondence history twice.
A writer-continuity plan. The acquiring sponsor does not always need the prior writer permanently. But it does need someone to absorb the existing corpus deeply enough to maintain vocabulary, cross-reference integrity, and narrative continuity through the next agency interaction. This is usually a one-time investment of four to six weeks of senior writer time. It is reliably cheaper than repairing the confusion created by a submission that sounds like it changed sponsors halfway through.
This work intersects with the partnership-termination playbook we wrote about earlier this quarter. The underlying mechanism is the same. The regulatory file is portable in form. The interpretive context attached to it is not portable unless someone deliberately makes it so.
The CGTxchange Implication
CGTxchange will likely surface a mixed set of assets. Some may have been shelved for capital reasons despite strong documentation. Others may have promising science but incomplete regulatory-transfer infrastructure because the original team was built for discovery rather than transfer. Acquirers should not assume either way. They should diligence the regulatory file as an operating asset, not as an archive.
Four questions should sit near the top of the regulatory-file review.
Can every major program decision be traced to a source? Dose, endpoint, population, vector, manufacturing process, assay strategy, comparability plan, and safety-monitoring decisions should each connect back to agency feedback, internal rationale, or data. Decisions that cannot be sourced are decisions the new sponsor will eventually have to defend in writing without knowing the original basis.
Are agency commitments visible and current? The acquirer should be able to distinguish open commitments, completed commitments, deferred commitments, and assumptions that the prior sponsor treated as settled. Commitments that fall between these categories are the ones most likely to surface as Information Requests in the next interaction.
Is the next agency interaction draftable from the file alone? If a new team cannot draft a credible pre-IND briefing package, Type B meeting package, IND amendment, or annual report from the inherited corpus, the file is not yet transaction-ready. The cost of making it transaction-ready is part of the price the acquirer is paying.
How recent was the last full briefing-book refresh? Programs whose most recent briefing book is more than eighteen months old will need a refresh before the next agency interaction, and the refresh will surface inconsistencies that the prior sponsor had been managing tacitly.
The Larger Pattern
The mid-cap M&A environment and the launch of CGTxchange are pulling in the same direction. More programs are changing hands more frequently, with shorter average tenure under each sponsor. The regulatory writing function — the part of the organization that carries narrative continuity across decisions, sponsors, and reviewers — is becoming the highest-leverage piece of the transfer.
CGTxchange is a useful signal of where cell and gene therapy may be heading: more shelved programs getting second lives, more assets changing hands, and more sponsors inheriting regulatory histories they did not create. That makes the regulatory writing layer more important, not less. The value of the file is not that it contains documents. The value is that it preserves the reasoning behind those documents well enough for the next sponsor to continue the conversation with regulators.
In a program hand-off, the regulatory file is where asset value either transfers cleanly or leaks away.