# Pasting sample and assay lists from Excel

> How samples and assays get into an experiment, and what one pasted table can carry: types, quantities, units, positions, QC limits and custom properties.

Source: https://clarida.bio/methods/importing-samples-and-assays
Updated: 2026-11-02

[Methods](https://clarida.bio/methods)

How samples and assays get into an experiment, and what one pasted table can carry: types, quantities, units, positions, QC limits and custom properties.

By [Jan Hellemans](https://clarida.bio/methods/importing-samples-and-assays#about-the-authors)

August 14, 2026 Updated November 2, 2026 11 min read

An experiment in Clarida is defined by the **samples** it measures and the **assays** it measures them with. Both are declared in the **Design** phase, in **Sample prep** and **Assay prep**, before a plate layout is generated; in an analysis-only experiment they come after the import.

Getting the lists in is the design-side counterpart to [Importing qPCR run files and Cq (Ct) tables](https://clarida.bio/methods/importing-instrument-data), which covers the file produced after a run. The vocabulary used here (sample types, assay types, reporter dyes) follows the [MIQE 2.0 guidelines](https://pubmed.ncbi.nlm.nih.gov/40272429/) (Bustin et al., 2025) and the [RDML](https://pubmed.ncbi.nlm.nih.gov/19223324/) data standard (Lefever et al., 2009).

**How to** covers pasting the sample sheet and the assay list you already keep; **How it works** explains what each column of a pasted table can carry.

## How to

### 1. Paste the sample sheet

In **Sample prep**, under **Bring in**, choose **Paste**. Copy the table from your spreadsheet, header row included, into **Paste data**. Under "When a pasted row name matches an existing sample", keep **Update matching samples** to add columns to samples you already have; **Create new samples (suffix collisions)** adds them as new ones. Then choose **Import**. See [What a pasted table may contain](https://clarida.bio/methods/importing-samples-and-assays#what-a-pasted-table-may-contain).

### 2. Review the extra columns

When the table has columns Clarida does not recognize, **Review paste import** opens before anything is written. Each column can fill a property you have, become a new text one, or be dropped with **Skip**; then choose **Import**. See [Custom properties: any other column](https://clarida.bio/methods/importing-samples-and-assays#custom-properties-any-other-column).

### 3. Paste the assay list

In **Assay prep**, under **Bring in**, choose **Paste**, paste the assay table into **Paste data** and choose **Preview pasted data**. A multiplex assay is several rows sharing one name. See [Assay columns and multiplex](https://clarida.bio/methods/importing-samples-and-assays#assay-columns-and-multiplex).

## How it works

### Ways to add samples or assays

Both sections offer input methods chosen to match how the list already exists in your hands, grouped as **Create** and **Bring in**:

- **Manual** · Add rows one at a time and edit any cell inline. Suited to a handful of entries, or to correcting a list that is already there.
- **Batch** (samples) or **Generate** (assays) · Create a numbered set of a chosen length (`Sample 01`, `Sample 02`, …), with one sample type for all. Useful when names carry no information and positions do the work.
- **Series** (samples only) · Create the standards of a dilution series from a starting quantity, its unit, a dilution factor and the number of points.
- **From library** · Pick entries already stored in your workspace library; assays also as a panel. A library sample or assay carries its stored properties with it, so nothing is retyped.
- **From file** · Read an Excel, CSV or text file, or a sheet of the lab notebook linked to the experiment, and pick the sheet or table to use.
- **Paste** · Paste a table from Excel, Google Sheets, or any tabular source.

**Paste** and **From file** are the routes that carry a whole table's annotation in one action: a file's rows go through the same reading as a paste.

### What a pasted table may contain

Pasted text is split into columns on **tab, comma, or semicolon**, whichever appears most often on the first line, defaulting to tab for Excel compatibility. A space is deliberately not a separator: sample names can contain spaces (`Liver RNA`), and treating them as column breaks would corrupt the names.

What Clarida does with the columns depends on whether the first row is a **header row**.

**With headers**, columns are matched by name, in any order, and the full set of recognized columns becomes available:

| Column | Description | Recognized by (aliases) |
| --- | --- | --- |
| Sample name ★ | The sample identifier | Sample, Sample Name, Name |
| Sample type | Control role, see the sample types below | Type, Sample Type |
| Quantity | Input quantity / concentration, used for standards | Quantity, Concentration, Input Quantity, Qty |
| Unit | Unit for the quantity, defaults to copies/µL | Unit, Units, Concentration Unit, Quantity Unit |
| Position | Plate position (A1–P24) or a plate-fill index | Position, Pos, # |
| Expected Cq min / max | Acceptable Cq window for a positive control | Expected Cq Min / Max, POS Cq Min / Max, Min Cq, Max Cq |
| NEG Cq floor | Lowest Cq a negative control may show before it fails | NEG Cq Floor, Neg Cq Floor, Cq Floor |
| NEG dCq margin | Minimum dCq a negative control must clear | NEG dCq Margin, Neg dCq Margin, Min dCq |
| Calibrator | Calibrator role, used when scaling to calibrator | Calibrator, Is Calibrator, is_calibrator |

★ Required. All other columns are optional.

Header names are trimmed and matched case-insensitively against the alias lists, exactly per alias rather than by substring, so an unlisted header is not auto-detected.

The **Calibrator** column marks the samples that relative quantities are scaled to under **Scale to calibrator**. It accepts yes/no, true/false, 1/0, or x, in any case. A blank cell leaves the role unset, and any other value leaves it unset with a row warning. A row whose type is a negative control cannot be a calibrator: a truthy cell there is ignored, with a warning. Like the type, the role is set only on samples the paste creates; on a row that matches an existing sample it is left unchanged, and the review notes it.

**Without headers**, the columns are read by position: first column sample name, second sample type, third quantity, fourth the unit that quantity is in. This is what makes a bare list of names work, since pasting one column of names turns each into a sample. Two further conveniences apply to headerless input. A single column of plain integers is read as **positions**, with names generated to match, and a list of names with no types is read as names alone.

The trade-off: **only a header row unlocks positions, quality-control limits, the calibrator role, and custom properties.** A headerless paste can carry four things; a paste with headers can carry everything.

### Custom properties: any other column

A column whose header matches none of the recognized names is **not an error and is not discarded**. It becomes a **custom property** on every row of the paste, named after the header.

This is the supported way to set a property on many samples at once. To record the tissue each sample came from, add a `Tissue` column to the table you are already pasting, and every sample receives its value in the same operation.

Before anything is written, a **review dialog** shows each column and what will happen to it:

- **Matched column** · Routed to the existing property it matches, and can be re-routed to a different one.
- **Unmatched or type-mismatched column** · Becomes a new experiment-local text property.
- **Any column** · Can be skipped.

The dialog is also what catches a mistyped canonical header. `Smaple Name` matches no recognized column, so it would otherwise quietly become a property called "Smaple Name" instead of filling the sample-name column. The review makes that visible before it lands rather than afterwards.

When a pasted name matches a sample already in the experiment, you choose whether to **update the matching sample**, the default, or to **create new samples**, suffixing the collision.

Custom properties on paste are a **Sample prep** capability. Assay prep recognizes its own columns, described below, and ignores any others. The library paste surfaces under Storage likewise take canonical columns only. The sample library paste reads its columns by position (name, type, quantity, unit) and has no Calibrator column; set the role with the **Calibrator** checkbox on each sample's card in the preview before importing.

### Assay columns and multiplex

Assay prep reads the same way, with headers matched by alias, or a positional fallback of name, dye, type, target name:

| Column | Description | Recognized by (aliases) |
| --- | --- | --- |
| Assay name ★ | The assay identifier | Assay, Assay Name, Name |
| Target | Target gene / amplicon | Part, Part Name, Target, Target Name, Target Gene, Gene |
| Dye | Reporter dye (defaults to SYBR when blank) | Reporter, Reporter Dye, Dye |
| Assay type | Gene of interest, reference gene, or a control | Type, Assay Type |
| Quencher | Probe quencher (defaults to BHQ1 when blank) | Quencher |
| Position | Plate position (A1–P24) or a plate-fill index | Position, Pos, # |

★ Required. All other columns are optional.

**A multiplex assay is written as several rows sharing one assay name.** The assay is what you pipette into the well; each row is one target measured inside it, distinguished by its dye:

| Assay | Target | Dye |
| --- | --- | --- |
| FLU.RSV | Influenza | FAM |
| FLU.RSV | RSV | CY5 |
| FLU.RSV | RNase P | HEX |

Three rows, one triplex assay with three targets. The targets of one assay would normally each use a different dye. Sharing one is allowed, since pathogen panels legitimately do it, but is flagged as a warning so you can check it.

Assay type accepts `gene_of_interest` (the default), `reference_gene`, `positive_control`, `negative_control`, and `internal_control`, each with the aliases listed in the in-app help. Note that `ntc` is a **sample** type only: an assay has no template to omit, so a negative-control assay is `negative control` or `neg_ctrl`.

### Sample types

The sample type classifies each entry as a test sample or a control. It is normalized case-insensitively after trimming, accepting common variant spellings. Sample prep reads the same types and values as an instrument import: they are listed once, with [the sample types an import reads](https://clarida.bio/methods/importing-instrument-data#negative-controls-ntc-nac-nrt-and-ntp), which also explains why a specific negative control says more than a generic one and why the scaling calibrator is a role, not a type.

A value matching none of them, or a row with no type at all, is treated as **Unknown**, and the paste reports the unmatched value as a row warning.

Aliases are matched per entity, not globally: `ntc` is a **sample** type, while a target control is `negative_control`. And an ambiguous token is deliberately not an alias, so `cal` is absent because it could mean a standard-curve point (`std`), an optical calibrator (`opt`), or an inter-run calibrator, which is not a type at all. (Nor is the scaling calibrator: that is the **Calibrator** role.) Leaving such a cell unrecognized lets you choose rather than having Clarida guess.

### Concentration units

A quantity is only meaningful with a unit, so the Quantity column pairs with an optional Unit column. Seven units are stored:

| Unit | Meaning | Recognized values |
| --- | --- | --- |
| copies/µL | Copy concentration per microliter (the default) | copies/µL, copies/uL, copy/uL, cp/uL, copies per uL, copies/microliter |
| ng/µL | Mass concentration per microliter | ng/µL, ng/uL, ng per uL, ng/microliter |
| nmol/µL | Amount concentration per microliter | nmol/µL, nmol/uL, nmol per uL, nanomol/uL |
| nM | Nanomolar | nM, nanomolar, nmol/L, nanomol/L |
| copies | A copy count with no volume | copies |
| fold | A fold change | fold, fold change, fold-change, x |
| dilution | A dilution factor | dilution, dilution factor, dil |

Matching ignores case and treats `µ` and `u` as the same character, so `copies/µL` and `copies/ul` are one unit. A quantity with **no** unit is stored as copies/µL without comment. A unit that is present but unrecognized falls back to the same default and is flagged as a warning, so a typo is visible rather than silent.

As with sample types, an ambiguous token is deliberately not an alias: a bare `cp` or `copy` could mean either `copies/µL` or the unit-less `copies`, so it warns instead of guessing.

### Fold and dilution are opposites

Clarida keeps them as two units because they count in opposite directions. A standard at 10 000 **fold** is the most concentrated point on the curve; the same sample at 10 000 **dilution** is the least. A single label could not say which, so the number alone did not tell you which way the curve ran.

Clarida stores the concentration itself, which always rises with the amount of template: a 1:10 dilution is stored as 0.1. Entering and reading a dilution as `1:10` is a presentation of that same number, not a different one. Because the stored value never changes direction, calculations such as amplification efficiency never need to know which unit you chose.

The combined spellings (`fold dilution`, `fold dil`, `fd`) are no longer recognized for exactly this reason: they cannot be told apart from either sense, so accepting one would silently reverse each curve that meant the other sense. They are flagged as unrecognized so you can state which you meant. Samples already saved under the old unit keep their stored value and label until you edit them.

`nmol/µL` is **not** the same as `nM`: nanomolar is per liter, so the two differ by a factor of a million. Both are offered because both are legitimate: the same relationship `copies` and `copies/µL` already have.

### Where the definitions go next

Samples and assays declared here feed the rest of the Design phase. The plate layout is generated from them, and the resulting run defines which wells hold which sample-assay combination. When instrument data is imported afterwards, that annotation is what the imported file is reconciled against: a sample name in the export matches a sample defined here, and a run that differs waits for your choice rather than merging silently.

Definitions are not frozen once entered. Names can be edited inline, types and quality-control limits set in bulk from the sample list, and properties added at any later point, including by pasting another column onto samples that already exist.

## About the author

- Jan Hellemans

  Co-founder, Clarida

  Leads the science and the methods at Clarida. Published the qBase method in 2007 and co-authored the MIQE guidelines.

  [Google Scholar](https://scholar.google.com/citations?user=L8EeDgwAAAAJ)

## Paste the sample sheet you already keep in Excel.

In Design, a pasted table splits on tab, comma or semicolon.

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