---
title: MDR Monitoring and Measuring Equipment: ISO 13485 7.6
description: How EN ISO 13485 clause 7.6 governs calibration, traceability, and software validation for monitoring and measuring equipment under MDR.
authors: Tibor Zechmeister, Felix Lenhard
category: Quality Management Under MDR
primary_keyword: monitoring measuring equipment MDR ISO 13485
canonical_url: https://zechmeister-solutions.com/en/blog/monitoring-measuring-equipment-control
source: zechmeister-solutions.com
license: All rights reserved. Content may be cited with attribution and a link to the canonical URL.
---

# MDR Monitoring and Measuring Equipment: ISO 13485 7.6

*By Tibor Zechmeister (EU MDR Expert, Notified Body Lead Auditor) and Felix Lenhard.*

> **EN ISO 13485:2016+A11:2021 clause 7.6 requires manufacturers to identify, calibrate, protect, and verify monitoring and measuring equipment whose results are used to demonstrate device conformity. Calibrations must be traceable to international or national measurement standards, software used in measurement must be validated, and out-of-tolerance results must trigger a documented impact assessment on devices already released.**

**By Tibor Zechmeister and Felix Lenhard.**

## TL;DR
- Clause 7.6 of EN ISO 13485:2016+A11:2021 governs monitoring and measuring equipment used to demonstrate product conformity.
- Every such instrument must be calibrated or verified against measurement standards traceable to international or national standards, or the basis used must be recorded.
- Calibration records, due dates, and status identification are required for every covered instrument.
- An out-of-tolerance finding requires a documented assessment of impact on previously released product.
- Software used to monitor or measure must be validated before first use and after changes.
- For a startup, a single calibration register, clear status labels, and an honest out-of-tolerance procedure cover almost all of clause 7.6.

## Why this matters

A caliper on a workbench is easy to ignore until it is wrong. If the caliper drifts by 0.1 mm and the engineer uses it to confirm that a machined part meets the drawing tolerance, every part released based on that caliper is suspect. If the part was a component in a Class IIa device, every finished device containing that part is suspect. Clause 7.6 exists so that this question never becomes a mystery.

Notified body auditors love clause 7.6 because it is binary. Either the instrument has a valid calibration certificate and a status label, or it does not. Either your software is validated, or it is not. Either your out-of-tolerance procedure captures impact assessment, or it is just a checkbox. This is one of the easiest places to get clean findings and one of the easiest places to collect avoidable non-conformities.

This post walks through clause 7.6, shows what "traceable to international standards" actually means in practice, covers software validation under 7.6 for test rigs and data acquisition, and closes with a lean calibration program a small team can actually run.

## What MDR actually says

**MDR Annex IX** requires the notified body, as part of the QMS audit, to assess whether the manufacturer's system ensures that the devices manufactured conform to the documentation and requirements applicable to them. Measurement and inspection evidence is central to that assessment. The MDR does not specify calibration in its own articles — instead, it relies on the harmonised QMS standard (EN ISO 13485:2016+A11:2021) to operationalise the requirement.

**EN ISO 13485:2016+A11:2021 clause 7.6 Control of monitoring and measuring equipment.** The standard requires the organisation to determine the monitoring and measurement to be undertaken, and the monitoring and measuring equipment needed to provide evidence of conformity of product to determined requirements. The organisation shall establish documented procedures to ensure that monitoring and measurement can be carried out and are carried out in a manner that is consistent with the monitoring and measurement requirements.

Where necessary to ensure valid results, measuring equipment shall be:

- calibrated or verified, or both, at specified intervals, or prior to use, against measurement standards traceable to international or national measurement standards; where no such standards exist, the basis used for calibration or verification shall be recorded;
- adjusted or re-adjusted as necessary, such adjustments being the subject of records;
- identified in order to determine its calibration status;
- safeguarded from adjustments that would invalidate the measurement result;
- protected from damage and deterioration during handling, maintenance, and storage.

The organisation shall perform calibration or verification in accordance with documented procedures.

