Record of processing activities: what must it contain and what mistakes should you avoid?

Record of processing activities: what must it contain and what mistakes should you avoid?

What Article 30 requires exactly

The record of the controller mentions, for each processing operation: the name and contact details of the controller (and of the DPO where applicable), the purposes, the categories of data subjects and data, the categories of recipients, the transfers to third countries with their safeguards, the envisaged time limits for erasure where possible, and a general description of the security measures.

The processor keeps its own record, per client: categories of processing carried out for each controller, transfers, security measures. A company is very often both at the same time: controller for its HR and prospecting, processor for the services provided to its clients. Both parts are then required.

The exemption for organisations with fewer than 250 employees falls away as soon as the processing is not occasional, involves a risk for the rights of individuals or relates to sensitive data: payroll, prospecting or customer management being regular processing operations, the exemption almost never applies in practice.

The template, column by column

ColumnExpected contentExample ('recruitment' processing activity)
PurposeThe objective, formulated in business languageManage applications and build a talent pool
Legal basisOne of the six bases under Article 6, justifiedPre-contractual measures; legitimate interest for the talent pool
Data subjectsCategoriesApplicants
DataCategories, highlighting sensitive dataIdentity, CV, salary expectations; never health data
RecipientsInternal and external, by categoriesHR, hiring managers, firm X (processor)
Transfers outside the EUCountries, safeguards (standard clauses, adequacy)EU hosting: none
Retention periodActive database then archiving, with reference2 years after last contact (CNIL guidelines)
Security measuresReference to general + specific measuresRestricted HR access, logging, encryption
OwnerThe business owner of the processing activityHR Director
DPIARequired or not, reference if carried outNot required

The 12 recurring errors found during inspections

  1. Confusing processing with tool: 'Salesforce' is not a processing activity; 'customer relationship management' is one, which relies on Salesforce.
  2. An absurd granularity: 400 unreadable micro-entries or 5 catch-all mega-processing activities; the right granularity is the business purpose (15 to 40 processing activities for an SME).
  3. Forgetting internal processing: payroll, video surveillance, badges, IT logs, access rights management: supervisory authorities often start there.
  4. Consent everywhere: the default legal basis for HR is contract or legal obligation, for B2B prospecting it is legitimate interest; poorly chosen consent weakens the entire processing activity.
  5. Absent or 'unlimited' durations: each entry must include a retention period justified by a text or framework, with the fate of data at expiry.
  6. Transfers outside the EU ignored: the US vendor of your support tool is a transfer to be documented, with supporting safeguards.
  7. Vague recipients: 'service providers' says nothing; named categories are expected, with a link to the list of processors and their contracts (Article 28).
  8. No processor section when the company processes for its clients: half the record is missing.
  9. A frozen record: dated from initial compliance and never reviewed; a record without a recent update date is an admission.
  10. No link with the rest: the entry must refer to the DPIA where it exists, security measures, privacy notices: the record is the table of contents of compliance.
  11. The SME exemption misunderstood: hiding behind 250 employees without checking the three conditions of the exemption.
  12. No owner: without a business owner per entry, no one reports changes and the record dies within six months.

Keeping the record alive without spending weeks on it

A living record relies on three mechanisms: one owner per entry, a short and regular review (quarterly for processing activities that change, annual for the rest), and integration into processes (every new tool or project goes through the record box, it is the best sensor for new processing activities). This is exactly what a compliance platform enables: templates, review alerts, automatic links to DPIAs, contracts and breaches, and one-click export the day the French data protection authority (CNIL) requests it.

Take action

Manage your compliance with Data Comply One: all-in-one software and outsourced DPO/CISO experts.

Discover the outsourced DPO →Test my GDPR compliance →

Sources

  • Regulation (EU) 2016/679 (GDPR), Articles 6, 28, 30 and 32, EUR-Lex.
  • The French data protection authority (CNIL), 'The record of processing activities': template and examples; retention period frameworks.
  • European Data Protection Board, position on the exemption under Article 30(5).

Frequently asked questions

Must the record be sent to the CNIL?

Not spontaneously: it is kept at its disposal and produced on request, typically at the start of an inspection. The French data protection authority (CNIL)'s reference frameworks and template are good starting points.

In what format should the record be kept?

The GDPR requires a written form, including electronic. A spreadsheet is suitable for starting; it quickly shows its limits (versions, links, reviews): the issue is not the format but the ability to maintain it.

One record per company or per group?

Each controller keeps its own; a group can share the tool and templates, with a view per legal entity.

Who must fill in the record: the DPO?

The DPO steers and controls, but the knowledge lies with the business units: the business owner + DPO (internal or outsourced) pairing is the only sustainable model.

Is the record sufficient to prove compliance?

No, it is the entry document for accountability: it must be linked with privacy notices, processor agreements, DPIAs and the breach register. A GDPR audit checks precisely this overall consistency.