Article 31·medium·Component: Chapter IV: Controller and ProcessorWhat this control requires
Controllers, processors, and their representatives must cooperate with the supervisory authority upon request, assisting in the performance of its tasks to ensure GDPR compliance. This control addresses Supervisory Cooperation.
In plain English
Controllers, processors, and their representatives must cooperate with the supervisory authority upon request, assisting in the performance of its tasks to ensure GDPR compliance. In practice, this means you can prove you representatives controller-level controls on a defined cadence.
Why it matters
GDPR administrative fines reach the greater of €20 million or 4% of global annual turnover. The European Data Protection Board (EDPB) coordinates supervisory-authority enforcement across the EU/EEA, and DPAs publish enforcement decisions citing specific Articles.
What an auditor looks for
A DPA or privacy auditor expects: a Records of Processing Activities (RoPA) entry, a documented lawful basis, evidence the Article's data-subject right is operationalised end-to-end, a named DPO contact (where required), and Article 30 records that match what the front-end actually does.
Within Chapter IV: Controller and Processor, the assessor will trace your implementation back to the catalogue reference (Article Article 31) and look for objective evidence on the latest two assessment cycles.
How to implement
Policy Management
Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.
Operational checklist
- Representatives. Document the trigger, the owner and the cadence.
- Processor. Document the trigger, the owner and the cadence.
- Cooperation. Document the trigger, the owner and the cadence.
- Tasks. Document the trigger, the owner and the cadence.
- Supervisory. Document the trigger, the owner and the cadence.
- Scope: controller, controllers, supervisory authority.
Evidence to collect
- Policy Document. A signed and version-controlled policy / standard / procedure document.
Signed policy or standard documents the safeguard. Focus: Cooperation with the supervisory authority.
Common pitfalls
- Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.
How it maps to other frameworks
Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.
Related controls in GDPR
- Article Article 36 — Prior consultation
- Article Article 37 — Designation of the data protection officer
- Article Article 29 — Processing under the authority of the controller or processor
- Article Article 33 — Notification of a personal data breach to the supervisory authority
- Article Article 24 — Responsibility of the controller
- Article Article 27 — Representatives of controllers or processors not established in the Union
References
- European Union — GDPR
- Catalogue identifier:
Article Article 31
Topics: governance riskpolicy management