How it works today in many organizations
An organization's GDPR documentation is rarely created in one go. The records of processing activities are set up because a customer or the supervisory authority asks for them. The first data protection impact assessment (DPIA) is written when a new applicant portal is introduced. The deletion concept has been an open item on the external data protection officer's list since the last meeting. And a data breach is reported by someone writing an email to "privacy@".
The result is scattered accordingly: "Records_2025.xlsx" on the HR network drive, "DPIA_Applicant_Portal_v3.docx" in the folder "Data protection/Impact assessments", the deletion concept as a PDF from last year and the incidents in a mailbox that two people can access. In small companies and associations, one person from administration, IT or the board takes on these tasks alongside their actual role. In larger organizations it is several departments, legal entities and locations. Anyone with a question about the applicant portal first has to know which folder holds the answer.
In between there is often an external data protection officer. They inform, advise and monitor – that is how Art. 39 GDPR describes the role. The documentation itself remains the duty of the controller, meaning the organization. In day-to-day work that line blurs: the external data protection officer receives files by email, revises them in their own templates and sends them back. The sentence "I sent you the revised version" then describes the entire maintenance process. In the end, only whoever sent the last email knows which version is current.
When the decision for data protection management software is made, a feature list is often ticked off: records available, template for the impact assessment available, area for incidents available. What is rarely checked is how they connect. An impact assessment refers to processing activities, a data breach affects systems and processing activities, a deletion rule applies to data from specific processing activities. These four tasks are not a catalog but one connected maintenance process.
The moment it becomes apparent
The fragmentation becomes visible at a handover. The person who maintained the records leaves the organization, or the contract with the external data protection officer ends. Suddenly it is unclear which version of the records applies, which processing activities the last impact assessment referred to and whether the retention periods from the concept were ever implemented. The successor starts by searching through drives and mailboxes before the actual work can begin.
The same gap shows up in a data breach. The 72-hour deadline under Art. 33 GDPR is running, and the question "Which processing activities and which data are affected?" has to be answered from four files that know nothing about each other. Anyone who first has to look for the right version at that moment loses the time needed to assess the incident.
The analysis
Five Gaps in Scattered GDPR Documentation
They do not come from a lack of care, but from keeping four connected tasks in separate files.
View processing activities in preecoThe structure does not fit the organization
Legal entities, locations or clients are separated by folder names. Every new unit duplicates the filing, and an overview across all units only comes about by hand.
Documents without references
Records, impact assessment, incidents and deletion concept refer to each other only in free text. When a processing activity changes, the related impact assessment stays outdated without anyone noticing.
Deadlines without a signal
The notification deadline, retention periods and review dates sit as dates in documents. No file shows by itself whether a deadline is still running or has already passed.
Roles without boundaries
Departments, internal owners and the external data protection officer work on the same folders. Either everyone sees everything, or information is passed on by email and goes stale along the way.
No provable version
Which version applied on a given date and who approved it cannot be derived from file names. Yet the accountability principle under Art. 5(2) GDPR requires exactly this evidence.
The target process in six steps
Data protection management software is a working tool, not advice. Selection therefore starts with your own organization and ends with the question of how the documentation is maintained over time. The following six steps serve as a practical overview of the key data protection and compliance criteria.
1. Clarify organization size and structure. How many legal entities, locations or – for external data protection officers – clients have to be documented separately? preeco | data protection supports multiple tenants: several organizations are managed in one team, and an organization selector switches between them. An association with a single office does not need this depth; a group of companies with subsidiaries does.
2. Determine your data protection needs. How many processing activities are there, how many of them are likely to involve a high risk, and how often do data subject requests and incidents occur? This shows whether you mainly need clean records or also guided impact assessments, an incident process and a deletion concept.
3. Assign roles. Decide who maintains, who approves and who advises. In preeco | data protection, user groups are freely defined and confidentiality classes are controlled per group. Departments contribute via data collection forms, and external people can do so by email without their own account. The external data protection officer advises and reviews in the system; responsibility for the documentation stays with the organization.
4. Set the documentation depth. Link the four tasks instead of keeping them side by side. An impact assessment takes over details from the linked processing activities, deletion classes refer to the processing activities they apply to, and an incident is connected to the affected processing activities. The "Relationships" tab on every document shows graphically what it is connected to.
5. Take over what exists. Existing records can be uploaded as DOCX or XLSX. An optional AI feature detects the processing activities they contain, and you decide in a preview which ones are taken over as drafts.
6. Schedule maintenance. Reminders by email and on the dashboard prompt reviews and deletion checks. Every approval creates an immutable revision, and the activity log records who changed what and when.
Data breach and deletion concept in context
Two tasks show particularly clearly why the connection matters. In a data breach, preeco | data protection records the incident with points in time, people involved and an assessment of the notification obligation. Included notification templates cover the notification to the supervisory authority under Art. 33 GDPR and the communication to data subjects under Art. 34 GDPR, and each notification shows whether the deadline is still running or was met.
In the deletion concept you sort your data into deletion classes that are linked to the processing activities; many details are taken over directly from the records. Deletion rules describe the specific deletion procedure. Tasks on the deletion rules trigger manual deletions or check automatic ones, and the task log appears in the export as evidence of execution.
Before and after in direct comparison
| Criterion | Before: scattered files | After: data protection management software |
|---|---|---|
| Structure | One folder per legal entity or client | Several organizations in one team with an organization selector |
| Connections | Records, impact assessment, incidents and deletion concept unlinked | Linked documents with a graphical view of relationships |
| Deadlines | Dates in documents and emails | Deadline status per notification, reminders for reviews |
| Roles | Sharing of entire folders | User groups and confidentiality classes |
| Collaboration | Revised versions by email | Tasks, comments and data collection forms |
| Verifiability | Latest file version without approval | Revision with every approval, activity log |
| Deletion | Concept without evidence of execution | Deletion rules with task log in the export |
| Continuity risk | Knowledge with one person or the external advisor | Documentation visible to everyone authorized |
In practice
This Is What It Looks Like in preeco | data protection
The three building blocks that jointly maintained GDPR documentation rests on.
Processing Activities and Systems
Processing activities under Art. 30 GDPR in a structured form, import of existing records as DOCX or XLSX and an automatic PDF revision with every approval.
Risk Analysis and Impact Assessment
Guided data protection impact assessment under Art. 35 GDPR, taking over details from the linked processing activities, with the assessment status Acceptable, Act/Review or Unacceptable and graphical risk mapping.
Deletion Concept
Deletion classes linked to processing activities, deletion rules describing the specific procedure, reminders for due deletion checks and an export with the task log as evidence.
What the switch means in practice
The switch is primarily an organizational task. The content already exists; it gets a structure in which responsibility, references and status are recorded. Gaps become visible along the way: a processing activity without a deletion class, an impact assessment whose processing activity changed long ago, an incident without a link to the records. These gaps are better found during the switch than during an inquiry from the supervisory authority.
A cloud environment of preeco | data protection is ready within 48 hours on working days. Onboarding includes setting up the organizational structure, user groups and permissions, an optional master data import and online training for administrators and users. Also plan time for clarifying the substance: who is responsible for which processing activity, who approves documents, and which retention period actually applies?
Three mistakes that make the selection unnecessarily hard
Confusing software with advice. Software does not replace a data protection officer, and an external data protection officer does not replace maintained documentation. Clarify in advance who maintains the content in the system and who advises.
Looking only at the records. The records are the foundation, but impact assessments, incidents and the deletion concept build on them. Check in your test whether these documents are connected to the processing activities.
Testing with someone else's examples. Run through a case of your own: one processing activity, an impact assessment for it, a fictitious data breach and the matching deletion class. Have the test carried out by the person who handles data protection day to day.
How to tell that it is time
Files and folders are not a mistake at the start. They become a risk once at least one of these points applies:
- Several legal entities, locations or clients have to be documented separately.
- The external data protection officer maintains your documentation in their own files.
- You cannot say which processing activities a data breach would affect.
- The deletion concept exists, but nobody can prove it is being implemented.
- Only one person knows where each document is.
If none of these apply, files are still fine. If two or more apply, your filing is already working against you.
How a selection works specifically in small and mid-sized companies is described in the practice guide GDPR software for SMEs.
FAQ
Frequently Asked Questions About Data Protection Management Software
One that fits your organization size and your data protection needs. What matters is the number of units to be documented separately, the number of processing activities, how roles are distributed and the documentation depth you need. A small team above all needs an interface it can use without long training, and linked documents instead of separate files.
No. The data protection officer informs, advises and monitors under Art. 39 GDPR; the software is the working tool in which the documentation is maintained. The two complement each other. preeco | data protection supports multiple tenants, so external data protection officers look after several organizations in one team and switch between them with an organization selector.
No. In preeco | data protection, processing activities, data protection impact assessments, data breaches and deletion concepts are kept as linked documents. Impact assessments and deletion classes take over details from the processing activities, incidents are connected to the affected processing activities, and the "Relationships" tab shows these references graphically.
You sort your data into deletion classes linked to the affected processing activities and describe the specific deletion procedure in deletion rules, with retention periods, methods and responsibilities. Retention periods depend on data category and purpose as well as on statutory retention obligations, for example under the German Commercial Code (HGB) and Fiscal Code (AO). Tasks on the deletion rules document their execution.
Through approved revisions. In preeco | data protection every approval automatically creates an immutable revision; for processing activities, two revisions can be compared in color and checked for integrity via stored SHA-256 checksums. The activity log per tenant records who changed what and when.
Go Through Your GDPR Documentation With Us
Bring your records, an impact assessment and your deletion concept. In 30 minutes we show, using one of your cases, how these documents connect in preeco | data protection.