Most organizations find out how complete their records are the first time a data subject asks what is held about them. If the answer requires emails to several departments and a week of manual research, the inventory exists on paper but does not work in practice. This article explains how to test your PDPL records of processing activities Article 19 readiness, using a four-field completeness test and a cross-reference method, so that access, erasure and portability requests can be answered from the record itself.
Note on scope: the Personal Data Protection Law (PDPL) is issued in the Kingdom and supervised by SDAIA, with detail in its implementing regulations. Confirm the exact article wording and current requirements against the published text before relying on any summary here.
Why access requests expose weak records
A data-subject request asks questions the record should already answer. What do you hold about this person? Why? For how long? Who else has received it? An inventory built as a list of systems and data categories usually answers the first question only. The rest sit in people's heads, contracts or separate spreadsheets.
The common cause is granularity. Records are written per department or per system, while requests and inspections are concerned with purposes. One system may serve several purposes, each with its own lawful basis, retention need and recipients. If the record does not separate them, the answer cannot be precise.
The four-field completeness test
Pick a single processing purpose, for example payroll, customer onboarding or marketing, and check whether the record states four things at that purpose level, without anyone needing to be asked.
- Purpose-specific lawful basis. The basis relied on for this purpose, and where consent is the basis, a pointer to the consent receipts. A single basis recorded for a whole system fails this test.
- Retention period and trigger. How long data is kept for this purpose, what event starts the clock, and what happens at expiry. Without this, an erasure request cannot be assessed.
- Third-party recipients. Each processor or recipient of data for this purpose, not a general statement that data is shared with service providers.
- Cross-border transfers. Whether data leaves the Kingdom for this purpose, to whom, and the assessment supporting the transfer.
Run the test on five or six purposes of different kinds. A record that passes on HR may fail on marketing. Score each field as complete, partial or absent, and note who had to be consulted to fill the gap. That last note shows where the knowledge actually sits.
What each field decides in a request
- Access: needs the purposes, recipients and retention periods for the data held about the person.
- Erasure: needs the retention trigger and the lawful basis, so you can tell whether deletion is due, or whether another obligation lets you keep the data.
- Portability: needs to know which data was provided by the person and which system holds it, so the extract is complete and bounded.
If one field is missing, the request becomes a research project, and the answer is likely to be slow or inconsistent.
The cross-reference method
A record can look complete and still disagree with the rest of the program. Cross-referencing checks that the processing record, consent receipts, retention schedule and transfer assessments tell the same story.
- Start from the record. Take each purpose row and its four fields.
- Match to consent receipts. For every purpose relying on consent, confirm that receipts can be located and that their wording matches the purpose in the record.
- Match to the retention schedule. Confirm that the period in the record equals the period in the schedule, and that systems actually apply it.
- Match to transfer assessments. For every cross-border recipient, confirm an assessment exists and covers that purpose.
- Match to contracts. Check that each named recipient appears in a contract or processing agreement that reflects the purpose.
- Log mismatches. Record each discrepancy with an owner and a correction date.
Mismatches are the useful output. They show where the documents have drifted apart, which is where an inspector or a requester will find a problem.
Signs it is time to act
- Answering a request depends on one person who knows where the data is.
- The inventory lists systems but not purposes.
- Retention periods exist in a policy but not in the record.
- Recipients are described generally rather than named.
- An SDAIA inspection or a significant request is expected and nobody has tested the record against either.
- Different teams give different answers about the lawful basis for the same activity.
What a good outcome looks like
A good outcome is practical rather than cosmetic. A DPO can open the record, select a purpose and read the lawful basis, retention period and trigger, recipients and transfer position. The consent receipts, retention schedule and transfer assessments agree with it. A request can be answered from the record, with a short check by the relevant owner, rather than from a fresh investigation. Ownership is also clear: each purpose has a named person responsible for keeping its row current when systems, vendors or uses change.
How we run this work
Our Personal Data Protection (PDPL) Program covers data inventory and records of processing, lawful bases, notices, data-subject rights, breach notification, transfers and DPO support. The project runs 8–12 weeks in four stages.
- Discover: interviews and data mapping across departments and systems.
- Assess: gaps against PDPL and its implementing regulations.
- Build: notices, processes, templates and controls.
- Operate: training, DPO support and first compliance review.
The four-field test and cross-reference method belong in the Discover and Assess stages, where purpose-level detail is gathered and compared with the documents already in place. Deliverables include the records of processing activities, privacy policy and notices, a data-subject request workflow, a breach response and notification plan, and a privacy impact assessment template.
A frequent related question is whether a data protection officer is required. It depends on the nature and scale of your processing under the implementing regulations. We assess this with you and can support the role on an interim basis.
Next step
If you are unsure whether your records could answer a request tomorrow, start by running the four-field test on a handful of purposes. If the gaps are wider than expected, our Personal Data Protection (PDPL) Program can take you from inventory to a working request process and a first compliance review.