1. Why the record matters even when it is not mandatory
The record of processing activities is the reasoned list of everything your company does with personal data. For each activity it describes which data is processed, for what purpose, on which legal basis, who receives it, where it is stored, for how long and with which measures. It is the document that an authority or a customer may ask for first. It is not a formal exercise.
Whether you are obliged to keep it depends on size, type of data and frequency of processing, so check with an adviser whether you are covered. The reasoning the record imposes, however, is useful to everyone: knowing what you process helps you make better choices about suppliers, security and retention periods. Even a single completed entry delivers a concrete benefit. It also helps explain to the team why certain information is needed.
2. Before you start: who compiles it and with what information
The record is not compiled at a desk by reading a template. It has to be built by talking to the people who run the processes: administration, human resources, sales, whoever manages the website and whoever looks after the systems. Each person knows one part of the reality, and the sum of the parts is the full picture. Assign the gathering to a specific person and set a time limit for completing it.
- List of management systems, software and paper archives in use.
- List of suppliers that receive or handle data on the company's behalf.
- List of websites, contact forms and active newsletters.
- Copies of the privacy notices in use and of contracts with suppliers.
- List of internal staff who access systems containing personal data.
3. How to compile it, step by step
Work by activity, not by data. An activity is a process with a clear purpose, for example managing job applications, issuing invoices or sending the newsletter. For each activity, complete an entry following the order below: each step produces information needed by the next. Working by activity is easier to verify and update than a scattered list of data.
- List the business activities involving personal data, one per line.
- For each activity, write its purpose in a concrete sentence, not a generic one.
- Indicate the categories of people involved: customers, employees, candidates, suppliers.
- Note the data processed and separate special categories, such as health data.
- State the legal basis and check that it is consistent with the privacy notice.
- List the recipients, internal and external, including suppliers that process data on your behalf.
- Indicate where the data is stored and for how long, with the deletion criterion.
- Describe the security measures applied to that specific activity.
4. The essential fields, in a table
Each entry should contain at least the information in the table. The content should be adapted to your activity and written in words that an outsider can understand without verbal explanation. A blank field is not neutral: it is a signal that the process needs checking before you proceed. A fragmentary but honest entry is better than a complete but invented one. Every missing field must be checked.
| Field | What to write | Generic example |
|---|---|---|
| Activity | The name of the process and its purpose in one sentence | Managing applications for an open position |
| Data processed | Categories of data, separating special categories | Personal details, contact information and CVs |
| Legal basis | The reason that makes the processing lawful | Pre-contractual steps requested by the person, to be verified |
| Recipients | Who receives the data, internal or external suppliers | Provider of the recruitment platform |
| Retention | For how long and under which deletion criterion | Deletion at the close of selection, unless obligations apply |
5. The most common mistakes
The first mistake is copying a generic template downloaded from the internet and treating it as complete. A record that does not describe actual processes does not protect the company, because in an inspection the gap between paper and reality quickly becomes apparent. The second mistake is stating a legal basis without checking that it is consistent with the privacy notice and with the data actually collected. The third is forgetting the suppliers that access systems for support.
Other frequent errors are keeping data without reason, recorded as indefinitely, and the absence of a responsible person. If the record depends on one person who then leaves the company, the document is lost with them. Always assign an owner and a deputy, and write in the entry who completed it and on what date. A record without signatures and dates is hard to defend.
6. How to verify and maintain the record
A record is verified with concrete questions: choose a few activities at random and ask those who carry them out whether the entry really describes what happens. Check that each supplier listed has a written agreement and that each declared measure is active, for example that backups have been restored in a test. Ask for documented proof, not a verbal confirmation. Each time you activate software, sign with a supplier or change a process, update the entry and note the review date.
7. How to get started
This week, choose the most sensitive activity, probably staff or customer management, and complete a single entry following the steps in this guide. A well-made entry shows the method and makes clear how much information the others will need. Keep track of the time it takes, as you will need it to plan the rest. Then take the entry to a data protection adviser or to a supplier familiar with the subject, and ask for a review.
Frequently Asked Questions
Does the record of processing activities need to be sent to the Garante, the Italian data protection authority?
As a rule, no. The record is a document you keep available and present when a supervisory authority requests it. It is not sent periodically, but it must reflect actual processing as of the date of the request. An adviser can confirm how to handle it in your case.
Can I use a spreadsheet for the record?
Yes, a well-structured spreadsheet is enough for many organisations. Content matters more than format: each entry must be complete, dated, up to date and have a clear owner. If the record grows, you may consider dedicated tools, but they are not essential to get started.
Who in the company should compile the record?
The data controller remains responsible, but compiling the record is a team effort. Usually one person coordinates and gathers information from function heads, with support from an adviser. Each entry should have an internal owner who knows the process and can confirm it when needed.
Does the record also cover supplier data?
It covers all processing of personal data, so it includes employees, candidates, suppliers who are individuals, and website visitors. The data of a legal entity is not personal data, but the names of company contacts are. Check borderline cases with your adviser.
How often should I update it?
Update it whenever something changes: a new process, a new supplier, a new system or a substantial modification. In addition, schedule a periodic review with a named owner, and record its date in the document. The frequency depends on how much your activity changes, so set it according to your own pace of change.