Is Your Hiring AI High-Risk Under the EU AI Act?
Almost certainly, if it helps decide who gets hired, promoted or let go. Here is what the EU AI Act covers in employment, what each party owes, and the new deadline.
What counts as high-risk
Annex III, point 4 of the AI Act lists two employment uses as high-risk:
- AI used for recruitment or selection: placing targeted job ads, analysing and filtering applications, and evaluating candidates.
- AI used to make decisions affecting the terms of work relationships, promotion or termination, to allocate tasks based on behaviour or personal traits, or to monitor and evaluate performance.
Classification follows the system’s intended purpose, not who presses the final button. A human reviewer is a required control, not a route out of scope. Not every HR tool is high-risk: a chatbot that answers benefits questions is not, while a tool that ranks applicants is.
The deadline moved
The Digital Omnibus on AI entered into force on July 27, 2026 and moved the application date for Annex III high-risk obligations from August 2, 2026 to December 2, 2027. Transparency duties under Article 50, such as telling people they are interacting with an AI system, still apply from August 2, 2026.
Provider (developer) duties
- A risk-management system across the lifecycle.
- Data governance, including examining training data for possible biases.
- Technical documentation and automatic logging.
- Instructions for use and a design that allows effective human oversight.
- Appropriate accuracy, robustness and cybersecurity.
- Conformity assessment, registration and post-market monitoring.
Deployer (employer) duties
- Use the system according to the provider’s instructions.
- Assign human oversight to people with the competence, training and authority to do it.
- Make sure input data you control is relevant and sufficiently representative.
- Monitor operation and report serious incidents.
- Keep the logs under your control for at least six months.
- Inform workers’ representatives and affected workers before putting a high-risk system into use in the workplace, and inform candidates that they are subject to it.
- Carry out a data-protection impact assessment where GDPR requires one.
If you substantially modify a vendor’s system or put your own name on it, you can become the provider and take on provider duties. See developer, deployer, or both.
It reaches non-EU companies
The Act applies to providers placing systems on the EU market and to deployers in the EU, and to non-EU providers and deployers whose system’s output is used in the EU. A U.S. vendor selling to EU employers is in scope.
What to do before December 2027
- Classify each HR AI use case against Annex III.
- Providers: build the technical file, logging and bias testing into every release.
- Deployers: ask providers for instructions and documentation, set up oversight and log retention, and plan worker information.
- Run bias testing that reflects the EU markets you hire in, within GDPR limits on special-category data.
Map your hiring AI against the laws that apply to you
Whether you build HR AI or deploy it, Fairly AI tests it, monitors the rules where you operate and keeps the evidence.
Schedule a discovery call