The DPIA and FRIA, run jointly: one assessment, two regimes, no duplicate work
The short answer
One investigation, two sign-offs
The DPIA and the FRIA examine the same system. Do the investigation once, then present the findings under both the Article 35 and Article 27 headings. Running two separate investigations produces duplicated work and contradictory documents.
What you will be able to do
- Distinguish what a Data Protection Impact Assessment (DPIA) under Article 35 of the GDPR (General Data Protection Regulation, Regulation (EU) 2016/679) is legally required to cover from what a Fundamental Rights Impact Assessment (FRIA) under Article 27 of the EU AI Act (Regulation (EU) 2024/1689) is legally required to cover.
- Apply the DPIA trigger test and the FRIA trigger test to one AI system and state, with reasons, whether each assessment is legally required for that system.
- Build a single crosswalk that maps every mandatory field of both regimes onto shared and regime-specific sections, so overlapping content is written once and the unique content of each is not lost.
- Produce a joint DPIA and FRIA for a high-risk system in your own organization that names the affected groups, the specific fundamental-rights harms, the mitigations, and the human-oversight measures.
- Explain why a data-protection-only assessment can pass while a discrimination harm goes unrecorded, using the difference in legal scope between the two regimes.
- Defend the joint assessment against the objection that combining the two documents weakens either one, and state the condition under which combining is legally safe.
- Identify where the joint assessment consumes your earlier artifacts (the AI systems inventory, the risk classification, the data provenance file, the conformity file) and where it feeds the evidence annex and the dossier.
- Sequence the assessment correctly in the deployment lifecycle: confirm the high-risk classification, obtain the provider's information and the data provenance, run one investigation, notify the authority, then deploy.
- Write a mitigation with teeth: a named owner, a metric broken down by the affected group, and a stop threshold, and explain why a mitigation lacking any of the three is boilerplate.
The ideas, one by one
The regimes overlap but neither contains the other
The DPIA is scoped to personal data; the FRIA is scoped to all fundamental rights but only for specific deployers. Some DPIA content (lawful basis, security) has no FRIA home; some FRIA content (non-discrimination analysis, human oversight, complaint mechanism, regulator notification) has no DPIA home. The shared center is written once.
Article 27(4) is the license to merge
The AI Act itself says the FRIA complements the DPIA where the DPIA already meets a FRIA obligation. Building one integrated document is not a shortcut; it is the legally sanctioned design.
The discrimination harm is what a data-only lens misses
A fully compliant DPIA can be produced for a system that discriminates, because disparate treatment is a fundamental-rights harm before it is a data-protection harm. The FRIA's affected-groups-and-specific-harms content is what forces the discrimination onto the page.
Know exactly who owes a FRIA
Public bodies (except Annex III point 2), private entities providing public services, and any deployer of creditworthiness or life-and-health-insurance systems. A private firm's internal high-risk hiring tool generally does not trigger Article 27, though it still owes a DPIA.
The assessment is a living document
Both regimes require review when the risk or situation changes. Build the joint assessment to be revised, and revise it when the model, the data, or the affected groups change.
Name the harm, then mitigate it
An honest assessment that names a serious harm and pairs it with an owned mitigation and a monitoring threshold is more defensible than a clean one that hides the harm. Softening a harm removes the trigger for the mitigation and leaves the harm to be found by a regulator or court.
File the FRIA
For Article 27 deployers, the assessment must be notified to the market-surveillance authority on the AI Office template. An unfiled FRIA is incomplete.
The joint assessment is load-bearing evidence
It consumes your inventory, classification, provenance, and conformity artifacts, and it feeds your evidence annex and dossier. It is one of the documents the board audit in Module 13 will pull first.
Sequence the assessment, do not tack it on
Confirm the high-risk classification, obtain the provider's Article 13 information and the data provenance file, then run one investigation, then notify, then deploy. Starting the FRIA before you have the provider's documentation forces a rewrite.
Reuse is allowed, blind reuse is not
A provider's or a prior assessment can seed the shared center, but the deployer must rewrite the context-specific FRIA wing (affected groups, frequency, human oversight). Adopting someone else's document wholesale leaves your own deployment unassessed.
The two triggers are independent
A DPIA is triggered by risky processing of personal data; a FRIA is triggered by the deployment of a high-risk Annex III system by an in-scope deployer. You can owe one without the other in either direction, so never infer one trigger from the other.
Consult the affected, do not guess about them
The most defensible affected-groups analysis draws on the people the system affects and their representatives. A desk-only analysis is the pattern a rights coalition later shows was done without genuinely looking.
Listen to it
The same lesson, talked through by two hosts as episode 79 of the podcast.
Real cases
These examples show the DPIA-and-FRIA relationship as it appears in real deployments and enforcement, with the assessment reasoning made explicit. The anchor case (France, CNAF) is treated in depth in the Section 5 scenario; here it is referenced only to connect the pattern.
Example 1: A public welfare fraud-scoring system (the pattern behind the anchor). A national benefits agency runs an algorithm that assigns every recipient a fraud-risk score. Because it processes personal data of tens of millions of people through systematic automated evaluation, a DPIA is mandatory under Article 35(3)(a) of the GDPR. Because the deployer is a public body running an Annex III high-risk system (public assistance benefits eligibility, Annex III point 5(a)), a FRIA is mandatory under Article 27 once that obligation is in force. The DPIA can find the data processing proportionate; only the FRIA's affected-groups analysis forces the agency to record that the scoring flags disabled claimants, single parents, and low-income households at higher rates. This is the anchor case pattern examined in Section 5.
Example 2: A bank's creditworthiness model (private, but still in FRIA scope). A commercial bank deploys an AI system to evaluate loan applicants' creditworthiness. The bank is a private entity, so a public-body FRIA trigger does not apply, but Annex III point 5(b) (creditworthiness and credit scoring) pulls any deployer, public or private, into the FRIA obligation. The bank also processes personal financial data at scale, triggering a DPIA. Here the joint assessment is unavoidable: both regimes apply to the same system. The DPIA covers lawful basis and data-subject rights; the FRIA covers whether the model's decisions disadvantage protected groups and what human-oversight and complaint routes exist for a rejected applicant.
Example 3: A life-insurance pricing model. An insurer uses AI to assess risk and set prices for life and health insurance. Annex III point 5(c) puts this squarely in FRIA scope for any deployer. The DPIA addresses the health data (a special category under GDPR Article 9); the FRIA addresses whether pricing produces discriminatory outcomes and whether affected people can contest a price. Two regimes, one system, one joint file.
Example 4: A city's public-transport surveillance system (FRIA yes, but note the carve-out). A municipal transport authority (a public body) wants to deploy an AI system. If the system falls under Annex III point 2 (safety components in the management of critical infrastructure, including road, rail, and other transport), the public-body FRIA trigger is expressly carved out for that point. A DPIA may still be required for the personal data. This example is the reminder that the FRIA scope has a specific exception, and reading Annex III point by point matters before you conclude a FRIA is owed.
Example 5: An internal HR screening tool at a private firm. A private company deploys a high-risk hiring-screening AI (Annex III point 4). Because it is a private entity not providing a public service, and hiring is not point 5(b) or 5(c), the Article 27 FRIA obligation generally does not bite, even though the system is high-risk and the firm has other deployer duties. A DPIA is still required because of the systematic automated evaluation of candidates. This is the case where the two regimes come apart: DPIA yes, FRIA generally no. The joint-assessment discipline still helps: running the fundamental-rights analysis voluntarily surfaces the discrimination risk that hiring tools are notorious for, even where Article 27 does not compel it. (see Topic 5.4) for the deeper treatment of hiring-AI law.
Example 6: A cross-border deployment where only one regime applies. A deployer outside the EU serves EU residents. Depending on the facts, the GDPR may apply through its territorial scope (Article 3) while the AI Act's deployer obligations attach differently. The lesson: do the regime-applicability analysis first, per system, per jurisdiction, and never assume that because one assessment is required the other automatically is, or the reverse. (see Topic 5.1) for the "does the law apply" gate.
Example 7: A hospital's diagnostic-support AI (special-category data drives the DPIA). A public hospital deploys an Annex III high-risk AI system that supports clinical decisions. As a public body deploying an Annex III system that is not point 2, it owes a FRIA. Because it processes health data at scale (a special category under GDPR Article 9), it also owes a DPIA under Article 35(3)(b). The joint assessment's shared center describes the clinical processes and the patients affected once; the DPIA wing handles the Article 9 lawful-basis and safeguards analysis; the FRIA wing handles whether the system's support decisions risk harming vulnerable patient groups and how a clinician's human oversight is exercised so the model advises rather than decides. This example shows the two wings doing genuinely different work on one system.
Example 8: A provider's assessment a deployer wants to reuse. A software provider has already produced a thorough impact assessment for its high-risk system. A deploying public body wants to avoid redoing it. Article 27(2) allows a deployer to rely, to the extent applicable, on a FRIA previously conducted or on one done by the provider, updating for its own context. The deployer cannot simply adopt the provider's document wholesale: the affected groups, the frequency of use, and the human-oversight arrangements are context-specific to the deployer. The defensible move is to take the provider's assessment as the base for the shared center and rewrite the deployment-specific FRIA wing. Reuse is permitted; blind reuse is not.
Example 9: A high-risk system with no personal data. A public authority deploys a high-risk Annex III system that operates only on aggregate, non-personal environmental readings to allocate a public service. Because no personal data is processed, no DPIA is triggered under Article 35. But because a public body deploys an Annex III system, a FRIA is still owed under Article 27. The result is a standalone FRIA, not a joint assessment. This example proves the two triggers are independent: the absence of a DPIA does not remove the FRIA, and reasoning from one trigger to the other is a mistake in both directions.
Example 10: A regulator comment mid-deployment. After a public deployer files its FRIA, the market-surveillance authority responds within the comment window and raises a concern about the human-oversight arrangements. Article 27(3), which puts the FRIA results before the market-surveillance authority, contemplates exactly this dialogue: the deployer must engage with the authority's view. The living-document design pays off here, because the deployer folds the comment and its response into the same assessment rather than starting a side document, and the exchange becomes part of the evidence that the deployment was scrutinized before launch. This is the pattern the Section 5 scenario dramatizes.
Where people go wrong
- "A DPIA is enough for a high-risk AI system." Wrong for the deployers Article 27 names. A DPIA satisfies the GDPR's data-protection scope. It does not, on its own, satisfy the FRIA's fundamental-rights scope, which reaches non-discrimination, dignity, good administration, and effective remedy. For a public body or a credit or insurance deployer, a DPIA alone leaves the Article 27 obligation unmet.
- "A FRIA replaces the DPIA." Also wrong. The two regimes are separate legal instruments with separate triggers and separate content. Article 27(4) says the FRIA complements the DPIA where the DPIA already meets a FRIA obligation; it does not say the FRIA absorbs or cancels the DPIA. Some DPIA content (lawful basis, security measures) has no FRIA home and must still be produced.
- "Combining the two documents weakens both." The opposite is true when done correctly. Combining prevents the two assessments from contradicting each other and forces one consistent set of findings. The condition for doing it safely is that every mandatory field of both regimes is present and traceable in the joint document. A crosswalk is how you prove that condition is met.
- "The FRIA is only about data protection because that is where AI risk lives." No. Data protection is one Charter right. The FRIA's defining feature is that it looks at all fundamental rights, and its most valuable output is usually the non-discrimination analysis, which a data-protection lens can miss entirely.
- "Every deployer of a high-risk system must do a FRIA." No. Article 27 targets three groups: public bodies (with the Annex III point 2 critical-infrastructure carve-out), private entities providing public services, and any deployer of creditworthiness or life-and-health-insurance systems (Annex III points 5(b) and 5(c)). A private firm running an internal high-risk hiring tool generally is not caught by Article 27, though it still owes a DPIA and other deployer duties.
- "The assessment is a one-time gate before launch." Both regimes make it a living document. The DPIA must be reviewed when the risk changes (GDPR Article 35(11)); the FRIA must be updated where the situation changes (AI Act Article 27(2)). Build the joint assessment to be revised, and revise it when the model, the data, or the affected groups change.
- "Naming a serious harm in the assessment creates liability, so soften it." The harm exists whether documented or not. Softening it removes the trigger for a real mitigation and leaves the harm to be discovered by a regulator, journalist, or court. A defensible assessment names the harm plainly and pairs it with a mitigation and a monitoring threshold. The falsification of an impact assessment is itself a governance failure.
- "Once the FRIA is written, the obligation is done." For the Article 27 deployers, the assessment must be notified to the market-surveillance authority (Article 27(3)) using the template the AI Office provides (Article 27(5)). An unfiled FRIA is an incomplete FRIA.
- "The provider did an assessment, so the deployer does not need to." Article 27(2) lets a deployer rely on a provider's or a prior assessment only to the extent applicable, updating for its own context. The affected groups, the frequency of use, and the human-oversight arrangements are deployer-specific. Blind adoption of the provider's document leaves the deployer's own context unassessed.
- "A high-risk system that does not use personal data needs neither assessment." The FRIA is not conditional on personal data; it applies to the deployment of a high-risk Annex III system by an in-scope deployer regardless of whether personal data is processed. A system could conceivably trigger a FRIA without triggering a DPIA. Do not use the absence of personal data to conclude no assessment is owed.
- "The affected-groups analysis can be done entirely from our own desk." An affected-groups section written with no input from the people the system affects, or their representatives, is the exact kind of assessment a rights coalition later shows was performed without genuinely looking. The GDPR's consultation duty (Article 35(9)) and the FRIA's affected-groups duty both point toward hearing from the affected, not guessing about them.
Questions people ask
- What is Data Protection Impact Assessment (DPIA)?
- An assessment required by Article 35 of the GDPR (Regulation (EU) 2016/679) before processing that is likely to result in a high risk to the rights and freedoms of natural persons. It must contain a systematic description of the processing, an assessment of necessity and proportionality, an assessment of the risks to data subjects, and the measures to address those risks. More on Data Protection Impact Assessment (DPIA)
- What is Fundamental Rights Impact Assessment (FRIA)?
- An assessment required by Article 27 of the EU AI Act (Regulation (EU) 2024/1689) before certain deployers put a high-risk Annex III AI system into use. It must describe the processes and intended use, the period and frequency of use, the categories of persons and groups affected, the specific fundamental-rights risks, the human-oversight measures, and the measures to be taken if risks materialize, including governance and complaint mechanisms. More on Fundamental Rights Impact Assessment (FRIA)
- What is GDPR (General Data Protection Regulation)?
- Regulation (EU) 2016/679, the European Union's data-protection law, in force since May 2018. It governs the processing of personal data and is the source of the DPIA obligation in Article 35. More on GDPR (General Data Protection Regulation)
- What is EU AI Act?
- Regulation (EU) 2024/1689, the European Union's horizontal law on artificial intelligence, in force since 1 August 2024. It is the source of the FRIA obligation in Article 27 and of the high-risk classification in Annex III. More on EU AI Act
- What is Annex III?
- The annex of the EU AI Act listing the categories of AI systems classified as high-risk, including (point 4) employment and worker management, (point 5(a)) access to essential public assistance benefits and services, (point 5(b)) creditworthiness evaluation and credit scoring, and (point 5(c)) risk assessment and pricing in life and health insurance, among others. More on Annex III
Keep going
This lesson builds AI risk and impact assessment, and that page shows the roles that hire for it. Every Certified AI Governance Professional (CAIGP) lesson.
Watch the lesson and prove it
Proving it happens inside the program: watch, explain it in your own words, and it goes on a record employers can check.
Watch the lesson and prove it →