Getting started
Quickstart
From a brand-new account to your first released result. Most labs finish this walkthrough in under an hour — nothing here requires IT help or a services contract.
Before you begin
You need an Aliquora account — start a free trial on any plan. The first account created for your lab is the administrator: it can configure everything below and invite the rest of the team when you're ready.
The one idea worth knowing up front: Aliquora adapts to your lab, not the other way around. Your sample statuses, screens, fields, and approval rules are all configurable — and the fastest way to configure them is to describe your lab in plain English and approve what the assistant proposes.
Step 1 — Let the Launch Assistant set up your lab
After sign-in you land on the Launch Assistant: a guided path from fresh account to go-live with a readiness checklist. Pick your lab type (environmental & water, cannabis, food & beverage, and more) and its one-click blueprint applies an industry profile — workflow stages, intake fields, release gates, and a starter test catalog for your lab type. Review every test's spec limits against your own methods before first use; where a pack doesn't ship limits, add yours in the Test Catalog.
Prefer to describe it yourself? Open Configure → Config Studio and type what you need — for example:
Set up my lab for drinking water compliance testing.
We log samples by bottle, run pH, turbidity and nitrates,
and results are reviewed by the lab manager before release. Config Studio answers with a previewed change set — every test, stage, and field it wants to create — that applies only after you approve it. Risky changes require an explicit confirmation, changes that weaken a compliance control require a reason and e-signature, and everything lands in the change ledger with one-click rollback.
Step 2 — Check your test catalog
Open Test Catalog and confirm the tests you run are there: code, name, units, method, and spec limits (reference ranges). Spec limits matter — they drive automatic out-of-spec flagging when results arrive. Add anything missing by hand, or ask Config Studio ("add a total coliform test, MPN/100 mL, SM 9223B").
Step 3 — Register your first sample
Go to Sample Management → New Sample. Enter the client, the material or source,
and pick the tests to schedule. The sample gets a tracking ID (like CHM-2026-0001)
and starts in your workflow's first stage. The intake form is yours to shape — Screen Studio lets
you relabel, reorder, hide, or add fields, and publishing a screen change updates the form for
everyone instantly.
Step 4 — Get results in
Three ways, use any mix:
- Type them. Open the sample, enter results per test. Values outside spec limits are flagged out-of-spec automatically.
- Upload an instrument export. Data Import accepts CSV, TSV, Excel, or pasted spreadsheet data. Columns auto-map, every file is classified row-by-row (matched / unmatched / duplicate / invalid) in a preview you must confirm, and nothing imports silently. Save the mapping as a template so that instrument is one click next time.
- Automate it. Point your instrument software's auto-export at a folder and run the Aliquora uploader agent on the instrument PC. New exports upload themselves; anything malformed is quarantined into a review queue instead of importing.
Imported results always land unverified — they queue for your review flow and never skip QC gates.
Step 5 — Review and release
Move the sample through your stages (or let approval chains route it). Verification is a deliberate act by a named person; verified results lock against silent changes, and every action lands in the audit trail. When the sample reaches release, generate the COA — it carries your lab's branding and shows Pass / Fail / Not evaluated per test, never implying evaluation that didn't happen.
Step 6 — Invite the team & open the portal
- Team: Settings → Team. Roles control who can enter results, approve, manage configuration, and sign.
- Clients: the customer portal gives your clients self-serve access to their own samples, statuses, and COAs — scoped so a client can only ever see their own work.
Where to go next
| If you want to… | Read |
|---|---|
| Automate instrument uploads from lab PCs | Instrument uploader |
| Integrate over the REST API | API reference |
| React to lab events from your own systems | Webhooks |
| Plan a regulated go-live | Onboarding checklist |
| Understand the AI's guardrails | AI technical overview |
| Map controls to Part 11 / ISO 17025 | Compliance docs |
This document describes Aliquora product capabilities as of the date provided and is offered for evaluation purposes. It is not legal or regulatory advice and is not a warranty of compliance. Each organization is responsible for validating and confirming that the system meets its own regulatory obligations. Generated by Aliquora · aliquora.com