Record of processing activities (ROPA): fields and template

A record of processing activities (ROPA) is the one part of a data map that the GDPR defines field by field. This article lists those fields for controllers and processors, gives a template to copy, and explains the small-company exemption, the proposed change to it, and the US laws that ask for similar work.

Data mapping and discovery covers inventories, flow maps and automated discovery, and this article covers the record itself. For the hours a manual ROPA takes, see What a manual data inventory costs.

What GDPR Article 30 requires

Article 30 of the GDPR has five paragraphs:

  • Paragraph 1 lists the contents of a controller's record.
  • Paragraph 2 lists the contents of a processor's record.
  • Paragraph 3 requires the records to be in writing, including in electronic form.
  • Paragraph 4 requires the controller or processor to make the record available to the supervisory authority on request.
  • Paragraph 5 exempts some organizations with fewer than 250 employees, as explained below.

Paragraphs 3 and 4 have two practical effects. A spreadsheet is a lawful format. The person who reads the record is a regulator who does not know your internal system names, so write "customer support ticketing (vendor: X)" and not "the old help desk".

Controller records, Article 30(1)

PointWhat the record must containNotes
(a)Name and contact details of the controller and, where applicable, of any joint controller, the controller's representative and the data protection officerThe same for every row. Put it in a header block.
(b)The purposes of the processingWrite "payroll and statutory tax filings", not "HR".
(c)A description of the categories of data subjects and the categories of personal dataUse a fixed list of categories so that rows match each other.
(d)The categories of recipients, including recipients in third countries or international organizationsInclude processors (your vendors), not only independent third parties.
(e)Where applicable, transfers to a third country or international organization, naming that country or organization, and for transfers under the second subparagraph of Article 49(1), documentation of suitable safeguardsName each country and the transfer mechanism, such as an adequacy decision or standard contractual clauses.
(f)Where possible, the envisaged time limits for erasure of the different categories of dataRegulators expect a retention rule, or a reason why there is none.
(g)Where possible, a general description of the technical and organizational security measures in Article 32(1)A summary or a link to your security documentation is enough. See GDPR Article 32 and security controls for personal data.

Processor records, Article 30(2)

PointWhat the record must contain
(a)Name and contact details of the processor and of each controller for which the processor acts, and where applicable, the controller's or processor's representative and the data protection officer
(b)The categories of processing carried out for each controller
(c)Where applicable, transfers to a third country or international organization, with the same identification and safeguard documentation as for controllers
(d)Where possible, a general description of the technical and organizational security measures in Article 32(1)

A processor organizes its record by customer, not by purpose. A SaaS company usually needs both kinds of record, because it is a controller for its own HR, sales and marketing, and a processor for the customer data it hosts. The processor record is often based on the company's data processing agreements and sub-processor list, because many customers sign the same standard terms. France's regulator, the CNIL, recommends two separate registers for an organization in that position.

Fines and an enforcement example

A breach of Article 30 falls under Article 83(4)(a), which sets a maximum fine of €10 million or 2% of total worldwide annual turnover, whichever is higher.

A recent decision shows what a regulator checks in a ROPA. In Decision 7FR/2025 of December 16, 2025, Luxembourg's regulator, the CNPD, reviewed a company's 40 processing entries after an on-site visit. The regulator found gaps under points (a), (c), (d) and (e) of Article 30(1). The company had fixed some entries during the investigation, but not all of them. The CNPD issued the following measures:

  • a reprimand;
  • a fine of €7,000;
  • an order to complete the record within two months.

The order listed the changes the company had to make:

  • add the missing categories of recipients;
  • replace generic terms for recipients with categories of recipients, and name the recipients in third countries;
  • state whether each activity involves a transfer to a third country, consistently across entries;
  • name each third country that receives personal data.

The company had fixed the gaps under points (a) and (c) by the decision date, so the order to complete the record covered only points (d) and (e), recipients and transfers.

A ROPA template to copy

The template covers every Article 30(1) point and adds operational columns, marked "recommended", that make the record useful for other privacy work. Use one row per processing activity, and keep the column order when you copy it into a spreadsheet.

