How it works today in most companies
The documentation is in place. The records of processing are complete, the data processing agreements are filed, the technical and organisational measures are described. For a few weeks everything is current. Then the real work begins: contracts expire, service providers change, a department introduces a new tool, and once a year everything is supposed to be reviewed anyway.
This work is usually organised in the data protection coordinator's calendar. There is a recurring reminder "Review DPA newsletter provider", every March. A second one says "TOM review IT", a third "Go through HR processing activities". Only she knows which reviews exist in total. For an overview she also keeps a file "Review_plan_data_protection_2026.xlsx", in which she marks completed reviews by hand with a date.
A review falls due, and the actual work lies with others. So the coordinator writes an e-mail to the head of IT: "Could you check by the end of the month whether the TOMs for the new data centre are still correct?" The answer arrives three weeks and one reminder later, as an attachment named "TOM_feedback_v2.docx". The coordinator copies the changes into the documentation, files the e-mail in a folder and ticks off the row in the spreadsheet.
Permissions are handed out the same way. Whoever is supposed to contribute gets an account, and because nobody has time to work out permissions in detail, many get the same role as the coordinator. The external data protection officer has full access too, although reading would be enough. That the manager of a store sees documents that are none of their business goes unnoticed.
Each of these workarounds is reasonable on its own. Together they produce documentation whose currency depends on one person: on her calendar, her mailbox and her memory.
The moment it becomes visible
It usually becomes visible in one of two moments. The first is an audit or a customer's supplier assessment: "When did you last review the processing agreement with your hosting provider, and who did it?" The answer is somewhere in an e-mail folder, but not with the contract in question.
The second moment is a change of staff. The coordinator goes on parental leave or leaves the company. Her recurring reminders run into a deactivated mailbox, nobody but her understands the spreadsheet, and the open requests to colleagues exist only as sent e-mails. The documentation has not disappeared. But nobody knows any more what has to be reviewed when.
The analysis
Five Reasons Documentation Goes Stale
They do not come from carelessness. They come from keeping dates, requests and permissions in tools that know nothing about the documentation.
View collaboration in preecoReview dates live in a personal calendar
A recurring reminder only knows its owner. If she is away, nobody is reminded of the annual review, and the records go stale unnoticed.
Requests by e-mail have no status
Whether a request has arrived, is in progress or is done is recorded nowhere. Follow-ups happen by gut feeling, and open requests get lost in full mailboxes.
The evidence sits next to the document
Who completed a review and when is stored in a mail folder or a spreadsheet row. In an audit this trail has to be pieced together by hand.
Too many permissions for too many people
Whoever needs to contribute quickly gets full access. People then see and change documents outside their area, and the documentation itself becomes a data protection risk.
A change of staff erases the memory
Dates, requests and context sit in one person's calendar and mailbox. When she leaves, her successor starts with a search instead of the work.
The target process in six steps
Documentation stays current when review dates, requests and permissions are attached to the document itself instead of calendars and mailboxes. These six steps describe the process, independent of the tool.
1. Define organisations and roles. First, clarify who works where and what they may do there. In preeco | datenschutz, organisations map the structure of the company, such as divisions, departments and sites. User groups bundle the permissions per module: read, edit, create, delete, release. The data protection officer gets a read-only role, the departments one that edits their own records.
2. Invite the team. New colleagues receive an invitation with the right user group and only the organisations they work in. Someone assigned to a single store sees only that store's documents.
3. Form responsibility groups. Work that a team does gets a group as its recipient, for example "IT team" or "Store managers". Groups are named after the function, not the people.
4. Assign tasks on the document. Instead of an e-mail there is a task with a title, priority and due date, linked to the contract or measure it concerns. It is assigned to one person, several people or a group. Those involved are notified, comment directly on the task, attach files and mark it as done.
5. Store reviews as review reminders. Every recurring review is entered on the document itself: date, repetition, assignees and a short message. On the due date the review reminder creates a task for the assigned people or groups. One overview shows all review reminders across all modules.
6. Handle handovers in the system. If someone is away only temporarily, for example on parental leave, the account is deactivated. If someone leaves the team, their access is removed, and a successor, a person or a group, takes over their tasks and review reminders.
How often to review
For most documents the GDPR sets no fixed review interval. It requires the records under Art. 30 GDPR to reflect the actual state and the measures under Art. 32 to be reviewed regularly. In practice, an annual review works well for processing activities and contracts, and a shorter one for high-risk measures. More important than the interval is that it is kept and can be evidenced.
Before and after compared
| Criterion | Before: calendar, e-mail and spreadsheet | After: review reminders, tasks and roles |
|---|---|---|
| Review dates | Recurring reminders in one person's calendar | Review reminders on the document, with repetition |
| Requests to colleagues | E-mail with a request and a follow-up | Task with priority, due date and status |
| Overview | Review plan spreadsheet, maintained by hand | Overview of all review reminders and "My tasks" on the dashboard |
| Evidence | Mail folder and spreadsheet row | Comments, files and completion on the task |
| Permissions | Full access for everyone who contributes | User groups and organisations per person |
| Collaboration | One person delegates, everyone else waits for e-mails | Tasks for people and responsibility groups |
| Change of staff | Dates and requests vanish with the mailbox | Successor takes over tasks and review reminders |
| Dependency risk | Currency depends on one person | Currency depends on the system and the team |
In practice
What This Looks Like in preeco | datenschutz
The three building blocks that carry the process described above.
User groups and organisations
Permissions per module, from read to release, bundled in user groups. Organisations decide which documents someone sees at all.
Tasks on the document
Tasks with priority and due date, linked to the document, for people or responsibility groups. In a list or board, with comments, files and watchers.
Review reminders
Recurring reviews on the contract, the processing activity or the measure. On the due date a task is created, and one overview shows all review reminders across all modules.
What the switch means in practice
The switch is manageable if it happens in the right order. Roles and organisations come first, because they decide who can be invited at all. Responsibility groups follow, and only then tasks and review reminders. Starting with review reminders means assigning them to people who later have to be swapped out.
The recurring reminders in the calendar are the best template. Each one becomes a review reminder on exactly the document it refers to. After that the calendar entry can be deleted, and the review plan spreadsheet has served its purpose.
Each person also sets in their profile how often they are notified: immediately, daily or weekly. For colleagues who contribute only occasionally, a weekly summary is often the better choice than every single e-mail.
Three mistakes that make the switch harder than necessary
Giving everyone the same role. Giving everyone administrator rights saves time on the first day and costs it in the audit. A separate role for the data protection officer and a restricted one for the departments are quick to set up, most easily as a copy of an existing one.
Attaching review reminders to people instead of groups. A review that comes up every year outlasts the person responsible today. Where a team reviews, the group belongs in the review reminder.
Creating tasks without a document. A task "Review TOMs" without a link is an e-mail in another form. Only the link shows on the document what was reviewed and by whom.
How to tell it is time
A calendar is enough for one person with a handful of documents. It becomes a risk when one of these applies:
- Review dates are kept in a personal calendar or a spreadsheet.
- You ask colleagues by e-mail for input on the documentation.
- Several people have full access although they look after only one area.
- You cannot say off-hand when a given contract was last reviewed.
- An absence of the coordinator would delay reviews by weeks.
If two or more apply, your documentation is current only as long as one person keeps it current.
FAQ
Frequently Asked Questions About Documentation as a Team
For most documents the GDPR sets no fixed interval. The records under Art. 30 GDPR must reflect the actual state, and the measures under Art. 32 must be reviewed regularly. An annual review is common, more often for high risks. What matters is that you can evidence the review.
A review reminder is a date on the document, optionally recurring. On the due date it creates a task for the assigned people or responsibility groups. The task is the actual work: with priority, due date, comments and the status done.
In many companies read access to the modules the data protection officer monitors is enough. A separate read-only user group separates oversight from maintaining the documentation, which lies with the coordinator and the departments.
When you remove someone's access to the team, you choose a successor, a person or a responsibility group. The successor takes over the tasks and review reminders. For a temporary absence such as parental leave, deactivate the account instead.
Each person sets in their profile how often they are notified: immediately, daily or weekly. Independently of that, they see their open tasks, including those of their responsibility groups, on the dashboard under "My tasks".
Go Through Your Review Plan With Us
Bring your calendar or your review plan spreadsheet. In 30 minutes we show how it turns into review reminders and tasks for your team.