Submissions
Client submissions in the lab queue · click a sample to open it, split it and print its robot label.
Split onto agar & pick colonies into a 96-well plate
Plate the sample onto media (agar ID = UID + media suffix), then pick colonies into the destination plate. Isolate ID = agar ID + 2-digit counter; wells fill down columns.
Labels
One scannable Code 128 label per item.
Combine samples into a pool
Select 2+ samples from this submission · a Pool ID is minted from the submission's labelling convention · every source is recorded for traceback.
A pool is treated as a new composite sample. The membership table keeps every contributing sample linked, so any result on the pool traces back to each source. Multiple pools can exist per submission. Samples are selected by UID here; the same convention applies to agar-level pools.
Pools in this submission
Each pool records its source samples for full traceback
Reagents · Recipes · Batches · Consumption
Configure what each test consumes, then watch the active batch deplete as runs happen.
Every test is configured with the reagents it uses per run. Each reagent has batches you activate or deactivate — consumption always draws from the active batch. Run a test and the configured amounts are deducted, logged, and the next batch opens automatically when one runs dry.
Test reagent recipes
Configure the reagents & per-run amount each test consumes · run a test to consume them
Reagent batch inventory
One active batch per reagent · activate / deactivate
| Reagent / Lot | Expiry | On hand | Status |
|---|
Consumption log
Each run deducts from the active batch — newest first
Quality Control · create a session, add the day's samples
Open a QC session for the day, then add the samples you need to run across every test.
A QC session collects all the samples due for QC on a given day — spanning different tests and clients. Each test in the session brings its own controls; nothing is released until every control passes — then results fan back out to each client.
Samples awaiting QC
Across all tests & clients · click Add to put into today's session
QC session · QC-2026-05-28
No samples yet
Quality control checks
One control set per test in the session · all must pass to release
Simulate a failing control (show how the whole run is blocked)
A run may mix tests and clients. Control types and accept ranges are defined per test. The gate is all-or-nothing for the whole run: if any one control fails, nothing releases until that run is repeated or the control passes. On release, each client only sees their own results (row-level multi-tenancy).