> 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?

### 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/blueprints/blueprint-fundamentals/what-are-blueprints.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.