> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stage3.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Adding Blueprints

> Organize your process guides into logical phases using Blueprints

## What Are Blueprints?

Blueprints are automatic groupings that organize Guides within your Core Process. They help you structure complex processes into logical phases or stages, making them easier to understand and navigate.

<Info>
  Blueprints are created automatically when you specify a Blueprint name while creating a Guide. You don't create Blueprints separately - they appear as you build your process.
</Info>

## How Blueprints Work in MPQA

Blueprints in MPQA are **automatically generated** based on the Guides you create:

1. **Blueprints are created through Guides** - When you create a Guide and enter text in the "Blueprint" field, the system automatically creates that Blueprint if it doesn't exist yet.

2. **Colors are assigned automatically** - The system assigns a unique color to each Blueprint automatically. You cannot manually choose Blueprint colors.

3. **Guides are grouped by Blueprint** - In the RACI matrix view, Guides are grouped under their Blueprint headers.

4. **Visual representation** - In the Visual and Process Flow tabs, each Blueprint appears as a colored bar with Guides displayed beneath it.

## Why Use Blueprints?

Blueprints provide several benefits for process organization:

* **Visual organization** - Color-coded Blueprint bars make it easy to distinguish between different phases at a glance
* **Logical grouping** - Group related Guides together to show stages or phases of your workflow
* **Better navigation** - Blueprints create clear sections in the RACI matrix
* **Process insights** - The system tracks how many Blueprints (process phases) exist

## Creating Your First Blueprint

<Steps>
  <Step title="Navigate to Your Core Process">
    Go to **Business Processes** in the left sidebar and select the Core Process where you want to add Guides.

    Make sure you're on the **RACI** tab to view and manage Guides.
  </Step>

  <Step title="Click Add Guide">
    Click the blue **"Add Guide"** button in the top right of the RACI matrix.

    This opens the "Create New Guide" dialog.
  </Step>

  <Step title="Enter Guide Details">
    Fill in the required information:

    * **Guide Name** (required)
    * **Responsible** (R): Who does the work
    * **Accountable** (A): Who approves the work
    * **Consulted** (C): Who provides input
    * **Informed** (I): Who is kept updated
  </Step>

  <Step title="Specify a Blueprint Name">
    In the **"Blueprint"** field (optional), type the name of the phase or stage this Guide belongs to.

    **Examples of good Blueprint names:**

    * "Initial Screening"
    * "Planning Phase"
    * "Execution"
    * "Final Review"
    * "Post-Launch"

    <Tip>
      If you leave the Blueprint field empty, the Guide will still be created but won't be grouped under a specific Blueprint.
    </Tip>
  </Step>

  <Step title="Create the Guide">
    Click **"Create Guide"** to save.

    The Blueprint you specified will automatically appear in the RACI matrix as a new section header, and your Guide will be listed underneath it.
  </Step>
</Steps>

## Adding More Guides to an Existing Blueprint

To add additional Guides to a Blueprint that already exists:

1. Click the **"Add Guide"** button to create another Guide
2. In the "Blueprint" field, type the **exact same name** as your existing Blueprint
3. The system will automatically group this new Guide under the existing Blueprint
4. Fill in the rest of the Guide details and click **"Create Guide"**

<Warning>
  Blueprint names are case-sensitive. "Planning Phase" and "planning phase" would create two separate Blueprints. Make sure to use exact spelling and capitalization.
</Warning>

## Blueprint Naming Best Practices

<Tabs>
  <Tab title="Do">
    Use clear, descriptive phase names:

    * "Discovery Phase"
    * "Budget Approval"
    * "Implementation"
    * "Quality Review"

    Be consistent with naming patterns:

    * "Phase 1: Planning"
    * "Phase 2: Execution"
    * "Phase 3: Review"

    Keep names concise (2-4 words):

    * "Initial Screening"
    * "Final Approval"
  </Tab>

  <Tab title="Don't">
    Avoid vague or generic names:

    * "Category 1"
    * "Other Stuff"
    * "Miscellaneous"

    Don't make names too long:

    * "This is the category for all activities related to planning"

    Avoid inconsistent naming:

    * "Planning", "Execution of Tasks", "After Everything is Done"
  </Tab>
</Tabs>

## Common Blueprint Patterns

Different types of processes benefit from different Blueprint structures:

<Tabs>
  <Tab title="Time-Based Phases">
    **Best for:** Processes with clear time-based stages

    **Example: Employee Onboarding**

    * Pre-Arrival Preparation
    * First Day Activities
    * First Week Training
    * 30-Day Integration
    * 90-Day Review

    **Why this works:** Clear time-based progression with distinct phases showing the journey.
  </Tab>

  <Tab title="Functional Groups">
    **Best for:** Processes with distinct functional areas

    **Example: Product Launch**

    * Product Development
    * Marketing Preparation
    * Sales Enablement
    * Launch Execution
    * Post-Launch Analysis

    **Why this works:** Functional groups that clearly delineate different types of work.
  </Tab>

  <Tab title="Approval Gates">
    **Best for:** Processes with decision points

    **Example: Investment Approval**

    * Initial Request
    * Financial Analysis
    * Risk Assessment
    * Executive Approval
    * Implementation

    **Why this works:** Clear stages with the critical approval gate highlighted.
  </Tab>

  <Tab title="Customer Journey">
    **Best for:** Customer-facing processes

    **Example: Sales Process**

    * Lead Generation
    * Qualification
    * Proposal Development
    * Negotiation
    * Closing
    * Customer Onboarding

    **Why this works:** Follows the customer journey with clear handoff points.
  </Tab>
