> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/transformations/audit-trail.md).

# Audit Trail

### Overview

Audit Trail records what changed, when, and by whom.

It supports compliance, governance, and delivery accountability.

### Key Concepts

* **Event**: a recorded change, such as a field update
* **Actor**: the Teammate or system process that made the change
* **Timestamp**: time the event was recorded
* **Context**: linked item details, such as a requirement or task

### How It’s Used

Use Audit Trail during approval reviews.

Use it to resolve “what changed?” questions quickly.

### Benefits

* Clear accountability for scope and status changes
* Faster investigations during delivery issues
* Stronger evidence for compliance audits

### Setup Steps

{% stepper %}
{% step %}

### Open an item

1. Open a requirement, task, or test case.
2. Locate the history or activity area.
   {% endstep %}

{% step %}

### Review change history

1. Scan for status, owner, and date changes.
2. Open details for high-impact events.
   {% endstep %}

{% step %}

### Capture evidence (optional)

1. Copy event details into an Artifact when required.
2. Include links back to the source item.
   {% endstep %}
   {% endstepper %}

### Best Practices

* Record rationale in comments when changing scope or approvals.
* Keep approvals inside the work item, not external threads.
* Use consistent statuses to reduce ambiguous history.

### Summary

Audit Trail is the source of truth for change history.

Pair it with structured requirements and statuses for clean governance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/transformations/audit-trail.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.