> 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/artifacts/creating-quick-notes.md).

# Creating Quick Notes

### Overview

Quick Notes support fast capture of context and decisions.

They are useful when a file upload is unnecessary.

### Key Concepts

* **Quick Note**: lightweight note that can be linked to work items
* **Permalink**: stable link for sharing and governance follow-up
* **Decision pattern**: consistent formatting used for retrieval

### How It’s Used

Create Quick Notes during meetings, reviews, and handoffs.

Link Quick Notes to requirements and tasks that depend on the context.

### Benefits

* Faster capture of decisions and rationale
* Reduced context loss across delivery cycles
* Better searchability through consistent patterns

### Setup Steps

{% stepper %}
{% step %}

### Create the Quick Note

1. Navigate to **Quick Notes** (or the entry point where Quick Notes are created).
2. Select **New quick note**.
3. Enter a short title aligned to intent.
4. Enter note content.
   {% endstep %}

{% step %}

### Link to delivery work

1. Capture the Quick Note permalink when available.
2. Add the link to the related requirement or task.
3. Add a comment with `Decision:` and `Approved by:` when the note records an approval.
   {% endstep %}
   {% endstepper %}

### Best Practices

* Use short titles with clear intent, such as meeting date + topic.
* Keep notes short. Promote stable content into an Artifact when needed.
* Use consistent decision patterns to support Console retrieval.

### Summary

Quick Notes should be linked to the items that rely on the captured context.


---

# 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/artifacts/creating-quick-notes.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.