</Tabs>

## How Blueprints Appear in Different Views

Blueprints display differently depending on which tab you're viewing:

### RACI Tab

In the **RACI Responsibility Matrix** view:

* Blueprints appear as section headers with the Blueprint name
* Each Blueprint shows the count of Guides it contains (e.g., "1 guides")
* Guides are listed in rows beneath their Blueprint header
* A **"Blueprint"** link appears next to each Blueprint name

### Visual Tab

In the **Process Flow** diagram:

* Each Blueprint appears as a **colored horizontal bar** across the top
* The Blueprint name is displayed on the left side of the bar
* Guide boxes appear beneath their respective Blueprint bar
* Each Blueprint has a unique automatically-assigned color (e.g., red, green, blue)
* **"Blueprint"** and **"Workflow"** links appear in each Blueprint bar

### Swimlane Tab

In the **Process Swimlane Chart**:

* Guides are organized by responsible person (swimlanes)
* Blueprints group Guides horizontally within each swimlane
* This view shows the cross-functional flow of your process

## Understanding Blueprint Colors

<Warning>
  Blueprint colors are assigned automatically by the system. You cannot manually choose or change Blueprint colors in MPQA.
</Warning>

The system assigns distinct colors to each Blueprint to make them visually distinguishable. These colors help you quickly identify which phase a Guide belongs to when viewing process diagrams.

## Blueprint Feature

Each Blueprint has an associated **"Blueprint"** link that appears in the RACI view.

This feature allows you to:

* Define standard templates or guidelines for Guides in that Blueprint
* Document best practices specific to that process phase
* Create reusable workflows for similar processes

## Editing and Managing Blueprints

### To Rename a Blueprint

Since Blueprints are created through Guides, to rename a Blueprint:

1. Click the edit icon (pencil) next to each Guide in the Blueprint you want to rename
2. In the "Edit RACI Assignments" dialog, update the Guide's Blueprint name to the new desired name
3. Use the **same new name** for all Guides you want grouped together
4. Click **"Save Changes"** for each Guide
5. Once all Guides have been updated, the old Blueprint will disappear and the new Blueprint will appear

### To Delete a Blueprint

To remove a Blueprint completely:

1. Either delete all Guides in that Blueprint, or edit them to assign them to a different Blueprint
2. Once no Guides remain assigned to that Blueprint, it will automatically disappear from the RACI matrix and all views

<Warning>
  There is no direct "delete Blueprint" button. Blueprints only exist as long as at least one Guide is assigned to them.
</Warning>

## Process Flow Insights

When you have Blueprints defined, MPQA provides insights about your process structure:

* **Total Guides:** Number of process steps defined
* **Blueprints:** Number of process phases (e.g., "2 process phases")
* **RACI Coverage:** Confirmation of clear accountability and responsibility assignments
* **Process Flow:** Indication of sequential progression through defined Guides

These insights help you understand the complexity and completeness of your process documentation.

## Best Practices

**Plan your Blueprints first**

Before creating Guides, sketch out the main phases of your process to ensure consistent Blueprint naming.

**Use consistent naming**

Double-check spelling and capitalization when entering Blueprint names to avoid creating duplicate Blueprints accidentally.

**Limit Blueprint count**

Aim for 3-7 Blueprints per process. Too many Blueprints can make the process harder to understand.

**Group logically**

Group Guides that naturally belong together in the same workflow stage or functional area.

## How Many Blueprints Should You Use?

General guidelines for Blueprint count:

| Process Complexity      | Recommended Blueprints                          | Example                            |
| ----------------------- | ----------------------------------------------- | ---------------------------------- |
| Simple (5-10 guides)    | 2-3 Blueprints                                  | Basic approval workflow            |
| Medium (10-25 guides)   | 3-5 Blueprints                                  | Department onboarding              |
| Large (25-50 guides)    | 5-7 Blueprints                                  | Enterprise sales cycle             |
| Very Large (50+ guides) | Consider splitting into multiple Core Processes | Full product development lifecycle |

<Tip>
  If you find yourself needing more than 7-8 Blueprints, consider whether your process should be split into multiple separate Core Processes instead.
</Tip>

## Troubleshooting

**My Guides aren't grouping under the same Blueprint**

Check that you're using the exact same spelling and capitalization for the Blueprint name. "Planning Phase" and "planning phase" are treated as two different Blueprints.

**I can't find where to edit a Blueprint directly**

Blueprints can't be edited directly. You must edit the Guides within that Blueprint to change or rename the Blueprint grouping.

**The Blueprint colors don't match my brand**

Blueprint colors are assigned automatically by the system and cannot be customized. Focus on using clear Blueprint names instead.

**My Blueprint disappeared**

Blueprints automatically disappear when they no longer contain any Guides. Check if all Guides were deleted or moved to other Blueprints.

## Next Steps

* [Adding Guides](/processes/adding-guides) - Learn how to create Guides within your Blueprints
* [Assigning RACI Roles](/processes/assigning-raci) - Understand how to assign responsibilities
* [Visual Process Flow](/processes/visual-diagrams) - See how Blueprints appear in visual diagrams
* [Working with Blueprints](/blueprints/working-with-blueprints) - Learn more about using Blueprints