A GDPR audit measures the gap between what your organisation really does with personal data and what the GDPR requires, then turns that gap into a prioritised action plan. It follows five steps (scoping, interviews, document review, sample checks, report), takes a few weeks for an SME and ends with a data map, a record of processing and a roadmap. At RGPD Conseil Maroc it is quoted on scope after a free 30-minute call.
- An audit measures gaps; compliance comes from fixing them
- Five steps: scoping, interviews, documents, sample checks, report
- A few weeks for an SME, two to three for a very small company
- The deliverable is a roadmap with owners and dates, not a long report
- Moroccan companies often need Law 09-08 checked in the same exercise
01In brief
A GDPR audit examines a defined scope, collects evidence, identifies deviations and produces a prioritized roadmap.
At RGPD Conseil Maroc, the audit is part of our GDPR compliance offer, quoted on request after a free 30-minute call.
02What to prepare
- Objective and scope of the processing or mission.
- Actors, tools, suppliers and flows concerned.
- Documents, contracts and decisions already available.
Talk to a DPO for 30 minutes, free of charge: they tell you what applies to your company and where to start.
03Boundaries
This content provides general information. It does not constitute legal advice tailored to any particular situation.
To compare GDPR audit costs, first compare the activities examined, interviews, required evidence and deliverables. An initial assessment, a document review and a multi-entity audit involve different work. A proposal should make those differences clear before you commit.
04Choose the audit objective
Explain the trigger: initial organisation, a European contract, an incident or a system change. Define the departments, locations and systems covered. A concrete question produces a more useful report than a request for “total compliance”. Identify staff who can explain practices and provide evidence.
05Check what will actually be examined
Ask which documents, interviews and samples are planned. Records, notices, contracts and procedures should be compared with actual operations. A documentary security review is not a penetration test. If technical testing is needed, commission a separate engagement with a suitable specialist.
06Ask for an actionable roadmap
A useful finding identifies the observation, evidence, risk and recommended action. The roadmap should support assignment of owners and deadlines. Ask for an anonymised report structure. Check whether drafting missing documents and following up remediation are included or belong to a later phase.
07Prepare an unambiguous quote request
List entities, priority activities and existing documents. Flag Moroccan requirements that need parallel assessment. RGPD Conseil Maroc defines scope and limitations before starting; read the commercial page’s published price together with those conditions. No audit guarantees that future incidents or regulatory reviews will never occur.
Illustrative example: a contact centre is preparing a tender response. A focused audit may examine campaigns, access, recordings and requested evidence. Auditing every HR and commercial function across the company would be a different scope.
08What a GDPR audit is, and what it is not
A GDPR audit is a structured review of how a company collects, uses, shares, protects and deletes personal data, compared with the requirements of the regulation. It looks at people, processes, contracts and tools, not only at documents. Its output is a list of gaps, ranked by risk, with a plan to close them.
It is often confused with other exercises that sound similar. The table below separates them, because buying the wrong one is the most common reason an audit disappoints.
| Exercise | What it answers | Does it replace a GDPR audit? |
|---|---|---|
| GDPR audit | Where are we against the regulation, and what do we fix first? | This is the audit |
| Certification or label | Does an accredited body confirm a defined scope at a point in time? | No, and no official GDPR certificate for companies exists in Morocco |
| Penetration test | Can an attacker break into our systems? | No, it covers security only |
| DPIA | What are the risks of one specific high-risk processing? | No, it covers one processing |
| Vendor questionnaire | Can this supplier be trusted with our data? | No, it covers one relationship |
09The five steps, week by week
The timing depends on size and on how quickly people are available, but the sequence is stable. A very small company can compress it into two or three weeks; a group with several entities runs the steps entity by entity.
| Week | Step | What happens | Your involvement |
|---|---|---|---|
| 1 | Scoping | Entities, processing, applicable frameworks (GDPR, Law 09-08), contacts | One kick-off meeting, existing documents |
| 2 | Interviews | HR, sales, IT, finance and management, one hour each | One hour per department |
| 3 | Document review | Contracts, policies, CNDP filings, notices, record of processing | Sharing documents |
| 3 to 4 | Sample checks | Accounts and access, backups, laptops, hosting, a few real files | Occasional access to tools |
| 4 to 5 | Report | Gap analysis, risk rating, roadmap, presentation to management | One restitution meeting |
10Who you will need to involve
The most frequent mistake is to hand the audit to IT alone. Most personal data sits in business processes, so the review only works if the people running those processes explain what they do.
| Function | What the auditor asks | Typical findings |
|---|---|---|
| HR | How are candidates, employees and leavers handled? How long are files kept? | CVs kept forever, ID copies in drawers |
| Sales and marketing | Where do contacts come from? How is consent recorded? | Purchased lists, no unsubscribe, tools outside the contract |
| IT | Who has access to what? Where is data hosted? What happens when someone leaves? | Shared accounts, former staff still active |
| Finance and procurement | Which suppliers receive personal data? Are contracts signed? | No data clause in supplier contracts |
| Management | Who owns compliance? What incidents occurred? | No named owner, undocumented incidents |
11How findings are rated
Each gap is scored on two axes: the risk it creates for individuals (and therefore for you) and the effort needed to fix it. The result is a short list of priorities, not a hundred equal items.
| Priority | Example gap | Typical timing |
|---|---|---|
| High | Sensitive data processed with no legal basis or no controls | Immediately |
| High | No processor agreement with a supplier holding customer data | Within weeks |
| Medium | Privacy notice incomplete on the website | Within the quarter |
| Medium | No tested incident procedure | Within the quarter |
| Low | Record of processing missing minor entries | Within the year |
A good audit leaves you with fewer than ten clearly named priorities. A report nobody reads does not reduce risk.
12What the final report should contain
- A data map of processing activities, flows and suppliers
- A first record of processing, ready to maintain
- The gap analysis against the GDPR and, where relevant, Law 09-08
- A risk rating for each gap with a short justification
- A roadmap with owners, dates and an effort estimate
- A management summary you can use with a client, auditor or investor
13Red flags in an audit quote
| Red flag | Why it matters |
|---|---|
| A very low price with no interviews | You will fill in a questionnaire alone and get generic output |
| No named deliverables | You cannot tell what you will have at the end |
| No roadmap | You learn the gaps but not what to do next |
| Promise of a certificate | No official GDPR certificate exists for a company |
| No mention of Moroccan law | CNDP obligations may be missed entirely |
14Example: auditing a 60-person Moroccan software company
This is an illustrative example, not a real client. A software company in Casablanca sells a product to customers in France and Belgium. Its customers send a security and GDPR questionnaire and ask for an audit right. The company commissions a four-week audit. Interviews show that customer data is copied into test environments, that two former employees still have production access, and that no processor agreement exists with the hosting provider. The report ranks these three items as high priority and proposes a 90-day plan. Six weeks later the company answers the customer questionnaire with evidence instead of promises.
15After the audit: three ways forward
None of these is imposed. The audit is useful on its own as long as someone owns the plan afterwards.
- Fix the gaps with your own team, using the roadmap as a project plan
- Ask the audit provider to run the remediation with you
- Hand ongoing follow-up to an outsourced DPO, from 4,900 MAD per month for a small company
16Audit scope when Morocco is involved
A company established in Morocco usually has to satisfy two frameworks at once. Law 09-08 requires filings with the CNDP before processing starts, while the GDPR relies on internal documentation and contracts. Auditing both together avoids doing the inventory twice and keeps the two sets of documents consistent. Ask the provider to confirm in writing that Law 09-08 and CNDP filings are in scope.
17More questions answered
How long does a GDPR audit take?
Two to three weeks for a very small company and four to six weeks for an SME, mostly depending on how quickly interviews can be scheduled and documents shared.
Who needs to be available?
A coordinator on your side, about one hour with each department head, and a few short sessions with IT for sample checks.
Does the audit include security testing?
Sample checks of accounts, backups, laptops and hosting are included. A full penetration test is a separate security service and can be recommended if needed.
Can we show the report to a customer?
Yes. A summary is usually prepared for that purpose, so customers see your measures and your plan without exposing every internal detail.
How often should an audit be repeated?
A lighter annual review is usually enough, with a full audit after a major change such as a merger, a new activity or a new hosting set-up.
What does it cost?
It is quoted on scope after a free 30-minute call, because the price depends on the number of entities, processing activities and interviews.
18Your starting dossier
- Business objective and scope
- Interviews and required documents
- Expected report and action plan
- Included remediation or separate phase
Describe the situation without submitting customer records, passwords or confidential documents in the initial form.
19Practical questions
What should I prepare before contacting RGPD Conseil Maroc?
Prepare: Business objective and scope; Interviews and required documents; Expected report and action plan; Included remediation or separate phase. Include your deadline and unresolved decisions. A summary is enough for the initial conversation.
Does an introductory call replace the engagement?
No. The introductory conversation clarifies your requirements. A proposal then defines documents reviewed, deliverables, responsibilities and price before work starts. Customer or regulator decisions are not guaranteed.
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 ↗