Records of processing activities: guide and free template

Back to Blog

Last updated: 27 October 2026 · By Gaute Wangen

Records of processing activities, often called ROPA, are your overview of which personal data the organisation processes, why, about whom, and who receives it. Almost every organisation must keep them under GDPR Article 30, and the supervisory authority can ask to see them. Here we go through the requirements, how to build the records step by step, a worked example and a free template you can use straight away.

What are records of processing activities?

GDPR calls them "records of processing activities", and they are often shortened to ROPA. In Norwegian they are called behandlingsprotokoll. All three names refer to the same document.

The records describe processing activities, not IT systems. A processing activity is something the organisation does with personal data for a specific purpose, such as paying salaries, recruiting, following up customers or sending a newsletter. One system can serve several activities, and one activity can use several systems.

Extract from records of processing activities with four activities: payroll and HR, recruitment, customer follow-up and newsletter, each with purpose, lawful basis and retention period

Good records are also a working tool. They make it easier to answer access and erasure requests, to write your privacy notice, to see which suppliers need a data processing agreement, and to spot where you need a data protection impact assessment (DPIA).

Who must keep records of processing?

The main rule is simple: every organisation that processes personal data must keep records of the processing activities it is responsible for. That applies both to the controller and to the processor, meaning a supplier that processes personal data on behalf of its customers.

GDPR Article 30(5) gives an exemption to organisations with fewer than 250 employees. The exemption does not apply if the processing

  • is likely to result in a risk to the rights and freedoms of data subjects,

  • is not occasional, or

  • includes special categories of personal data (such as health data) or data about criminal convictions and offences.

Payroll and HR are ongoing, not occasional, and often include health data such as sickness absence. That is why the Norwegian Data Protection Authority (Datatilsynet) says the exemption is narrow, and that in practice, almost without exception, every organisation must keep records of its processing activities. Assume you need them.

The records are not filed anywhere, but you must make them available to the supervisory authority on request (Article 30(4)).

What must the records contain?

Requirements for the controller (Article 30(1))

Requirement

What it means in practice

Example

Name and contact details

The organisation, any joint controller and representative, and the data protection officer if you have one

Example AS, privacy@example.no

Purposes

Why you process the data

Pay salaries and meet employer obligations

Data subjects

Which groups of people the data is about

Employees and former employees

Personal data

Which types of data

Contact details, national identity number, bank account, salary, sickness absence

Recipients

Who the data is disclosed to, including recipients outside the EEA

Tax authorities, the labour and welfare administration, payroll supplier

Transfers outside the EEA

Which countries or organisations, and which transfer mechanism you rely on

None, or "Supplier in the USA, EU standard contractual clauses"

Retention periods

When the different types of data are deleted, where possible

See step 4 below

Security measures

A general description of the technical and organisational measures

Access control, multi-factor authentication, encrypted transfer, logging

Requirements for the processor (Article 30(2))

If you deliver services where you process personal data for customers, you also need processor records. They are shorter and must contain:

  • name and contact details for you and for each customer (controller) you process data for, and any data protection officer,

  • the categories of processing you carry out for each customer,

  • any transfers to countries outside the EEA, with the transfer mechanism,

  • a general description of the security measures.

What we recommend adding

The law only requires the points above, but the records become much more useful with a few extra columns. Datatilsynet's own template also has more columns than the legal minimum.

  • Lawful basis: which basis in Article 6 you rely on, and any condition in Article 9 for special categories.

  • Source: where the data comes from.

  • Systems and storage location: where the data is kept.

  • Processors: which suppliers process the data, and whether a data processing agreement is in place.

  • Owner: who in the organisation owns the activity.

  • DPIA: whether a data protection impact assessment has been considered, and whether one has been done.

  • Last reviewed: a date.

How to build your records of processing in six steps

1. Clarify your role

For each activity, decide whether you are the controller or a processor. Whoever decides the purposes and means is the controller. If you process data on a customer's instructions, you are a processor, and the activity belongs in the processor records.

2. Map the processing activities

Go through the organisation department by department: HR and payroll, finance, sales and marketing, customer service, IT and your core business. Ask each department: Which personal data do you process, why, and in which systems? One activity per purpose gives the right level of detail. "Recruitment" is an activity. "Excel" is not.

3. Describe each activity

Fill in the purpose, lawful basis, data subjects, personal data and recipients. Be specific. "Customer data" is too vague. "Name, email and phone number of contact persons at customers" is precise enough to be useful.

Include every supplier that processes the data: payroll system, cloud office suite, CRM and newsletter tool. Each of them normally needs a data processing agreement, and the records are a good place to check that it exists.

4. Set specific retention periods

"As long as necessary" is not a retention period. Tie each period to an event and a duration, for example "six months after the position is filled" for applications from candidates who were not hired. Where a legal requirement sets the period, such as bookkeeping rules for accounting records, refer to that requirement. The periods in your records are your own decisions, so give the reasons for them.

5. Describe the security measures

A general description is enough: access control, multi-factor authentication, encryption, logging, backup and training. Which measures you need depends on the risk, and the best way to find that is a risk and vulnerability analysis.

6. Give the records an owner, and keep them up to date

