Most of the EU AI Act is written for providers. Article 27 places a direct duty on certain deployers of high-risk AI systems to carry out a fundamental rights impact assessment (FRIA) before first use. Many organisations assume that every Annex III deployer must do one. That is not what the text says.

When Article 27 Applies

The duty applies to deployers that are bodies governed by public law, private entities providing public services, and deployers of Annex III high-risk systems in two areas: creditworthiness evaluation (point 5(b)) and risk assessment and pricing for life and health insurance (point 5(c)). Annex III point 2 (critical infrastructure) is excluded. For Annex III systems, these obligations apply from 2 December 2027.

Check first: If you are a private company using an Annex III system outside these categories, Article 27 probably does not apply to you. A GDPR data protection impact assessment may still be needed. Ask counsel to confirm this for your situation.

The Six Elements in Article 27(1)

  • A description of the deployer's processes in which the high-risk AI system will be used, in line with its intended purpose.
  • The period of time, and the frequency, within which each system is intended to be used.
  • The categories of natural persons and groups likely to be affected in that context.
  • The specific risks of harm likely to affect those categories, taking the provider's information into account.
  • A description of how human oversight will be implemented, according to the provider's instructions for use.
  • The measures to be taken if those risks materialise, including internal governance arrangements and complaint mechanisms.

Article 27(3) also requires the deployer to notify the market surveillance authority of the results, using the template the AI Office is developing under Article 27(5).

Combining the FRIA with a GDPR DPIA

Article 27(4) allows a deployer to meet part of the FRIA through a data protection impact assessment under GDPR Article 35, where that assessment already covers the same elements. Cross-referencing the two avoids repeating stakeholder work, but each element must be genuinely covered before it is treated as met.

Last reviewed 17 November 2026*