Data Protection Readiness Checklist
Compliance starts with an inventory, not a policy: what personal data you hold, why, for how long, who else receives it, and what happens when there is a breach.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Data Protection Readiness Checklist?
Data protection compliance starts with an inventory rather than a policy. Almost every obligation that follows, retention, access requests, breach reporting, depends on knowing what personal data you hold and where it is, and the systems that cause problems are the ones nobody thinks of as systems: a spreadsheet, a shared inbox, a form tool.
The cheapest compliance work available is deleting what you cannot justify holding. Data you do not hold cannot be breached, cannot be requested, and does not need a retention rule.
- Starts with the inventory, because every other duty depends on it
- Treats deleting unjustifiable data as the cheapest compliance work available
- Covers the privacy notice as a factual statement rather than a template
- A breach section built around the notification clock and an internal reporting route
- Editable and exportable as PDF, CSV, Markdown or a Google Form
Updated
How to use the Data Protection Readiness Checklist
- List every place personal data lives, including spreadsheets, inboxes, form tools and backups.
- Write down the lawful basis for each category, flag anything sensitive, and delete what you cannot justify.
- Set a retention period per category and automate the deletion.
- Publish a privacy notice that names the real recipients, and name an owner for access and deletion requests.
- Write down how a breach is reported internally, know your notification deadline, and walk through one scenario.
Worked examples
Starting from nothing
Input
Inventory section
Output
Data mapped, lawful bases written, unjustifiable data deleted
Everything else depends on knowing what you hold.
A subject access request arrives
Input
Rights section
Output
Named owner, known deadline, every copy locatable
You generally cannot ask what the request is for.
A spreadsheet emailed to the wrong person
Input
Breach section
Output
Reported internally within hours, logged, assessed
The regulator clock starts at organisational awareness.
Background and insight
A lawful basis is required for every set of personal data you hold, and "we have always had it" is not one. Writing the basis down per category is quick and forces the useful question of whether you need the data at all. Anything sensitive, health, biometrics, beliefs, data about children, carries extra conditions in most regimes and should be minimised aggressively.
Retention is where organisations drift. Keeping everything forever is a decision rather than a default, and it is the wrong one: it enlarges every breach and makes every access request harder. A period per category, with the deletion automated, is the fix.
On people's rights, two things matter operationally. A privacy notice has to name the real third parties who receive data, because a template naming services you do not use is a written false statement rather than a harmless placeholder. And access or deletion requests arrive with a statutory deadline, you generally cannot ask what they are for, and answering them means knowing where every copy lives, which is why the inventory comes first.
Security has one unglamorous leader: misdirected email is among the most commonly reported breach causes anywhere, which makes training on it more valuable than most technical controls. Beyond that, limit access to those who need it and review the list quarterly, require two-factor everywhere personal data lives, and encrypt devices and backups, because a lost encrypted laptop is frequently not a reportable breach while a lost unencrypted one usually is.
Breach handling runs on a clock that starts when the organisation becomes aware, often 72 hours to notify a regulator, with a separate duty to tell affected individuals where the risk is high. That means staff must know within hours who to tell, which is an internal process question rather than a legal one. Keeping a log of every incident, including the ones you decide not to report along with the reasoning, is itself a requirement in several regimes.
Common use cases
Small businesses without a privacy lead
The obligations in order of what actually causes problems.
Startups before a first audit
An inventory, retention rules and processor contracts, which is most of what is asked for.
Teams handling sensitive data
The extra conditions, minimisation and access review.
Preparing for a breach
The internal reporting route and the clock, decided before it is needed.
Tips and limitations
- The shadow systems cause the breaches: spreadsheets, shared inboxes and form tools.
- Train people on misdirected email. It is among the most reported breach causes anywhere.
- Review who can reach each system quarterly. Access accumulates as people change roles.
- Log the incidents you decide not to report, with the reasoning. That is itself a requirement.
- Walk through one breach scenario with the people who would handle it. An untested process is a document.
Sources and further reading
- Data protection, UK Government. Obligations, rights and registration
- Protecting Personal Information: A Guide for Business, Federal Trade Commission. US guidance on holding and securing personal data
- Data protection in the EU, European Commission. GDPR principles, rights and transfers
Frequently asked questions
Where should a small organisation start with data protection?
With an inventory: every place personal data lives, including spreadsheets, shared inboxes, form tools, analytics and backups. Then a lawful basis for each category, then deleting what you cannot justify. Policies written before the inventory tend to describe a system nobody has.
How long should we keep personal data?
As long as the purpose requires and no longer, with a documented period per category and the deletion automated. Keeping everything indefinitely is a decision that enlarges every breach and makes every access request harder, and it is rarely justifiable.
What has to happen when a subject access request arrives?
It is answered within a statutory deadline, and in general you cannot require a reason for it. Practically, that means someone owns the process and you know where every copy of that person's data lives, which is why the inventory comes first.
How quickly must a data breach be reported?
In many regimes within 72 hours of the organisation becoming aware, with a separate duty to inform affected individuals where the risk to them is high. That makes the internal reporting route, who tells whom within hours, the part worth writing down in advance.
Do we need contracts with suppliers who handle our data?
Usually yes. Most regimes require specific terms with a processor, and you remain responsible for what they do with the data. List every supplier that touches personal data, check the contract terms, and check where the data physically goes.
Is there an in-depth guide to the Data Protection Readiness Checklist?
Yes. “Why Checklists Work, and How to Use One Properly” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.