When equipment is found to be out of conformity with requirements, the organisation shall assess and record the validity of the previous measuring results. The organisation shall take appropriate action on the equipment and any product affected.

Records of the results of calibration and verification shall be maintained.

The organisation shall validate the application of computer software used in the monitoring and measurement of requirements. Such software shall be validated prior to initial use and, as appropriate, after changes to such software or its application. The specific approach and activities associated with software validation and revalidation shall be proportionate to the risk associated with the use of the software. Records of such activities shall be maintained.

Plain-language translation: if the number it gives you ends up in a batch record, a verification report, or a release decision, the instrument is covered by 7.6. Calibrate it. Label it. Validate any software that reads or processes the signal. When it drifts, figure out which devices were affected by the drift.

## A worked example

A five-person startup is finalising production of a Class IIa electromechanical therapy device. The production and test workflow uses the following measurement equipment:

1. Digital calipers (2 units) — dimensional inspection of incoming machined parts.
2. A calibrated torque screwdriver — enclosure assembly.
3. A programmable DC power supply — functional test.
4. A bench digital multimeter — electrical safety preliminary checks.
5. A custom LabVIEW-based test rig — automated functional test, records pass/fail per unit and logs raw measurements.
6. A temperature and humidity logger — storage area monitoring.

Here is what the calibration program looks like:

**Register.** One spreadsheet: equipment ID, description, location, calibration interval, last calibration date, next calibration date, calibration certificate reference, status, responsible person. That is it. Seven columns.

**Calibration sources.** Calipers, torque screwdriver, power supply, and multimeter are sent annually to an accredited calibration laboratory whose certificates reference national measurement standards. Certificates are scanned into the register folder.

**Status labels.** Each physical instrument has a small sticker with its ID, last calibration date, and next calibration due. Anyone on the shop floor can see at a glance whether the instrument is in date.

**Test rig.** The LabVIEW software is validated per clause 7.6's software validation requirement. The validation protocol covers requirements, installation qualification, operational qualification, and performance qualification against known inputs. Validation was done before first production use and is repeated after any software change. The underlying DAQ card inside the test rig is calibrated annually against national standards.

**Out-of-tolerance handling.** When the annual calibration of one of the calipers comes back with a 0.08 mm drift beyond acceptable tolerance, the startup opens a documented out-of-tolerance assessment. They review which batches were released using that caliper since the last in-date calibration, compare the drift against the dimensional tolerance margins on the affected drawings, and conclude that all affected parts were still within specification even accounting for the drift. This conclusion is recorded, signed, and attached to both the calibration record and the affected batch records. No field action is needed, but the evidence trail is complete.

When the notified body auditor walks the shop floor during Stage 2, they pick two instruments at random, check the labels, pull the certificates, verify traceability, and ask to see one out-of-tolerance record. The whole audit of clause 7.6 takes 20 minutes and closes with zero findings.

## The Subtract to Ship playbook

Clause 7.6 does not need a complex eQMS module. It needs discipline and one honest spreadsheet.

**1. Make the list once, and make it complete.** Walk your production area, your lab, your test rigs, your storage monitoring. Write down every instrument whose output ends up in a release decision, a batch record, a validation report, or a complaint investigation. That is your 7.6 scope. Everything outside that scope (the coffee machine thermometer, the office ruler) is not covered and does not need calibration.

**2. Use accredited calibration laboratories where possible.** An ISO/IEC 17025 accredited lab gives you traceability to national or international standards automatically, with a certificate you can hand to an auditor. Pay for this. It is almost always cheaper than trying to manage traceability yourself.

**3. If you calibrate in-house, document the reference.** Some instruments (a pipette, a simple timer) can be verified in-house. Clause 7.6 requires that the basis for verification be recorded. That means: which reference was used, what procedure, what acceptance criteria, what result.

**4. Status labels are boring and non-negotiable.** Every instrument in scope gets a label. ID, last cal date, next cal due, and who to contact. The label is the first thing an auditor looks for. No label, finding.

