First sample → first report

Duration: ~15 minutes

Welcome to Agrometrisis. This tutorial walks you from your very first login all

the way to downloading a signed PDF analysis report. No prior LIMS experience

is assumed. By the end of these 15 minutes you will have completed a full

cycle: contact → sample → analysis record → measurements → review → approval

→ released PDF.

The cycle mirrors the workflow required by ISO/IEC 17025:2017 (clauses §7.4

sample receipt, §7.5 technical records, §7.8 reporting of results). Each step

maps to specific clauses — citations appear at the end of each section so you

can later correlate using the system with meeting the standard.

1. Before you begin

Goal: confirm you have everything needed to complete the cycle without

interruption. Duration: ~30 seconds.

Get the following ready:

User credentials. Your IT team has provisioned your account and given

you a username (usually your work email) and a temporary password. Keep

them at hand.

A modern browser. Latest Google Chrome or Mozilla Firefox. Safari and

Edge work too, but Chrome is the recommended test platform.

A real sample on the bench. E.g. a soil sample that has just arrived

at the lab. We will not use mock data — the tutorial assumes you have

something genuine to log so the cycle is meaningful.

Knowledge of the method. You need to know which LabMethod applies to

the sample. E.g. "Soil pH per ISO 10390". If you are unsure, ask your

quality manager before continuing — changing methods mid-analysis triggers

corrective action.

When you finish this step, you should have: username, password, an open

browser at the Agrometrisis URL, and a sample in front of you.

Goal: sign in and land on the Dashboard. Duration: ~30 seconds.

