> 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/ai/finding-decisions-and-approvals.md).

# Finding Decisions and Approvals

### Overview

Decisions often live in comments, meeting summaries, and status changes.

Console finds them without manual digging.

### Key Concepts

* **Decision**: explicit direction that changes scope or execution
* **Approval**: confirmation that a requirement or deliverable is accepted
* **Decision pattern**: consistent formatting used for retrieval, such as `Decision:`

### How It’s Used

Use this workflow during governance meetings.

Use it after meetings to validate what was decided and what changed.

### Benefits

* Faster decision retrieval
* Clearer audit trail for approvals
* Reduced rework caused by lost context

### Setup Steps

{% stepper %}
{% step %}

### Open Console

1. Open **Console**.
2. Confirm Project scope (if prompted).
   {% endstep %}

{% step %}

### Use decision-focused queries

For example:

* `decisions from last week`
* `what was approved for revenue recognition`
* `show approvals for UAT scope`
* `summarize key decisions for project X`

{% hint style="info" %}
Screenshot placeholder: Console search box with a decision query and results list.
{% endhint %}
{% endstep %}

{% step %}

### Open the source item

1. Click the best result.
2. Jump to the original requirement/task/comment.
3. Copy the permalink for sharing, when needed.
   {% endstep %}
   {% endstepper %}

### Best Practices

Use a consistent comment pattern:

* `Decision:` what was decided
* `Approved by:` who approved
* `Date:` when it was approved
* `Scope:` what it applies to

For example:

`Decision: Approve revenue recognition rules v2. Approved by: Line of Business lead. Date: 2026-02-17. Scope: Order-to-Cash.`

### Troubleshooting

<details>

<summary>Console results look incomplete</summary>

Common causes:

* access is limited to certain Organizations or Projects
* decisions were captured outside Transform
* decision language is inconsistent (“ok”, “yep”, “LGTM”)

Fix: standardize on `Decision:` and `Approved by:` comments.

</details>

<details>

<summary>I need an audit-grade approval trail</summary>

Use item history and audit trail views where available.

See [Audit Trail and Compliance](/collaboration-and-automation/audit-trail-and-compliance.md).

</details>

### Summary

Decisions are easiest to find when captured consistently and linked to the source item.

Console should be used with source validation for audit-grade outcomes.

Related:

* [Using Console for Natural Language Search](/ai/using-console-for-natural-language-search.md)
* [Console Search Tips and Examples](/ai/console-search-tips-and-examples.md)
* [Comments and Mentions](/collaboration-and-automation/comments-and-mentions.md)
* [Comments and History](/collaboration-and-automation/comments-and-history.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 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/ai/finding-decisions-and-approvals.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.