> 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/tutorial-set-up-a-first-blueprint.md).

# Tutorial: Set Up a First Blueprint

### Overview

Blueprints define reusable structure for new Projects.

Blueprints reduce setup time and standardize governance.

### Key Concepts

* **Blueprint**: reusable configuration for new Projects
* **Processes**: reusable process map used for navigation and reporting
* **Systems**: reusable application inventory linked to processes
* **Segmentation**: Segment Types and Segments used for scoping and reporting

{% hint style="info" %}
Segment Types and Segments are scoped to the Organization level.
{% endhint %}

### How It’s Used

Use a Blueprint before creating many Projects.

Use one Blueprint per line of business when delivery patterns differ.

### Benefits

* Standard structure across Projects
* Faster onboarding for delivery teams
* Cleaner reporting and traceability

### Setup Steps

{% stepper %}
{% step %}

### Create the Blueprint

1. Navigate to **Blueprints**.
2. Select **New blueprint**.
3. Enter a name aligned to the line of business.
4. Select **Create**.

Related: [Creating Blueprints](/blueprints/creating-blueprints.md)
{% endstep %}

{% step %}

### Define Processes

1. Open **Processes** in the Blueprint.
2. Add a small process set, such as 10–30 entries.
3. Add parent processes when rollups are needed.

Related: [Processes](/blueprints/creating-blueprints/processes.md)\
Related: [Process Hierarchy](/blueprints/creating-blueprints/process-hierarchy.md)
{% endstep %}

{% step %}

### Define Systems and System Types

1. Open **Systems** in the Blueprint.
2. Create System Types for consistent classification.
3. Add Systems and link Systems to Processes.

Related: [Create Systems](/blueprints/systems-management/create-systems.md)\
Related: [System Types](/blueprints/systems-management/system-types.md)
{% endstep %}

{% step %}

### Define Segmentation (optional)

1. Open **Segmentation**.
2. Define Segment Types aligned to reporting needs.
3. Add Segments for the Organization structure.

Related: [Segmentation](/blueprints/segmentation.md)
{% endstep %}
{% endstepper %}

### Best Practices

* Start small. Expand after teams start delivering work.
* Standardize naming for Processes and Systems.
* Keep Segment Types stable to protect reporting continuity.

### Summary

Next action:

* Create a Project from the Blueprint: [Create a Project](/getting-started/create-a-project.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/tutorial-set-up-a-first-blueprint.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.