ISO 17025 Software: A UK Buyer's Guide for Accredited Calibration Labs

If you run a UK calibration laboratory — or an internal calibration function inside a manufacturer — the software question is not "which tool is ISO 17025 certified." No software is. ISO/IEC 17025 accredits laboratories for technical competence; it does not certify products. The real question is narrower and more useful: which features does a tool need so that your laboratory can demonstrate compliance against the clauses an assessor actually checks?

This guide maps the buying decision onto the standard. It covers what ISO 17025 software is, the clauses the tool has to support, how calibration software differs from a full LIMS, and a checklist you can walk a vendor through in half an hour. It is criteria-based — no product league tables — because the right tool depends on your scope, your instrument count, and whether you are accredited or working toward ISO 9001 traceability.

For the clause-by-clause detail of the standard itself, the companion guide to the full ISO/IEC 17025 requirements walks every section. This post stays on the software decision.

What "ISO 17025 Software" Actually Means

There is a persistent search for "ISO 17025 certified software," and it is worth clearing up first. ISO/IEC 17025:2017 — General requirements for the competence of testing and calibration laboratories is the third edition, published in 2017, and it sets requirements for laboratories. The accreditation that demonstrates a laboratory meets it is granted in the UK by the United Kingdom Accreditation Service (UKAS), which describes itself as "the national accreditation body for the United Kingdom, appointed by government, to assess organisations that provide certification, testing, inspection and calibration services." UKAS holds that role by statute — the Accreditation Regulations 2009 state that "UKAS is appointed for the purposes of Article 4(1) of the EC Regulation as the national accreditation body."

What none of that does is certify a piece of software. So "ISO 17025 software" is shorthand for a tool that helps a laboratory satisfy the standard's requirements. A useful tool maps onto the clauses that govern calibration work day to day:

• §6.4 Equipment and §6.5 Metrological traceability — the equipment register and its traceability chain
• §7.6 Evaluation of measurement uncertainty — uncertainty captured against each result
• §7.8 Reporting of results — calibration certificates that carry the required fields
• §7.11 Control of data and information management — the data integrity and system-validation requirement that applies directly to the software itself

The rest of this guide is organised around supporting those clauses.

The Clauses Your Software Has to Support

Traceability and the Equipment Register (§6.4, §6.5)

ISO/IEC 17025:2017 §6.5 requires the laboratory to establish and maintain metrological traceability of its measurement results through a documented unbroken chain of calibrations, each contributing to the measurement uncertainty, back to an appropriate reference — in UK practice, the National Physical Laboratory directly or via a UKAS-accredited calibration laboratory. The ISO/IEC 17025 requirements guide covers the §6.5 wording and the supporting UKAS traceability policy in full.

For the software, that translates into a concrete requirement: every instrument record must hold its reference-standard lineage, not just its latest certificate. The tool should let you record which reference standard was used for each calibration, link to that reference's own certificate, and show the chain when an assessor asks. A flat certificate library that cannot express "this gauge was calibrated against that reference, which holds this UKAS certificate" is not supporting §6.5 — it is storing PDFs.

This is the same equipment-register backbone that underpins general calibration management software; for an accredited lab the difference is that the traceability chain is mandatory and assessed, not optional.

Measurement Uncertainty (§7.6)

ISO/IEC 17025:2017 §7.6 requires the laboratory to evaluate measurement uncertainty for every calibration. In the UK the method is set out in UKAS publication M3003, and the certificate states the expanded uncertainty with its coverage factor. Software supporting §7.6 should let you record the uncertainty against each result rather than treating the certificate as an opaque attachment, and ideally surface a calibration where the uncertainty is missing before it enters the audit-ready set.

If your supplier did not state expanded uncertainty in the form your customer expects, the free Measurement Uncertainty Calculator covers Type A and Type B contributions per the GUM. The deeper treatment is in the measurement uncertainty guide.

Reporting of Results (§7.8)

ISO/IEC 17025:2017 §7.8 sets out what a calibration certificate must contain: laboratory and customer identification, a unique certificate number, the calibration date, item identification, the calibration method, results with measurement uncertainty, environmental conditions where they affect results, a statement of how the results are metrologically traceable, and the authorising signature. The tool should validate a certificate against this field set rather than accept whatever PDF is uploaded.

You can test a single certificate against the §7.8 field set in the browser with the free Calibration Certificate Completeness Checker — no upload, no signup. For the certificate workflow specifically, see the calibration certificate software guide.

Control of Data and Information Management (§7.11)

