What evidence do auditors commonly ask for on A.1.2.9 Records related to processing PII?

Processing inventory carrying each required element; Named owner accountable for its accuracy and completeness; Evidence the inventory is maintained through change, not rebuilt for audits; Secure storage and access control over the inventory itself; Linkage from inventory entries to the corresponding impact assessments.

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

Inventory owned by nobody, so it decays between audits

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

`A.1.2.9` Records related to processing PII

The organization must identify, and keep securely, the records that back up its processing obligations. Usually this is an inventory of processing activities recording: the kind of processing; its purposes; the categories of personal data and of individuals, noting special groups such as children; the categories of recipients, including any located in third countries or at international organizations; an overall account of the technical and organizational safeguards; and the privacy impact assessment report. A named person must be responsible for keeping the inventory accurate and complete.

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

Policy repository / GRC workspace

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

none for this control

governing documentDocuments that govern the control

Processing inventory carrying each required element · Policy repository / GRC workspace
Named owner accountable for its accuracy and completeness · Document repository
Evidence the inventory is maintained through change, not rebuilt for audits · Policy repository / GRC workspace
Secure storage and access control over the inventory itself · Policy repository / GRC workspace
Linkage from inventory entries to the corresponding impact assessments · 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

Inventory owned by nobody, so it decays between audits
Recipient categories recorded without third country recipients, hiding the transfers
Inventory built from a system list, so processing done in spreadsheets and by suppliers is missing
Security measures described identically for every activity, which tells a reader nothing
Inventory itself unprotected despite mapping exactly where the organization's personal data lives

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.8 Joint PII controller · A.1.3.2 Determining and fulfilling obligations to PII principals