Hi @PaulS0848

You've touched on a common need among Blueprint users. Currently, Blueprint doesn't have native versioning capabilities, but there is a practical workaround that many of us are using successfully. Here's the approach I recommend:

1. Create Duplicates as You Progress

As you move through your design iterations, create duplicate Blueprints at key milestones. This allows you to preserve each significant version while continuing to evolve your design.

2. Record Version Information in the Application Purpose Field

Within each Blueprint, use the Application Purpose field (found in the Application Context tab) to document version information:

• Include a version number
• Add the date
• Optionally, note key changes or the reason for this version

Example format: "Financial Services Onboarding v0.3 - 12-May-2025"

3. Organize Your Dashboard This approach creates multiple Blueprints on your dashboard, each representing a different version. You can easily identify them by the version information in their names. When to Use This Approach:

• This method is particularly valuable when:
• Your Blueprint will undergo multiple iterations
• You need stability for importing into the Estimator App or App / Dev Studio
• You need to grant Editor access to different users for different version
• You want to enable stakeholders to view alternate stages
• You can filter on version numbers using the grid view as per below

The Pega product team is aware of the need for native versioning, and I can confirm it's currently on the roadmap for implementation in a future release.