A treatment register is one of the most concrete and statutory tools for keeping track of personal data, yet it is an area that is often forgotten or handled carelessly.
Many organizations know they have a responsibility, but few have a structured way to actually live up to it.
In this article, we explore what a processing register is, why it matters, and how it ties together GDPR requirements with the growing cybersecurity regulations in the form of NIS2.
What is a treatment register?
A processing register is a documentation of all the activities within an organization where personal data is processed. It can involve everything from managing employee payroll information to a case system logging who has reported an IT case.
According to Article 30 of the GDPR, most organizations are required to keep such a register. This applies to anyone with more than 250 employees, but also to smaller organizations if the processing is not occasional, involves sensitive data or may pose risks to the rights of individuals.
In practice, this requirement affects, in principle, all authorities, municipalities, regions and most private companies.
The register shall contain at least:
- Name and contact details of the data controller
- The purposes of the processing — why is the data processed?
- Which categories of data subjects are affected (e.g. customers, employees, citizens)
- What categories of personal data are processed?
- If the data is shared with third parties or transferred outside the EU/EEA
- How long the data is saved
- An overall description of security measures
Why is it important — and what happens if you miss it?
The short answer: The Swedish Data Protection Authority (IMY) may demand to see your processing records during an inspection.
But compliance is only part of the picture. The real value of a well-managed treatment record is the insight it provides. Do you actually know where all the personal data is in your organization? What systems handle it? Who is responsible? For most organizations, the answer to at least one of those questions is: no.
A treatment registry forces the mapping needed to:
- Conducting impact assessments (DPIA) when new treatment is planned
- Handle requests for record excerpts or deletion within the statutory time frame
- Identify risks associated with suppliers and data processors
- Show regulatory authorities that you work systematically and responsibly
The GDPR connection — more than just a form
GDPR is based on the principle of accountability: it’s not enough to comply with the law — you must be able to prove that you do. The processing record is the very backbone of this proof.
It is also the starting point for a DPIA (Data Protection Impact Assessment), the risk assessment required when new processing may pose high risks to individuals. Without an updated processing record, you simply don't know when a DPIA needs to be done.
Another critical link: data processing agreements. GDPR requires that you have written agreements with all external parties that process personal data on your behalf — cloud service providers, IT systems, external consultants. The processing register is the natural place to document which processors are connected to each processing.
NIS2 and the connection to information security
The NIS2 Directive tightens cybersecurity and risk management requirements for a broad group of essential and digital services. It covers an increasing number of sectors and requires systematic risk identification, incident reporting and information security governance.
There is a natural overlap with the treatment registry here. NIS2 requires organizations to map their information assets, their systems and their dependencies on suppliers. It is essentially the same mapping exercise that a treatment registry is based on, but with a broader security focus.
In practice, this means that an organization that has a well-maintained treatment register already has an important foundation for NIS2 work. Those that lack it, or have a register that is years old and never updated, will have difficulty meeting the requirements of both regulations.
Think of the processing register as a shared map: GDPR uses it to protect individual rights, NIS2 uses it to protect organizational resilience. Both need the map to be up to date.
Common mistakes to avoid
- The treatment record is created once and never updated, it is a living document, not a one-time task
- You document systems, not processing, the focus should be on why and how data is processed, not just which systems exist and what data they contain
- Responsibility falls to an individual without any involvement in the business, the treatments are owned by the respective business area
- You miss out on processing that takes place in everyday tools such as email, calendar and task systems
- The connection to data processing agreements and DPIA processes is completely missing
How do you get started?
The best advice is to start simple and build out gradually. An inventory of the organization's most central systems and processes quickly provides a record that is better than nothing at all and provides a good basis for an audit.
Start by identifying:
- Which systems handle personal data? (HR systems, case systems, email, intranet, surveillance cameras, etc.)
- What is the purpose of each treatment?
- Who within the organization is responsible for each treatment?
- Are there data processing agreements in place for external suppliers?
The next step is to ensure that the register is actually used, that it is updated when new systems or processes are added, and that it is linked to your DPIA process and your assistance agreements.
Support for treatment records in your existing systems
Many organizations try to manage the treatment register in spreadsheets or separate document archives, which makes it difficult to keep up to date and almost impossible to connect to other processes. The problem is not just administrative: a register that lives in its own silo can never become the living tool that GDPR actually requires and needs.
Easit GO provides ready-made support for processing registers as an integrated part of the platform. This means that each processing can be documented in a structured manner with all mandatory fields — and at the same time linked directly to related objects in the system: the IT services and systems that handle the data, the suppliers and data processors involved, as well as linked DPIAs and assistance agreements.
The relational model in GO makes it possible to navigate these dependencies visually, making it easy to see the whole picture and not just an isolated row in a spreadsheet.
This means that when a new service is launched, a new system is procured or a supplier is replaced, the treatment register can be updated in the same flow, not as a separate task that is postponed and forgotten. The result is a register that actually stays up to date and that withstands oversight.
Frequently asked questions about treatment records
What is a treatment register?
A processing record is a list of all activities in which an organization processes personal data. According to GDPR Article 30, it must document why the data is processed, which categories of data and data subjects are affected, how long the data is stored and what security measures are in place.
Do all organizations have to have a treatment register?
In practice, yes. Formally, the requirement applies to organizations with more than 250 employees, but also smaller organizations if the processing is not temporary, involves sensitive data or may pose risks. This means that in principle all authorities, municipalities and regions are required to keep a processing register.
What happens if you don't have a treatment register?
The Swedish Data Protection Authority (IMY) may require to see the processing register during supervision. If it is missing, or if it is clearly incomplete, the organization risks fines and demands for action. It can also be difficult to handle requests for register extracts or deletion without a current register.
How is the treatment register related to NIS2?
NIS2 requires systematic mapping of information assets, systems and vendor dependencies — essentially the same exercise that the treatment registry is based on. An organization with a well-maintained treatment registry therefore already has an important foundation for NIS2 compliance.
How often should the treatment register be updated?
The processing register should be a living document that is updated continuously — when new systems are implemented, processes change or suppliers are replaced. GDPR does not require a specific update frequency, but the register must always reflect the actual processing in the organization.
Would you like to see how the treatment register works in Easit GO? Book a demo or give us a call and we'll show you how it connects with your services, systems and supplier relationships.
Read also:

Henrik Traveler
Commercial Product Manager
henrik.resare@easit.com
+46 70 249 36 06