# Each sponsor’s qPCR method in its own workspace, on every run

> Research-use qPCR analysis for contract labs: a workspace per client on a Center account, each sponsor’s method versioned, exports it can reopen.

Source: https://clarida.bio/for/cros
Updated: 2026-10-29

[For CROs](https://clarida.bio/for)

Research-use qPCR analysis from co-authors of MIQE, geNorm and qBase. Each experiment records which version of the sponsor’s method it started from.

[Talk to a founder](https://clarida.bio/talk-to-us?topic=pilot) · [For your sponsor’s QA](https://clarida.bio/for/cros#for-your-sponsors-qa)

## How a sponsor’s spec is handled today

A new sponsor arrives with its own SOP, reference genes and acceptance criteria, and most contract labs turn that into a per-client Excel template: checked once, reused for each study. For routine work it is a sound way to run a service, and the specs differ for a reason. For qPCR in cell and gene therapy alone, 37 authors from 24 organizations, CROs among them, point to the lack of harmonized validation guidance ([Hays et al., 2024](https://doi.org/10.1208/s12248-023-00880-9)).

What strains it is the twelfth client and the first amendment. Templates multiply, an old copy gets opened, and the sponsor stays answerable for work it outsources, so its queries reach your analysts months later. A number rebuilt from the files then has to match the one already reported.

| Today | With Clarida |
| --- | --- |
| A per-client Excel template, copied for each new study | The client’s method saved once as a settings set; each experiment records the set and version it started from |
| An amended spec saved over the template the earlier runs used | The amendment becomes version 2; experiments already run stay on the first |
| Every sponsor’s files in one shared drive | A workspace per client, which only its members can open |
| A queried number rebuilt from the files, slightly different | The saved analysis reopens with the data, settings and result it was made from |

A per-client Excel template today? [When is your spreadsheet enough?](https://clarida.bio/compare/spreadsheets#when)

## The questions a sponsor’s auditor asks

Sponsors review the systems behind outsourced work, before they place it and again in an audit. Clarida is research-use software, not a validated GxP, GLP or 21 CFR Part 11 system. For the studies that do not need one, this is what it shows an auditor.

Figure 1: One sponsor’s study across an amendment: runs 1 to 3 keep version 1 of the method, the settings they ran with, and runs 4 and 5 start from version 2. A query on run 2 finds version 1. Illustrative data.

- **Which version of our method produced this number?** Each experiment records the settings set and version it started from, and its report names both. An amendment is saved as the next version, which earlier runs never take on (Fig. 1; [settings sets](https://clarida.bio/methods/settings-sets)).
- **Why was this well left out?** Each exclusion shows whether it came from a person or a rule, with any note typed for it; none made by hand is undone automatically. The instrument’s own flags stay as they came ([Analyze](https://clarida.bio/qpcr/analyze#exclusion)).
- **How was the result calculated?** The report opens each section with a methods sentence written from the settings used: the reference genes, the test, the groups and the correction. A saved report is frozen, names the Clarida release that made it, and a change becomes its next version ([Report](https://clarida.bio/qpcr/report#methods)).
- **Can another client see our data?** No: each client has its own workspace, and what the account shares across them is in [For your sponsor’s QA](https://clarida.bio/for/cros#for-your-sponsors-qa).

## Start from the specs and files you have

- **The sponsor’s spec.** Its QC thresholds and analysis choices go into one settings set; the assays with their reference genes and control ranges, the mix and the cycling protocol into a [preset](https://clarida.bio/methods/presets) that each of that client’s runs starts from.
- **Run files from every cycler in the lab.** CFX, LightCycler 480, QuantStudio, Rotor-Gene or RDML, curves included, or a Cq table from any instrument. The Cq your instrument called is kept, beside any Cq Clarida calls from the curves ([importing instrument data](https://clarida.bio/methods/importing-instrument-data)).
- **One instrument PC, several clients.** [Porta](https://clarida.bio/security/porta) brings finished run files into Clarida, and can share each client’s folder with its own workspace alone.
- **Studies already analyzed elsewhere.** Bring their Cq values and go on from there; qbase+ archives [import free](https://clarida.bio/qbase-plus/import), read-only.

## For your sponsor’s QA

What Clarida is, what it records and who can see a client’s data.

- **What it is**: Research-use qPCR analysis software. It is not a validated GxP, GLP or 21 CFR Part 11 system and has no electronic signatures. Where a study calls for validation, that stays with your lab. Clinical trial data needs a separate written agreement with us ([terms](https://clarida.bio/terms)).
- **What it records**: For each experiment: the settings set and version it started from; earlier states of its design and parameters in the History tab, each with its author and time; analyses stored with the data and choices they used; each exclusion, marked as a person’s or a rule’s, with any note; reports kept unchanged and numbered once saved. It does not log every edit, and any member of a workspace can delete in it: nothing is signed off or locked by a person.
- **Who sees a client’s data**: The members of that client’s workspace, and your account’s owner, who is added to each new one. Currently there is no read-only role, so a sponsor sees its results in what you send it.
- **What clients share**: The account’s plan and its capacity, and the library items Clarida and kit makers publish for everyone. Never an experiment, a run or a result.
- **Where the data lives**: In the EU: the app runs in Amsterdam, the database in Stockholm, and everything travels over HTTPS.
- **Handing data over**: Each experiment, at any time: as RDML, the open qPCR format other software reads; as an Excel workbook; as its report, in PDF and HTML. RDML carries the data, Cq values and curves; the report states the analysis choices, and the workbook names the settings set each experiment started from.
- **When a contract ends**: The experiments stay viewable and exportable; no new ones can be created.
- **Who built it**: Jan Hellemans led the qBase paper and Jo Vandesompele the geNorm one, and both co-wrote the MIQE guidelines that sponsors’ specs cite ([meet them](https://clarida.bio/about)).
- **Not yet**: The name of whoever excluded a well, electronic signatures or sign-off, a read-only role for sponsors, reports in your own layout, exporting all experiments at once, absolute quantification and dPCR. A log of every edit is not built in yet; it is set up on request for a Center account.

## Frequently asked questions

### How is it priced across several clients?

On the Center plan, priced with you around your volume: that plan holds a workspace per client in one account. The Lab and pay-as-you-go rates are on [pricing](https://clarida.bio/pricing?audience=commercial&billing=annual).

### Can a sponsor log in to see its own results?

Not yet as a viewer: anyone in a workspace can work in it. Send the sponsor the report, the workbook or the RDML file instead.

### Can each sponsor get the report it expects?

Partly. You choose what goes into the report and write its headline and conclusion, while the numbers, methods sentences and QC come from the analysis. Its layout is Clarida’s, so a sponsor’s house format stays your own document, built from the export.

### Can you try it on one client first?

Yes. We set up one client’s method with you, run its next study on it, and you decide from there. A free account lets you try it on your own run files today.

### Does it analyze dPCR?

Not yet: analysis is qPCR and RT-qPCR. If a client’s work needs dPCR too, ask us about timing.

Updated October 29, 2026

## Run one client’s next study from its own method

We set up that client’s spec with you as a preset, run its next study on it, and you decide from there.

[Talk to a founder](https://clarida.bio/talk-to-us?topic=pilot)
