GDPR Compliance RAID Log
This is a practical guide to building a raid log for a gdpr compliance project — a consolidated log of Risks, Assumptions, Issues and Dependencies, adapted to the realities of achieving GDPR data-protection compliance.
What a RAID Log is
A raid log is a consolidated log of Risks, Assumptions, Issues and Dependencies. For the full concept and how it works in general, see RAID Log. On a gdpr compliance project it plays the same role, tuned to this kind of work.
Why it matters for a GDPR Compliance project
GDPR Compliance projects live or die on achieving GDPR data-protection compliance. A well-built raid log gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how gdpr compliance projects drift into avoidable delay and cost.
What to include
- Risks
- Assumptions
- Issues
- Dependencies
- Owners and status
GDPR Compliance-specific considerations
Tailor the raid log to the risks that most often derail gdpr compliance projects:
- Data mapping and records
- Consent and rights processes
- Ongoing accountability
Example
On a real gdpr compliance project, the raid log would be shaped by achieving GDPR data-protection compliance. In particular, it should explicitly account for the project’s biggest risks — data mapping and records, consent and rights processes, ongoing accountability — rather than treating them as afterthoughts.