What evidence do auditors commonly ask for on Art.37 Designation of the data protection officer?

The Article 37(1) assessment, made whether or not an officer was appointed, showing how core activities, large scale and regular and systematic monitoring were judged; The designation record, with evidence the contact details were both published and communicated to the supervisory authority; The officer's qualifications and experience measured against the data protection risk the organisation's processing presents; Where a group officer is appointed, evidence of accessibility from each establishment including language and working hours; The officer's other roles and duties, with the conflict of interests analysis for each.

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

No appointment made and no assessment on file, so the absence of an officer cannot be justified when it is challenged

GDPR · Chapter IV - Controller and Processor

`Art.37` Designation of the data protection officer

Designate a data protection officer where the processing is carried out by a public authority or body, except for courts acting in their judicial capacity, where the core activities consist of processing operations which by their nature, scope or purposes require regular and systematic monitoring of data subjects on a large scale, or where the core activities consist of processing on a large scale of special category data or of personal data relating to criminal convictions and offences. A group of undertakings may appoint a single data protection officer provided that officer is easily accessible from each establishment. Designate on the basis of professional qualities, in particular expert knowledge of data protection law and practice and the ability to fulfil the Article 39 tasks. The officer may be a staff member or fulfil the tasks under a service contract. Publish the officer's contact details and communicate them to the supervisory authority.

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

The designation record, with evidence the contact details were both published and communicated to the supervisory authority · Regulator portal / correspondence
Where a group officer is appointed, evidence of accessibility from each establishment including language and working hours · Document repository

governing documentDocuments that govern the control

The Article 37(1) assessment, made whether or not an officer was appointed, showing how core activities, large scale and regular and systematic monitoring were judged · Policy repository / GRC workspace
The officer's qualifications and experience measured against the data protection risk the organisation's processing presents · Document repository
The officer's other roles and duties, with the conflict of interests analysis for each · 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 appointment made and no assessment on file, so the absence of an officer cannot be justified when it is challenged
Contact details published on the website but never communicated to the supervisory authority, which is a separate requirement
The role given to the head of information technology, legal or compliance, who determines purposes and means and therefore cannot independently monitor them
A single group officer with no realistic capacity or language coverage for the establishments nominally served

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.36 Prior consultation · Art.38 Position of the data protection officer