Remote ISO 9001:2026 Transition Audit: 7.1.5 on Screen

The audit plan arrives from your certification body, and one line in it changes how you prepare: Day 2, 09:00–10:30, remote via video call — 7.1.5 Monitoring and measuring resources.

You know where the calibration evidence is. The gauge register is a spreadsheet on the quality drive. The supplier certificates sit in a second folder, named however each lab names its PDFs. The torque tools are tracked in a third workbook that production maintains. The out-of-tolerance assessments are in a ring binder in the metrology room. If the auditor were on site, you would walk them over and open the binder. On a screen-share you can’t do that. They will see what you can find and share, and they will see how long it takes you to find it.

This article explains how 7.1.5 sampling changes when the transition audit is remote, and what to have open before the call starts.

What is verified, and what is not

ISO 9001:2026 was published on 16 September 2026. The transition rules are in Global ACI document TECH-3-TR, "Transition Requirements for ISO 9001:2026". Global ACI is the body formed from IAF and ILAC. The document was issued on 4 September 2026 and sets a three-year transition. Accredited ISO 9001:2015 certificates stop being valid after 30 September 2029.

Section 5.2 of that document says the transition audit can be combined with a surveillance audit or a recertification, or held as a separate audit. It also says the audit may be conducted remotely using information and communication technology (ICT) under IAF MD 4 (now Global ACI TECH-3-003), as long as the audit objectives can be met. Whether your audit is remote is your certification body’s decision. Ask them now. Don’t assume either way.

Clause 7.1.5 is not in Global ACI’s summary of key changes, and the document calls the overall changes "minimal". The list is explicitly "not limited to" the items it names, so that is not proof the wording is identical. Check 7.1.5.1 and 7.1.5.2 against your purchased copy of the standard. Be careful with secondary sources that claim new 7.1.5 obligations, such as software validation. We found no primary source for those claims.

What follows applies whether or not the text moved. The auditor is still testing the same thing: can you show, from your records, that the measuring resources behind your conformity decisions were fit for purpose?

Why remote sampling is harder, not easier

On site, an auditor checks 7.1.5 by moving between the shop floor and the records. They pick up a thread plug gauge at a machine, read its ID, and ask for its record. Or they start from a certificate and ask to see the gauge it belongs to. Each direction checks the other.

Over a video call the auditor loses the walk, so they make up for it in three ways:

1. They ask for more retrieval. They can’t see the gauge rack, so they ask you to bring up more records in less time.
2. They ask for a live camera on the floor. Someone at the cell points a tablet at an instrument so the auditor can read its identification. This tests 7.1.5.2 b) directly: the instrument must be identified so that its status can be determined.
3. They treat delay as information. A certificate that takes six minutes to find will rarely become a nonconformity by itself. It will make the auditor sample deeper, though, and a deeper sample finds more.

There is also an integrity check that many teams miss. If you edit a cell in a spreadsheet while the screen is shared, the auditor sees evidence being created during the audit. Don’t touch records during the session. If something is wrong, say so and record it as a finding against yourself.

A worked example: twenty minutes of remote 7.1.5 sampling

This is a realistic sequence based on how transition and surveillance audits typically run. Your auditor’s order will differ, but the logic is the same.

Minute 0–3. "Show me the measuring equipment used to release parts on line 4." The auditor wants a filtered view, not the full register. If your register can’t be filtered by location or process, you will be scrolling, and they will notice.

Minute 3–6. They pick three IDs: an M10 thread plug gauge, a click torque wrench, and a gauge that came back from the lab last month. Choosing a recently returned item is deliberate. It is the one most likely to show an as-found failure.

Minute 6–9. "Can someone show me the torque wrench at the station?" A colleague on the floor points a tablet camera at it. The auditor checks that the ID on the tool matches the record, and that its status can be read from the tool or traced to the record.

Minute 9–13. "Open the certificate." Now they check 7.1.5.2 a). Was the instrument calibrated at the specified interval against standards traceable to international or national measurement standards? Does the certificate show as-found results? Do the reported values and uncertainty support your tolerance? A pass against the lab’s specification is not the same thing.

Minute 13–17. "The as-found was out of tolerance. What did you do?" This is the question that produces nonconformities. 7.1.5.2 requires you to determine whether the validity of previous measurement results has been adversely affected, and to take appropriate action. The auditor wants that assessment linked to the instrument record. A page in a binder two buildings away doesn’t do that.

Minute 17–20. "Who had this gauge between calibrations, and what stops someone using an overdue one?" The first question tests whether you can define the scope of a recall. The second tests 7.1.5.1’s requirement that resources are maintained to ensure their continuing fitness for purpose.

The screen-share preparation table

| Auditor asks for | What they are testing | Have this open before the call |
|—|—|—|
| Equipment for a process or line | Completeness of the register | A filtered register view by location or process |
| A specific ID on camera | 7.1.5.2 b) identification and status | A floor contact with a tablet, briefed on where the instruments are |
| The current certificate | 7.1.5.2 a) interval and traceability | Certificates attached to the asset record, not stored in a separate folder |
| As-found vs. as-left | Whether failures are visible | As-found and as-left values recorded on the calibration record |
| An OOT impact assessment | Validity of previous results | The assessment linked to the instrument and calibration event |
| Possession history | Recall scope | Check-out and allocation trail for the interval |
| Overdue control | Continuing fitness for purpose | Your rule (block or warning) and evidence it is applied |
| Non-traceable items | 7.1.5.2 a) basis for calibration | The documented basis where no national or international standard exists |

Pre-call checklist

• Confirm the audit format, the ICT platform and the timing with your CB in writing.
• Run a 15-minute technical rehearsal: screen-share, a second camera, and audio from the floor.
• Pick one person to drive the screen and one person to answer. Don’t do both jobs.
• Scan any evidence that exists only on paper and link it to the asset record before the audit, not during it.
• Pre-build saved views: overdue now, returned in the last 90 days, OOT in the last 12 months.
• Share read-only views. No live edits during the session.
• If you are IATF 16949-certified, IATF has its own audit rules. Don’t assume the Global ACI remote-audit provision applies to your IATF audit. Confirm with your CB.

The objection: "We’ll just send the spreadsheets in advance"

Sending documents before the audit is useful, and many CBs ask for it. It doesn’t replace live sampling, though. A spreadsheet you email is a snapshot you chose. The auditor will still ask to see the live record during the call and compare the two. If they don’t match, you have a bigger conversation than the one you were trying to avoid.

A second objection is that remote audits are lighter. Not necessarily. Under IAF MD 4 the CB must be satisfied that the audit objectives can be met remotely. If your evidence can’t be shown over ICT, the CB may decide that part of the audit needs to happen on site. That decision is theirs, not yours.

Where PrüfDesk fits, and where it does not

PrüfDesk manages the calibration records layer. It gives you:

• an instrument register you can filter by location;
• calibration due dates calculated automatically;
• pass/fail records with as-found/as-left values and certificates attached to the asset;
• reusable procedure templates that can be overridden per unit;
• configurable overdue blocking, either a hard block or a soft warning;
• a check-out and allocation trail;
• PDF compliance reports, with unlimited users, so the floor contact and the auditor’s guide can both log in.

Plans are Starter at €49/month for 250 assets, Professional at €129/month for 1,000 assets, and Enterprise at €299/month for unlimited assets.

It is not a QMS. It does not write your impact-assessment procedure, does not run calibrations for you, and does not certify you. A clean screen-share depends on your records, not your software.

If your 7.1.5 evidence is spread across three files and a binder, talk to us about your 7.1.5 evidence, and we will show you what the twenty-minute sample looks like with it all in one place.