A diagnostics startup with a CLIA LDT already often arrives at a familiar decision point. The assay is stable, early performance data look concordant, and someone in the pipeline starts asking about a clinical study. The real question is not whether the company will eventually need one, but whether starting now serves the timeline or drains resources better spent elsewhere, producing data the team is not yet positioned to use.
Most guidance treats this transition as a regulatory formality. In practice, it is also a sequencing decision with meaningful implications for capital allocation, operations, reimbursement strategy, and future study design. A live LDT can run as a commercial phase: generating revenue and supporting clinical use while validation expansion work proceeds alongside it. The key challenge is determining when a study is likely to create actionable value and how to design early studies so a single dataset can support multiple downstream objectives. The call usually lands on the clinical operations lead, so the framing here is operational rather than abstract.
Why Sequencing Matters More Than Timing
The move from LDT to clinical study is a resource-allocation decision before it is a compliance milestone, and sequencing errors compound in both directions. Starting too early risks generating costly clinical data before the assay design, performance characteristics, or operating procedures have stabilized. Waiting too long can allow launch-driven design decisions to limit the regulatory and commercialization options the company may later want to pursue.
The regulatory backdrop now gives startups more room to launch under CLIA. The FDA 2024 final rule that would have regulated LDTs as medical devices was vacated by a federal court in March 2025 and formally rescinded by the FDA in September 2025, returning oversight largely to the traditional CLIA/CMS framework and FDA’s historical enforcement-discretion approach [1]. This does not remove the case for FDA-grade evidence when a company intends to pursue a 510(k) or De Novo clearance for broader market access. It does, however, allow many companies to sequence commercial launch and evidence generation separately, provided the clinical study is ultimately designed to support the destination the company has in mind.
The Cost of Getting the Order Wrong
Two failure modes show up repeatedly.
The first is starting a concordance study before the assay is stable across reagent lots and pre-analytical conditions. In one HBsAg EIA pre-validation study, shipping simulation at elevated temperature produced an increase in false-positive signal. Because the issue was identified during pre-validation, it could be addressed through updated acceptance criteria and specimen-handling controls. Had it surfaced mid-study, it would have confounded the results and forced a restart.
The second is a design choice that narrows the submission pathway without anyone noticing. A convenience sample or a weak reference comparator can satisfy a CLIA launch and still be the exact thing a future 510(k) reviewer rejects, which turns into a repeat study on a longer timeline than the original.
Assay Maturity Thresholds: What “Ready” Actually Means
There are two readiness states, and teams often conflate them.
An LDT is ready for clinical use under CLIA once analytical validation demonstrates reliable performance for its intended use. This typically includes characteristics such as accuracy, precision, analytical sensitivity (including limit of detection where applicable), analytical specificity, reportable range or linearity for quantitative assays, and other required performance specifications. Standard operating procedures, quality controls, and acceptance criteria should also be established. This aligns with the requirements of 42 CFR 493.1253, [2] which requires laboratories to establish performance specifications for tests developed or modified in-house, often using validation frameworks such as the CLSI EP series [3].
An assay is ready to support a clinical study when additional evidence shows performance holds across the real-world variation that could threaten study validity. This includes lot-to-lot reagent stability, pre-analytical conditions of specimen collection, shipping, storage, and freeze-thaw, each with defined acceptance criteria. The key distinction is not whether the assay can produce clinically reportable results. It is whether the major sources of analytical variability have been characterized and sufficiently controlled, so they are unlikely to confound the interpretation of clinical performance data.
Performance Criteria That Signal Go-Readiness
A clinical-operations lead can apply a simple go/no-go check against the validation dossier. Precision should be characterized using an appropriate study design, as per CLSI EP05. Analytical sensitivity should be established using methods such as CLSI EP17. Method comparison data should be documented against a predefined comparator using an approach such as CLSI EP09. Evidence of lot-to-lot reproducibility and the stability of specimens under anticipated collection, shipping, storage, and handling conditions should also be available.
Taken together, these data provide confidence that analytical variability is unlikely to obscure the interpretation of clinical performance. When those are in hand, the assay can carry a clinical study. When any of those are missing, the next step is additional pre-validation work, not a clinical study start.
When the Validation Dossier Is Structurally Insufficient
The gaps that cause the most trouble at the clinical study stage are predictable: sample-type coverage that does not adequately represent the intended-use population, insufficient evaluation across the assay’s measuring range, a comparator method that supports launch but not a future submission, or documentation that records results without fully establishing the performance characteristics required for an in-house test [2].
A dossier built to meet the minimum requirements for a CLIA launch is often structurally insufficient for a clinical study intended to support broader regulatory, reimbursement, or commercialization goals. The issue is not necessarily data quality; it is that the data were generated to answer a different question.
A related trap is worth naming: an assay that works in principle from promising early data is a different thing from one that is analytically validated and stable. On the Oropouche program, a partially developed assay concept with encouraging preliminary data still required full analytical validation in-house to surface robustness and specificity issues the early data did not reveal.
Study Design Decisions That Preserve Regulatory Optionality
Two study-design elements are difficult and expensive to change once testing is underway: the comparator strategy and the sample population. Both should be defined early in the planning process.
For a concordance study that may ultimately support a regulatory submission, the comparator method should be selected upfront, along with a predefined approach for handling discordant results and, where appropriate, the use of a secondary method for adjudication. Comparator selection often looks flexible early and is the most expensive thing to revisit later.
The sample population is the other anchor. The number of positive and negative specimens, representation of the intended-use population, and distribution across analyte concentrations drive specimen collection, study timeline, and overall feasibility. These parameters are most effective when established before specimen collection begins, ensuring the study generates data that remain valuable beyond the immediate launch.
Concordance Study vs. Clinical Utility Study: Choosing the Right Evidence Architecture
The two study types answer different questions.
A clinical concordance study asks whether the assay agrees with an established reference method. A clinical utility study asks whether using the test changes clinical decisions or patient outcomes.
At the LDT stage, concordance data are often the near-term priority because they help establish comparative performance and support clinical performance claims. Clinical utility evidence typically becomes more important when demonstrating the value of the test to healthcare systems, clinicians, and payers. The key is aligning the evidence strategy with the intended downstream objective before the first sample is collected. A study designed only for immediate launch may not generate the evidence needed for future regulatory, reimbursement, or commercialization goals.
How to Structure Data Collection So It Serves Multiple Future Uses
A single study can serve CLIA documentation, investor diligence, and a possible FDA submission at the same time, and the lever for that is sample-population design. The cohort should be sized and characterized to the most demanding foreseeable use rather than the minimum CLIA launch requirement. It is common to design around the CLIA minimum and discover later that a 510(k) needs a substantially larger and more representative set, which forces repeat collection. Defining sample size, population characteristics, and study objectives before collection begins allows early specimens to support both near-term commercialization and potential future regulatory work. The goal is not to overbuild the study, but to collect the right data once in a way that preserves future options.
Running a Clinical Study Alongside Active Clinical Operations
The factor startups most consistently underestimate is operational, not regulatory. Study demands and clinical throughput compete for the same instruments, staff, and reagents. CLSI-aligned validation can require a substantial number of replicates, and those replicates draw directly on the capacity already committed to patient testing.
Replicate Testing, Throughput, and TAT: Where Validation Logic Conflicts with Operations
The workable approach is to integrate validation into routine operations rather than run it as a separate track. Validation runs get scheduled around clinical workload, using lower-volume periods and available instrument capacity, with staffing and sample preparation coordinated against the clinical calendar. The trade-off is speed: validation may extend over a longer period to protect patient turnaround times. The constraint is managed by spreading the work across the calendar, while replication levels, acceptance criteria, and documentation standards stay fixed. The scope of validation does not shrink.
SOP Depth Requirements at the Clinical Study Stage
SOPs that support CLIA clinical operations are designed to ensure analytical reliability, quality control, and consistent execution of routine testing. A defensible clinical study typically requires additional layers of documentation: predefined handling of pre-analytical variables, specimen acceptance and rejection criteria supported by stability and performance data, and procedures detailed enough that reviewers or auditors can trace how study specimens were collected, processed, tested, and reported.
The transition from routine clinical operations to study execution does not require replacing the existing quality system; it requires extending it. When laboratories begin a clinical study without adapting SOP depth to support study-specific traceability, predefined controls, and documentation expectations, gaps often appear during review.
Timeline Compression Without Compromising Evidence Quality
Compression is possible when the scope of work changes without lowering the evidence standard. Nexus shortened a validation-related timeline from approximately 20 weeks to 4 weeks in the context of a bridge study, not a full from-scratch validation.
The technical basis for that compression was that core analytical performance characteristics (i.e., accuracy, precision, limit of detection, and specificity) had already been established under a previously validated configuration. The purpose of a bridge study is not to repeat the complete validation package, but to demonstrate that the modified configuration maintained comparable performance. The timeline reduction came from appropriately narrowing the study objective, not from reducing validation rigor.
What Pre-Validation Work Actually Buys
Front-loaded pre-validation removes downstream risk and shortens the overall timeline. The concrete activities are workflow stress-testing, shipping simulation under temperature extremes, and development of QC materials, all done before the formal study begins.
The HSV-1/2 program illustrates why contingency planning belongs in this phase. When HSV-2 (FAM) oligos became unavailable, the team preserved the timeline by transitioning to an HSV-2 (Cy5) and RPP30 (FAM) configuration. Because the oligo sequences and underlying amplification chemistry were unchanged, the team anticipated comparable performance and verified the alternate configuration before use. Once the original reagents became available, the standard fluorophore configuration was restored.
A predefined alternative workflow does not eliminate supply-chain risk, but it prevents a single reagent delay from becoming a study timeline failure.
A Decision Framework for Sequencing a Clinical Study
Four variables govern the sequencing decision: assay maturity, regulatory destination, study-design flexibility, and operational capacity. Each deserves an honest assessment against the current dossier and the live lab load before the company commits.
The Signals to Move Now
The signal to move is a combination of factors, not a single milestone. Analytical validation is complete and holding across reagent lots and pre-analytical conditions. A reference comparator is defined, and the company has access to a sample population that represents the intended use across the reportable range. The regulatory destination is clear enough to guide the study design. The lab has the operational capacity to complete required testing without compromising patient turnaround.
When these conditions align, delay can create its own cost by slowing evidence generation, partnerships, and future commercialization opportunities. The decision to start should be driven by assay readiness and strategic alignment, not simply by the passage of time.
The Signals to Wait, and How to Use the Time
Deferral is the right call when robustness data are thin, when the comparator or sample population is still unsettled, or when the regulatory destination is undecided. Waiting only creates value when the time is used to remove those uncertainties. That means completing the additional validation stability work, building and banking the specimens the study will need (e.g., positives, low-prevalence analytes, and full reportable-range coverage), locking the comparator strategy, and strengthening the SOPs to study grade. That foundational work allows the eventual study to run more efficiently and produces data that is more defensible under regulatory, clinical, and commercial review.
How Nexus Structures Clinical Study Support for LDT Partners
Nexus runs R&D and clinical operations in the same facility, so validation work can be scheduled into live operations instead of bolted on afterward. Nexus designs and validates assays in-house and treats sample sourcing as a critical-path item from the first planning conversation, the point where the prevalence, specimen type, and reportable-range coverage of a study get pressure-tested before any samples are collected. Pre-validation surfaces the real-world risks, shipping, storage, and lot variation among them, before they reach a formal study.
Nexus is a CLIA-certified, CAP-accredited, HIPAA-compliant laboratory in Watertown, Massachusetts, processing self-collected specimens with results delivered through API or SFTP, and works without volume minimums. For a diagnostics startup sequencing the LDT-to-study transition, that combination shortens the distance between a working LDT and a study that holds up.
A useful first step for a team with an LDT running and a clinical study on the horizon is a sequencing review: where the dossier stands today, what the regulatory destination will require, and what to validate before study samples are collected. Nexus works with partners to map that sequence for a specific assay.
