# Gdpr Ropa Audit

> Guides the audit of Records of Processing Activities (RoPA) against GDPR Article 30 requirements for both controllers and processors. Activate when verifying RoPA completeness, validating mandatory fields, or preparing for supervisory authority inspections. Keywords: RoPA, Article 30, records audit, processing activities, controller records, processor records.

- Skill: `mukul975-2/gdpr-ropa-audit` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds add mukul975-2/gdpr-ropa-audit`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mukul975-2/gdpr-ropa-audit/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- License: Apache-2.0
- Author: mukul975 (https://skillmd.com/u/mukul975-2)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/mukul975-2/gdpr-ropa-audit

---


# Conducting GDPR Article 30 Records Audit

## Overview

Article 30 of the GDPR mandates that every controller and processor maintain written records of processing activities under their responsibility. This skill provides a structured methodology for auditing RoPA entries against the exhaustive field requirements specified in Art. 30(1) for controllers and Art. 30(2) for processors, ensuring completeness, accuracy, and readiness for supervisory authority review.

## Controller Record Requirements — Art. 30(1)

Each processing activity record maintained by the controller must contain:

| Field | GDPR Reference | Description |
|-------|---------------|-------------|
| Controller identity and contact details | Art. 30(1)(a) | Name, address, and contact details of the controller, joint controller, and DPO |
| Purposes of processing | Art. 30(1)(b) | Specific, explicit, and legitimate purposes for each processing activity |
| Categories of data subjects | Art. 30(1)(c) | Identification of all data subject groups (employees, customers, patients, minors) |
| Categories of personal data | Art. 30(1)(c) | Types of personal data processed per activity (identifiers, financial, health, biometric) |
| Categories of recipients | Art. 30(1)(d) | All recipients including processors, joint controllers, and third-country recipients |
| International transfers | Art. 30(1)(e) | Transfers to third countries or international organisations with safeguard documentation |
| Retention periods | Art. 30(1)(f) | Envisaged time limits for erasure of different categories of data |
| Technical and organisational measures | Art. 30(1)(g) | General description of Art. 32 security measures protecting the data |

## Processor Record Requirements — Art. 30(2)

| Field | GDPR Reference | Description |
|-------|---------------|-------------|
| Processor identity and contact details | Art. 30(2)(a) | Name and contact details of the processor(s), each controller on behalf of which the processor acts, and the DPO |
| Categories of processing | Art. 30(2)(b) | Categories of processing carried out on behalf of each controller |
| International transfers | Art. 30(2)(c) | Transfers to third countries or international organisations with safeguard documentation |
| Technical and organisational measures | Art. 30(2)(d) | General description of Art. 32 security measures |

## Audit Methodology

### Phase 1: Inventory Validation

1. Retrieve the current RoPA from the data protection management system or document repository.
2. Cross-reference the RoPA against the enterprise application inventory to identify processing activities not yet recorded.
3. Verify each business unit has submitted processing activity declarations by comparing against the organisational chart.
4. Check that shadow IT and informal data processing (spreadsheets, shared drives) have been captured through departmental interviews.
5. Validate that both automated and manual processing activities are represented.

### Phase 2: Field Completeness Check

1. For each controller record, verify all seven mandatory fields under Art. 30(1)(a)-(g) are populated with specific, non-generic content.
2. For each processor record, verify all four mandatory fields under Art. 30(2)(a)-(d) are completed.
3. Flag entries where purposes are described in overly broad terms (e.g., "business operations" rather than "payroll calculation for employment contract performance").
4. Confirm retention periods are expressed as specific durations or criteria rather than "as long as necessary."
5. Verify that security measures reference actual implemented controls, not aspirational statements.

### Phase 3: Accuracy Verification

1. Sample 20% of RoPA entries and conduct interviews with processing owners to verify accuracy of recorded purposes, data categories, and recipients.
2. Compare stated data flows against actual system architecture diagrams and data flow maps.
3. Validate that international transfer records match the actual data routing observed in network and application logs.
4. Confirm that listed recipients still have valid legal basis and contractual arrangements (Art. 28 agreements for processors, Art. 26 arrangements for joint controllers).

### Phase 4: Currency Assessment

1. Check the last-reviewed date for each RoPA entry against the organisation's defined review cycle (recommended: at least annually, or upon material change).
2. Identify entries that reference discontinued systems, former employees as contacts, or expired contracts.
3. Verify that new processing activities introduced since the last review cycle have been added to the RoPA.
4. Cross-reference against the change management log and DPIA register to identify unrecorded changes to processing.

### Phase 5: Reporting and Remediation

1. Produce an audit findings report categorising issues by severity: Critical (mandatory field missing), Major (field incomplete or inaccurate), Minor (formatting or administrative issue).
2. Assign remediation owners and deadlines for each finding.
3. Schedule a follow-up review within 30 days for critical findings and 90 days for major findings.
4. Update the RoPA governance procedure to address systemic gaps identified during the audit.

## Exemption Considerations

Article 30(5) provides a limited exemption for organisations with fewer than 250 employees, but this exemption does not apply when:
- Processing is likely to result in a risk to data subjects' rights and freedoms
- Processing is not occasional
- Processing includes special categories of data under Art. 9(1) or personal data relating to criminal convictions under Art. 10

In practice, most organisations with any regular customer or employee data processing will not qualify for this exemption.

## Common Audit Findings

1. **Missing processor records**: Controllers maintain their own records but fail to ensure their processors maintain Art. 30(2) records.
2. **Stale contact information**: DPO or controller representative details are outdated following organisational restructuring.
3. **Vague purpose descriptions**: Purposes are described at department level rather than per processing activity, failing to demonstrate purpose limitation under Art. 5(1)(b).
4. **Absent retention schedules**: Retention periods recorded as "in accordance with policy" without specifying the actual duration or deletion criteria.
5. **Incomplete transfer documentation**: International transfers recorded without specifying the safeguard mechanism (SCCs, adequacy decision, BCRs, or derogation relied upon).
6. **No security measure description**: The Art. 30(1)(g) field left blank or containing only "encryption" without describing the broader organisational and technical measures in place.

## Integration Points

- **DPIA Register**: Cross-reference RoPA entries flagged as high-risk with the Art. 35 DPIA register.
- **Breach Log**: Verify that processing activities involved in past breaches have updated security measures in their RoPA entries.
- **Vendor Register**: Validate that all processors listed in the RoPA have corresponding Art. 28 data processing agreements.
- **Training Records**: Confirm processing owners have completed required data protection training.