Teams starting a GDPR programme often ask for a definitive list of required documents. The regulation does not provide one. What it does require is that you can show you comply, which is the accountability principle in Article 5(2). In practice, that means written policies, records, notices and contracts that match what your organisation actually does with personal data.
This article sets out the documents most organisations need, why each one matters, and a sensible order for producing them.
Start with the principle: documents must reflect reality#
A regulator or customer auditor will not be impressed by a polished policy that nobody follows. Before drafting anything, establish three facts:
- What personal data you collect, and from whom (employees, customers, website visitors, suppliers).
- Why you use it, and which lawful basis applies.
- Where it goes: internal systems, processors, and any transfers outside the EEA or UK.
Every document below depends on those answers. Skipping this step is the most common reason GDPR documentation ends up generic and unusable.
Documents the regulation explicitly expects#
These items are tied directly to specific obligations. Missing them is a visible gap.
| Document | Why it is needed |
|---|---|
| Record of processing activities (RoPA) | Article 30 requires controllers and processors to keep records of processing. Some smaller organisations have limited exemptions, but few can rely on them in practice. |
| Privacy notices | Articles 13 and 14 require you to tell individuals how their data is used. You typically need separate notices for customers, website visitors, employees and job applicants. |
| Lawful basis assessment and consent records | You must identify a lawful basis for each processing activity. Where you rely on consent, you must be able to show who consented, when, and to what. |
| Data processing agreements | Article 28 requires a contract with each processor, covering instructions, confidentiality, security, sub-processors and deletion or return of data. |
| Data protection impact assessments (DPIAs) | Required under Article 35 for processing likely to result in high risk, such as large-scale monitoring or sensitive data. |
| Personal data breach procedure and register | Articles 33 and 34 set notification duties. You also need to record breaches, including those you decide not to report. |
| Data transfer documentation | Where data leaves the EEA or UK, you need a valid transfer mechanism, such as standard contractual clauses, plus supporting assessment. |
Policies and procedures that make the programme work#
These are not all named in the regulation, but without them it is hard to show that you have appropriate organisational measures in place.
Governance documents#
- Data protection policy: management's commitment, scope, principles and responsibilities.
- Roles and responsibilities: who owns privacy, who approves new processing, and, where you have appointed one, the Data Protection Officer's remit and reporting line. Check whether Article 37 requires a DPO for your organisation.
- Training and awareness plan: what staff are taught, how often, and how completion is recorded.
Operational procedures#
- Data subject rights procedure: how you receive, verify, log and respond to access, rectification, erasure, restriction, portability and objection requests within the required timescales.
- Retention and disposal schedule: how long each category of data is kept, and how it is securely deleted.
- Privacy by design procedure: a simple checkpoint so new systems, vendors and projects are reviewed before launch.
- Vendor due diligence process: how processors are assessed before and during the relationship.
- Marketing and cookies procedure: consent handling, preference management and opt-out processing.
Security documents#
Article 32 requires security appropriate to the risk. Supporting documents usually include an information security policy, access control rules, incident response procedures and backup arrangements. If you already run an ISO 27001 management system, much of this exists and should be mapped rather than rewritten. Our article on what an ISO 27001 toolkit should include covers that overlap.
Records and evidence to keep#
Policies describe intent. Records prove execution. Auditors and regulators will look for the latter, so plan to retain:
- Completed DPIAs with decisions and sign-off.
- The data subject request log, with dates received, actions taken and response dates.
- The breach register and any notifications made.
- Training attendance and completion records.
- Signed processor agreements and vendor review outcomes.
- Consent records and, where relevant, withdrawal records.
- Internal review or audit results and the actions that followed.
- Management review or privacy steering group minutes.
These records are the difference between saying you comply and showing it.
A practical order of work#
Trying to write everything at once leads to stalled projects. A more manageable sequence:
- Map your data. Build the RoPA first. It drives most other decisions.
- Fix external-facing items. Update privacy notices and cookie information so they match the RoPA.
- Secure the contracts. List your processors and put compliant agreements in place, starting with those handling the most sensitive data.
- Put incident and rights procedures in place. Both have strict timescales, so teams need a rehearsed process.
- Assess high-risk processing. Run DPIAs where triggers apply.
- Formalise governance. Finalise the policy, retention schedule, training and review cycle.
Then keep the set alive. Review documents at least annually and whenever you introduce a new system, supplier or purpose for processing data.
Common documentation mistakes#
- Copying a template without adapting it to your actual processing.
- Treating the RoPA as a one-off exercise rather than a living record.
- Having a rights procedure but no log to show it was used.
- Signing processor agreements without checking sub-processor and transfer terms.
- Writing policies nobody has read or been trained on.
If you are working across several frameworks, it can help to see how other standards structure their documents. Our guides on Cyber Essentials and ECC-1:2018 show how the same ideas of policy, procedure and record apply elsewhere.
Frequently asked questions#
Does GDPR require a specific set of documents?#
No. The regulation sets obligations and expects you to demonstrate compliance. Some documents, such as records of processing, processor contracts and privacy notices, are clearly required by specific articles. Others are the practical means of meeting broader obligations.
Do small organisations need all of these documents?#
The depth can be proportionate, but the core is still needed. Even a small business needs privacy notices, processor agreements, a way to handle rights requests and a breach process. The documents can be shorter, but they should not be absent.
Who should own GDPR documentation?#
Ownership should sit with a named person or team, such as a DPO, privacy lead or compliance manager. Business units should still own their own processing entries and approve changes, because they understand how the data is actually used.
If you would rather start from a structured base than a blank page, the GDPR Toolkit is a ready-to-use documentation set you can adapt to your own processing. If you want to talk through where to begin, you can contact the AdWiser team.
