What does ISO/IEC 17020 require for in-service checks?

Where relevant, equipment is checked between regular calibrations. ILAC P15 asks the inspection body to define what the checks are, how often they run and what counts as acceptable. The UKAS gap analysis maps this requirement from clause 6.2.9 to clause 6.2.6 in the 2026 edition.

What changed for equipment in ISO/IEC 17020:2026?

UKAS rates metrological traceability (clause 6.2.7) and technology requirements (clause 6.2.9) as major changes, and it lists new clauses on equipment records of use (7.4.3) and data systems (7.5.1 and 7.5.2). Defective equipment and equipment records are rated no change. The transition ends in March 2029.

Can an inspection body use commercial software under ISO/IEC 17020:2026?

Yes. NATA's application document for the 2026 edition says commercial off-the-shelf software may be considered pre-validated when it is used within its specified application range. Software changes and configuration amendments still need change control and validation before implementation.

Does Axiospec record in-service checks?

Not as a separate record type. Keep your in-service check log in your quality system. You can attach the check procedure to the instrument as its SOP, and a file to any calibration record.

Can a small inspection body use Axiospec?

Yes. The free plan covers up to 50 active instruments with unlimited users, and a new workspace starts with 45 days on Professional for up to 1,500 active instruments. Accreditation is decided by your accreditation body. Axiospec keeps the calibration records and does not certify conformance.

Does Axiospec force technicians to fill in every required field?

Yes, by default. When you select a standard, the fields that standard requires are marked on the calibration form and the save is blocked until they are filled. Enforcement is on for every workspace unless an admin turns it off in Settings. There is one deliberate exception. A brand new workspace is not held to the standard fields until it has logged its first calibration, so a first run is never trapped behind a form it cannot save. Full strictness applies from the second calibration onward. The public REST API enforces the same requirements on write.

For inspection bodies

ISO/IEC 17020 calibration requirements under clause 6.2

ISO/IEC 17020 clause 6.2 requires an inspection body to define the equipment that significantly influences inspection results, calibrate it under an established program, keep measurements traceable and deal with defective equipment. ISO/IEC 17020:2026 replaced the 2012 edition in March 2026 and moved some of those clauses, so the checklist below gives both sets of numbers from the UKAS gap analysis. Axiospec gives inspection bodies one register to identify each instrument and capture its calibration against traceable standards.

Create your account

ISO/IEC 17020 clause 6.2 calibration checklist

6.2.4 (2012: 6.2.4, 6.2.6): Equipment that influences results

Define the equipment with a significant influence on inspection results and identify it uniquely where appropriate. Calibrate measuring equipment of this kind before it enters service and then under an established program. ILAC P15 asks for a recorded justification when such equipment is not calibrated.

6.2.6 (2012: 6.2.9): In-service checks

Where relevant, check equipment between regular calibrations. ILAC P15 asks the inspection body to define the nature of the checks, how often they run and the acceptance criteria.

6.2.7 (2012: 6.2.7, 6.2.8, 6.2.10): Metrological traceability

Keep measurements traceable to national or international standards of measurement where these are available, and keep evidence of correlation or accuracy where traceability does not apply. The 2026 edition gathers reference standards and reference materials into this clause, and UKAS rates the change as major.

6.2.9 (2012: 6.2.13): Technology used in inspections

Inspection technology has to be suitable and adequate, with data integrity and security procedures and maintained hardware and software. NATA applies this to computers, automated equipment, data processing, AI, augmented reality and remote inspection techniques.

6.2.10 (2012: 6.2.14): Defective equipment

Have documented procedures for defective equipment. Take it out of service by segregating or clearly marking it, and look at what the defect means for earlier inspections before deciding on corrective action.

6.2.11 (2012: 6.2.15): Equipment records

Record relevant information on the equipment, including software. That normally means its identification and, where appropriate, calibration and maintenance details.

7.4.3 (new in 2026): Equipment records of use

UKAS lists equipment records of use as a new clause. ILAC P15 already advised that inspection records should show which item of equipment with a significant influence was used for each inspection activity.

7.5.1 and 7.5.2 (new in 2026): Data systems

UKAS lists validation of data systems and safeguarding of data as new clauses. NATA expects information management systems to be validated for their intended purpose, with changes to software or configuration under change control.

ISO/IEC 17020:2026: what changes for equipment

ISO/IEC 17020:2026 was published in March 2026 and replaces the 2012 edition. UKAS and INAB, the Irish accreditation body, both describe a three-year transition, with the final deadline in March 2029.

Equipment control stays in clause 6.2, but the numbering changes. In the UKAS gap analysis, the calibration requirement moves into 6.2.4 with a minor change and in-service checks move from 6.2.9 to 6.2.6. Three former clauses combine in 6.2.7, Metrological traceability, with a major change. The software clause becomes 6.2.9, Technology requirements, also rated major. Defective equipment and equipment records are rated no change at 6.2.10 and 6.2.11.