**5. Validate test software before production.** Any test rig or measurement software used to accept or reject product must be validated under clause 7.6's software validation requirement. This is not full software-as-a-medical-device lifecycle work; it is targeted validation of inputs, outputs, and risk controls, proportionate to the risk of a wrong measurement. Document it in a protocol, execute it, sign it off, keep the records.

**6. Write an honest out-of-tolerance procedure.** When calibration reveals drift, the procedure must require assessment of previously released product. The procedure must name who does the assessment, what criteria they apply, and how the result is recorded. No "we will decide case by case" language. Define it before you need it.

**7. Protect the instruments.** Clause 7.6 also requires safeguarding from unauthorised adjustment and protection from damage. A calibrated torque screwdriver left loose in a drawer with the setting exposed will drift. A calibrated multimeter dropped off a bench is suspect. Build basic physical care into the work environment.

This program — one spreadsheet, one procedure, labels on instruments, accredited calibration contracts for critical tools, validated test software — is clause 7.6 done right. It takes about two days to set up and a few hours a month to maintain.

## Reality Check

1. Do you have a complete list of every instrument used to generate evidence of device conformity?
2. Does every instrument in that list have a current calibration certificate traceable to international or national standards?
3. Is every instrument labelled with its calibration status?
4. If an auditor asked you to prove that a measurement taken three months ago was valid, could you trace the instrument used, its calibration status at that time, and its certificate?
5. Do you have a documented procedure for out-of-tolerance findings that requires impact assessment on released product?
6. Has your test software or data acquisition software been validated before first use, and after every change?
7. Are instruments physically protected from damage and unauthorised adjustment in day-to-day use?
8. Is the calibration register reviewed at management review as part of QMS performance?

## Frequently Asked Questions

**What does "traceable to international measurement standards" mean in practice?**
It means the instrument is calibrated against a reference whose own calibration can be traced through an unbroken chain to a primary standard maintained by a national metrology institute. An ISO/IEC 17025 accredited calibration laboratory provides this chain through its certificate.

**Does every caliper and ruler in the building need calibration?**
No. Only the ones whose measurements are used to demonstrate conformity to product requirements. The ruler on the reception desk is outside scope. The caliper used for incoming inspection is inside scope.

**What counts as software validation under clause 7.6?**
It is a targeted validation of the software used in measurement or monitoring, proportionate to the risk of a wrong measurement. Inputs, outputs, algorithms, risk controls, and user interactions are tested against a specification. This is separate from EN 62304 software lifecycle work, which applies to the device software itself.

**How long do calibration records need to be kept?**
At least as long as the related product records, which under MDR means at least 10 years after the last device is placed on the market, and at least 15 years for implantable devices.

**What if an instrument is found out of tolerance at calibration?**
You must assess and record the validity of previous measurement results, take action on the equipment, and take appropriate action on any affected product. If the impact assessment shows that released product may be non-conforming, your non-conforming product and CAPA processes take over.

**Do environmental monitoring loggers (temperature, humidity) need calibration?**
Yes, if their data is used to demonstrate that storage or process conditions met specifications. If the logger's output ends up in a batch record or a validation report, it is in scope of clause 7.6.

## Related reading
- [MDR Production Controls: ISO 13485 Section 7.5](/blog/production-controls-iso-13485-7-5) — the wider production control framework around 7.6.
- [Process Validation Under MDR and ISO 13485](/blog/process-validation-mdr-iso-13485) — how 7.6 supports 7.5.6 process validation evidence.
- [Validating QMS Software Tools Under MDR](/blog/validating-qms-software-tools-mdr) — broader software validation expectations for QMS tools.

## Sources
1. Regulation (EU) 2017/745 on medical devices, consolidated text. Annex IX.
2. EN ISO 13485:2016+A11:2021, Medical devices — Quality management systems — Requirements for regulatory purposes. Clause 7.6.

---

*This post is part of the [Quality Management Under MDR](https://zechmeister-solutions.com/en/blog/category/quality-management) cluster in the [Subtract to Ship: MDR Blog](https://zechmeister-solutions.com/en/blog). For EU MDR certification consulting, see [zechmeister-solutions.com](https://zechmeister-solutions.com).*