# System Versioning: Drafts, Releases, and History

> Understand system drafts, release versions, and inspect read-only version history.

Canonical URL: http://modelmonster.ai/docs/managing-systems/system-versioning-model/

## Article Metadata

- Reading time: 3 min

System versioning gives your organization a clear record of how an AI system changes over time. It separates working changes from released system states, helping teams preserve meaningful milestones and review earlier versions. This guide explains when to release a version, how your organization's review settings affect that release, and how to inspect version history.

## Understand the version lifecycle

![Version lifecycle from Active through Draft and release, with previous releases preserved as read-only history](/media/original_images/visual-1-system-version-lifecycle.png)

An **Active** version is the system state your organization has released. When you edit an Active system, Model Monster starts a new **Draft**. The Draft collects your changes until your team is ready to release the next version.

### Work with a draft

The system header shows the current version number and status. When the status is **Draft**, users with edit access can update the System Blueprint and other system information, then save those changes to the working version.

![System header showing the version number, Draft status, and available release action](/media/original_images/visual-2-draft-system-header.png)

### Decide when to release a new version

Release a new version when the accumulated changes affect the system's risk profile. This creates a clear record of the system state that your organization is prepared to review and rely on.

Version-worthy changes can include updates to:

- **System Blueprint structure**
- **Policies** applied to the system
- **Applicable risks** and their treatment
- **Use Case** context
- **Attached evidence** or supporting documentation

> **Marcellus tip:** Ask whether a future reviewer would need the changed system state represented as a distinct released record. If the answer is yes, plan to release a new version.

### Release the draft

Before releasing, confirm that the draft accurately represents the system state you want to preserve. Then follow the action shown in the system header.

#### If your organization does not require review:

1. Open the draft system.
2. Select **Finalize new version**.
3. Confirm that the version becomes **Active**.

Finalization is the publication point for the version. Later changes begin another draft rather than changing the released record.

#### If your organization requires review:

1. Open the draft system.
2. Select **Submit for review**. If it is unavailable, resolve the policy or Use Case issues shown first.
3. Add an optional comment for the reviewers.
4. Review the configured reviewers and add any eligible additional reviewers you need.
5. Select **Submit**.

![Submit for review dialog showing the optional comment, configured reviewers, additional reviewers, and Submit action](/media/original_images/visual-3-submit-for-review-dialog.png)

The version changes from **Draft** to **In review**. For more information about the system review process, continue with [System Review Workflow](/docs/managing-systems/system-review-workflow/).

> **Note:** If you expected **Finalize new version** but see **Submit for review**, your organization requires review before a draft can become Active.

## Review version history

![Overview tab with the Version timeline widget, recent versions, and the All versions link in the upper-right corner](/media/original_images/visual-4-overview-tab.png)

The **Version timeline** widget on the system's **Overview** tab shows the most recent versions. To see the complete history, select **All versions** in the widget's upper-right corner.

![Full version history page showing search, status filter, and rows with multiple version statuses](/media/original_images/visual-5-system-versions-page.png)

On the full history page, you can:

- Search the available version records
- Filter the list by status
- Review each version's status and available metadata

If a search or filter returns no matches, clear or adjust it to return to the full list.

For a historical version with an available archive, select **View archive** on its row.

When a new version becomes Active, the previous Active version becomes **Archived**, preserving its released state for review and comparison. They are read-only: opening an earlier version does not make it editable and does not change which version is Active.

## Next steps

- Read [System Review Workflow](/docs/managing-systems/system-review-workflow/) if your organization requires approval before release.
- Review [System View and the Blueprint](/docs/modeling-your-systems/system-view-and-the-blueprint/) to understand the system structure each version preserves.