The requirement text in the checklist above follows the public sources we could check, mainly for the 2012 edition. Read the 2026 text of clauses 6.2.4, 6.2.6, 6.2.7 and 6.2.9 during your gap analysis, then update any procedure that cites the old numbers.

How Axiospec helps ISO/IEC 17020 teams

Every instrument identified and controlled

Keep one live register of the inspection equipment with its status, interval and history, so the equipment that influences results is identified in one place.

Traceable calibration on the asset

Record the reference standard and certificate behind each calibration so traceability to measurement standards is visible on the instrument.

Calibrations on either side of your in-service checks

Axiospec has no separate record type for in-service checks, so keep your check log in your quality system and attach the check procedure to the instrument as its SOP. Log the calibrations on either side of those checks from any web browser, or from the mobile app while offline in the field.

Audit-ready records in one click

Calibrations are written to a tamper-evident ledger with attribution and timestamps, then exported as a complete pack for any instrument.

Out-of-tolerance results ask for an impact

An accepted Fail or Damaged quarantines the instrument, and the record asks for the impact to be written. A Pass with as-found readings out of tolerance needs an impact too, and unrecorded ones show in Needs attention.

Calibration software for ISO/IEC 17020 clause 6.2

ISO/IEC 17020 expects an inspection body to know which equipment influences its results, calibrate it under an established program, keep measurements traceable and deal with defective equipment. The standard names no software. The practical question is which system holds the equipment register and calibration history so that an assessor can follow them.

In Axiospec each instrument has an identifier, an interval and a live status: in tolerance, due, overdue, or quarantined. Calibrations are logged with as-found and as-left readings, the reference standard and its certificate, then written to a tamper-evident ledger. With ISO/IEC 17020 selected, the form requires the reference standard, certificate and tolerance. A Due Calendar shows what is due and overdue, with reminders before each date, and each calibration can be exported as part of an audit pack. A manager can set an instrument Out of Service, which is a separate status from quarantine.

Axiospec is not an inspection management system. It does not hold inspection reports, in-service check logs or the validation of your other data systems. The free plan covers up to 50 active instruments, and we load existing records at no charge on every plan. Axiospec keeps the equipment records; it does not certify or guarantee conformance, which your accreditation body decides.

ISO/IEC 17020 calibration: common questions

Does ISO/IEC 17020 require calibration?

Yes, for measuring equipment with a significant influence on inspection results. It is calibrated before it enters service and then under an established program. ILAC P15 asks that any decision not to calibrate such equipment is justified and recorded.
What does ISO/IEC 17020 require for in-service checks?

Where relevant, equipment is checked between regular calibrations. ILAC P15 asks the inspection body to define what the checks are, how often they run and what counts as acceptable. The UKAS gap analysis maps this requirement from clause 6.2.9 to clause 6.2.6 in the 2026 edition.
What changed for equipment in ISO/IEC 17020:2026?

UKAS rates metrological traceability (clause 6.2.7) and technology requirements (clause 6.2.9) as major changes, and it lists new clauses on equipment records of use (7.4.3) and data systems (7.5.1 and 7.5.2). Defective equipment and equipment records are rated no change. The transition ends in March 2029.
Can an inspection body use commercial software under ISO/IEC 17020:2026?

Yes. NATA's application document for the 2026 edition says commercial off-the-shelf software may be considered pre-validated when it is used within its specified application range. Software changes and configuration amendments still need change control and validation before implementation.
Does Axiospec record in-service checks?

Not as a separate record type. Keep your in-service check log in your quality system. You can attach the check procedure to the instrument as its SOP, and a file to any calibration record.
Can a small inspection body use Axiospec?

Yes. The free plan covers up to 50 active instruments with unlimited users, and a new workspace starts with 45 days on Professional for up to 1,500 active instruments. Accreditation is decided by your accreditation body. Axiospec keeps the calibration records and does not certify conformance.
Does Axiospec force technicians to fill in every required field?

Yes, by default. When you select a standard, the fields that standard requires are marked on the calibration form and the save is blocked until they are filled. Enforcement is on for every workspace unless an admin turns it off in Settings. There is one deliberate exception. A brand new workspace is not held to the standard fields until it has logged its first calibration, so a first run is never trapped behind a form it cannot save. Full strictness applies from the second calibration onward. The public REST API enforces the same requirements on write.

Axiospec is a documentation and workflow tool. It helps you produce clean, traceable records that support ISO/IEC 17020 compliance; certification depends on your own processes, scope, and assessor.

See it on your own equipment

Create a free account and switch on ISO/IEC 17020 fields in minutes. No credit card.

Got a gage list? Send it over and we load it for you, usually in a couple of business days. Free on every plan.