AI Act Checklist for AI Agents: Articles 12 and 14

Before worrying about Article 12 logging or Article 14 human oversight, check one thing: does this AI agent's task fall inside one of the AI Act's eight Annex III areas? Only agents inside that scope face the two articles' specific legal obligations; map automatic event logging to Article 12 and a working stop-and-override mechanism to Article 14 for those agents, and keep the same controls as good practice for the rest.
An AI agent is not automatically a high-risk AI system
A DSI asked to show that the company's AI agents comply with the AI Act usually starts from the wrong question: which article applies to every agent. Most of the regulation's specific technical obligations, including Article 12 on record-keeping and Article 14 on human oversight, apply in full only to AI systems the regulation classifies as high-risk. An internal agent that drafts release notes or triages support tickets is not automatically in that category, and treating every agent as if it were invites either wasted compliance effort or, worse, a false sense that unrelated controls cover the real obligation.
Article 6 of the AI Act sets two routes into high-risk status. The first covers AI systems that are themselves, or are a safety component of, a product already subject to third-party conformity assessment under EU harmonisation legislation listed in Annex I. The second is more relevant to most software teams: "AI systems referred to in Annex III shall be considered to be high-risk." An AI agent only enters this second route if the task it performs falls inside one of Annex III's listed areas, not because it is agentic, autonomous, or built on a large language model.
Article 6(3) adds a filter even inside Annex III: a listed system is not high-risk if it does not pose a significant risk of harm to health, safety, or fundamental rights, for example because it performs a narrow procedural task or only improves the output of a completed human activity. That filter has its own hard limit: an Annex III system "shall always be considered to be high-risk where the AI system performs profiling of natural persons," with no narrow-task exception available.
For a DSI building an inventory, the practical sequence is to list what each agent is actually used for, not what model or framework it runs on, check that use against the eight Annex III areas, apply the Article 6(3) filter and its profiling exception where a listed area is involved, and only then decide which of Article 12 and Article 14's specific requirements are a legal obligation for that agent rather than a voluntary good practice borrowed from the same two articles.
The same four-step sequence is easier to follow as a diagram than as a paragraph:
List what the agent's task actually is, check it against the AI Act's eight Annex III areas, apply the Article 6(3) filter and its profiling exception, and only then treat Article 12 logging and Article 14 oversight as a legal requirement rather than good practice.
Where an agentic workflow actually lands in Annex III
Annex III lists eight areas, worded on the European Commission's AI Act Service Desk as: biometrics, where its use is permitted under relevant Union or national law; critical infrastructure; education and vocational training; employment, workers' management and access to self-employment; access to and enjoyment of essential private and public services and benefits; law enforcement, where permitted under relevant Union or national law; migration, asylum and border control management, where permitted under relevant Union or national law; and the administration of justice and democratic processes.
An agent that triages internal support tickets, drafts marketing copy, or reviews a pull request does not fall inside any of these eight areas on the face of it. An agent that screens job applicants, scores a loan or benefit application, or feeds an output into a law-enforcement or border-control decision does, which is why the same question, which Annex III area, if any, does this agent's task fall into, has to be asked agent by agent rather than answered once for an entire fleet.
Article 6(4) puts a paper trail on that judgment call: a provider that concludes an Annex III system is not high-risk must document that assessment before placing it on the market or putting it into service, which means the scope decision itself, not only the resulting controls, is something a DSI needs to be able to produce during an audit.
The obligations split cleanly along that same boundary:
| Inside Annex III (high-risk) | Outside Annex III | |
|---|---|---|
| Article 12 automatic logging | Legal obligation | Good practice only |
| Article 14 human oversight | Legal obligation | Good practice only |
| Article 6(4) classification documentation | Required before market or service | Not required |
Article 12 and Article 14, translated into agent controls
Once an agent's task is confirmed to fall inside Annex III, or a team decides to apply the same discipline as good practice regardless, Article 12 and Article 14 translate into a short list of concrete controls rather than a block of legal text.
None of these controls require guessing what regulators will accept later: each row maps to wording already published on the European Commission's own AI Act Service Desk, not to a generic security best practice relabelled for compliance, which is the difference between a control that holds up in an audit and one that merely sounds related to the article it is supposed to satisfy.
| AI Act requirement | What it means for an agent | Control that satisfies it |
|---|---|---|
| Automatic logging over the system's lifetime (Article 12) | Every tool call the agent makes needs a persistent, unprompted record | Each call is logged and linked to an agent, a ticket, and a result |
| Logs traceable enough for risk and post-market monitoring (Article 12) | The log has to show who authorised an action, not only that it happened | The log records the explicit approval granted or denied for each call |
| Effective human oversight while in use (Article 14(1)) | A person supervises the run, not only a summary afterward | Human approval is required before a specific call executes, not after |
| Understand capabilities and limits, avoid over-reliance (Article 14(4)(a)(b)) | The overseer has to know what the agent can and cannot do, and not rubber-stamp its output | Review covers the actual output, never only the agent's own summary of it |
| Override or disregard the output (Article 14(4)(d)) | A person can decide not to use the agent's result in a specific case | Each tool carries one of three states, allowed, approval, or denied |
| Interrupt or halt the system (Article 14(4)(e)) | Someone has to be able to stop the agent mid-run, safely | A run can be stopped, its identity revoked, or a tool removed, without touching other agents |
What falls outside Annex III still deserves the same discipline
None of the reasoning above removes the operational case for logging and human review on agents outside Annex III. An agent that merges code, sends a customer message, or publishes content can still cause damage that a log would have made traceable and an approval gate would have stopped, independent of which legal article applies. The difference Article 6 draws is which controls are a binding obligation with a documented classification behind them, and which are a choice a team makes because the risk is real even where the regulation does not mandate the control.
Article 14(4)(c) adds one more expectation for a high-risk system's overseer: being able to correctly interpret the system's output using the interpretation tools made available, which only works if the output a reviewer sees is the actual result of the call, not a paraphrase the agent wrote about its own work.
This is also where a ticket-review discipline already described on this blog applies without any AI Act classification attached to it: a reviewer other than the requester checking the actual delivery, and a log of who approved what, is the same shape of control whether the agent in question ever touches an Annex III task or not.
A log kept for an agent outside Annex III also keeps the classification decision honest over time. If a support agent is later given a feature that touches, say, access to an essential public service, the operational history already shows what the agent was doing before and after that change, which is the same kind of evidence Article 6(4) asks a provider to produce for an Annex III system judged not high-risk, applied here to a system that crossed into Annex III rather than one that started there.
Calibrate what gets logged to the task, not a fixed template
Article 12 does not fix one logging format for every system; it requires a level of traceability suited to the system's intended purpose. The one concrete minimum the regulation sets is narrower than agentic workflows in general: for remote biometric identification systems listed in Annex III, point 1(a), logs must at least capture the start and end time of each use, the database checked, the data that produced a match, and who verified the result. Most agentic workflows will need their own proportionate equivalent, not that specific list.
That calibration cuts both ways. A support agent whose worst-case action is a poorly worded reply does not need the same logging depth as an agent feeding a decision into one of Annex III's eight areas, and treating every agent to the biometric-identification minimum would record detail the task never produced in the first place, without making the log any more useful for the risk the agent actually carries.
Timing: when these obligations start to bite
The strictest obligations do not apply immediately. The European Commission's own description of the AI Act lists 2 December 2027 as when the strict obligations for high-risk AI systems begin, which gives a DSI a planning horizon rather than an immediate deadline for Annex III systems identified today. Article 12 and Article 14 compliance for a newly classified agent is still worth building before that date, since retrofitting logging and an oversight interface into an agent already in production is slower than designing both in from the start.
A classification done today is not necessarily permanent either: if an agent is redeployed into a new task area, or an existing task is extended into one of the eight Annex III areas, the Article 6 assessment has to be redone for that new use, not inherited from the agent's original, non-high-risk role.
That December 2027 milestone sits inside a longer phase-in schedule for the whole AI Act:
Charted, the same five milestones show how far apart the deadlines really sit:
European Commission, AI Act regulatory framework, updated 19/10/2026
| Milestone | Applicable from | Months after entry into force |
|---|---|---|
| Prohibited practices & AI literacy | 2 February 2025 | 6 |
| GPAI models & governance rules | 2 August 2025 | 12 |
| General applicability | 2 August 2026 | 24 |
| High-risk systems, Annex III | 2 December 2027 | 40 |
| High-risk systems, Annex I | 2 August 2028 | 48 |
Building this into a compliance audit
The classification memo required by Article 6(4), the per-call log Article 12 expects, and the human-approval record Article 14 implies are exactly the kind of evidence an auditor asks for months after the fact, not at the moment a system was built. Atipol's compliance-audit use case covers gathering that evidence with read-only agents, so a person reviews each control and the audit log itself records the human oversight behind that review, at atipol.ai/use-cases/compliance-audit.
For the parts of an agent's compliance picture this checklist does not cover, how the GDPR and the AI Act interact across an agent's full lifecycle, or who pays when a general-purpose AI model itself turns out to be non-compliant, see atipol.ai/agentic-ai-blog/agentic-ai-gdpr-ai-act and atipol.ai/agentic-ai-blog/ai-act-sanctions-gpai.
Keeping that evidence current matters as much as collecting it once: an agent's task, and with it its Annex III exposure, can change faster than an annual compliance review cycle, which is one more reason the log and the approval record described above need to run continuously rather than being reconstructed from memory when an auditor asks for them.
Frequently asked questions
Does Article 12 of the AI Act require logging for every AI agent, or only high-risk ones?
Only AI systems classified as high-risk under Article 6, mainly the eight areas listed in Annex III such as employment, essential services, or law enforcement, are legally required to meet Article 12's automatic-logging requirement. An agent whose task falls outside those areas can still log every call as good practice, the same way Article 12 is often implemented, but the article itself does not make that logging a legal obligation for that agent.
What must an AI agent's human overseer be able to do under Article 14?
Article 14(4) lists five things an overseer must be able to do: understand the system's capabilities and limits, avoid over-relying on its output, correctly interpret that output using the tools made available, decide not to use the system or override its result in a specific situation, and interrupt or halt the system so it comes to a safe stop. Article 14(1) also requires the system itself to be built so a person can supervise it throughout its use, not only review it afterward.
If an AI agent is not high-risk under the AI Act, does a company still need to document that?
Yes, for a system inside one of Annex III's eight areas that a provider judges not high-risk under the Article 6(3) filter: Article 6(4) requires documenting that assessment before the system is placed on the market or put into service. For an agent that never falls inside Annex III in the first place, the AI Act does not impose this specific documentation duty, though keeping a record of why an agent was judged out of scope is still useful evidence for an audit.
Sources
- European Commission, AI Act Service Desk, Article 6, consolidated text as of 27/07/2026
- European Commission, AI Act Service Desk, Annex III, accessed 11/11/2026
- European Commission, AI Act Service Desk, Article 12, consolidated text as of 27/07/2026
- European Commission, AI Act Service Desk, Article 14, consolidated text as of 27/07/2026
- European Commission, AI Act regulatory framework, updated 19/10/2026
The public demo shows a fictional organization at work, no account needed. The free plan includes a project, three agents and an agent lead.