ColumnArt. 30(1)Example entry
Activity IDrecommendedPA-014
Processing activity(b)Recruiting and candidate assessment
Business ownerrecommendedHead of Talent
Purpose(s)(b)Assess applicants for open roles; communicate with candidates; keep a talent pool with consent
Legal basisrecommended (needed for notices)Steps before a contract, Art. 6(1)(b); consent for the talent pool, Art. 6(1)(a)
Categories of data subjects(c)Job applicants; referees
Categories of personal data(c)Contact details; CV and employment history; interview notes; right-to-work documents
Special-category or criminal data(c), with a recommended flagDisability information that a candidate gives to request adjustments
Source of the datarecommendedApplicant; recruitment agencies; referees
Systems usedrecommendedSYS-031 applicant tracking system; SYS-002 email
Recipients(d)Hiring managers; ATS vendor (processor); background-check provider (processor)
Third-country transfers and safeguards(e)United States: ATS vendor, under standard contractual clauses
Retention / erasure time limit(f)Unsuccessful candidates: 6 months after the decision; talent pool: until consent is withdrawn, or 24 months
Security measures(g)SSO with MFA; role-based access in the ATS; see security policy v4
DPIA required / referencerecommendedNo; reason recorded in the DPIA screening log
Last reviewedrecommended2026-09-15, by the DPO

The example values are illustrations, not recommended retention periods. Set your own periods from your legal analysis and local employment rules. Put the controller's name, contact details, representative and DPO (point (a)) in a header above the table.

Keep the "Systems used" column as IDs that point to a separate system inventory. When a vendor changes, you then update one inventory row instead of every ROPA entry that names the vendor. Building privacy datasets that stay usable explains this structure.

Regulator templates

Some supervisory authorities publish their own templates. The CNIL's register page offers a spreadsheet template in ODS format, aimed at smaller organizations. The ICO's documentation guidance mentions basic templates for UK controllers and processors. A national template is a good starting point if most of your processing happens in that country.

The 250-employee exemption

Article 30(5) says that paragraphs 1 and 2 do not apply to an organization with fewer than 250 employees, unless the processing it carries out meets any of these conditions:

  • it is likely to result in a risk to the rights and freedoms of data subjects;
  • it is not occasional;
  • it includes special categories of data (Article 9(1)) or personal data about criminal convictions and offences (Article 10).

The Article 29 Working Party, which the EDPB replaced, published a position paper on the Article 30(5) exemption from keeping records of processing activities on April 19, 2018. The paper made three points:

  1. The three conditions are alternatives, so any one of them triggers the record-keeping duty.
  2. The first condition covers "a risk (not just a high risk)".
  3. A small organization that loses the exemption needs records only for the processing that triggered the duty.

Most small companies keep records because of the "not occasional" condition. The paper's own example is a small organization that processes employee data on a regular basis, which is not occasional and so must be in the record. A 40-person company therefore needs records for payroll, HR and customer billing, but can leave out one-off activities that carry no risk. Employee sick-leave data also meets the special-category condition.

The proposed change

On May 21, 2025, the European Commission proposed a change to Article 30(5) in a simplification package for small and mid-cap companies (COM(2025) 501). The proposed text exempts organizations with fewer than 750 employees, unless their processing "is likely to result in a high risk" within the meaning of Article 35. The proposal removes three of today's conditions: processing that is not occasional, processing likely to result in a risk, and the separate special-category condition. In Joint Opinion 01/2025 of July 9, 2025, the EDPB and EDPS supported simpler record-keeping. They also asked why the Commission chose 750 employees instead of the 500 it had considered earlier.

The Legislative Observatory file for 2025/0130(COD) records these steps:

  • February 25, 2026: the lead Parliament committee adopted its report and opened negotiations.
  • June 26, 2026: Parliament and Council negotiators agreed a text.
  • July 2, 2026: the committee approved the agreed text.
  • November 23, 2026: indicative date for the plenary vote.

As of October 19, 2026, Parliament has not voted, and no amending regulation has appeared in the Official Journal. Law-firm and news reports give different employee thresholds for the agreed text, so check the final text before relying on a number. The current 250-employee rule applies until an amending regulation is published and in force. On November 19, 2025, the Commission proposed further GDPR changes in a separate "Digital Omnibus" (COM(2025) 837). That proposal follows its own procedure, 2025/0360(COD), and is separate from the Article 30(5) change described above.

A company that answers access requests, writes a privacy notice and runs DPIAs needs most of the same information even without a duty to keep the record.

US equivalents

No comprehensive US state privacy law requires an Article 30-style record by name, but several laws require work that depends on the same information.

