What ISO/IEC 17025 asks of lab software
ISO/IEC 17025:2017 does not certify software. An accreditation body assesses the laboratory, and the assessor looks at whether the lab's records can be trusted. When those records live in a LIMS, a handful of clauses become questions about the software. This page lists them, says what an assessor typically checks under each, and shows where Agrometrisis answers it.
The assessor wants to know that data cannot change without a trace, that only authorised people can change it, and that it survives a failure.
- Every change is recorded. Each create, update and delete is written to the Audit Trail in the same transaction as the change itself: if the audit row cannot be written, the change does not happen. A second, independent layer of database triggers records the old and new values of every table in the Database Audit. Neither log can be edited from the application.
- Who opened what. The Record Access Log shows who opened which sample, analysis or contact, and when. The Login Log records every sign-in attempt, successful or not.
- Access by role. What each role may do is set in Role Permissions, and the server checks it on every request, not only the screen.
- Two timestamps. A sample collected in the field carries both the time of collection and the time it was recorded in the LIMS, side by side (see Why every sample carries two timestamps).
- Backups. Automatic Backup copies the lab's database on a schedule to an off-site target (Google Drive, FTP or Dropbox).
- Two-factor sign-in. Mandatory MFA for all users sends every user to set up an authenticator app before they can work.
§7.5 Technical records
The assessor checks that original observations are kept and that later changes are visible and justified.
- Late entries need a reason. An event dated more than 7 days back (a sample receipt, an analysis, a calibration, a training record and others) cannot be saved without a Reason for the late entry, which is kept with the change (see Why a late entry asks for a reason).
- Amend, not edit. Once an analysis is reviewed or approved its measurements are locked. Changing them takes an Amend by the Lab Director with an Amendment Reason, and every changed value carries that reason in the audit trail, with its value Before and After (see Why amend, not edit).
§8.4 Control of records
The assessor asks how long records are kept, who decides when they go, and whether anything can be lost by mistake.
- Retention Policies set, per record type, whether records are archived, destroyed, anonymised or kept indefinitely. Nothing runs on its own: the system proposes a batch, and it executes only once a person authorises it, optionally with a second signer (Dual authorisation of records disposition).
- Legal Holds are checked again at the moment a batch runs, and held records are skipped. Every executed batch is listed in the Disposition Log.
- The lab can export all of its data at any time.
§6.4 and §6.5 Equipment and metrological traceability
The assessor picks a result and asks: was the instrument calibrated when this was measured?
- Calibration on the analysis date. Approval checks that every instrument used had a calibration in force on the day of the analysis, not today. If it did not, approval stops until the gap is fixed or a documented override (with a written reason) is recorded.
- Fit for use. A calibration is judged fit when the as-found error plus its uncertainty stays within the tolerance.
- Expired lots. Using an expired reagent or reference-material lot asks for a Reason for using an expired lot, kept in the audit trail.
§7.8 Reporting of results
The assessor checks that issued reports cannot drift, that changes produce a new version, and that conformity statements follow a stated rule.
- Frozen versions. Approval freezes the report. A change after approval issues a new version (v2, v3…), the Report history keeps every one, and Print frozen version reproduces exactly what the customer received.
- Decision rules. Each Acceptance Criteria entry carries its Decision Rule (simple acceptance, guard bands, ILAC G8, customer-specified). Conformity is computed on the server, and an indeterminate result stops approval unless overridden with a reason (see Why decision rules and conformity statements).
- Separation of duties. The reviewer cannot be the analyst, and the approver cannot be the reviewer. With E-signature on analysis approval turned on, the approver re-enters their password, and the report prints the approver's name and job title.
§6.2 Personnel
The assessor asks whether the person who did the work was competent for it at that time.
- User Competencies record each person's status per method (in training, supervised, authorised, suspended, expired). At review and approval the system checks that the analyst held an authorised competence on the analysis date, wherever the lab has set a Competency Requirement for that method.
- Training Records, Supervised Practice and Competency Monitoring keep the history behind each authorisation.
What the software does not do for you
Software can make records trustworthy and easy to retrieve. It cannot write your quality manual, choose your methods or validate them, or decide your scope: those remain the laboratory's work, and accreditation is granted to the laboratory. For how to pull the evidence together before a visit, see Preparing for an accreditation assessment.
You can see each of these screens in the live demo, with no sign-up, or try them on your own data with the 30-day free trial.