What evidence do auditors commonly ask for on Art.16 Right to rectification?

Rectification records showing the date received, the date the correction took effect, and every system changed; The procedure for propagating a correction to every copy, including downstream warehouses, reports and exports; Where a correction is disputed, the data subject's supplementary statement recorded alongside the data rather than filed separately; Evidence of the Article 19 notification to recipients following each rectification.

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

The record corrected in the system of origin while copies in the warehouse, the CRM and the backup restore path keep the old value

GDPR · Chapter III - Rights of the Data Subject

`Art.16` Right to rectification

On request, rectify inaccurate personal data concerning the data subject without undue delay, and, having regard to the purposes of the processing, complete incomplete personal data, including by means of the data subject providing a supplementary statement.

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

Rectification records showing the date received, the date the correction took effect, and every system changed · Data governance / DLP tooling
Evidence of the Article 19 notification to recipients following each rectification · Regulator portal / correspondence

governing documentDocuments that govern the control

The procedure for propagating a correction to every copy, including downstream warehouses, reports and exports · Policy repository / GRC workspace
Where a correction is disputed, the data subject's supplementary statement recorded alongside the data rather than filed separately · 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 record corrected in the system of origin while copies in the warehouse, the CRM and the backup restore path keep the old value
Rectification refused because the controller regards its own record as accurate, with no supplementary statement recorded
Without undue delay interpreted as the full one month by default rather than as promptly as the systems allow
Corrections made but recipients never told, so the inaccurate value persists outside the organisation

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.15 Right of access by the data subject · Art.17 Right to erasure (right to be forgotten)