LawRequirementWhat it needs from your data map
California (CCPA as amended by the CPRA, and CPPA regulations)Risk assessments for listed processing activities from January 1, 2026, with attestations and summaries due to the CPPA by April 1, 2028. Cybersecurity audit certifications are due from April 1, 2028 to April 1, 2030, depending on revenue (CPPA).Categories of personal information, purposes, systems and recipients for each assessed activity
Minnesota Consumer Data Privacy ActData security practices "including the maintenance of an inventory of the data that must be managed" (Minn. Stat. 325M.16)A data inventory. This is the closest US match to Article 30.
Other state comprehensive laws, for example Virginia, Colorado, Connecticut, Texas and OregonData protection assessments before targeted advertising, sale of personal data, certain profiling, or processing of sensitive dataWhich activities involve those kinds of processing, and what data each activity uses
All of the aboveConsumer rights requests: access, deletion, correction and opt-outWhich systems hold a person's data and how to search them. See DSAR automation: building the data subject request workflow.

Thresholds and assessment triggers differ by state and have changed since several laws were passed, so check the current statute. For California, see The CPRA and the 2026 CCPA regulations. For Utah, see The Utah Consumer Privacy Act in practice.

A company under both regimes can keep one register, starting with the Article 30 columns. Then add columns for the US categories of personal information, and for whether an activity counts as a sale, sharing, targeted advertising or sensitive-data processing.

Not legal advice. The records you need depend on your size, activities and jurisdictions. Confirm specifics with counsel or the relevant regulator.

Techniques for building a ROPA

Start from purposes, then attach systems

List the business processes first: hire, pay, sell, support, market, secure and analyze. Break each process into processing activities, then ask which systems each activity uses. A ROPA built from a system list looks like an IT asset register and misses purposes that involve many tools.

Pre-fill before you interview

Pull a list of candidate systems from the SSO catalog, expense reports and cloud accounts before each team meeting. People correct a draft faster than they recall from memory, and the list includes tools they would forget.

Use fixed value lists

Set a fixed list of data categories, data subject types, legal bases and transfer mechanisms, and enter them through dropdowns. Free text leads to "email", "e-mail address", "contact info" and "PII" in one column, so a filter for one of those values misses the rows with the others.

Keep the inventory separate from the ROPA

Keep systems in one table and processing activities in another, linked by IDs. A spreadsheet with two tabs is enough. Vendor details, hosting regions and security measures are then stored only on the systems tab.

Assign owners and review dates

Give every row a named owner and a last-reviewed date. Add a step to vendor procurement that creates or updates the ROPA row, and a step to engineering design reviews for new data stores.

Write recipients and transfers precisely

Name the category of each recipient, such as "payroll processor" or "tax authority", instead of "partners" or "third parties". For each transfer, name the country and the mechanism. The CNPD order above covered the recipient and transfer entries.

Decide when to automate

Tools can build a system list, scan for personal data, and keep ROPA entries linked to live inventory records, but they cannot decide purposes or legal bases. To compare manual work with vendor quotes, read What a manual data inventory costs, or send your counts of teams and systems through Data map cost estimate. The privacy tech stack: privacy technology by layer shows where ROPA tools fit among other privacy tools.

FAQ

What is a ROPA?

A ROPA is a written list of an organization's processing activities. For each activity, the record gives the purpose, the people and data involved, the recipients and any transfers. Article 30 also requires the retention period and the security measures.

Does the ROPA have to be in a particular format?

No. Article 30(3) requires only that the record is in writing, which includes electronic form. National templates from the CNIL and the ICO are optional.

Do we have to publish our ROPA?

No. The ROPA is an internal record that you must show to the supervisory authority on request, under Article 30(4). Much of the same information appears in your privacy notice.

Is legal basis a required ROPA field?

Article 30(1) does not list it, but your privacy notice must state it under Articles 13 and 14, so most templates include it, including the one above.

How detailed should a purpose be?

Detailed enough that a regulator can tell what the processing does. "Marketing" covers too much. "Sending a monthly product newsletter to customers who opted in" describes one activity.

Does a processor need its own ROPA?

Yes. Article 30(2) gives processors their own record, organized by each controller they act for. A company that is both a controller and a processor keeps both records.

Does the UK have the same rule?

Yes. The UK GDPR keeps the Article 30 duty and the same 250-employee exemption. The ICO says its guidance is under review after the Data (Use and Access) Act 2025, so check the current guidance.

Need this built?

We build scripts that pull system and field lists from your databases and cloud accounts into a ROPA as part of our Data science services. Tell us about your project, and we will reply with questions or a rough plan.

Privacy engineering notes by email

When we publish a new guide on data mapping, DSR automation or AI privacy, we send it to this list. Nothing else.