Request a quote
Emergency SectorsCareers About us Blog Get in touch
Desk by a window with a laptop, an open notebook and two cups of coffee

The record of processing activities: the systems, locations and retention periods IT fills in

A record of processing activities belongs to the organisation, not to the IT team. But a record without IT is a list of intentions: which systems carry a processing activity, where the data sits, who receives it and how long it really exists is only known to whoever runs the environment. This article is about those columns and how to keep them current.

7 min read Written by the ITproposal team
Short answer

The record of processing activities is required for almost every organisation with staff, and belongs to the controller. The exemption for smaller organisations does not apply when processing is more than occasional, and payroll is not occasional.

IT fills in the columns that describe reality: which systems, which suppliers and sub-processors, where the data and backups sit, which retention period is technically configured and which security measures are running.

A record goes out of date with every new application and every new integration. Tie updating it to your change process. Purposes, lawful basis and the legal judgement are not IT’s; we are not lawyers.

What a record of processing activities is, and whose it is

Article 30 of the GDPR, kept in the UK GDPR, requires the controller to keep a record of processing activities: an overview, per processing activity, of what you do with personal data. The ICO can ask to see it, and publishes templates for it. It is also the document you need first yourself in a data breach, a subject access request or when taking on a new supplier.

There is an exemption for organisations with fewer than 250 employees, but it does not apply where the processing is likely to result in a risk, is not occasional or includes special category data. HR and payroll are not occasional, so in practice almost every organisation with staff needs a record.

The record is organised by processing activity, not by system: “payroll”, “recruitment”, “customer service”, “CCTV”. That is the language of the process. IT thinks in systems: the HR package, the mail platform, the ticketing service. IT’s job is to link the two, and that is the part missing from most records.

The columns in a record of processing activities that IT fills in

The law lists a fixed set of information per processing activity. Part of it comes from the process owner or the privacy lead; part of it only IT can fill in honestly:

  • From the process: the purpose, the categories of data subjects (employees, customers, applicants) and the categories of personal data, and in practice the lawful basis too.
  • From IT: the categories of recipients, including every cloud service and supplier that processes the data; transfers to countries outside the UK or the European Economic Area; the retention periods as technically configured; and a general description of the technical and organisational security measures.

A few columns are not in the law but make the record usable, and they come from IT as well: the system or application, the storage location of data and backups, the supplier and whether there is a data processing agreement, and which roles have access. Without those columns you cannot say within a few hours which processing activities a breach affects.

From system list to processing activity

Do not start with an empty record but with the list you already have: the asset register, the application list or the licence overview. Then add what has arrived out of sight:

  • Applications that sign in through single sign-on. The list of connected applications in your identity platform, such as the enterprise applications in Microsoft Entra ID, often shows services nobody put in a record.
  • Subscriptions on invoices and credit cards. A free trial that became a paid subscription, with customer data in it.
  • Integrations. Every link between two systems is a place where data is passed on, sometimes to a third party in the middle.

Then build a mapping table: each processing activity points to the systems that carry it, and each system to the activities it carries. The mail platform sits in almost every activity; the HR package in a handful. That table is what connects the record to reality, and to the agreements you have with each supplier, as described in our article on the data processing agreement with your IT supplier.

Retention: what the record says and what happens

Retention is where the gap between the record and reality is widest. The record says applicant data is deleted after a fixed period; in reality it sits in a shared mailbox, an export file and three years of backups.

So fill the column with what is technically configured, per location:

  • In the system itself: does it delete automatically or does someone have to, and is a record truly deleted or only hidden.
  • In mail and documents: is there a retention policy, or does everything stay.
  • In backups: how long they are kept. A deleted record lives on until the last backup containing it has expired, and that belongs in the record.
  • In log files and exports: often the forgotten copies.

If the configured period does not match what the process requires, that is not a fault in the record but a task for IT. How to delete data and media verifiably at the end is covered under data destruction and secure wiping.

Locations, recipients and transfers

“The data is in the cloud” is not a location. For the record you want to know, per system:

  • Which region the data is in, and whether that is a setting you chose or a default of the supplier. For Microsoft 365, the data location of your tenant is shown in the admin centre.
  • Where backups and recovery copies sit, because they can be in another region or with another party than the primary data.
  • From which countries support is provided. A helpdesk outside the UK or EEA that can reach the data is also a transfer.
  • Which sub-processors there are. The supplier should be able to provide that list, with their locations.

Ask for this information from every new supplier before the contract, and put it in the record straight away. Working it out afterwards takes longer and gives less certain answers.

Upkeep: the record ages with every change

A record of processing activities filled in once is a historical document a year later. Every new application, every new integration, a supplier moving data centres or a retention policy being changed alters a line.

  • Tie it to your change process. A change request that introduces a new system or data flow carries a fixed question: which line in the record changes because of this.
  • Agree who maintains which column. The process owner the purpose and data subjects; IT the systems, locations, retention and measures.
  • Schedule a fixed review. Once a year, put the mapping table next to the actual application list to find what slipped in.
  • Keep the versions. With a date per change you can show what the record looked like at a given moment, which is exactly what is asked after an incident.

For a small organisation a spreadsheet is enough, as long as it has an owner and a version history. Software only helps once someone already has the habit of keeping it up to date.

Where our work stops

What we do. For the environments we supply, configure or manage, we provide the IT columns of the record of processing activities: the systems and the mapping table, the suppliers and sub-processors as far as we know them, the storage locations of data and backups, the retention periods as technically configured and a description of the security measures. When we make a change, we report which line it affects. We work under ISO/IEC 27001; that describes how we work, not a judgement on your processing.

What we do not do. We are not lawyers and not a data protection officer. We do not set purposes, lawful bases or statutory retention periods, we do not assess whether processing is lawful, and we do not declare that a record is complete or compliant. The record belongs to the controller; its legal content belongs with your privacy lead, your data protection officer or a privacy lawyer.

Frequently asked

Questions we get about this

The five that come up most often.

What is a record of processing activities?

A record of processing activities, often called a ROPA, is an overview of all processing of personal data in an organisation, with for each activity the purpose, the data subjects, the types of data, the recipients, the retention periods and the security measures, among other things. It is required under Article 30 of the GDPR and the UK GDPR, and the regulator can ask to see it.

Do small organisations need a record of processing activities?

In practice almost always. The exemption for organisations with fewer than 250 employees does not apply when processing is not occasional, is likely to result in a risk or involves special category data. HR and payroll are not occasional, so anyone with staff almost certainly needs a record. If in doubt, put the question to a privacy lawyer.

What must a record of processing activities contain?

The law requires, per activity, the controller’s contact details, the purpose, the categories of data subjects and personal data, the recipients, international transfers, the retention periods and a description of the security measures. Add the system, the storage location and the supplier, or the record will be of little use in an incident.

Who maintains the record of processing activities?

The record belongs to the controller, and is usually coordinated by a privacy lead or data protection officer. The content comes from several sides: process owners provide purpose and data subjects, IT the systems, locations, retention and measures. Agree for each column who keeps it up to date.

Can you draw up or check our record of processing activities?

We provide the IT columns for the systems we manage and keep them up to date when something changes. We do not draw up a record in the legal sense or check whether it is complete or lawful: we are not lawyers and not a data protection officer. That part belongs with your own privacy lead or a privacy lawyer.

Shall we fill in the IT columns of your record?

We put the systems, locations, suppliers and configured retention periods next to your record of processing activities and show where they differ. The legal content stays with your privacy lead.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call