> 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/getting-started/what-is-transform.md).

# What Is Transform

Understand what Transform does and why it reduces rework during business transformation delivery.

### Overview

Transform turns project context into structured work. That structure reduces rework and improves governance.

Transform is designed for complex transformation delivery. It connects requirements, tasks, tests, and artifacts to maintain traceability.

### Key Concepts

<figure><img src="https://1679440205-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbO5MkvlsUXaVsGsjqKWy%2Fuploads%2FFYL0qJ6MqPt3d9h3ZKCk%2FScreenshot%202026-05-19%20at%209.47.37%E2%80%AFAM.png?alt=media&amp;token=734b5384-89f4-4b23-8790-0651498e1632" alt=""><figcaption></figcaption></figure>

* **Account**: top-level container
* **Organization**: container for a client, department, or business unit
* **Project**: delivery container for a single initiative
* **Blueprint**: reusable structure applied to new Projects
* **Artifact**: supporting file or reference for project context
* **Console**: natural-language search across Transform data (if enabled)

Start with [Key Concepts and Terminology](/getting-started/key-concepts-and-terminology.md).

### How It’s Used

Transform is typically used in four loops:

1. Capture context from artifacts, meetings, and decisions.
2. Convert context into requirements that represent scope.
3. Deliver scope through tasks and validate through testing.
4. Review change history to support governance and auditability.

### Benefits

* Less rework from lost context and inconsistent documentation
* Clear traceability from requirements to delivery and validation
* Faster onboarding for new teammates through linked project history
* Stronger governance through recorded decisions and change history

### Setup Steps

Follow the default setup path:

* [Start Here](/getting-started/start-here.md)

### Best Practices

* Link scope to delivery: requirements → tasks → tests.
* Capture decisions in comments, not side channels.
* Reuse Blueprints to standardize structure across Projects.
* Keep naming consistent across Organizations and Projects.

### Summary

Core pages:

* [Start Here](/getting-started/start-here.md)
* [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.md)
* [Understanding the Interface](/getting-started/understanding-the-interface.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/getting-started/what-is-transform.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.