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

# Processes

Set up a reusable process map for a Blueprint.

### Overview

Processes are the primary structure inside a Blueprint. They model workflows, phases, and workstreams for delivery tracking.

### Key Concepts

* **Process**: reusable workflow, phase, or workstream
* **Hierarchy**: parent-child rollups for navigation and reporting
* **Linking**: relationships to Systems and Segments for traceability

### How It’s Used

Use Processes to group Requirements and Tasks by business flow. Use hierarchy for rollups in reporting and reviews.

Processes defined in a Blueprint can be included in new Projects. Some UI labels may refer to Projects as Transformations.

### Benefits

* Consistent structure across Projects
* Cleaner reporting by workflow and ownership
* Faster navigation for delivery teams

### Setup Steps

{% stepper %}
{% step %}

### Create a process

1. Navigate to **Blueprints**.
2. Open a Blueprint.
3. Open **Processes**.
4. Select **Add process**.

Define:

* **Name**
* Optional fields when enabled, such as Code, Owner, and Description
  {% endstep %}

{% step %}

### Build hierarchy (optional)

Create parent processes for rollups. Add child processes that represent real subsets.

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

{% step %}

### Link to Systems and Segments (optional)

Link processes to Systems to clarify technology scope. Link processes to Segments to support reporting by business dimension.

* [Create Systems](/blueprints/systems-management/create-systems.md)
* [Segmentation](/blueprints/segmentation.md)
  {% endstep %}
  {% endstepper %}

### Best Practices

* Use one naming pattern across Blueprints.
* Keep hierarchies to 2–3 levels for most teams.
* Avoid creating processes for single tasks.

### Summary

Processes define the Blueprint structure used for delivery tracking.

Hierarchy and linking improve navigation and reporting.

Related:

* [Process Hierarchy](/blueprints/creating-blueprints/process-hierarchy.md)
* [Create Systems](/blueprints/systems-management/create-systems.md)
* [Systems Management](/blueprints/systems-management.md)
* [Segmentation](/blueprints/segmentation.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/creating-blueprints/processes.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.