ISO/IEC 17025 field guide

ISO/IEC 17025 calibration software: what auditors actually check.

An ISO/IEC 17025 assessment is not a tour of your software. An assessor samples actual work and checks whether the lab can reconstruct it, justify its methods, and show the evidence behind its results. This guide maps common samples to clauses in ISO/IEC 17025:2017 and separates what CaliberOS can support today from what belongs in your lab’s controlled process.

Clause 6.4: equipment records and calibration intervals

An assessor may pick an instrument off the bench and ask for its identity, location, calibration status, and the basis for its interval. Clause 6.4.7 calls for a calibration programme that is reviewed and adjusted as necessary, and 6.4.13 addresses equipment records where relevant. An interval should reflect the equipment’s use, stability, risk, and constraints; the standard does not prescribe one universal annual schedule.

CaliberOS records asset tags, serial numbers, locations, interval lengths, and next due dates. The asset log captures changes to those values. The software does not set or approve intervals for you. Keep the rationale, review and authorization, service evidence, and restrictions on use in your controlled records.

Clause 6.5: metrological traceability

A traceable result has a documented, unbroken chain of calibrations to an appropriate reference, with each step contributing to uncertainty. For one reported result, identify the reference standard, retrieve the calibration certificate in effect at the time, and check that its range and uncertainty support the work. The fact that a reference was in date is not enough if it was unsuitable for the measurement.

Use the CaliberOS register to identify equipment and references by tag or serial number. It does not currently build or verify metrological traceability chains. Keep provider certificates, applicable scope, and relationships between results and references in your controlled system. ILAC P10 provides policy context for evaluating acceptable traceability routes.

Clause 7.5: technical records and amendments

Ask a second technician to reconstruct one calibration without help from the original operator. They should find the observations and calculations, dates, the people responsible for work and checking results, and the conditions or methods needed to understand what happened. When a value is corrected, a reviewer should be able to trace the change to the original rather than seeing only the final number.

CaliberOS keeps before-and-after values, actor, and time for asset-record changes in a hash-chained log. This is not the technical record of a calibration. Measurement events, original readings, and amendments to those readings are not stored by the current asset workflow. Keep them under your lab’s technical-record controls.

Clause 7.6: evaluation of measurement uncertainty

For a calibration, an assessor may ask you to explain the uncertainty budget behind a reported result. Show the contributors relevant to the method, such as the reference standard’s uncertainty, repeatability, resolution, and environmental effects. Keep the budget and its assumptions under review as equipment, conditions, or methods change. Do not infer uncertainty from the interval or from a pass indicator.

CaliberOS does not calculate uncertainty or maintain uncertainty budgets today. Use your validated methods and calculation tools, and retain the evidence alongside each applicable result. The register supports identification of equipment and references; suitability and uncertainty remain the responsibility of your lab.

Clause 7.8.4: calibration certificates

Check the issued certificate against the technical record. Calibration reporting under 7.8.4 includes, as applicable, measurement uncertainty, influential conditions, a statement on metrological traceability, and results before and after adjustment or repair if available. Do not put an interval recommendation on a certificate or label unless it has been agreed with the customer, as addressed in 7.8.4.3.

CaliberOS certificate generation is planned and not available today. Continue using your approved templates and release workflow. Before considering a change, test a revised certificate, an instrument that needed adjustment, and a result with a special reporting requirement. The new process must preserve both the final report and the evidence used to issue it.

References: ISO/IEC 17025:2017 standard overview · ILAC policies on traceability and uncertainty (P10 and P14) · ILAC G24 / OIML D 10 recalibration interval guidance · Perry Johnson Laboratory Accreditation assessment checklist.

FAQ

Frequently asked questions

Can software give my lab ISO/IEC 17025 accreditation?

No. Accreditation applies to your lab and its scope of activities. Software can help maintain evidence but does not replace competent personnel, controlled procedures, or assessment.

Does ISO/IEC 17025 require annual calibration?

There is no universal annual interval. Maintain and review a calibration programme, and justify intervals based on your equipment, use, performance, risk, and applicable constraints.

Does CaliberOS calculate measurement uncertainty?

No. Keep your validated uncertainty budgets, methods, and calculations in your controlled system.

Which evidence can I organize in CaliberOS today?

You can organize asset identifiers, locations, intervals, and due dates and track changes to those fields. Technical calibration records, linked traceability evidence, and certificate issuance are not part of the current asset workflow.

Start with a sample register.

Test whether a colleague can find the right instrument and schedule without leaving your controlled records behind.

Join the waitlist