Conducting Prior Consultation Process
Guides the GDPR Article 36 prior consultation process with supervisory authorities when a DPIA indicates high residual risk. Covers timeline requirements, documentation, and outcome handling. Activate when DPIA residual risk remains high or when preparing regulatory submissions. Keywords: prior consultation, Article 36, DPIA, high risk, supervisory authority.
Conducting Prior Consultation Process
Overview
Article 36 requires controllers to consult the supervisory authority prior to processing where a DPIA under Art. 35 indicates that the processing would result in a high risk in the absence of measures taken by the controller to mitigate the risk, and the controller is unable to sufficiently mitigate that risk.
When Prior Consultation Is Required
Prior consultation is mandatory when all of the following conditions are met:
- A DPIA has been conducted under Art. 35.
- The DPIA identifies high risks to data subjects' rights and freedoms.
- All reasonably available mitigation measures have been applied.
- Residual risk remains high despite mitigation efforts.
Required Documentation (Art. 36(3))
The controller must provide:
- Respective responsibilities of controller, joint controllers, and processors
- Purposes and means of the intended processing
- Measures and safeguards to protect data subjects
- DPO contact details
- The completed DPIA under Art. 35
- Any other information the authority requests
Timeline
| Phase | Duration | Reference |
|---|---|---|
| Authority initial response period | 8 weeks from receipt | Art. 36(2) |
| Extension for complex cases | Up to 6 additional weeks | Art. 36(2) |
| Maximum total period | 14 weeks | Art. 36(2) |
| Processing commencement | Only after advice received or deadline expired | Art. 36(2) |
Consultation Process
Step 1: Pre-Submission Preparation
- Verify the DPIA is complete with all Art. 35(7) mandatory elements.
- Confirm all available mitigation measures have been documented.
- Document why residual risk remains high despite mitigation.
- Obtain DPO review and sign-off.
- Prepare the submission package with all Art. 36(3) documents.
Step 2: Submission
- Submit to the competent supervisory authority (lead authority for cross-border processing under Art. 56).
- Use the authority's prescribed format if available.
- Retain proof of submission with date stamp.
Step 3: Authority Engagement
- Respond promptly to requests for additional information.
- Track the 8-week deadline and any extension notifications.
- Do not commence processing until advice is received or deadline expires.
Step 4: Outcome Handling
| Outcome | Action |
|---|---|
| Authority approves | Proceed subject to any conditions specified |
| Authority provides recommendations | Implement recommendations, document compliance |
| Authority objects or restricts | Do not proceed; revise processing design; resubmit if appropriate |
| No response within deadline | Document that consultation was submitted and deadline expired; may proceed |
Member State Variations
Art. 36(5) permits Member State law to require prior consultation for processing in the public interest, including social protection and public health. Controllers must check local implementing legislation.
Common Reasons for Triggering Prior Consultation
- Large-scale biometric identification systems
- Systematic public area surveillance with facial recognition
- Processing of genetic data at population scale
- Automated decision-making with legal or similarly significant effects where mitigation is insufficient
- Novel technology processing with unpredictable risk profiles
No additional documents ship with this skill.
Related Skills
Data Subject Rights for AI Systems
Implements data subject rights mechanisms for AI systems including right to explanation of AI decisions, contestation procedures, human review, model…
Lawful Basis for AI Training Data
Assesses lawful basis for AI training data processing per EDPB April 2025 report on LLMs and general-purpose AI. Covers legitimate interest balancing…
Managing Consent for Analytics Cookies
Managing consent for analytics cookies and implementing privacy-preserving measurement. Covers GA4 privacy configuration, consent mode fallback behav…
Applying Privacy Design Patterns
Systematic application of the eight privacy design patterns per Hoepman: minimize, hide, separate, abstract, inform, control, enforce, and demonstrat…
User Input
[COMMUNITY] Assess EU Data Act (Regulation 2023/2854) compliance for connected products, data holders, and data processing service providers