Skip to main content
    FRIA
    5 min readUpdated 2025-01-27

    When is FRIA Required?

    Understand the triggers and requirements for conducting a Fundamental Rights Impact Assessment under Article 27.

    Fundamental Rights Impact Assessment (FRIA)

    Article 27 of the EU AI Act requires certain deployers to conduct a Fundamental Rights Impact Assessment before deploying high-risk AI systems.

    Who Must Conduct a FRIA?

    FRIA is required when all of the following conditions are met:

  1. You are a deployer (not just a provider)
  2. The AI system is classified as high-risk (Annex III)
  3. You fall into one of these categories:
  4. - Public body / body governed by public law

    - Private entity providing public services

    - Deployer of certain Annex III systems (credit scoring, insurance, emergency services)

    Specific Triggers

    #### Public Authorities

    Any public body deploying high-risk AI must conduct a FRIA.

    Examples:

  5. Government agencies
  6. Municipalities
  7. Public hospitals
  8. State universities
  9. Regulatory bodies
  10. #### Private Entities Providing Public Services

    Private organizations performing public functions:

    Examples:

  11. Private hospitals under public contracts
  12. Utility companies
  13. Public transport operators
  14. Social service providers
  15. #### Specific Annex III Use Cases

    Regardless of public/private status, FRIA is required for:

  16. Credit scoring (essential services access)
  17. Life/health insurance risk assessment
  18. Emergency services dispatch prioritization
  19. FRIA Timing

    ScenarioWhen to Conduct FRIA
    First deploymentBefore putting the system into use
    Material changesBefore implementing significant changes
    New use caseBefore extending to new applications
    Periodic reviewAs defined in your governance policy

    What FRIA Must Include

    Article 27 specifies six mandatory elements:

    (a) Process Description

  20. How the deployer uses the AI system
  21. Intended purpose in operations
  22. Decision points affected
  23. (b) Time Period & Frequency

  24. Duration of intended use
  25. How often it will be used
  26. Scale of affected individuals
  27. (c) Affected Categories

  28. Natural persons/groups likely affected
  29. Vulnerable group identification
  30. Geographic scope
  31. (d) Specific Risks to Fundamental Rights

  32. Right-by-right risk analysis
  33. Harm categories
  34. Severity and likelihood assessment
  35. (e) Human Oversight Measures

  36. Oversight design
  37. Competence requirements
  38. Intervention authority
  39. (f) Mitigation & Governance

  40. Risk mitigation measures
  41. Governance arrangements
  42. Complaint mechanism
  43. Monitoring plan
  44. Notification Requirements

    After completing your FRIA:

  45. Notify the market surveillance authority (unless exempt)
  46. Use the prescribed template (when available)
  47. Update when circumstances change
  48. Exemptions

    You may be exempt from notification (not from conducting FRIA) if:

  49. National security exemption applies
  50. Military/defense context
  51. Research-only use (not affecting people)
  52. Integration with DPIA

    If you've already conducted a DPIA (Data Protection Impact Assessment) under GDPR, you can:

  53. Reference and build upon the DPIA
  54. Reuse relevant risk analyses
  55. Extend rather than duplicate
  56. However, FRIA has broader scope than DPIA:

    AspectDPIAFRIA
    FocusPersonal data protectionAll fundamental rights
    TriggerHigh-risk data processingHigh-risk AI deployment
    RightsPrivacy & data protectionDignity, non-discrimination, safety, etc.