Do not promote an assumption to a fact
Examples include treating a related target as interchangeable, extending a species claim, or assuming specimen compatibility from analyte presence alone. Mark these statements as unresolved.
ELISA Assay Selection Guide
Research catalogue guide
Choose an ELISA kit by question, evidence, and documentation
Shortlisting an ELISA product starts before the catalogue search. Define the measurement you need, the analyte identity, the species and specimen context that matter, and the documentation required for your study. A product name alone rarely resolves those questions.
Use this guide to turn a broad search into a reviewable shortlist. Record what the supplier states, what supporting documents actually show, and what remains unknown. The result is not a universal protocol or a performance claim; it is a disciplined way to compare catalogue records and identify questions for the supplier or your own validation plan.
01 · Research questionWhat biological or analytical question is the measurement intended to inform?
02 · AnalyteIs the target identity, form, and nomenclature unambiguous?
03 · ContextWhich species, specimen type, and measurement setting must be supported?
04 · DocumentationWhich protocol, range, controls, and evidence need verification?
Decision workflow
Move from an open search to a defensible shortlist
Use this workflow to organize catalogue review before technical comparison. Each stage separates a decision question from a verification checkpoint. If the catalogue record or linked source documents do not answer a question, record it as unresolved rather than filling the gap with assumption.
- 01Target definition
Define the analyte
Decision question: What exactly do you need to measure? Confirm the target name, relevant synonyms, molecular form, and intended measurand. A related target name is not automatically interchangeable with the analyte in your study.
Verification: Compare the target named in the individual product record with your research question and note any unresolved terminology.
Checkpoint: the analyte identity and intended measurement are stated in terms that can be reviewed. - 02Study model
Confirm species and study context
Decision question: Does the product documentation address the species and study context you are evaluating? Keep the species named in the record separate from the species in your study; do not generalize across species without supporting documentation.
Verification: Record the stated species, study model, and any applicability limits in the source document.
Checkpoint: species relevance is explicit, supported by documentation, or clearly flagged for review. - 03Specimen fit
Review specimen information
Decision question: Is the specimen or matrix relevant to your planned work, and is that compatibility stated by a source? Look for specimen information, matrix details, and any handling notes in the individual product documentation.
Verification: Distinguish a documented specimen from an inferred one. The presence of an analyte in a biological material does not by itself establish that a kit supports that material.
Checkpoint: specimen compatibility is supported by a source document or remains an open supplier question. - 04Research setting
Clarify the measurement context
Decision question: Does the stated application align with your research design and intended use? Capture the context in which you expect to interpret the measurement, including the study population or model and the purpose of the comparison.
Verification: Compare the application language in the catalogue record with the technical documentation. Category placement can support discovery, but it does not replace study-specific review.
Checkpoint: the product’s stated application and your research purpose have been compared without extending the claim. - 05Run design
Plan controls and interpretation
Decision question: Which blanks, standards, controls, and replicates are needed for your run to be interpretable? Define the role of each control and identify likely sources of variation before prioritizing performance fields.
Verification: Check the product documentation for supplied materials, control descriptions, and plate or run guidance. Do not treat a generic control plan as a universal protocol.
Checkpoint: control roles, replicate decisions, and unresolved sources of variation are listed for review. - 06Source review
Verify documentation before shortlisting
Decision question: Which decision-critical fields are actually supported by the record or its linked source documents? Review protocol access, stated range, sensitivity, precision, storage information, controls, and citations only when the relevant source states them.
Verification: Label each item as manufacturer documentation, a peer-reviewed application report, internal validation, or unsupported inference. Mark unavailable values as unavailable rather than estimating them.
Checkpoint: every comparison claim has a traceable source, and remaining questions are ready for supplier review.
If target or species is unclearPause the shortlist and return to the individual record or source document.
If specimen or context is unresolvedKeep the product in review status and formulate a specific documentation question.
If documentation is sufficientCompare records consistently, then retain the source trail with the shortlist.
Browse human ELISA kitsBrowse animal ELISA kitsBrowse biomarker research kitsSearch all productsComparison checklist
Compare what is documented—not what is assumed
Build a comparison record for each individual product. The fields below are review prompts, not populated performance claims. Enter a value only after checking the product record, protocol, technical sheet, or other identified source document.
| Field | What to verify | Record status |
|---|---|---|
| Catalogue identity | Product name, catalogue number, product ID, and the target named by the supplier. | Record exactly |
| Supplier | Supplier identity or supplier identifier shown in the catalogue record. | Record exactly |
| Protocol access | Whether instructions or technical documentation are available for review. | Available / not located |
| Stated range | The range as stated in the applicable source document, including units and context. | Source required |
| Sensitivity | The supplier’s stated definition and value, without substituting another detection metric. | Source required |
| Precision | Within-run or between-run information, if documented, with the conditions reported. | Source required |
| Storage | Storage conditions, stability language, and handling information in the current documentation. | Source required |
| Controls | Included or recommended controls and their stated roles. | Source required |
| Citations | Manufacturer references, application reports, or other sources linked to the exact product or method. | Distinguish evidence |
Catalogue examples for record-level review: Human Hemopexin ELISA Kit · Human CRP ELISA Kit · Rat Osteopontin ELISA Kit · Dog NGAL ELISA Kit · Hexanoyl-Lysine (HEL) ELISA kit
Execution planning
Give every well a documented role
Plate planning should make the source of a signal and the limits of interpretation visible. Blanks can help identify background introduced by reagents or the plate context; standards provide the reference relationship used for quantitation when the method specifies them; controls provide a defined comparison point; and replicates help expose variation within the planned run.
The exact number, placement, preparation, and acceptance criteria are method- and study-dependent. The diagram is therefore conceptual, not a universal protocol. Follow the individual product documentation and your established laboratory procedures.
Before a run, annotate the plate map with sample identifiers, dilution or preparation notes where applicable, control roles, and plate or batch identifiers. This makes later review possible without relying on memory.
Illustrative plate map · roles only
BSSCR1R1R2R2BSCR3R3R4R4C
BlankStandardControlSample replicate
Evidence review
Keep documentation, validation, and inference separate
A useful shortlist records not only what appears persuasive, but what kind of evidence supports each statement. Evidence can inform a question without answering every other question about a product, specimen, species, or study.
Study-specific confirmation
Internal experiments can address the conditions, matrices, controls, and reproducibility questions relevant to your laboratory. They should be described as your validation evidence, not as a universal supplier claim.
Contextual external evidence
Published applications may show how a method was used in a particular context. Check whether the product, species, specimen, and analytical setting match your question before drawing a comparison.
Start with the exact product record
Product pages, protocols, technical sheets, and stated specifications define what the supplier has documented. Capture the document identity and the field it supports rather than paraphrasing beyond its scope.
Explain how to move from browsing to questions.
Explain how to move from browsing to questions.
This section covers Give a practical final review sequence. using the available product and source context.
- Supplier catalog evidence is retained for product identity, catalog details and comparison context.
- Precedes CTA.
- Unsupported performance, protocol and interchangeability claims are excluded from this public copy.