The records are only useful if they are accurate. Give them an owner, and update them when you introduce a new system, change supplier or start new processing. Review the whole record at least once a year.

Example: records of processing for a mid-sized organisation

The example is a consultancy with 60 employees and shows six typical activities. The template has the same example filled in.

Processing activity

Purpose

Lawful basis

Data subjects

Personal data

Recipients and processors

Outside the EEA

Retention

Payroll and HR

Pay salaries, follow up employees and meet employer obligations

Contract (Art. 6(1)(b)), legal obligation (Art. 6(1)(c)), Art. 9(2)(b) for sickness absence

Employees

Contact details, national identity number, bank account, salary, sickness absence

Tax authorities, the labour and welfare administration, payroll supplier (processor)

No

Payroll data as required by bookkeeping rules. The personnel file is deleted when employment has ended and it is no longer needed

Recruitment

Assess applicants for vacancies

Steps prior to entering a contract (Art. 6(1)(b))

Applicants

CV, application, contact details, references

Recruitment system (processor)

No

Six months after the position is filled, unless the applicant consents to longer storage

Customer follow-up

Follow up customers and agreements

Legitimate interests (Art. 6(1)(f))

Contact persons at customers

Name, job title, email, phone

CRM supplier (processor)

No

Two years after the last customer relationship

Newsletter

Send a professional newsletter

Consent (Art. 6(1)(a))

Subscribers

Name, email, sign-up time

Newsletter tool (processor)

Yes, USA. EU standard contractual clauses

When the subscriber unsubscribes

IT operations and logging

Run and secure the IT systems

Legitimate interests (Art. 6(1)(f))

Employees, contractors

Username, IP address, sign-in logs

IT operations supplier (processor)

No

Logs are deleted after six months

Visitor registration

Keep track of who is on the premises

Legitimate interests (Art. 6(1)(f))

Visitors

Name, organisation, time

None

No

Three months

The retention periods and lawful bases in the example are examples. They must be assessed for each organisation.

Template for records of processing activities

Download the template for records of processing activities (Excel)

The template has five tabs:

  1. Guidance: the six steps in short form, and who must keep records.

  2. Controller: general information at the top, and one row per processing activity with every requirement in Article 30(1) and the recommended extra columns. The lawful basis is chosen from a dropdown list.

  3. Processor: the records for suppliers that process personal data for customers (Article 30(2)).

  4. Example: the six activities from the example above, filled in.

  5. Lists: the values in the dropdown lists, which you can adapt.

Datatilsynet also offers simple templates for both kinds of records, in Norwegian. Ours covers the same requirements and adds guidance, dropdown lists and a completed example.

Common mistakes in records of processing

  • One row per system instead of per activity. The records should show what you do with the data and why, not just where it is stored.

  • Vague purposes. "Administration" or "running the business" says nothing.

  • No specific retention periods. "As long as necessary" is the most common weakness.

  • Missing suppliers. Cloud services, payroll systems and newsletter tools are often forgotten, and then the overview of data processing agreements is incomplete too.

  • Forgetting the processor role. If you deliver a service where you process customers' personal data, you also need processor records.

  • Records that are never updated. Records from 2018 rarely describe reality today.

Records of processing, DPIA and risk analysis: how do they fit together?

The records of processing are the overview: they tell you which processing you do. When processing is likely to result in a high risk to the data subjects, GDPR Article 35 requires a data protection impact assessment (DPIA). The records are the natural place to see which processing should be assessed.

A risk and vulnerability analysis looks at risk to the organisation and helps you choose the security measures you describe in the records. The three fit together, and the work is easier when they build on the same overview of systems and suppliers.

From spreadsheet to records that stay up to date

A spreadsheet works well to get started. It gets hard to keep up to date when systems and suppliers change, and when the same information must match across the records, the data processing agreements and the risk assessments.

In Cyrigo, your records of processing activities build on the same registers as the rest of the platform, so every processing activity is linked to the IT systems and suppliers it uses. There is no separate spreadsheet to keep in sync. A short pre-assessment tells you when a DPIA is needed, DPIAs are carried out in the platform, and privacy risks get their own register, using the same risk method and treatments as the rest of your risk work. Cyrigo is developed in Norway and hosted in Scandinavia.

See how it works on the product page, or book a demo.

Records of processing: frequently asked questions

Is a ROPA the same as records of processing activities?

Yes. ROPA is short for records of processing activities. In Norway the document is called behandlingsprotokoll.

Do small organisations need records of processing?

Almost always. The exemption for organisations with fewer than 250 employees does not apply when the processing is ongoing, is likely to result in a risk or includes special categories of data. Payroll and HR almost always meet at least one of these conditions.

Do the records have to be sent to the supervisory authority?

No. You must make them available if the authority asks for them.

Can we use Excel?

Yes. The records must be in writing, which includes electronic form. There are no requirements for format or tools.

How often should the records be updated?

Whenever you start new processing, introduce a new system or change supplier. Also review the whole record at least once a year.

Who is responsible for the records?

The organisation as controller, and therefore its management. The day-to-day work can sit with the data protection officer, a privacy lead or the owner of each processing activity.

Back to Blog