This is the clause that applies most directly to the software itself. As the ISO/IEC 17025 requirements guide sets out, §7.11 requires that laboratory information management systems are validated for fitness for use, protected from unauthorised access, safeguarded against tampering and loss, and maintained so the integrity of the data is preserved, with records of system failures and the corrective actions taken.

For a buyer that means asking concrete questions of any tool:

• System validation — can you record that the system, as configured, produces correct outputs? You do not re-validate a vendor's code for unmodified commercial software, but you must validate your own use of it.
• Access control — are there real user roles, so a production operator with read access cannot alter a calibration record?
• Tamper-resistance and audit trail — does every change to a record carry who, when, and what, so the data cannot be quietly edited?
• Backup and loss prevention — is the data backed up, and can you get it out?
• Integrity on calculation and transfer — where the tool calculates or moves data, can you confirm the result is correct?

A spreadsheet on a shared drive struggles with every one of these. That difficulty is the practical reason most accredited labs eventually move to dedicated software — not the calibration arithmetic, which a spreadsheet handles, but the §7.11 data-control burden, which it does not.

Calibration Software vs LIMS — Which Fits a Calibration Lab

A laboratory information management system manages an entire testing workflow across many test types: sample login, allocation, results, and reporting. Calibration software is narrower — instruments, certificates, intervals, traceability, and uncertainty.

For a calibration-only laboratory, or an in-house quality team managing a fleet of measuring equipment, the broad LIMS is usually more than the workflow needs and more than the budget wants. A focused calibration tool covers the calibration clauses directly without the sample-management apparatus. The clause-7.11 data-control requirement applies either way, so that is not the deciding factor; scope and cost are. If your laboratory's accredited activity is genuinely multi-disciplinary testing, a LIMS may be right. If it is calibration, a calibration tool usually fits better.

The Buyer Checklist

Walk a real instrument and a real certificate through any tool before committing:

1. Can you record an instrument's reference-standard lineage — not just its latest certificate — so the §6.5 traceability chain is visible on one screen?
2. Does the tool capture measurement uncertainty against each result, and flag a certificate that is missing it?
3. Does it validate a certificate against the §7.8 field set on upload, rather than accepting any PDF?
4. Are there genuine user roles, an audit trail on every record change, and a backup-and-export path that satisfies §7.11?
5. Can you produce the full history of one instrument — every certificate, calibration date, due date, out-of-tolerance event — in a single screen for an assessor?
6. Does recalibration scheduling send reminders before the due date, so a lapsed calibration is caught before the assessment, not during it?
7. Is the pricing in GBP, on a flat monthly basis, without a per-user surcharge for read-only colleagues — and is support async within a UK business day?

If a vendor cannot show items 1 through 5 in a thirty-minute walk-through, the tool is not built for an ISO/IEC 17025 workflow, whatever the marketing says.

A Note on "Best Calibration Software"

Buyers reasonably search for the best calibration software, the best cloud calibration software, the best gauge calibration software, and so on. The honest answer is that "best" depends entirely on your scope and instrument count — a dimensional-only lab on a UKAS schedule has different needs from a manufacturer running mixed in-house and supplier-side calibration. Rather than ranking products, work the checklist above against the clauses your assessment is judged on. A tool that supports §6.5, §7.6, §7.8, and §7.11 cleanly, in GBP, at SME scale, is the best calibration software for you — and that is the only sense in which the question has an answer.

How CalProof Fits

CalProof was built for UK calibration teams managing 20 to 500 instruments under ISO 9001 or ISO/IEC 17025. Every instrument record holds its reference-standard lineage and traceability chain; every certificate is checked against the ISO/IEC 17025 §7.8 field set on upload; user roles and a full audit trail support the §7.11 data-control requirement; recalibration reminders fire before due dates; and the whole record set exports as CSV plus the underlying PDFs, so there is no vendor lock-in on your compliance evidence.

GBP pricing from £29 a month. No per-user fees on Pro and above. UK data hosting. No long-term contract.

To see the output before signing up, the sample audit pack is ungated and downloads as a single PDF — the same shape CalProof produces for surveillance and customer audits.

Sources

• ISO/IEC 17025:2017 — General requirements for the competence of testing and calibration laboratories
• ISO 9001:2015 — Quality management systems — Requirements
• UKAS — About the United Kingdom Accreditation Service
• The Accreditation Regulations 2009 — Regulation 3 (Appointment of UKAS)
• NPL — UK National Metrology Institute

This guide applies to UK calibration laboratories and in-house calibration functions. ISO/IEC 17025 requirements are assessed by UKAS against your laboratory's specific scope; software supports compliance but does not confer it. This is not legal or compliance advice — consult your accreditation body or assessor for the requirements specific to your accredited activity.