What Are Blueprints?
Blueprints are high-level business process frameworks that define how your organization operates. They describe:- Major process categories (e.g., Acquisition, Operations, HR)
- Key process areas within each category
- Relationships between processes
- Inputs, outputs, and stakeholders
Why Generate Workflows from Blueprints?
Category-Level Workflows
Create comprehensive workflows that cover entire process categories, not just individual procedures
Strategic Alignment
Ensure operational workflows align with your strategic process framework
Process Coverage
Quickly identify and create workflows for all major business processes
Consistency
Maintain consistent workflow structure across related processes
Blueprint vs Guide Generation
| Aspect | Blueprint Generation | Guide Generation |
|---|---|---|
| Scope | Broad, category-level | Narrow, procedure-specific |
| Detail Level | High-level tasks | Detailed step-by-step |
| Use Case | Creating process frameworks | Converting existing SOPs |
| Output | Multiple related workflows | Single workflow |
| Customization Needed | Significant | Moderate |
How to Generate Workflows from Blueprints
1
Navigate to Workflow Templates
Go to Administration > Workflows Templates in the main navigation.
2
Click 'Generate from Blueprint'
Click the Generate from Blueprint button in the top right corner.
3
Select a Blueprint
Choose the business process blueprint you want to convert:
- Acquisition Process Blueprint
- Operations Management Blueprint
- HR & People Management Blueprint
- Financial Management Blueprint
- Custom blueprints your organization has created
4
Choose Process Category
Blueprints contain multiple process categories. Select which category to generate workflows for:Example - Acquisition Blueprint:
- Pre-Acquisition Analysis
- Due Diligence
- Closing & Transition
- Post-Acquisition Integration
5
Configure Generation Settings
Set preferences for workflow generation:
- Task Detail Level: Summary tasks vs. detailed tasks
- Include Sub-Processes: Generate workflows for sub-processes too
- Auto-Assign Stakeholders: Assign tasks based on blueprint stakeholder roles
- Link Related Workflows: Create dependencies between related workflows
Blueprint generation creates broader workflows than guide generation. Expect to refine and add detail after generation.
6
Review Generated Workflow Structure
AI shows you a preview of what will be created:
- Main workflow name
- Number of tasks
- Sub-workflows (if applicable)
- Key stakeholders
- Major milestones
7
Customize Workflows
Review and edit the generated workflows:
- Add missing tasks
- Break down high-level tasks into subtasks
- Define task dependencies
- Assign to specific roles in your organization
- Set estimated durations
8
Save Workflow Templates
Save the generated workflows as templates in your library.Each category-level workflow becomes a separate template you can use to create instances.
Use Cases for Blueprint Generation
Use Case 1: New Acquisition Process
Scenario
Scenario
Your company has acquired a new business. You need comprehensive workflows to manage the entire acquisition process from due diligence through integration.
Solution
Solution
Generate workflows from the Acquisition Blueprint:
- Select “Acquisition Process Blueprint”
- Generate workflows for all categories (Due Diligence, Closing, Integration)
- Customize with company-specific details
- Create a workflow instance for the new acquisition
- Assign to acquisition team
Use Case 2: Standardizing Operations
Scenario
Scenario
You’re standardizing operations across multiple business locations. You need consistent operational workflows for inventory, quality control, customer service, etc.
Solution
Solution
Generate workflows from the Operations Blueprint:
- Select “Operations Management Blueprint”
- Choose relevant categories (Inventory, Quality, Service)
- Customize for your industry and operations
- Deploy the same workflows across all locations
Use Case 3: Building HR Infrastructure
Scenario
Scenario
You’re scaling your team and need structured workflows for hiring, onboarding, training, and performance management.
Solution
Solution
Generate workflows from the HR Blueprint:
- Select “HR & People Management Blueprint”
- Generate workflows for Recruitment, Onboarding, Development
- Customize for your company culture and policies
- Create instances for each new hire or review cycle
Category-Level Workflows
Blueprint generation creates category-level workflows, which are broader than procedure-level workflows:Category-Level: Acquisition Due Diligence
- Scope: Entire due diligence process
- Tasks: 15-25 high-level tasks covering financial review, legal review, operational assessment, etc.
- Duration: 30-90 days
- Stakeholders: Multiple teams (finance, legal, operations, HR)
Procedure-Level: Financial Statement Review
- Scope: Just the financial statement review portion
- Tasks: 8-12 detailed tasks for analyzing financial statements
- Duration: 3-7 days
- Stakeholders: Finance team only
Refining Blueprint-Generated Workflows
Blueprint generation gives you a starting framework. You’ll need to refine it:1
Add Detail to Tasks
Blueprint tasks are high-level. Break them down into specific, actionable subtasks.Example:
- Blueprint Task: “Conduct financial due diligence”
- Refined Tasks:
- Review 3 years of financial statements
- Analyze revenue trends and patterns
- Verify accounts receivable aging
- Assess debt structure and obligations
- Identify financial risks and opportunities
2
Define Dependencies
Blueprint generation suggests dependencies but can’t know all your specific sequencing requirements.Carefully review and adjust task dependencies to match your actual process flow.
3
Assign to Your Org Structure
Blueprint uses generic roles (e.g., “Finance Manager”). Update these to match your organization:
- Generic: “Finance Manager”
- Your Org: “Sarah Chen - Director of FP&A”
4
Set Realistic Durations
Add estimated durations to tasks based on your team’s capacity and the scope of work.
5
Add Evidence Requirements
Specify what evidence should be uploaded for each task to ensure accountability.
6
Test and Iterate
Create a test instance and run through it with your team. Gather feedback and refine the template.
Linking Related Workflows
Blueprint generation can create dependencies between related workflows: Example: Acquisition Process Workflow: Pre-Acquisition Analysis ↓ (Must complete before starting) Workflow: Due Diligence ↓ (Must complete before starting) Workflow: Closing & Transition ↓ (Must complete before starting) Workflow: Post-Acquisition IntegrationWhen you enable “Link Related Workflows,” the system ensures workflows are completed in sequence. You can’t start Due Diligence until Pre-Acquisition Analysis is complete.
Best Practices
Start Broad, Then Narrow
Start Broad, Then Narrow
Generate the broad category-level workflow first. Then create more detailed procedure-level workflows for complex tasks within it.
Involve Process Owners
Involve Process Owners
Blueprint generation creates a framework, but process owners know the details. Involve them in refining the workflow.
Don't Over-Customize Initially
Don't Over-Customize Initially
Get the workflow working with basic customization first. Add advanced features and details after you’ve run it a few times.
Version Your Blueprints
Version Your Blueprints
As your processes evolve, update your blueprints. Regenerate workflows periodically to stay aligned.
Use for Strategic Processes
Use for Strategic Processes
Blueprint generation works best for strategic, high-level processes (acquisitions, major projects, annual cycles). Use guide generation for tactical, operational tasks.
Blueprint Generation vs Manual Creation
Use Blueprint Generation When
- You have a documented business process framework
- You need multiple related workflows
- You want to ensure strategic alignment
- You’re setting up processes for the first time
Use Manual Creation When
- You have a unique, one-off process
- The workflow is very simple (3-5 tasks)
- You need complete control over every detail
- No blueprint exists for your process
Common Challenges
Generated Workflows Are Too Generic
Generated Workflows Are Too Generic
Solution: This is expected. Blueprint workflows are intentionally high-level. Your job is to add the specific details for your organization.
Too Many Tasks Created
Too Many Tasks Created
Solution: Consolidate related tasks or use sub-workflows. Break large workflows into smaller, more manageable pieces.
Unclear Task Assignments
Unclear Task Assignments
Solution: Blueprints use generic roles. You must map these to your actual organizational roles and people.
Missing Process Details
Missing Process Details
Solution: Combine blueprint generation (for structure) with guide generation (for details). Generate the framework from the blueprint, then generate specific subtasks from guides.