Open your browser and enter the Agrometrisis URL provided by IT (e.g.

https://lims.your-lab.gr).

The sign-in screen appears. Fill in:

Username (your work email)
Password (the temporary one from IT)

Click Sign in.
If your lab has multi-factor authentication enabled, you will be prompted

for a one-time code from your authenticator app. Enter it and click

Confirm.

If this is your first sign-in, the system may ask you to replace the

temporary password with one of your own. Choose a strong password

(12 characters minimum) and save it.

When you finish this step, you should see: the Dashboard with live

metric cards — e.g. samples awaiting analysis, pending reviews, overdue

calibrations. Your name and role (e.g. ANALYST, REVIEWER, LAB_DIRECTOR)

appear top-left. The left navigation bar shows the sections Contacts,

Samples, Analyses, Settings.

Related clause: signing in fulfils the general ISO/IEC 17025 §6.2 requirement

that every activity is performed by identified and authorised personnel.

3. Create a contact

Goal: register the customer who owns the sample. Every sample in the

system must be linked to a contact — this is the first link in the chain

of custody. Duration: ~1.5 minutes.

From the left navigation bar click Contacts. The list of all lab

customers appears.

In the top-right toolbar click the "+" button. A new page opens

("New Contact") with tabs Info / Addresses / Phones / Emails. The

last three tabs are disabled until you first save the Info tab — you

cannot add a phone or email before the first save.

On the Info tab, fill in the following fields. Required fields are

marked with a red asterisk (*):

First name (): e.g. "George".
Last name (): e.g. "Papadopoulos".
Contact type: pick whichever fits from the lab's list — e.g.

"Customer", "Farmer", or "Agronomist" (the options are tailored to the

agricultural/lab domain, not generic business categories).

VAT number (taxId): e.g. "123456789". The system validates

the checksum; if it is wrong, an error message appears below the field.

Click Save. The page stays open and the other three tabs become

enabled.

Go to the Phones tab and click "+" to add a phone (number, with or

without international prefix; optional label).

Go to the Emails tab and click "+" to add a valid customer email — it

will be used later to deliver the final PDF report, so double-check it.

When you finish this step, you should see: a success message after the

first save, the Addresses/Phones/Emails tabs now active, and your phone/email

appearing on their own tabs (not on the Info tab). Make a mental note of the

last name — you will need it in the next step to locate your contact quickly

in a larger list.

Related clause: logging the contact implements ISO/IEC 17025 §7.4.1 —

every test item is accompanied by a sufficiently identified

customer/submitter.

4. Create a sample

Goal: register the physical sample in the system so you can track it

through its lifecycle. Duration: ~2 minutes.

From the left navigation bar click Samples. The list of all lab

samples appears, sorted by most recent.

In the top-right toolbar click "+" again. The "New sample" dialog

opens.

Fill in the fields:

Sample code (sampleCode): you can either type your own code or

leave the field blank — if blank, the system will auto-generate a

unique code on save according to the configured numbering pattern

(e.g. SAM-2026-00041). For your first sample, leave it blank and let

auto-numbering do the work. The field hint reads "Leave blank for

auto-numbering".

Contact (contactId, *): click the field and start typing the

last name you just saved. Pick your contact from the dropdown.

Lab Method (labMethodId): optional here, but recommended to set

now — e.g. "Soil pH per ISO 10390" (the method you identified in step 1).

The system automatically "pins" the current Standard Operating Procedure

(SOP) version onto the sample, so that if the SOP evolves later, the

version in force at intake is retained.

Sampled at (collectedAt, *): when the sample was actually taken

in the field. If you do not know the exact time, use 09:00 of the

relevant day. The field requires date and time (microsecond

precision, so simultaneous samples are distinguishable).

Condition on Arrival (conditionOnArrival, *): pick OK for

a sample that arrived in pristine condition. If the seal was broken,

the quantity was insufficient, or the sample was not properly

preserved, pick the matching value (Damaged, **Insufficient

quantity, Unpreserved, Other**). For this tutorial assume

OK. (Picking anything else automatically reveals a mandatory

"Customer Consultation" section — see

record-customer-consultation-7.4.3.md if you need it.)

Crop (cropId): optional but recommended. E.g. "Olive".

Click Save.

When you finish this step, you should see: the new sample at the top of

the samples list with status Received and an auto-assigned code (e.g.

SAM-2026-00041).

Related clause: logging the sample code, owner, sampling time, and arrival

condition fulfils ISO/IEC 17025 §7.4.1 for unique identification and §7.4.3

for documenting receipt anomalies.

5. Create an analysis record

Goal: open an AnalysisRecord against the sample's aliquot, so measurement

entry can begin. Duration: ~1.5 minutes.

From the left navigation bar click Analyses (not from inside the

sample — it is a separate top-level section). The list of all the lab's

analysis records appears.

In the top-right toolbar click "+". A new page opens ("New Analysis").
Fill in:

Contact (contactId): pick the same customer you registered in

step 3. The Aliquot list right after it filters automatically to

that customer's available aliquots.

Aliquot (aliquotId, *): the system automatically creates one

aliquot ("Aliquot 1" or similar) for every new sample, so you will

usually see a single option here corresponding to the sample from

step 4. Pick it.

Sampling Date and Analysis Date: fill in the relevant dates

(the analysis date can be today).

Area (area, in the lab's own unit — Settings › Area Unit): e.g. 12.5.
Analysis Type (analysisTypeId, *): e.g. "Soil".
Simplified Report: leave unchecked for a full report.
Accreditation Scope (accreditationScopeId): optional. If left

blank, the report will be released as non-accredited. If you pick an

active scope, the final report will carry the accreditation mark

(per §5.3).

Click Save.

Important: the Lab Method is not selected again here — it was

already set on the sample itself, in step 4. The record's

sopVersionAtCreation is derived automatically from the sample's method the

moment you click Save here.

When you finish this step, you should see: a new row in the analyses

grid with status DRAFT. Click the row to enter the analysis record

detail page (/analyses/:id) — that is where you will finish the remaining

steps. The top-right of the page shows a coloured status chip — for DRAFT.

Related clause: binding to a specific LabMethod (on the sample) and

auto-logging the SOP version at analysis-record creation time fulfils

ISO/IEC 17025 §7.2.1.3 (verifiable traceability to the method actually

applied).

6. Enter measurements

Goal: record the actual numeric values measured at the bench for every

Element of the method. Duration: ~3 minutes.

On the analysis record detail page, at the bottom, you will see the

measurements grid. It has one row per Element included in the method

you picked. For example, a soil-pH method will show a row for **pH (1:5

H2O); a macronutrient method will show rows for N, P, K**,

Ca, Mg, S.

Click the Measurement field (measurement) on the first row. Type

the numeric value you measured at the bench, e.g. 6.8 for pH or 42.5

for nitrogen in mg/kg. Press Tab to move to the next row.

Repeat for every Element. You do not need to save per row — values are

auto-saved when you leave the cell.

For every value you enter, if there is a linked AcceptanceCriterion

in the accreditation scope or in the method, the app automatically

evaluates conformity:

Green indicator — value within limits (PASS).
Amber indicator — value in the uncertainty band (CONDITIONAL).
Red indicator — value out of limits (FAIL).

If you notice anything special (e.g. you used an alternative procedure

for one element), enter a brief comment in the Notes field of that

row.

Once all values are entered, confirm every row has a measurement (the

record cannot move past DRAFT with empty Element rows).

When you finish this step, you should see: a fully populated

measurements grid with numeric values in every row and conformity colour

indicators next to each value (where applicable). The record remains in

DRAFT status.

Related clause: the measurements grid is the technical record (technical

record) required by ISO/IEC 17025 §7.5.1 — legible, traceable, with

automatic comparison against acceptance limits where defined.

7. QC check + review

Goal: move the record from DRAFT to REVIEWED by passing an independent

check. Duration: ~2 minutes.

The principle in ISO/IEC 17025 is segregation of duties: the analyst

who entered the measurements cannot review the same record. There must be

a second certified user as reviewer (REVIEWER role).

On the analysis record detail page, in the top action bar, find the

Submit for review button. This action moves the record from DRAFT

to REVIEWED only when a second user runs it; if you run it as the

analyst, the system rejects with "self-review not allowed". This is

intentional.

Before clicking "Submit for review", confirm you have:

measurement values in every Element row;
selected the correct accreditation scope (if applicable);
filled any observations/recommendations you intend to include.

Ask your reviewer to sign in and open the same analysis record. On

their page they see the DRAFT status and a **Review and approve

review** button.

When the reviewer clicks that button, the system checks that they hold

the required review competency (competency guard) for the record's

method/instrument and, if it passes, moves the record to REVIEWED.

Note: the instrument-calibration and accreditation-scope checks do

not run at this step — they run later, at the final Approval

(step 8), when the lab director performs it. If they block there, see

handle-calibration-overdue.md.

If the competency check fails, you see an informative error message and

the transition is blocked. Ask the quality manager to record the

required authorisation.

When you finish this step, you should see: the record in REVIEWED

status. The Status log now shows two rows: who created the record and who

reviewed it, both with timestamps. Measurements remain technically editable

until final approval — the real lock kicks in at the next step.

Related clause: the DRAFT → REVIEWED transition with an independent

competency check satisfies ISO/IEC 17025 §7.7 (ensuring validity of results)

and §6.2 (personnel competence).

8. Approval and report release

Goal: approve the record and release the official PDF report to the

customer. Duration: ~2 minutes.

Final approval is reserved for users with the LAB_DIRECTOR role (or

any other role authorised to sign reports). If you are an ANALYST or

REVIEWER, your work is complete in the previous step — ask the lab

director to sign in and finish.

The lab director opens the record in REVIEWED status and finds the

Approve button in the action bar.

Before allowing the transition, the system automatically runs several

ISO 17025 checks, including:

Calibration guard: does the instrument used for measurement have

an active, non-overdue calibration? (If not, see

handle-calibration-overdue.md.)

Approval-competency guard: is the director authorised to approve

for the specific method/instrument?

Accreditation-scope guard: if an accreditation scope was picked,

is its status ACTIVE?

QC-conformity and instrument-maintenance checks.

For your first sample in a fresh test environment these checks usually

pass cleanly. If one blocks, an informative error message names the

specific issue.

Once the checks pass, the system performs the following in one atomic

transaction:

moves the record status to APPROVED — from this point the

measurements lock permanently; no edits are allowed without a formal

amendment process (§7.8.8);

auto-generates a report number (reportNumber) via the

auto-numbering system (e.g. RPT-2026-00007);

creates a new ReportVersion row — the immutable "snapshot" of

the released report. If an amendment is later needed (§7.8.8), a

new version is created and the old one is preserved as history;

emits a REPORT_READY event that triggers an email notification to

the customer (if the email template is configured).

The record page now exposes a Download PDF button ("Download report

PDF"). Click it.

A small loading spinner with a dark backdrop appears and the app

generates the PDF on the backend. In a few seconds your browser

auto-downloads the file (e.g. RPT-2026-00007.pdf).

Open the PDF. It should contain:

a header with the lab logo and contact details;
customer and sample details;
the measurements table with conformity indicators;
the accreditation mark (if a scope was chosen);
the lab director's signature/name and the approval timestamp;
a report number and version number (usually v1).

When you finish this step, you should see: the record in APPROVED

status, a PDF in your browser "Downloads" folder, and an outgoing email to

the customer with the report attached. The chain of responsibility is

complete: analyst → reviewer → lab director, each step timestamped and

named.

Related clause: releasing a named PDF report with a report number, a

version number, and the signature of a responsible person fulfils

ISO/IEC 17025 §7.8.1 (report content) and §7.8.2 (release identification).

9. What's next

Congratulations — you have completed your first full cycle in Agrometrisis.

In ~15 minutes you covered the entire flow from contact to signed PDF. Now

you can dive into specialised workflows.