> 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/blueprint-fundamentals/what-are-blueprints.md).

# What Are Blueprints?

Understand why Blueprints exist and how they standardize delivery structure across Projects.

### Overview

Blueprints define reusable structure for Project delivery work. They standardize naming, hierarchy, and reporting fields.

### Key Concepts

* **Blueprint**: reusable structure applied to new Projects
* **Process**: business workflow, phase, or workstream tracked in a Blueprint
* **System**: application or platform linked to Processes
* **Hierarchy**: parent-child structure used for rollups

### How It’s Used

Create one Blueprint per delivery method. For example: an ERP implementation approach.

Reuse the Blueprint to create multiple Projects with consistent structure.

### Benefits

* Faster Project creation with fewer setup decisions
* More consistent reporting across Projects
* Cleaner governance through standardized structure

### Setup Steps

1. Create a Blueprint.
2. Define Processes and hierarchy.
3. Add Systems and System Types.
4. Define segmentation when reporting requires it.

### Best Practices

* Keep Blueprints reusable and avoid client-specific naming.
* Use hierarchy for rollups, not for single tasks.
* Document naming conventions in an internal SOP.

### Summary

Blueprints are reusable templates for Projects. They define Processes, Systems, and hierarchy for consistent execution.

Related:

* [Blueprint Fundamentals](/blueprints/blueprint-fundamentals.md)
* [Creating Blueprints](/blueprints/creating-blueprints.md)
* [Processes](/blueprints/creating-blueprints/processes.md)
* [Process Hierarchy](/blueprints/creating-blueprints/process-hierarchy.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/blueprints/blueprint-fundamentals/what-are-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.