> 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/collaboration-and-automation/tracking-changes-and-decisions.md).

# Tracking Changes and Decisions

Use history and activity feeds to understand what changed, when, and why.

### Overview

Activity tracking shows a timestamped record of updates.

Use it for audits, handoffs, and “why did this change?” moments.

{% hint style="info" %}
Screenshot placeholder: item detail view with an Activity/History tab.
{% endhint %}

### Key Concepts

* **Activity feed**: chronological list of comments and changes
* **History**: field-level change record (when enabled)
* **Decision pattern**: consistent formatting used for approvals and rationale

### How It’s Used

Use this workflow during weekly governance.

Use it during investigations and handoffs.

### Benefits

* Faster validation of progress signals
* Better accountability for approvals
* Reduced rework caused by missing context

### Setup Steps

{% stepper %}
{% step %}

### Open the item

Open the task, requirement, test case, or Project for review.
{% endstep %}

{% step %}

### Open Activity / History

Look for:

* status changes
* assignee changes
* field edits
* comments and mentions
* links added/removed (requirements ↔ tasks ↔ tests)
  {% endstep %}

{% step %}

### Capture the decision

When a decision appears in the thread:

* add a short summary comment using `Decision:`
* @mention the approver or owner
* link supporting Artifacts
  {% endstep %}
  {% endstepper %}

### Best Practices

* Put approvals in comments, not in direct messages.
* Use consistent tags: `Decision:`, `Approved by:`, `Blocked by:`.
* Summarize meeting outcomes in one comment.

### Troubleshooting

<details>

<summary>I can’t see Activity or History</summary>

Possible causes:

* feature not enabled for the Account
* role does not have access to history

Ask an Account Admin to confirm configuration and permissions.

</details>

<details>

<summary>The history is noisy</summary>

Do this:

* filter by user (if available)
* filter by event type (status/assignee/comments)
* standardize on a single “Decision” summary comment per change

</details>

### Summary

Activity tracking provides the evidence layer for decisions and scope changes.

Related:

* [Comments and History](/collaboration-and-automation/comments-and-history.md)
* [Understanding Activity Feeds](/collaboration-and-automation/understanding-activity-feeds.md)
* [Audit Trail and Compliance](/collaboration-and-automation/audit-trail-and-compliance.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/collaboration-and-automation/tracking-changes-and-decisions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.