Assay Development is the process of designing, optimizing, and validating a diagnostic test method—the reagents, protocols, and detection chemistry that measure a specific analyte—so it reliably and reproducibly generates accurate results before the method is locked into a manufacturable in vitro diagnostic (IVD) product.
What is Assay Development?
An assay is the analytical method itself: the chemistry, biology, and instrumentation that convert a biological sample into a measurable signal. Assay development covers everything from choosing the analyte and detection principle—whether immunoassay, PCR, colorimetric, electrochemical, or lateral flow—through establishing the reagent formulation, sample preparation, and testing protocol that will eventually be incorporated into a commercial diagnostic product.
Assay development typically begins during feasibility studies and runs alongside hardware, cartridge, microfluidics, and software development for benchtop or point-of-care platforms. The process concludes when the analytical method is frozen for design verification. From that point onward, any modification must proceed through formal design change control rather than experimental optimization.
Why Assay Development matters in medical device development
A diagnostic device is only as reliable as its underlying assay. Poorly optimized assays increase the risk of false-positive or false-negative results, directly affecting clinical decisions and patient safety. Consequently, regulatory agencies evaluate analytical performance as rigorously as hardware and software performance during FDA submissions and EU IVDR conformity assessments.
Assay development also has significant implications for manufacturing. Methods that appear robust during laboratory development may fail when scaled to production because of reagent variability, matrix interference, or inconsistent manufacturing processes. Correcting these issues after design freeze often requires repeating analytical verification, updating technical documentation, and delaying regulatory submissions.
During audits, reviewers expect objective evidence demonstrating that analytical performance claims—including sensitivity, specificity, precision, reportable range, and limit of detection—were established through structured validation studies rather than assumptions.
How Assay Development works
Assay development follows a structured progression, with each stage generating objective evidence that supports the design history file and technical documentation.
- Analyte and method selection. Identify the target biomarker, detection chemistry, and platform technology (such as ELISA, PCR, lateral flow, biosensors, or chemiluminescence) based on clinical need and technical feasibility.
- Reagent and protocol optimization. Optimize antibodies, primers, enzymes, buffers, incubation conditions, washing steps, and sample volumes to maximize sensitivity while minimizing background noise and variability.
- Analytical feasibility studies. Evaluate early assay performance using contrived or spiked samples to determine whether target analytical sensitivity and specificity appear achievable before formal validation.
- Analytical validation. Conduct structured performance studies using recognized CLSI protocols, including precision (CLSI EP05), linearity and reportable range (CLSI EP06), method comparison (CLSI EP09), and limit of detection and limit of blank (CLSI EP17).
- Stability and robustness studies. Demonstrate reagent shelf life, in-use stability, shipping robustness, temperature tolerance, and storage performance under expected operating conditions.
- Design transfer. Freeze the assay formulation and operating protocol before verifying them under ISO 13485 design controls and transferring the process into manufacturing.
Risk management under ISO 14971 runs throughout assay development because analytical hazards—including cross-reactivity, interfering substances, matrix effects, carryover, and high-dose hook effects—can directly affect diagnostic performance. Under the FDA Quality Management System Regulation (QMSR), effective February 2026, assay development also falls within design controls aligned with ISO 13485:2016. For point-of-care or CLIA-waived products, usability engineering under IEC 62366-1 evaluates how intended users collect samples, operate the test, and interpret results.
Common challenges and best practices
One of the most common mistakes is developing the assay independently of the instrument or cartridge. A reader or microfluidic cartridge designed without considering assay requirements may fail to deliver the required sample volume, incubation time, mixing efficiency, or temperature control. Successful development programs integrate assay scientists with hardware and software engineers from the beginning.
Another recurring challenge is insufficient analytical validation. Small feasibility studies often fail to represent real-world clinical specimens. Performance can deteriorate when samples contain interfering substances such as hemolysis, lipemia, bilirubin, medications, or endogenous antibodies. Expanding sample diversity and replicate testing throughout development significantly reduces late-stage surprises.
Supply-chain stability is another frequently overlooked risk. Antibody clones, enzymes, fluorophores, or other critical reagents may change over time or become unavailable. Qualifying alternate suppliers before design freeze minimizes the likelihood of expensive assay redevelopment after commercialization.
Strong development programs also incorporate manufacturability early. Assays that perform well under controlled laboratory conditions should be evaluated using production-intent materials, automated dispensing equipment, and realistic manufacturing tolerances long before design transfer.
How SJML helps with Assay Development
SJML supports assay development across diagnostic, laboratory, and point-of-care platforms as part of its end-to-end IVD engineering services. Multidisciplinary teams combine assay chemistry, microfluidics, electronics, embedded software, and systems engineering to move candidate assays from early feasibility through analytical verification and production readiness.
Risk management under ISO 14971, usability engineering under IEC 62366-1, and design controls aligned with ISO 13485 are integrated throughout development. SJML also supports design verification, technical documentation, and design transfer into ISO-classified cleanroom manufacturing. For manufacturers pursuing FDA or EU IVDR approval, SJML’s QARA team assists with regulatory strategy, analytical performance documentation, and technical file preparation built directly on assay development data.
Talk to SJML’s engineering team →
Frequently asked questions
Assay development is the iterative process of designing and optimizing the analytical chemistry, reagents, and testing protocol. Assay validation is the structured evaluation that demonstrates the finalized assay meets predefined performance claims for precision, sensitivity, specificity, linearity, limit of detection, and other analytical characteristics. Validation begins only after the assay design has stabilized.
Assay development typically starts during feasibility and proof-of-concept activities, running alongside instrument, cartridge, and software development. It continues through optimization until the analytical method is frozen for design verification. After design freeze, further changes require formal design change control within the quality management system.
Although no single standard governs assay development itself, manufacturers typically use CLSI EP-series documents—including EP05 (precision), EP06 (linearity), EP09 (method comparison), and EP17 (limit of detection)—alongside ISO 13485 for design controls, ISO 14971 for risk management, and Regulation (EU) 2017/746 (IVDR) for technical documentation and performance evaluation requirements.
Development studies often use limited reagent lots, controlled laboratory conditions, and relatively small sample sets. During manufacturing, lot-to-lot reagent variation, automated dispensing tolerances, environmental conditions, raw material variability, and broader clinical sample diversity can reveal performance issues that were not apparent during laboratory optimization. Designing for manufacturability early substantially reduces this risk.
The limit of detection (LoD) is the lowest concentration of an analyte that an assay can reliably distinguish from a blank sample with an acceptable level of confidence. It is typically established following CLSI EP17 and forms one of the core analytical performance characteristics submitted to regulatory authorities alongside precision, specificity, sensitivity, and linearity.
Related terms
- Analytical Validation
- Design Verification
- Design History File (DHF)
- Point-of-Care Testing (POCT)
- In Vitro Diagnostic Regulation (IVDR)
