RESOURCE — EU AI ACT
Deployer compliance checklist (Article 26, paragraphs 1-12)
Article 26 of Regulation (EU) 2024/1689 sets the obligations of deployers of high-risk AI systems. The twelve paragraphs below are each restated in plain English, with the evidence a deployer should hold to demonstrate compliance. Article 4 (AI literacy) and Article 50 (transparency) sit alongside Article 26 and are included as separate overlays.
Article 26 — the twelve paragraphs
Use the system in line with the provider's instructions
Requirement: Take appropriate technical and organisational measures so that the high-risk AI system is used according to the instructions for use accompanying the system.
Evidence to hold: Standard operating procedure per system; signed acknowledgement from each operator that they have received the instructions for use.
Assign human oversight to a competent natural person
Requirement: Human oversight must be assigned to natural persons who have the necessary competence, training and authority, and the necessary support.
Evidence to hold: Named oversight role with role description; training records mapped to Article 4; documented authority to intervene or suspend.
Without prejudice to other Union or national law
Requirement: Paragraphs 1 and 2 are without prejudice to other deployer obligations and to the deployer's freedom to organise its own resources and activities to implement the human-oversight measures indicated by the provider.
Evidence to hold: Internal note mapping Article 26 duties against parallel obligations under GDPR, sectoral law and works-council agreements.
Ensure relevant and representative input data — where you control it
Requirement: To the extent the deployer exercises control over input data, the deployer shall ensure that the input data is relevant and sufficiently representative in view of the intended purpose of the high-risk AI system.
Evidence to hold: Data-governance policy; control inventory identifying which input fields the deployer (vs. provider) owns; documented data quality checks on the controlled fields.
Monitor operation; suspend and notify on serious risk
Requirement: Monitor operation on the basis of the instructions for use. Where the deployer has reason to consider that use may present a risk within the meaning of Article 79(1), inform the provider or distributor and the market-surveillance authority without undue delay and suspend the use of the system. Report serious incidents per Article 73.
Evidence to hold: Monitoring runbook; incident log with timestamps; escalation path to provider and competent authority; documented suspension procedure.
Retain automatically generated logs for at least six months
Requirement: Keep the logs automatically generated by the high-risk AI system to the extent they are under the deployer's control. Retention is at least 6 months unless other applicable Union or national law (notably GDPR) requires otherwise.
Evidence to hold: Log export procedure; retention policy; immutable storage evidence; integration with GDPR retention rules.
Inform workers' representatives and affected workers before workplace deployment
Requirement: Employers who are deployers of a high-risk AI system in the workplace must, prior to putting it into service or use, inform workers' representatives and the affected workers that they will be subject to its use.
Evidence to hold: Works-council briefing minute; written notice to affected employees dated before go-live; intranet publication evidence.
Register use in the EU database — public bodies and Union institutions
Requirement: Deployers that are public authorities, agencies or bodies, or Union institutions, bodies, offices or agencies, shall register their use of high-risk AI systems in the EU database referred to in Article 71 before putting them into service.
Evidence to hold: Confirmed registration; internal reference to the Annex VIII Section C data submitted.
Use the provider's information for the GDPR DPIA where applicable
Requirement: Where applicable, deployers shall use the information provided under Article 13 to comply with their data-protection-impact-assessment obligation under Article 35 GDPR. The DPIA remains the deployer's responsibility.
Evidence to hold: DPIA document explicitly referencing the provider's Article 13 instructions; DPO sign-off; periodic-review cadence.
Judicial authorisation for post-remote biometric identification
Requirement: Deployers of post-remote biometric identification systems in the context of investigations for a targeted search of a suspected or convicted person must request prior authorisation from a judicial or administrative authority whose decision is binding (with the limited exemption in Article 26(10)).
Evidence to hold: Authorisation log per use; internal review of timeliness; restricted to law-enforcement deployers — does not apply to HR-tech.
Inform affected persons of high-risk-AI-driven decisions
Requirement: Deployers of high-risk AI systems referred to in Annex III that make decisions, or assist in making decisions, related to natural persons must inform the persons concerned that they are subject to the use of the high-risk AI system.
Evidence to hold: Standardised disclosure text embedded in decision letters (offer, rejection, performance review); audit trail showing the disclosure was sent.
Cooperate with competent authorities
Requirement: Deployers shall cooperate with the relevant competent authorities on any action those authorities take in relation to the high-risk AI system to implement this Regulation.
Evidence to hold: Single point of contact identified; document-production playbook; legal-hold procedure for AI-system records.
Article 4 + Article 50 overlays
Ensure sufficient AI literacy of staff and other persons handling the system
Requirement: Providers and deployers shall take measures to ensure, to their best extent, a sufficient level of AI literacy of their staff and other persons dealing with the operation and use of AI systems on their behalf, taking into account technical knowledge, experience, education, training and the context of use. In force since 2 February 2025.
Evidence to hold: Role-based literacy mapping; documented training per person with timestamp; refresher cadence.
User-facing AI-interaction notice
Requirement: Providers shall ensure that AI systems intended to interact directly with natural persons are designed so that those persons are informed they are interacting with an AI system, unless this is obvious from the context. Applies from 2 August 2026.
Evidence to hold: Disclosure copy reviewed; placement near first point of interaction; accessibility check.
Emotion-recognition / biometric-categorisation notice (deployer)
Requirement: Deployers of emotion-recognition systems or biometric-categorisation systems shall inform the natural persons exposed to the system of its operation and process personal data in accordance with the GDPR and the Law Enforcement Directive. Applies from 2 August 2026.
Evidence to hold: Pre-exposure notice; lawful-basis assessment under GDPR; record of any explicit consent if relied upon.
Deep-fake and public-interest text disclosure (deployer)
Requirement: Deployers of an AI system that generates or manipulates image, audio or video content constituting a deep fake shall disclose that the content has been artificially generated or manipulated. Deployers of AI systems generating text published with the purpose of informing the public on matters of public interest must disclose the AI generation, with limited exemptions. Applies from 2 August 2026.
Evidence to hold: Standard disclosure caption; editorial workflow check; exemption-rationale memo if relying on Article 50(4) exemption.
How to use this checklist
- For each high-risk AI system in your inventory, walk through the twelve Article 26 rows and the four overlay rows.
- Mark each row as Present / Partial / Missing and attach the document reference for the evidence column.
- Missing items become work-package tickets with an owner and a target date. Partial items either get closed or trigger an explicit accepted-risk note signed by the executive owner.
- Re-run the checklist after every provider version upgrade, every Article 73 serious-incident report and at least annually.
Article 27 FRIA — separate workflow
Article 27 obliges certain deployers (public bodies, private operators of services of general interest, and deployers of two specific Annex III sub-points) to perform a fundamental-rights impact assessment before first use. It is not folded into the Article 26 checklist because the triggers and the evidence pack differ. Private HR-tech deployers should still consider running FRIA as best practice and as preparation for customer due-diligence questionnaires.
Phasing — what applies when
- 2 February 2025: Article 4 AI-literacy and Article 5 prohibited-practices apply.
- 2 August 2025: Governance, GPAI and penalty provisions apply.
- 2 August 2026: Annex III high-risk regime, Article 26 deployer obligations, Article 27 FRIA and Article 50 transparency apply; supervision and enforcement framework operational.
- 2 August 2027: Article 6(1) Annex I product-embedded high-risk regime (AI as safety component or product covered by Union harmonisation legislation — machinery, medical devices, etc.).
- Note: The Digital Omnibus political agreement of 7 May 2026 proposes to postpone certain Annex III high-risk deadlines. Until formally adopted and published in the Official Journal, the dates above remain authoritative.
Sources
- Regulation (EU) 2024/1689 (AI Act), Articles 4, 5, 26, 27, 50, 71, 73, 79 and Annex III — eur-lex.europa.eu/eli/reg/2024/1689/oj
- Regulation (EU) 2016/679 (GDPR), Articles 13, 22, 35.
- European Commission AI Act Service Desk — Article 26 explanatory notes (current 2026).
Note: PowerQuant supplies software and documentation for use in your internal compliance process — not legal advice. The applicability of each Article 26 paragraph depends on your specific deployment context.
PowerQuant Module 1
Twelve-paragraph Article 26 evidence pack, prepared from your system inventory and signed by your nominated oversight role. Delivered in 5 working days. Fixed fee, no subscription.
Price in EUR: FOUNDER_DECISION (placeholder pending Alex confirmation).