What evidence do auditors commonly ask for on Art.12 Transparent information, communication and modalities for rights?

The request register showing receipt date, response date, and any extension with its notification and stated reasons; Readability evidence for the privacy information, such as a plain language review or a reading age assessment; The identity verification standard applied, with the reasoning that it is proportionate rather than routine; Every refusal or fee decision with the manifestly unfounded or excessive justification recorded against it; Refusal responses showing both the supervisory authority complaint route and the judicial remedy were given.

What is the most common gap auditors find on Art.12?

The one month clock started when the request reached the privacy team rather than when it reached the organisation

GDPR · Chapter III - Rights of the Data Subject

`Art.12` Transparent information, communication and modalities for rights

Provide the Article 13 and 14 information and every Article 15 to 22 and 34 communication in a concise, transparent, intelligible and easily accessible form, in clear and plain language, with particular care where the information is addressed to a child, normally in writing including by electronic means. Facilitate the exercise of data subject rights and do not refuse to act unless the controller demonstrates it cannot identify the data subject. Provide information on action taken without undue delay and in any event within one month of receipt, extendable by two further months where the complexity and number of requests requires it, with the data subject informed of the extension and its reasons within the first month. Where no action is taken, say so within one month with the reasons and inform the data subject of the right to lodge a complaint with a supervisory authority and to seek a judicial remedy. Act free of charge; a reasonable fee or refusal is available only for manifestly unfounded or excessive requests, and the controller bears the burden of demonstrating that character. Additional information may be requested only where there are reasonable doubts about the requester's identity.

Source: GDPR, Art.12. 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 GDPR in the compliance library.

Many articles apply only where their condition is met (a data protection officer under Article 37, an impact assessment under Article 35, a representative under Article 27); the condition is in each statement.

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

Readability evidence for the privacy information, such as a plain language review or a reading age assessment · Data governance / DLP tooling
Every refusal or fee decision with the manifestly unfounded or excessive justification recorded against it · Document repository

governing documentDocuments that govern the control

The request register showing receipt date, response date, and any extension with its notification and stated reasons · Policy repository / GRC workspace
The identity verification standard applied, with the reasoning that it is proportionate rather than routine · Policy repository / GRC workspace
Refusal responses showing both the supervisory authority complaint route and the judicial remedy were given · 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

The one month clock started when the request reached the privacy team rather than when it reached the organisation
Extensions taken without notifying the data subject inside the first month, which is the condition attached to the extension
Identity verification demanded as standard from every requester, adding friction Article 12(6) does not permit
Refusals issued without the complaint and judicial remedy information, which is a breach separate from the refusal itself

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

Art.11 Processing which does not require identification · Art.13 Information to be provided where personal data are collected