What evidence do auditors commonly ask for on Art.19 Notification obligation regarding rectification, erasure or restriction?

A recipient register per dataset, current enough to answer who must be told when a record changes; Notification records tied to individual rectification, erasure and restriction actions, with dates and recipients; The impossible or disproportionate effort assessment for any recipient not notified; The response given to a data subject who asked which recipients were informed.

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

No recipient register exists, so the obligation cannot be performed and is silently skipped

GDPR · Chapter III - Rights of the Data Subject

`Art.19` Notification obligation regarding rectification, erasure or restriction

Communicate every rectification, erasure or restriction of processing carried out under Articles 16, 17(1) and 18 to each recipient to whom the personal data has been disclosed, unless this proves impossible or involves disproportionate effort. Inform the data subject about those recipients if the data subject requests it.

Source: GDPR, Art.19. 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

Notification records tied to individual rectification, erasure and restriction actions, with dates and recipients · Data governance / DLP tooling
The impossible or disproportionate effort assessment for any recipient not notified · Data governance / DLP tooling

governing documentDocuments that govern the control

A recipient register per dataset, current enough to answer who must be told when a record changes · Policy repository / GRC workspace
The response given to a data subject who asked which recipients were informed · 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

No recipient register exists, so the obligation cannot be performed and is silently skipped
Notification treated as covered by the processor contract rather than as an act the controller must carry out and evidence
Recipients told about erasures but not about rectifications or restrictions, which the Article treats identically
A data subject's request to know the recipients answered with categories when the specific recipients are known

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.18 Right to restriction of processing · Art.20 Right to data portability