Calibration lab management software for 2027: what is changing and what to look for

1. Customers will expect to find their own certificates

The most common request a laboratory answers is a copy of a certificate it has already sent, usually the night before somebody else's audit. Email attachments get lost, change hands and arrive without their amendments. The direction is towards a customer portal: each customer signs in and sees its own instruments, due dates, certificates and reports, work in progress, quotes and invoices.

What to look for: a portal under your laboratory's name rather than the vendor's; sign-in without passwords to manage; each customer limited to its own company by the system, not by a filter on a screen; and no charge per customer login, because a laboratory may have hundreds. CalibraWorks has all four, on every plan, and lets you switch each portal section on or off. See the customer portal.

2. Every document will need to prove itself

A PDF can be edited, and a certificate passed from a contractor to a principal to a site office has had three chances to be. Increasingly the person relying on a certificate is not the customer who received it, and needs to check it without phoning anybody.

What to look for: a QR code on the certificate and the label that opens a public page with no login; a code that is random rather than a sequence anybody could count through; a clear answer when a certificate has been amended or withdrawn, not merely when it is valid; and verification that keeps working whether or not the laboratory's subscription is current. CalibraWorks uses a 12-character random code, shows superseded and withdrawn certificates as such, checks the laboratory's digital signature where it signs, and never switches verification off. How verification works.

Machine-readable certificates are a related thread. International work on a Digital Calibration Certificate, led by Germany's PTB, aims at certificates a customer's system can read directly. Ask any vendor what it plans; CalibraWorks does not produce those files today.

3. Inspection and calibration under one roof

Many Australian calibration businesses also test and tag, inspect lifting gear or check medical equipment, and many test-and-tag businesses are adding calibration. Two systems mean two customer lists, two schedules and two invoices for the same customer.

What to look for: one customer register, schedule and invoice, with the two documents kept strictly apart. A calibration certificate states what an instrument reads against a reference, with uncertainty, under ISO/IEC 17025 §7.8. An inspection report to AS/NZS 3760:2022 states that an item met the standard's criteria, and carries no grade, no uncertainty and never an accreditation mark. In CalibraWorks the document follows the item, both kinds can sit on one job, and there is no module fee for doing both.

4. Clear answers on where data is held

Tenders and supplier questionnaires ask where records are held more often than they used to, and a vague answer costs work. The honest answer has two parts: where the records live, and what leaves the country.

What to look for: a named region for the database, the files and the application; a list of every sub-processor and its location; and a privacy policy that matches it. CalibraWorks holds records, files and the application in Sydney, and names its exceptions — Hostinger and Stripe — on the security page.

5. Connections to the customer's own systems

Larger customers run asset systems and ERPs of their own, and would rather read due dates and certificates from the laboratory than re-key them. The safe pattern is read-only access with keys the laboratory issues, scopes and revokes, so nothing reaches a certificate except through the laboratory's own screens.

What to look for: a documented API, keys per integration, read-only by design, and the ability to export everything as plain files regardless. CalibraWorks has a read-only REST API with a public OpenAPI description, and exports every record as CSV at any time.

6. Intervals justified by history

Fixed intervals are easy to administer and hard to defend in both directions: an instrument that drifts steadily may be failing between calibrations, and one that has been stable for years may be costing its owner a calibration it does not need. ILAC-G24 describes methods for reviewing intervals, and ISO/IEC 17025 §7.8.4.3 limits what a certificate may recommend without the customer's agreement.

What to look for: analysis from each instrument's own calibration history, a recommendation with its reasoning, and no change made without a person deciding. CalibraWorks shows which instruments are drifting, unstable or stable once they have enough calibrations on record, and recommends shorter or longer intervals for a person to weigh.

What does not change

The standard. Uncertainty on every result, traceability to calibrated references, competent and authorised signatories, a declared decision rule wherever pass or fail is stated, immutable records and a working quality system are what assessments test, and they are the floor any new capability sits on. A language model may help with paperwork — CalibraWorks uses one only to propose things a person accepts or rejects — but no model should compute a result, set an uncertainty or decide a pass or fail. Ask every vendor where that line is.

How to plan for it

• List what your customers ask you for most often, and check which of it they could find themselves.
• Check that every certificate you issue can be verified by somebody you have never met.
• If you do inspection as well as calibration, count how many systems hold each customer.
• Write down where your records are held and what leaves Australia, before a tender asks.
• Ask your largest customers whether they would read your records from their own systems.
• Pick ten instruments with long histories and ask whether their intervals are still right.

For the full list of requirements to hold a system to today, read the 2026 buyer's guide, and for what each CalibraWorks plan includes, the feature comparison.