What evidence do auditors commonly ask for on A.1.3.2 Determining and fulfilling obligations to PII principals?

Register of obligations owed to individuals, by jurisdiction and processing activity; Documented mechanism delivering each obligation, with the responsible owner; Published description for individuals of what is fulfilled and how; Contact point on the same channel used for collection, with monitoring evidence.

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

Obligations listed by jurisdiction with no mechanism mapped against them

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

`A.1.3.2` Determining and fulfilling obligations to PII principals

The organization must identify and document the legal, regulatory and business obligations it owes to the individuals whose data it processes, and must provide the means to fulfil them, making sure those means are easy to use and prompt. It must explain clearly to individuals how far, and in what way, each obligation is met, and give them a current contact point offered through a channel comparable to the one used to gather the data and the consent.

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

Contact point on the same channel used for collection, with monitoring evidence · SIEM / log platform

governing documentDocuments that govern the control

Register of obligations owed to individuals, by jurisdiction and processing activity · Policy repository / GRC workspace
Documented mechanism delivering each obligation, with the responsible owner · Document repository
Published description for individuals of what is fulfilled and how · 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

Obligations listed by jurisdiction with no mechanism mapped against them
Contact point offered by post or telephone when the data was collected online, which is a barrier not a channel
Means provided but not resourced, so timeliness fails under any real volume
Business obligations, meaning contractual promises made to customers, omitted from the register

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.2.9 Records related to processing PII · A.1.3.3 Determining information for PII principals