EvidenceSheet
ISO/IEC 27701:2025 · Planning

6.1.1 General

In planning the privacy information management system, the organization shall take account of the issues identified under 4.1 and the requirements under 4.2, and shall identify the risks and opportunities it must deal with so that it can be confident the PIMS will deliver its intended outcomes, avoid or lessen unwanted effects, and keep improving. It shall plan how to respond to those risks and opportunities, how to build the responses into the processes of its PIMS and carry them out, and how to judge whether they worked. Privacy risk, meaning risk to the organization and to PII principals that stems from processing PII, is handled through the processes in 6.1.2 and 6.1.3.

Source: ISO/IEC 27701:2025, 6.1.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.

3
artefacts
0
held by a system
1
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

  • Evaluation of the effectiveness of the actions · Document repository

governing documentDocuments that govern the control

  • Planning record linking context and interested party requirements to risks, opportunities and actions · Document repository
  • Integration of the actions into PIMS processes · Document 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

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

5.3 Roles, responsibilities and authorities · 6.1.2 Privacy risk assessment