# AI audit trail: the execution logs EU compliance teams ask for

> What an AI audit trail must show an EU compliance reviewer: the fields skilder records for every run, a sample exported record, and how to use it in an incident and in a quarterly review.

Language: en · Category: governance · Author: Nicolas Corod (Founder and chief executive officer) · Published: 2026-11-03

"Do you log AI usage?" is the question on most vendor security questionnaires, and almost every vendor ticks yes. For a compliance reviewer it is the wrong question. The one that decides an audit is narrower: show me the record of one run, and tell me which fields I can rely on.

For some companies that question now has a legal floor. Under the [EU AI Act](https://eur-lex.europa.eu/eli/reg/2024/1689/oj), the European regulation on artificial intelligence, deployers of high-risk AI systems must keep the logs those systems generate for at least six months (Article 26(6)). This article answers the question for skilder: what each run records, what an exported record looks like, and how a reviewer uses it in an incident and in a periodic review.

## What is an AI audit trail?

An AI audit trail is the record of what an AI assistant did on a company's behalf: who asked, which business capability ran, which tools it called with which inputs, what came back, and which rule allowed or refused each step. A chat transcript shows the conversation. An audit trail shows the actions.

The distinction matters once assistants act. When Claude, ChatGPT or Copilot only drafts text, the conversation is most of the evidence. When the same assistant reads a CRM, lists purchase orders or sends a message, the evidence is the sequence of tool calls, and a transcript rarely contains it. Deloitte's 2025 report [HR Reimagined: Agentic AI for HR](https://d1lzrgdbvkolkd.cloudfront.net/4669_2_HR_Reimagined_Agentic_AI_b3d3a3c6f7.pdf) lists it as a design principle: agents should "maintain audit of all actions & decision paths".

An audit trail also needs a unit of permission to point at. In skilder that unit is the role, the [permission boundary for AI agents](/en/blog/least-privilege-ai-agents/): a bundle of skills and scoped tools granted to a team, so every call reads as "this person, through this role".

## Which EU rules ask for AI execution logs?

No single EU text says "log your AI assistant". Three regimes combine. The General Data Protection Regulation (GDPR) requires a company to demonstrate how it processes personal data. The AI Act requires automatic logs for high-risk systems. The Digital Operational Resilience Act (DORA) requires financial entities to record and classify incidents affecting their information and communication technology (ICT). Each asks a different question of the same log.

| Rule | Applies to | What it asks | What the log must answer |
| --- | --- | --- | --- |
| [GDPR](https://eur-lex.europa.eu/eli/reg/2016/679/oj), Articles 5(2) and 33 | Any organisation processing personal data of people in the EU | Demonstrate compliance; notify a personal data breach within 72 hours where feasible | Which personal data an assistant touched, for whom, and when |
| AI Act, Articles 12, 19 and 26(6) | Providers and deployers of high-risk AI systems, such as Annex III uses in hiring or credit | Automatic logging over the system's lifetime; logs kept for at least six months | How the system operated, when, and on what input |
| [DORA](https://eur-lex.europa.eu/eli/reg/2022/2554/oj), Article 17 | Banks, insurers, investment firms and other financial entities, since 17 January 2025 | Detect, record and classify ICT-related incidents | The timeline of an incident and the systems it reached |

The AI Act's high-risk timetable has moved. The [Digital Omnibus on AI](https://eur-lex.europa.eu/eli/reg/2026/1744/oj), Regulation (EU) 2026/1744, entered into force on 27 July 2026 and postponed the Annex III obligations to 2 December 2027. Most use of a general assistant at work is not high-risk in the first place. GDPR and DORA apply today, and a trail built for them already covers most of what the AI Act will ask. Logs are one part of an [enterprise AI governance framework](/en/blog/enterprise-ai-governance/), not a substitute for it.

## What does skilder record for each run?

skilder keeps an execution trace of every tool call an assistant makes through it, attributed to a person through the role they used and grouped by session, and the audit log is exportable. Each record carries the fields below, named as they appear in skilder's call log.

| Field | What it holds | Why a reviewer cares |
| --- | --- | --- |
| `id` | Unique identifier of the call | A finding can point at one exact record |
| `calledAt` | Timestamp in UTC, ISO 8601 | Builds the incident timeline |
| `user` | The person who ran the role, identifier and name | Attribution to a person, not to "the AI" |
| `role` | The role the assistant used | Shows which permission boundary applied |
| `skill`, `skillVersion` | The skill whose instructions were followed, and its version | Ties the run to an approved version of the method |
| `tool`, `kind` | The tool called, and whether it was a connector tool (`mcp`) or a skilder step such as loading a skill (`static`) | Separates actions on business systems from internal steps |
| `input`, `output` | The arguments sent to the tool and what it returned | The evidence itself |
| `status` | `COMPLETED`, `FAILED`, `TOOL_ERROR`, `REFUSED` or `PENDING` | Shows what happened, including what was stopped |
| `guardrail` | Outcome, rule and reason, when a guardrail rule covered the call | Explains a refusal by name |
| `error` | The error text, when there is one | Separates a broken tool from a blocked action |
| `session` | Session identifier and the task summary the assistant gave | Groups the calls of one request |
| `parentCallId` | The call that triggered this one | Rebuilds the chain of a multi-step run |
| `durationMs`, `origin`, `isTest` | Duration, where the call came from, whether it was a test run | Keeps test runs out of the production review |

Guardrails are rules written as scripts that check a tool call before or after it runs, enforced by skilder rather than by the assistant, in observing or blocking mode. A refusal in skilder's own workspace shows what a reviewer gets: the call is marked refused, the rule is named, and the reason states that the rule's script timed out after 3,000 milliseconds. No silent failure, and no guessing.

## What does an exported record look like?

The records below use sample data. Talvero Bau AG is a fictitious construction company and every value is invented. The first record is one call from a weekly site report run; the second is a call a guardrail refused.

```json
{
  "id": "0x5a1c02",
  "calledAt": "2026-11-02T07:41:12.304Z",
  "status": "COMPLETED",
  "kind": "mcp",
  "tool": "site_diary_list_entries",
  "durationMs": 640,
  "skill": { "id": "0x5a0f11", "name": "Weekly site report" },
  "skillVersion": 4,
  "user": { "id": "0x5a0e07", "name": "Anna Keller" },
  "role": { "id": "0x5a0e20", "name": "Site Reporting" },
  "session": { "id": "0x5a1bf8", "prompt": "Prepare the weekly site report for the Sion depot extension" },
  "input": "{\"site\":\"SION-07\",\"from\":\"2026-10-26\",\"to\":\"2026-11-01\"}",
  "output": "{\"entries\":12}",
  "error": null,
  "guardrail": null,
  "parentCallId": "0x5a1bfe",
  "origin": "AGENT",
  "isTest": false
}
```

```json
{
  "id": "0x5a1c09",
  "calledAt": "2026-11-02T07:43:55.018Z",
  "status": "REFUSED",
  "kind": "mcp",
  "tool": "mail_send",
  "user": { "id": "0x5a0e07", "name": "Anna Keller" },
  "role": { "id": "0x5a0e20", "name": "Site Reporting" },
  "guardrail": {
    "outcome": "REFUSED",
    "rule": { "id": "0x5a0d31", "name": "No external recipients" },
    "reason": "recipient domain is outside talvero.example"
  }
}
```

Many reviewers prefer to work through a quarter of activity in a spreadsheet. The same two records, flattened into rows:

```csv
id,calledAt,user,role,skill,skillVersion,tool,status,guardrail_outcome,guardrail_rule,session_id,parentCallId,isTest
0x5a1c02,2026-11-02T07:41:12Z,Anna Keller,Site Reporting,Weekly site report,4,site_diary_list_entries,COMPLETED,,,0x5a1bf8,0x5a1bfe,false
0x5a1c09,2026-11-02T07:43:55Z,Anna Keller,Site Reporting,Weekly site report,4,mail_send,REFUSED,REFUSED,No external recipients,0x5a1bf8,0x5a1c02,false
```

The flattening is a reviewer's choice. Check the export format your workspace offers before building a review template on it.

## How does a reviewer read a trace in the call log?

The call log in the skilder workspace answers a reviewer's questions in a fixed order: when, who, through which role, what was called, and what was stopped.

1. **Set the window.** The incident period, or the quarter under review.
2. **Narrow it.** Filter by person, role, skill, tool or status. A filter on guardrail outcome lists every refused or flagged call; a text search runs across tool names, payloads and errors.
3. **Open a session.** Its calls appear in order, under the task summary that started them.
4. **Open one call.** The full input and output, the skill version and the guardrail verdict.
5. **Export the selection** and attach it to the file, with the call identifiers quoted in the finding.

## How do you investigate an incident with the trace?

Take a sample case. A project manager at Talvero Bau reports that a client received a site report containing another client's figures. Under GDPR Article 33, the company may have 72 hours to notify the supervisory authority, and the notification must describe the categories and approximate number of people and records concerned. The trace is how that scope gets established.

1. **Find the run.** Search the window for the client's site code in the payloads. One session comes up, with its task summary.
2. **Rebuild the chain.** Follow `parentCallId` from the report back to the data calls. The diary call used a date filter but no site filter, and returned entries from two sites.
3. **Find the cause.** The run followed version 4 of the report skill, published two days earlier. Version 3 filtered by site.
4. **Scope the exposure.** List every call made with version 4 since its publication: how many reports, for which sites, run by whom. That list is the core of the notification.
5. **Contain it.** The skill owner returns to version 3, and the finding cites the call identifiers.

Without the trace, step 4 becomes an estimate. IBM's breach research ties the extra cost of shadow AI to exactly this gap, as the [shadow AI statistics for 2026](/en/blog/shadow-ai-statistics-2026/) show: a company that cannot say who ran what, on which data, struggles to scope a breach quickly.

## How do you run a periodic compliance review?

A quarterly review checks that the rules on paper match the calls in the log. A practical sequence:

1. **Export the quarter**, with test runs excluded through `isTest`.
2. **Check attribution.** Every call that changes data outside the conversation has a person and a role.
3. **Review refusals.** Each refused or flagged call names a rule and a reason; confirm the rule still matches the written policy.
4. **Compare versions.** The skill versions that ran in production are the versions their owners approved.
5. **Read whole sessions.** Sample a few per role and read them end to end, not call by call.
6. **Check who reads the log.** It holds names and business data, so it is personal data under the GDPR in its own right: limit access and set its retention.
7. **Record findings with call identifiers**, so the next review can verify the fix.

Where the log is stored matters as much as what it holds. skilder hosts in Switzerland, with Infomaniak by default, and in the European Union; on-premise deployment is available on request. The trade-offs are covered in [sovereign AI in Switzerland](/en/blog/sovereign-ai-switzerland/).

## What should you ask any vendor about AI execution logs?

The same questions work for an assistant vendor, a gateway or skilder itself:

- Is each call attributed to a person, through a role, or only to an API key?
- Does the record hold inputs and outputs, or only metadata?
- Are refusals logged with the rule and the reason?
- Does the record name the version of the instructions that ran?
- Can the log be exported in a format your own tools read?
- Can retention be set to your legal minimum, such as six months under the AI Act for high-risk systems, or longer where sector rules require it?
- Who at the vendor can read the log?

Skilder's confirmed answers are on its [trust and security page](/en/trust/). To map these questions onto your own review, a [free 30-minute exchange with an expert](https://koalendar.com/e/meet-with-nicolas-9?utm_source=skilder.ai&utm_medium=blog_ai_audit_trail) is a practical place to start.

**Takeaway:** a log that says "the AI did it" fails an audit. Ask for the record of one run, field by field, and check that it names a person, a role, a version and a reason.

To walk through what your AI audit trail needs to show a compliance reviewer, [book a free 30-minute exchange with an expert](https://koalendar.com/e/meet-with-nicolas-9?utm_source=skilder.ai&utm_medium=blog_ai_audit_trail).
