A GDPR audit checklist covers six blocks: scope and governance, processing and lawful bases, transparency, suppliers and transfers, security, and rights, breaches and remediation. For each line, collect an answer and a document that proves it. Score what is done, in progress or missing to decide what to fix first. Moroccan companies should add Law 09-08 and CNDP filings to the same list.
- Six blocks: governance, processing, transparency, suppliers and transfers, security, rights and breaches
- Every line needs an answer and a proof
- Score each line: done, in progress, missing
- Add Law 09-08 and CNDP filings if you operate in Morocco
- The checklist finds gaps; remediation closes them
A credible GDPR audit defines its scope, links every processing activity to a purpose and lawful basis, reviews transparency, contracts, transfers, security and operational procedures, then converts gaps into owned and prioritised remediation actions.
Control areas8Core audit coverage
OutputRoadmapPrioritised findings
FormatPDFDownloadable checklist
01Scope and governance
Entities and activities
List the entities, products, locations, teams and systems included in the audit.
Accountability
Identify business, IT, security, HR, marketing, legal and executive owners.
Existing evidence
Gather previous audits, DPIAs, incidents, regulator correspondence and remediation plans.
Talk to a DPO for 30 minutes, free of charge: they tell you what applies to your company and where to start.
02Processing, lawful bases and transparency
Inventory
Compare the record of processing with actual applications, files, forms and working practices.
Lawful bases
Document the lawful basis for each purpose rather than defaulting automatically to consent.
Notices
Review information provided to customers, candidates, employees, users and prospects.
03Vendors, transfers and security
Processors
Review roles, instructions, contracts, subprocessors and end-of-contract deletion or return.
Transfers
Identify hosting, support and remote access outside the EEA, then document the mechanism and assessment.
Security
Connect organisational and technical measures to risk, including access, backups, encryption, logging and continuity.
04Rights, breaches and remediation
Rights requests
Test intake, identity verification, internal search, decision, response and deadline evidence.
Breaches
Review the incident register, escalation, risk assessment and notification preparation.
Action plan
Assign priority, owner, deadline, dependencies and closure evidence to every finding.
05How to use this checklist
Use the checklist as a working document rather than a one-off questionnaire. Assign each block to the person who actually knows the answers, collect the supporting document for each line, and mark the status. The aim is not to produce a perfect score but to know, in one view, what is solid, what is partial and what is absent.
A line without evidence is an assumption. Auditors, customers and investors will ask for the document, so collect it while you answer.
06Scoring your results
Give two points for done and documented, one point for in progress, and zero for missing. Divide your total by the maximum to get a percentage. It is an internal prioritisation tool, not a certification.
| Score | Reading | Next step |
|---|---|---|
| Below 40 % | Foundations missing | Start with governance, record and supplier contracts |
| 40 to 70 % | Foundations in place, significant gaps | Three-month action plan |
| 70 to 90 % | Good level | Document and maintain |
| Above 90 % | Very good level | Annual review and project-based checks |
Do not publish this score as 'compliance'. It is a working indicator, and no official GDPR certification exists for companies.
07Priorities when many lines are empty
| Priority | Action | Why first |
|---|---|---|
| 1 | Name an owner and open a record of processing | Everything else depends on knowing what you process |
| 2 | Sign processor agreements with the suppliers holding most data | The most requested document in customer reviews |
| 3 | Check transfers and hosting locations | Frequent hidden gap with cloud tools |
| 4 | Fix access control and leavers | Cheap and reduces real risk |
| 5 | Write retention rules and apply them | Less data to protect and to disclose |
08Evidence to collect for each block
| Block | Documents |
|---|---|
| Governance | Owner appointment, policies, training records |
| Processing and lawful bases | Record of processing, legal basis per purpose |
| Transparency | Privacy notices, cookie banner, employee notices |
| Suppliers and transfers | Processor agreements, sub-processor list, transfer documents |
| Security | Access matrix, backup test, encryption evidence, patching policy |
| Rights and breaches | Request log, incident procedure, breach register |
09Adding the Moroccan layer
These items sit alongside the GDPR lines. Companies that work with Europe usually need both lists, and a single inventory feeds both.
- CNDP filings and receipts for each processing activity
- Authorisations for sensitive data, CIN numbers or biometrics where relevant
- Transfer authorisations for tools hosted outside Morocco
- Information notices that mention the CNDP receipt number
- Employee information on CCTV, geolocation and monitoring
10Who should answer which block
| Block | Best placed to answer |
|---|---|
| Governance | Management and compliance lead |
| Processing and lawful bases | Business owners with the compliance lead |
| Transparency | Marketing, HR and legal |
| Suppliers and transfers | Procurement and IT |
| Security | IT or security lead |
| Rights and breaches | Compliance lead and customer service |
11From checklist to action plan
Once the checklist is complete, convert every missing or partial line into an action with an owner, a deadline and a completion criterion. Review the plan monthly for the first quarter. If you need an independent view or a scoped audit, a short call is usually enough to decide how much outside help you need.
12More questions answered
How long does it take to complete the checklist?
One to two hours with the right people in the room, longer if several entities or sites are involved.
Can we send the completed checklist to a customer?
A summary is more useful than the raw list. Share the evidence a customer asked for and keep detailed gaps for internal use.
Is the checklist enough to be compliant?
No. It identifies gaps. Compliance comes from fixing them and keeping the evidence current.
Should we repeat it?
Yes, once a year and after any major change such as a new tool, a new activity or a new European customer.
Does it cover Law 09-08?
The additional Moroccan lines above do. Add your CNDP receipts and transfer authorisations to the evidence list.
Can you review our answers?
Yes. A free 30-minute call with a DPO helps you turn the answers into a prioritised plan.
13Move from checklist to a documented decision
Define an audit scope that can be completed
A GDPR audit may cover one legal entity, a product, a function such as HR, a digital channel or the entire privacy programme. Scope should identify the systems, time period, countries, groups of individuals and vendors reviewed. Without those boundaries, price and timing become uncertain and findings tend to remain too generic.
The engagement should also state interviewees, samples, rating criteria and exclusions. A documentary GDPR audit can test whether records, notices, contracts and operational evidence are consistent. It does not automatically include penetration testing, security certification or a legal opinion covering every regulatory regime relevant to the organisation.
Build a controlled evidence room
Create a simple structure linking each control to dated evidence: records of processing, notices, forms, contracts, retention decisions, access reports, incident tickets, rights-request exercises and committee minutes. A policy that is not applied is insufficient; the review should compare written commitments with systems and observed working practices.
Evidence should be proportionate and protected. The audit does not require unlimited disclosure of personal data. Define temporary access, confidentiality, copy retention and authorised reviewers before collection, especially where the material contains employee, health or security information.
Turn findings into a funded roadmap
Each finding should identify the observed fact, supporting evidence, risk, relevant requirement and recommended action. Priority should reflect potential impact, likelihood, regulatory urgency, technical dependencies and effort. A collection of document templates without an owner, deadline and acceptance criterion is not an operational remediation plan.
After the closing meeting, leadership decides which risks to address and assigns owners and budgets. Closure evidence should be agreed in advance and then checked. Follow-up testing can confirm implementation, but it cannot create permanent assurance because processing, vendors, technology and applicable guidance continue to change.
14Get the PDF version
Receive the structured PDF version for your audit preparation.
15Frequently asked questions
Is a GDPR audit mandatory?+
Not in every case, but controllers and processors must be able to demonstrate and monitor compliance.
How long does a GDPR audit take?+
It depends on scope, processing complexity, legal entities, vendors and the availability of evidence.
What is the difference between an audit and remediation?+
The audit establishes findings. Remediation implements and documents the chosen corrective actions.
Does a GDPR audit include penetration testing?+
Not normally. Deep technical testing requires a qualified cybersecurity specialist.
What should the final report include?+
Scope, methodology, findings, risk levels, recommendations, priorities, owners and limitations.
This guide provides a general framework and does not replace an assessment of your circumstances or reserved legal advice.
16Need a scoped GDPR audit?
RGPD Conseil Maroc reviews the evidence and delivers a prioritised, decision-ready roadmap.
17Download the
full checklist.
The same checklist as a one-page PDF. Download the GDPR audit checklist (PDF) ↓
Keep reading
GDPR compliance
Audit, record of processing, policies and procedures: your Law 09-08 and GDPR compliance built on your real processing.
See the offer ↗ Free 30-min call ↗