When an AI agent recommends closing an alert, someone will eventually ask why. In a bank or fintech, an agent working AML, sanctions, fraud or KYC alerts is part of a regulated control, and the answer has to come from a record, not from an engineer's memory of how the system behaved that day.
The people who answer for that control, the analyst, the MLRO, the model risk team and eventually an examiner, each need to see something different, and all of them need it to come from the same record. That is a higher bar than most AI dashboards set.
We rewrote this page on November 5, 2026. The earlier version opened with a Gartner statistic behind a paywall that we couldn't check, so it's gone. It also quoted Margaret Mitchell, and that sentence doesn't appear on the page it linked to, so we removed it too. The old examples came from trading, logistics and healthcare and pointed to a free-trial offer we don't have. This version is written for compliance teams supervising AI agents in financial crime work, and it says plainly where the rules apply and where they don't yet.
The trace, explain, decide, control, replay test is an editorial test for judging whether an AI agent explainability dashboard will hold up in front of a model risk committee or an examiner: Trace, Explain, Decide, Control, Replay. It is not a regulatory standard or a product certification.
An explainability dashboard for agentic AI decisions should show, for every decision an agent touched, what started it, which sources the agent read, the steps it took, the evidence it gathered, what it recommended and why, how sure it was and what it couldn't find. It should also show which agent and model version did the work, how much autonomy that agent had at the time, who made the final decision and with what reason, any override, and any pause or kill-switch event. If a reviewer can open one case months later and follow it from alert to decision without asking an engineer, the dashboard works. If it only shows averages and a confidence score, it doesn't.
The earlier version of this page made one point that still holds: traditional business intelligence dashboards summarize what happened, and that isn't enough once software starts acting on its own. A BI dashboard shows alert volumes, closure times and trends. It can tell you how many alerts were worked last week. It can't tell you why the agent recommended escalating one particular alert, which sources it skipped, or whether the analyst agreed.
An agent doesn't produce one output from one model. It reads an alert, decides what to look up, calls tools, reads results, and builds a recommendation over several steps. The explanation is the path, not a single score. That's why feature-importance charts borrowed from credit scoring don't go far enough here. They explain one model's output. They don't show which records the agent pulled or what it did when a source came back empty.
A note on the term. "Agentic dashboard" gets used for two different things. Some vendors mean dashboards that agents build for you, the agentic BI sense. This article is about the other sense: dashboards for watching, explaining and governing what AI agents do. If you run AI agents on regulated alerts, it's the second kind you'll be asked to show, and the design questions for agentic dashboards in that sense start with the record underneath, not the charts on top.
Good agentic AI dashboard design starts with the record, because a dashboard can only show what was recorded. For any decision, a reviewer should be able to see what started it, which sources the agent read, the steps it took, the evidence it gathered, what it recommended and why, and who made the final call. For each decision an agent touches, capture:
| Field | What to record | Why a reviewer needs it |
|---|---|---|
| Trigger | The alert, case or request that started the work, with its source system | Ties the agent's work to a specific control |
| Sources read | Each data source and record the agent consulted, and any that failed or returned nothing | Shows what the agent knew and what it didn't |
| Steps | Each action and tool call, in order, with its result | Lets someone follow the path as well as the answer |
| Evidence | The documents, transactions and matches the agent relied on | Lets the analyst check the reasoning against facts |
| Recommendation | What the agent suggested, its stated reasons and its confidence, plus the gaps it flagged | Separates the agent's view from the human decision |
| Version | Agent version, model version and configuration live at the time | Lets you replay the case against what actually ran |
| Autonomy | What the agent was allowed to do on its own that day, and who set it | Shows the control boundary at the moment of decision |
| Human decision | Who decided, what they decided, when, and the reason code | Shows accountability sits with a named person |
| Overrides and stops | Any override of the agent, any pause and any kill-switch event, with who and why | Shows the controls were actually used |
The old page listed data inputs, decision path tracking, metrics, human oversight and visualizations as the parts of a dashboard. Those were the right headings. The table above is what each one has to hold when the decisions are regulated. If you want a document your team can test this against, our audit trail and evidence checklist walks through the evidence points an examiner asks for on each alert.
Two things are easy to miss. Record what the agent didn't find, because "no adverse media found" means something different when one of three sources was down. And keep the version and autonomy fields on the record itself rather than in a separate configuration history, because that's the first thing a replay needs.
A case that looks clean because a source quietly failed is worse than a case with a flagged gap. When you assess any dashboard, ask to see a record where a source came back empty, and check that the gap sits on the record where the analyst will see it.
One record serves four audiences, and a dashboard that tries to give them all the same screen usually serves none of them well.
The executives the old page wrote for sit closest to the second view. They don't need every trace. They need to know the controls are working and where people are disagreeing with the agents.
The earlier version recommended confidence scores, sensitivity to input changes, scenario simulations and deviation analysis. Some of those help. Some give a false sense of comfort if they're shown alone.
Metrics worth putting on the oversight view:
Metrics to treat with care:
The EU AI Act is the clearest statement of what regulators mean by logs and oversight, even where it doesn't apply to your agents. For high-risk AI systems, Article 12 of Regulation (EU) 2024/1689 says the systems "shall technically allow for the automatic recording of events (logs) over the lifetime of the system". Article 14 says they must be designed so they "can be effectively overseen by natural persons during the period in which they are in use".
Article 14 also lists what the people overseeing a system should be able to do. They should stay aware of the tendency to over-rely on the system's output, which the Act calls automation bias. They should be able to interpret the output correctly, to decide not to use it or to "disregard, override or reverse" it, and to stop the system "through a 'stop' button or a similar procedure". Read that list next to the decision record above and it's close to a dashboard specification.
Two limits matter.
So Articles 12 and 14 are a design benchmark here, not a legal requirement for these agents. They're a good benchmark, because they describe what a supervisor will recognize as oversight.
In the US, the guidance changed on April 17, 2026. The OCC, the Federal Reserve and the FDIC issued revised model risk management guidance. The Federal Reserve's SR 26-2 supersedes and replaces SR 11-7, the 2011 model risk guidance, and SR 21-8, the 2021 interagency statement on BSA/AML models. If your policies still cite either one as current, they need updating.
The revised guidance says it plainly: "Generative AI and agentic AI models are novel and rapidly evolving. As such, they are not within the scope of this guidance." It doesn't set enforceable standards, and the agencies expect it to be most relevant to banks with over $30 billion in total assets. Read the attachment to OCC Bulletin 2026-13 before you rely on any summary, including this one.
Out of scope doesn't mean ungoverned. The same document says a bank's "risk management and governance practices should guide the determination of appropriate governance and controls for any tools, processes, or systems not covered in this document." In practice that means your own framework has to say who approves an agent, how its autonomy is set, how it's monitored and how it's stopped. A dashboard is where you show that framework is running.
Two voluntary references help fill the gap. NIST's AI Risk Management Framework defines explainability as "a representation of the mechanisms underlying AI systems' operation" and treats it separately from interpretability, which is about what an output means in context (NIST AI 100-1). The FINOS AI Governance Framework has a control written for agents, MI-21 Agent Decision Audit and Explainability, which calls for logging, documentation and explainability mechanisms for agent decisions. Neither is a regulation. Both are useful checklists to hold a vendor's dashboard against. For how regulators already read explainability across lending, fraud and AML, see our piece on explainable AI in finance, and for reporting workflows, how explainable AI supports automated regulatory reporting.
If you're asking which vendors provide explainability dashboards that satisfy executives and regulators, ask each vendor to show you the following on a real case, not on slides:
Ask also what the dashboard doesn't do. A vendor that says its dashboard makes you compliant, or that its agents need no human decision, is telling you something about how it thinks about accountability.
Every team owns its own human-in-the-loop review design. The dashboard only shows whether that design is being followed. For FluxForce, that record sits in AI Model Governance, which is described below with its limits.
Illustrative scenario, not a customer result.
This is an illustrative scenario, not a customer case. A mid-sized bank runs AI agents on transaction monitoring alerts. The agents gather evidence and recommend, and analysts decide. Eight months after one alert was closed, internal audit picks it for testing and asks the team to show how the decision was reached.
The team opens the case on the replay view. The record shows the alert, the agent version and model version that were live that day, and the autonomy setting: the agent could prepare cases and recommend, and it couldn't close anything on its own.
The auditor can see who decided, on what evidence and under which settings, without asking anyone to reconstruct it. The timeout flag is what makes the record trustworthy. Without it, the case would have looked complete when it wasn't.
AI agents can read alerts, gather evidence from the sources you connect, recommend an outcome with reasons and record every step. They don't own the decision. Your institution, its analysts, its MLRO and its model risk owners stay accountable for every determination, escalation, filing and model change.
| Component | Responsibility | Boundary |
|---|---|---|
| Alert source | Raises the alert from your existing monitoring, screening or fraud system | Keeps running; agents work its alerts without replacing it |
| Investigation agent | Reads sources, gathers evidence, records each step and recommends with reasons | Cannot fill gaps in data you don't hold, and flags the gaps it finds |
| Decision record | Holds trigger, steps, evidence, recommendation, versions, autonomy and the human decision | Shows what was recorded; it doesn't make a decision defensible on its own |
| Analyst | Reviews the case, decides and records a reason code | Acts within the authority your institution delegates |
| MLRO or compliance head | Watches overrides and disagreements, decides on escalations and sets agent autonomy | Accountability cannot be delegated to an agent |
| Model risk owner | Approves agent and model versions and reviews drift and override signals | Decides whether a version stays in use, changes or is rolled back |
You decide how much each agent does without review. Any setting can be changed at any time, and every agent has a kill switch.
High-risk AI systems shall technically allow for the automatic recording of events (logs) over the lifetime of the system (Article 12). They must be designed so they can be effectively overseen by natural persons while in use, with overseers able to stay aware of automation bias, interpret the output, disregard, override or reverse it, and stop the system (Article 14). Annex III lists creditworthiness and credit scoring, with the exception of AI systems used for the purpose of detecting financial fraud.
EU. Applies to high-risk AI systems only; the article uses Articles 12 and 14 as a design benchmark and does not classify AML, sanctions or fraud agents as high-risk.
2026-11-05
Sets the date of application of Sections 1, 2 and 3 of Chapter III to 2 December 2027 for AI systems classified as high-risk pursuant to Article 6(2) and Annex III, and to 2 August 2028 for systems under Article 6(1) and Annex I.
EU. Timing only; does not change the Annex III fraud-detection carve-out cited here.
2026-11-05
Generative AI and agentic AI models are novel and rapidly evolving and not within the scope of the guidance; a banking organization's risk management and governance practices should guide controls for tools not covered; most relevant above $30 billion in total assets; SR 26-2 supersedes and replaces SR 11-7 and SR 21-8.
US banks supervised by the OCC, Federal Reserve and FDIC; nonbinding supervisory guidance.
2026-11-05
Explainability refers to a representation of the mechanisms underlying AI systems' operation, whereas interpretability refers to the meaning of AI systems' output in the context of their designed functional purposes.
Voluntary framework, not regulation.
2026-11-05
Implements comprehensive logging, documentation, and explainability mechanisms for agent decisions to support regulatory compliance, security incident investigation, and decision accountability; capture all factors, inputs, reasoning steps, and outcomes.
Industry control catalogue, not regulation.
2026-11-05
| Metric | Definition | Decision guardrail |
|---|---|---|
| Override rate by agent and alert type | Decisions where the analyst decided differently from the agent's recommendation, divided by decisions with an agent recommendation, by agent and alert type. | Report by alert type; an average across types hides the scenario that matters. |
| Overrides read | Overrides reviewed by a senior person, divided by all overrides. | Read every override while an agent or version is new. |
| Evidence completeness | Decisions where every expected source was read and returned a result, by source. | A silent source failure is a gap, not a clean case. |
| Replay success | Sampled past cases that a reviewer could rebuild from the record alone, against the version live at the time. | A case that needs an engineer to explain it counts as a failure. |
| Version approvals | Agent and model versions that went live with a named approver on record, divided by all versions that went live. | Anything below all of them is a control gap. |
| Autonomy changes and stops | Every change to an agent's autonomy and every pause or kill-switch use, with who and why. | Check each entry has a reason as well as a timestamp. |
An explainability dashboard for agentic AI decisions is the visible part of a control. Underneath it sits a record of what each agent did, what it couldn't do, who decided and under which settings. Build that record first and the dashboard becomes a set of views over it: one for the analyst, one for the MLRO, one for model risk and one for whoever replays the case later.
The rules point the same way without prescribing a screen. The EU AI Act describes logs and oversight for high-risk systems from December 2027, and US guidance leaves agents to each bank's own governance. Either way, the team that can open any past case and walk through it will have an easier examination. If you want to see what that record looks like on your own alerts, request a FluxForce demo.
It's a set of views over the record of each AI agent decision: what triggered the work, the sources read, the steps taken, the evidence, the agent's recommendation and reasons, the versions and autonomy in force, and the human decision. In financial crime work, its job is to let reviewers and examiners follow and replay each case.
A BI dashboard summarizes outcomes such as volumes and trends. An agent explainability dashboard explains individual decisions: the path the agent took, what it relied on, what it missed and who decided. Some vendors use "agentic dashboard" for dashboards that agents build; this article covers dashboards for governing agents.
The trigger, every source read and any that failed, each step and tool call, the evidence relied on, the recommendation with reasons, confidence and gaps, the agent and model version, the autonomy level and who set it, the human decision with a reason code, and any override, pause or kill-switch event.
Not by name. For high-risk systems, Article 12 requires automatic logging and Article 14 requires effective human oversight, including the ability to override or stop the system. For Annex III systems those apply from 2 December 2027, and Annex III's credit-scoring entry excludes AI used to detect financial fraud.
No. The revised guidance issued on April 17, 2026 says generative and agentic AI models are not within its scope, and it supersedes SR 11-7, the 2011 guidance. It says a bank's own risk management and governance practices should decide the controls for tools it doesn't cover.
Override rate by agent and alert type, the share of overrides someone senior reviewed, evidence completeness by source, version changes with approvers, and every autonomy change, pause or kill-switch use. A single confidence score is weak on its own because it shows how sure the agent was, not whether it was right.
Only within the authority your institution gives it, and the record should show that setting on every decision. In a defensible design, a named person decides escalations and filings, and every agent can be paused with a kill switch. Your analyst makes the call.
Ask them to replay an old case against the version live at the time, show a case with a failed source, show an override and who reviewed it, change an agent's autonomy and show the record of it, pause an agent and show the event, and export a case file an examiner can read on its own.