# A call per sample and target, made only when the replicates agree

> Call each sample present or absent per target from qPCR data, with its own Cq cut-off, replicate agreement and control checks. Research use only.

Source: https://clarida.bio/qpcr/detection
Updated: 2026-10-29

[Use it for · Present or absent calls](https://clarida.bio/qpcr)

Bring a screening run. Clarida calls each sample present, absent or inconclusive per target, against its own Cq (Ct) cut-off. For research use.

[Start free](https://app.clarida.bio/login) · [Each step, with its defaults](https://clarida.bio/qpcr/detection#how-it-works-in-clarida)

4 [experiments](https://clarida.bio/pricing#whats-an-experiment) in your first month, then 2 a month. No card.

> **experiments**: The runs and analysis behind one scientific question. Counted once, when you create it. Re-analyzing, reporting and exporting are free, with no limit on samples, assays or runs. [How pricing counts experiments](https://clarida.bio/pricing#whats-an-experiment)

1. [Step 1: Define](https://clarida.bio/qpcr/define)
2. [Step 2: Design (used here)](https://clarida.bio/qpcr/design)
3. [Step 3: Execute](https://clarida.bio/qpcr/execute)
4. [Step 4: Import (used here)](https://clarida.bio/qpcr/import)
5. [Step 5: Analyze (used here)](https://clarida.bio/qpcr/analyze)
6. [Step 6: Report](https://clarida.bio/qpcr/report)

Marked: the steps where present or absent calls relies on parts of its own.

- **New experiment**: qPCR start page › Detection
- **Already ran the plate**: Analysis only › Import & review

## What you get

A call table: one row per sample, one column per target, one call in each cell. Above it, three cards answer the questions in order: what was tested (samples × targets), whether the controls passed, and the result, such as “3 of 7 positive”. A Detected column counts the positives in each row. With controls configured, a QC dot on every row and column shows where a failing one points. Hover a cell to see its count, for example 2/3.

Save the analysis and it is kept as a frozen record, with the cut-off each target was called against. Add it to a PDF or HTML file with the Report builder, which carries the call grid and the counts.

Figure 1: A call for every sample and target, and one cell opened: two replicates fall below the eae cut-off, one gives no Cq, so the call is inconclusive. Illustrative data.

## How is a call made?

As a kit insert’s interpretation table states it, for every unknown sample and every target you test.

- **Detected**: Every included replicate has a Cq below the target’s cut-off
- **Not detected**: No included replicate has
- **Inconclusive**: The replicates disagree; Clarida does not average its way to a call
- **Not measured**: Nothing is left to judge, so a gap never reads as a negative

Where Clarida differs from most kit inserts: a failing control flags the result, and never changes the call.

- **The internal control (IAC, often called IPC) fails in a sample**: That sample’s row is flagged; its calls stay as computed, and there is no Invalid call
- **A positive or no-template control fails**: The target it implicates is flagged, on its column
- **The IAC’s acceptable range**: Its kit’s, else the experiment’s positive-control range; with neither, it must amplify

## How it works in Clarida

01 In the app: Design › Assay Prep

### A cut-off for each target, and which ones are controls

Each target carries its own detection cut-off, in Cq. Its type decides whether it becomes a column of the call table or a check on it. A gene of interest or a reference gene gets calls; a control is checked.

- **Detection cutoff (Cq):** per target; left empty, the experiment’s default applies
- **Target type:** gene of interest by default; the three control types (positive, negative, IAC) are checks

In full on [the Design page](https://clarida.bio/qpcr/design#assay-prep)

02 In the app: Import › Import & annotate

### Your run in, with every sample’s role

Import the instrument’s file or a Cq table, and each well is matched to its sample and assay. The type you give each sample matters here: only unknowns get a call.

- **Checked, not called:** positive, no-template, no-RT and other negative control samples

On the Import page: [Import & annotate](https://clarida.bio/qpcr/import#import)

03 In the app: Analyze › Raw data

### Curves to check before you trust a call

When the file brings curves, you see each well’s amplification and melt plot, and choose whose Cq the call uses. A late, noisy curve close to the cut-off is exactly the one worth a look.

- **Cq source:** automatic by default, the cycler’s when the file has it, otherwise Clarida’s, for the whole experiment
- **Cq method:** a curve fit per well (Clarida’s default), a baseline and threshold, the second-derivative maximum

In full on [the Analyze page](https://clarida.bio/qpcr/analyze#raw-data)

04 In the app: Analyze › Sample/Assay QC

### Controls checked per sample and per target

The internal amplification control is checked in every unknown, so a sample where it failed is flagged. Positive control samples must amplify each target, and negatives must stay clean. The verdicts carry through to the call table.

- **Negative controls:** automatic by default, a Cq floor or a ΔCq margin

In full on [the Analyze page](https://clarida.bio/qpcr/analyze#sample-assay-qc)

05 In the app: Analyze › Detection

### The call table, recomputed as you work

Detection computes as soon as you open it, and again whenever a Cq, an exclusion, a sample type or a cut-off changes. An excluded well leaves the call, which is then made on the replicates that remain. Save the analysis to freeze it.

- **Detection Cq cut-off:** the experiment’s default, empty unless you set it (any Cq counts); shared with Genotype calling

On the Report page: [Report builder](https://clarida.bio/qpcr/report#content)

## Why it is done this way

A cut-off per target, not one for the plate, because where a Cq stops meaning “present” depends on the assay: its efficiency, its background and the purpose of the test. Choosing that value is a validation decision made per assay, often by the kit maker ([Caraguel et al., 2011](https://pubmed.ncbi.nlm.nih.gov/21217022/)). Clarida applies the value you give it and records it with every saved result.

Replicates are combined by agreement rather than averaged, because near the limit of detection a target present at a few copies amplifies in some reactions and not in others, by chance alone ([Forootan et al., 2017](https://pubmed.ncbi.nlm.nih.gov/28702366/)). A mean Cq would hide that; an inconclusive call shows it, and asks you to repeat the sample or decide.

A negative means little without proof that the reaction could have worked. An internal control in each sample shows that inhibition or a failed extraction did not cause it ([Hoorfar et al., 2004](https://pubmed.ncbi.nlm.nih.gov/15131141/)), and no-template wells show that a positive is not contamination. MIQE 2.0 asks for both kinds of control to be reported ([Bustin et al., 2025](https://pubmed.ncbi.nlm.nih.gov/40272429/)).

## What it doesn’t do

- **A diagnostic test**: Not in Clarida: calls are for research use, such as screening panels, GMO checks, food and veterinary studies
- **Overruling a call by hand**: Exclude a replicate, or change the target’s cut-off
- **Finding your cut-off: limit of detection, probit**: Not in Clarida: you bring the cut-off, often from the kit maker
- **Calls in the Excel notebook and RDML**: In the PDF and HTML report, as the call grid and counts

## Frequently asked questions

### Which Ct cut-off is used for a target?

The target’s own detection cut-off first, then the experiment’s default. If neither is set, any Cq counts as detected, which is rarely what a screening run wants.

### Does a failing IPC make the call invalid?

No. Clarida has no Invalid call: the sample’s row is flagged and the call stays as computed, for you to judge. A strongly positive sample that suppresses its internal control is flagged like any other failure.

### Can a kit bring its own cut-offs?

Yes. A kit can bring its cut-offs into your experiment. To use another value for your run, change the target’s own cut-off: the experiment’s default never overrides it.

### Are your controls called too?

No. Only unknown samples get a call, and only on targets of interest and reference genes. Controls appear as QC verdicts beside the table, and in Sample/Assay QC.

Updated October 29, 2026

## Call your own screening run.

Import a run you already have and read its call table. 4 experiments in your first month, then 2 a month. No card.

[Start free](https://app.clarida.bio/login) · [Talk to a founder](https://clarida.bio/talk-to-us?topic=demo)
