> 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/blueprints/creating-blueprints.md).

# Creating Blueprints

Create a Blueprint and define the reusable structure for new Projects.

### Overview

Creating a Blueprint establishes reusable delivery structure. Blueprints are typically created before creating many Projects.

### Key Concepts

* **Blueprint scope**: reusable structure for future Projects
* **Processes and Systems**: primary structure used for traceability and reporting
* **Segmentation**: optional Organization-level structure for consistent reporting

### How It’s Used

Use this workflow during initial rollout. Use it again when a new delivery method is introduced.

### Benefits

* Faster onboarding for new Projects
* More consistent naming and reporting across initiatives
* Reduced rework from inconsistent structure

### Setup Steps

{% stepper %}
{% step %}

### Create the Blueprint

1. Navigate to **Blueprints**.
2. Select **New Blueprint**.
3. Set the name and description.

Use a stable naming pattern, such as `{method} Blueprint`.
{% endstep %}

{% step %}

### Define Processes

Define Processes to represent workflows, phases, or workstreams.

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

{% step %}

### Add Systems

Add Systems that support delivery scope.

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

{% step %}

### Define segmentation (optional)

Define Segment Types and Segments when reporting needs consistent structure.

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

### Best Practices

* Keep the first Blueprint minimal and expand after use.
* Standardize naming before creating many Processes and Systems.
* Treat Blueprint changes as governed updates.

### Summary

Creating a Blueprint establishes reusable structure for Projects. Processes and Systems are the primary building blocks.


---

# 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/blueprints/creating-blueprints.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.