The FDA just announced two major steps advancing its real-time clinical trials (RTCT) initiative, and there's a real chance your organization is underestimating what this signals.
This isn't a pilot program tucked into a corner of the Oncology Center of Excellence anymore. FDA is moving RTCT toward standard operating procedure — which means the gap between sponsors who have the data infrastructure for it and those who don't is about to matter significantly more. According to the FDA's press announcement, the agency is taking two concrete steps as part of a deliberate initiative to advance RTCT implementation across drug development programs.
I want to walk through what this means in practice, and — more importantly — what your compliance posture needs to look like as this becomes a broader expectation.
What the FDA Just Announced
The announcement signals continued expansion of RTCT beyond its oncology roots and toward a framework that will affect how trial data is submitted, reviewed, and acted upon across development programs. The FDA wants to move from a model where it reviews data at the end of a trial to one where it can access and evaluate trial data as it's generated. That shift has enormous implications — for review timelines, for how sponsors manage their data integrity obligations, and for how quickly effective therapies can reach patients.
The agency first operationalized this concept through its Real-Time Oncology Review (RTOR) program, launched in 2018. Under RTOR, FDA begins reviewing efficacy data before a sponsor formally submits a biologics license application or new drug application, allowing the agency to be ready to act the moment an application arrives. Since its launch, RTOR has supported dozens of oncology drug approvals and consistently compressed review timelines. What this new announcement suggests is that the agency is now building the regulatory, technical, and operational infrastructure to extend that model more broadly.
Real-time clinical trials require data systems to maintain 21 CFR Part 11 audit trail readiness from the first day of trial conduct — not at the pre-submission review stage. That distinction alone should reframe how most sponsors think about their trial readiness.
What Real-Time Clinical Trials Actually Are
It helps to be precise here, because "real-time" can mean different things depending on context.
In FDA's framework, RTCT refers to a model of clinical trial conduct and data management where trial data is continuously collected, processed, and made available to the FDA — not batch-submitted at trial end. The key enabling technologies are electronic data capture systems, wearables and digital health tools, remote patient monitoring, and the data standards infrastructure to make all of that interoperable and trustworthy.
| Dimension | Traditional Trial | Real-Time Clinical Trial (RTCT) |
|---|---|---|
| Data submission timing | Batch at endpoint | Continuous / rolling |
| FDA access to data | Post-trial submission | Concurrent with trial conduct |
| Site monitoring | Periodic in-person SDV | Risk-based, remote monitoring |
| Patient participation model | Site-centric | Decentralized / hybrid options |
| Protocol adaptations | Limited, pre-specified | Supported through adaptive design |
| Review timeline start | Begins after NDA/BLA filing | Begins during trial conduct |
| Data integrity demands | High | Higher — real-time scrutiny |
The last row is the one sponsors should sit with. When FDA is reviewing your data in real time, there is no clean-up window before submission. Your systems, your processes, and your data governance need to be audit-ready from day one of your trial — not from the day you're assembling your submission package.
Why This Changes the FDA-Sponsor Relationship
The traditional clinical development model is, in my view, fundamentally backwards in one important way: the FDA gets involved seriously at the end of a multi-year, multi-hundred-million-dollar process, and then can ask questions that require sponsors to go back and reconstruct context that would have been easy to capture in real time.
RTCT inverts that. If the FDA is watching the data come in, they can flag concerns early — a signal that a primary endpoint is underperforming, a question about a patient subgroup, a data integrity issue that needs explanation. That's good for patients, because problematic trials get stopped sooner and effective therapies get approved faster. And it's potentially good for sponsors too, because early feedback is vastly cheaper than late feedback.
But it also means FDA's reviewers will be forming impressions of your trial — your data quality, your monitoring practices, your protocol adherence — well before you sit down to write your submission. The clinical trial space has always been one where reputation precedes you. RTCT accelerates that dynamic considerably.
The FDA's Real-Time Oncology Review program demonstrated that concurrent data review can compress review timelines by months — and RTCT extends that logic from post-trial review to trial conduct itself. Understanding that distinction is the starting point for getting your compliance program right.
The Three Compliance Domains RTCT Puts Under Pressure
Sponsors who want to participate in real-time trial frameworks — or who simply want to be ready when RTCT becomes a broader standard — need to think about compliance in three distinct areas.
1. Data Systems and 21 CFR Part 11 Readiness
Real-time data submission means your electronic records and electronic signatures systems are under ongoing scrutiny, not end-of-study audit scrutiny. FDA's 21 CFR Part 11 requirements for audit trails, access controls, and data integrity don't change under RTCT, but the window for discovering and remediating gaps closes dramatically.
Sponsors should conduct a frank assessment of their EDC systems, database validation status, and audit trail completeness before pursuing any RTCT engagement. In my experience working with sponsors preparing for pre-NDA meetings, the most common Part 11 gaps are in audit trail configuration — specifically, systems that capture that a record was changed but not what it was changed from and to. Under traditional review timelines, that kind of gap surfaces late. Under RTCT, it surfaces while FDA is actively watching. The difference between those two scenarios, in terms of the remediation conversation you'll be having, is not small.
If your 21 CFR Part 11 compliance program hasn't been reassessed in the past two years, RTCT is a good reason to schedule that review now.
2. Clinical Quality Agreements and CRO Oversight
If you're using a contract research organization — and most mid-size sponsors are — your clinical quality agreement needs to explicitly address data access, data transfer timelines, and FDA data sharing protocols for an RTCT scenario. Many CQAs currently in use were drafted without any consideration of real-time FDA access to trial data, because that wasn't an expectation when they were written.
This is a contract update that needs to happen before you're enrolled in an RTCT program, not after. The liability and operational questions around who controls the data pipeline to FDA, what happens when a discrepancy is discovered in real time, and how the sponsor's quality oversight role functions under continuous review — all of that needs to be addressed in the agreement. Sponsors whose clinical quality agreements do not address real-time FDA data access are exposed to operational and contractual gaps that cannot be remediated mid-trial.
3. Adaptive Protocol Design and IRB Alignment
RTCT's real power shows up when it's paired with adaptive trial design. If the FDA can see your data in real time, there's a natural opportunity to build protocols that allow pre-specified adaptations based on interim results — dosing adjustments, patient population refinements, early stopping rules. But adaptive designs require more rigorous statistical pre-specification, more sophisticated IRB engagement, and tighter internal governance around unblinding and data access controls.
Sponsors who have never run an adaptive trial should not assume RTCT is purely a technology question. It's a protocol design question, a biostatistics question, and an organizational governance question as well.
Industry Data Points Worth Understanding
The average time from Phase 1 clinical trial initiation to FDA approval for a new drug has historically exceeded ten years, with the clinical phases alone accounting for roughly six to seven years of that timeline. According to the Tufts Center for the Study of Drug Development, the fully capitalized cost of developing a new approved medicine exceeded $2.6 billion in their most recent comprehensive estimate — a figure that is likely higher today given inflation and increasing trial complexity.
The decentralized and hybrid clinical trial model, which RTCT both requires and facilitates, has been growing rapidly since the COVID-19 pandemic accelerated its adoption. The global decentralized clinical trials market was valued at approximately $8 billion recently and is projected to continue expanding, driven by pressure from both FDA and sponsors to run faster and more representative trials.
For sponsors in the $50 million to $500 million annual revenue range — a segment representing a significant share of the active IND pipeline — the infrastructure investment required for RTCT participation is real but manageable, especially when measured against the time-to-market advantage that faster FDA review timelines represent. The sponsors who will struggle are those who wait until they're six months from an IND submission to discover their data systems weren't built for this.
What Regulated Sponsors Should Do Right Now
The announcement doesn't require immediate action from every sponsor with an active IND. But it signals a direction that organizations should be moving toward deliberately, and the earlier you start building the capability, the more options you'll have when your next pivotal trial is in design.
Audit your data infrastructure. Before anything else, understand what your EDC system can and cannot do in terms of real-time data access, audit trail completeness, and standards compliance — specifically CDISC CDASH and SDTM. If you're running trials on legacy or heavily customized systems that weren't built with continuous data access in mind, that's the conversation to have with your IT and clinical operations teams now.
Review your CRO agreements. Pull your current clinical quality agreement and look for language — or the absence of language — around FDA data access, data transfer protocols, and monitoring approaches. Flag what needs to be updated before your next study initiation.
Read FDA's existing RTCT-adjacent guidance. FDA has issued guidance on RTOR, decentralized trials, and real-world evidence that collectively describes the infrastructure this initiative builds on. The decentralized clinical trials guidance issued in 2023 in particular gives a clear picture of what operational readiness looks like. If your quality team hasn't read it, they should.
Talk to your IRB early. If you're contemplating an adaptive design under an RTCT framework, your IRB engagement will need to start earlier and run deeper than a traditional fixed-design protocol review. Most IRBs are still building their own competency in adaptive design review, and the lead time for that conversation matters more than most sponsors expect.
Consider a pre-IND or Type B meeting with FDA. If you're in early-stage development and considering RTCT for a pivotal trial, a pre-IND meeting is the right forum to ask FDA directly about their current thinking, eligibility criteria for specific programs, and what they'll be looking for in terms of data infrastructure. That meeting is free for most sponsors — and the cost of that conversation, measured against the cost of designing a trial that FDA can't engage with in real time because your systems aren't ready, is essentially zero.
I've helped clients prepare for FDA pre-submission meetings specifically around data readiness questions, and the consistent finding is that the organizations that go in with a clear-eyed picture of their gaps come out with actionable feedback. The ones who go in hoping everything will be fine tend to leave with more homework than they expected.
A Note on Who Gets Left Behind
The concern I have about this initiative isn't that it's moving in the wrong direction — it clearly isn't. The concern is that the compliance and technology requirements for RTCT participation are not trivial, and smaller sponsors who lack the internal infrastructure or the external relationships to build it quickly will find themselves at a disadvantage at exactly the moment when FDA review timelines are being compressed for sponsors who are ready.
That gap isn't insurmountable. The tools exist, the guidance is largely in place, and the FDA has generally been willing to engage with sponsors who come in good faith and ask the right questions. But it requires deliberate investment — not a scramble when you're three months from your IND submission.
The sponsors who will benefit most from RTCT are the ones who treat this announcement not as a policy update to file away, but as a signal about where FDA is heading and a prompt to honestly assess whether their operations are ready to move with it.
Jared Clark, JD, MBA, PMP, CMQ-OE, CQA, CPGP, RAC is Principal Consultant at Certify Consulting, where he has guided 200+ clients through FDA compliance programs with a 100% first-time audit pass rate across eight-plus years of practice.
Last updated: 2026-07-15
Jared Clark
Principal Consultant, Certify Consulting
Jared Clark is the founder of Certify Consulting, helping organizations achieve and maintain compliance with international standards and regulatory requirements.