What evidence do auditors commonly ask for on 8.1 Operational planning and control?

Process criteria and controls for the processes that process PII; Operational records giving confidence processes ran as planned; Change control and review of unintended changes; Control of externally provided processing, including processor contracts and oversight.

What is the most common gap auditors find on 8.1?

Operational control assumed from the SoA with no process criteria

ISO/IEC 27701:2025 · Operation

`8.1` Operational planning and control

The organization shall plan, run and control the processes it needs to satisfy the PIMS requirements and to carry out the actions decided under clause 6, by setting criteria for those processes and managing them against those criteria. It shall keep enough documented information to be confident that the processes ran as intended. It shall manage changes it plans, examine the effects of changes it did not intend, and act to limit any harm where needed. It shall also keep control over processes, products and services supplied from outside that bear on the PIMS, which for a PIMS means the processors and subcontractors handling PII for it.

Source: ISO/IEC 27701:2025, 8.1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27701:2025 in the compliance library.

artefacts

held by a system

at each review

hard

to go live

Document repository

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

Operational records giving confidence processes ran as planned · Document repository
Change control and review of unintended changes · Document repository

governing documentDocuments that govern the control

Process criteria and controls for the processes that process PII · Document repository
Control of externally provided processing, including processor contracts and oversight · Vendor register / contract repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Operational control assumed from the SoA with no process criteria
Processors controlled by contract signature alone with no oversight
Unintended changes such as a system migration never reviewed for their effect on PII

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

7.5.3 Control of documented information · 8.2 Privacy risk assessment