What evidence do auditors commonly ask for on A.1.3.4 Providing information to PII principals?

The notice as actually presented, in each channel and language used; Evidence of delivery at the point of collection; Evidence of permanent accessibility after collection; Readability or comprehension assessment appropriate to the audience, especially where children are involved.

What is the most common gap auditors find on A.1.3.4?

Notice legally complete and written at a reading level the audience cannot use, which fails the intelligibility requirement

ISO/IEC 27701:2025 · Annex A Table A.1 PIMS controls for PII controllers

`A.1.3.4` Providing information to PII principals

The organization must give individuals information, clear and easy to find, that names the controller and explains how their data is processed. The information must be prompt, brief, complete, open and understandable, easy to reach, and written in plain wording that fits the people it is meant for; where suitable it is provided when the data is collected and stays available at all times afterwards.

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

Evidence of delivery at the point of collection · Document repository
Evidence of permanent accessibility after collection · Document repository
Readability or comprehension assessment appropriate to the audience, especially where children are involved · Document repository

governing documentDocuments that govern the control

The notice as actually presented, in each channel and language used · Policy repository / GRC workspace

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

Notice legally complete and written at a reading level the audience cannot use, which fails the intelligibility requirement
Notice linked at collection and then buried, so it is not permanently accessible in practice
Notice available in the organization's language only while collection happens in others
Layered notice whose top layer omits something material rather than summarising it
Notice provided after collection where before was practicable

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

A.1.3.3 Determining information for PII principals · A.1.3.5 Providing mechanism to modify or withdraw consent