Project Versions

A version of a Project is a collection of changes between “creation” and “completion.”

• Creation is when the version record is created.
• Completion happens when a subsequent version is created or the project is submitted for approval (since changes are frozen at that point).

Versions are named automatically in sequence — Version 1, Version 2, and so on.

When Versions Are Created

Versions are created automatically at key points in a project’s lifecycle:

• Project creation: A first version is created when the project is initially built.
• Approval submission: A version is created each time a project is submitted for approval, preserving the state that was sent for review.
• Rescope: When an approved project is sent back for changes (rescoped), a new version is created as the project re-enters the building state.

Users can also create versions manually at any time while the project is in a building state. This is useful for marking milestones or saving a known-good state before making significant changes.

What Versions Track

Each version captures a snapshot of the project’s core data at a point in time. The following are tracked and can be restored:

• Resources assigned to the project
• Professional Services and their configurations
• Subservices under each service
• Governance items (assumptions, risks, etc.)
• Travel & Expense items
• Survey recommendations
• Phases

Note: Versions do not backup, restore, or update information about third-party services (vendor quotes).

Viewing Versions

Navigate to the Versions section in your project to see a list of all versions. Each version shows:

• The version name (e.g., “Version 3”)
• A description explaining why the version was created
• The user who created the version
• The date the version was created

Reverting to a Previous Version

You can revert a project to any previous version. When you revert a version, ScopeStack does not overwrite the current state — instead, it creates a new version that brings the project back to the state captured by the selected version.

The revert process:

1. A new version is created with a description indicating which version was reverted.
2. All tracked items — resources, services, subservices, governance items, expenses, phases — are rolled back to match the reverted version.
3. Items that were deleted after the reverted version are recovered.
4. Items that were added or changed after the reverted version are reverted.

This means the full history is preserved. You can always see what changed and when, even after a revert.

Versions in Documents

The current version number can be inserted into your project documents via merge data, allowing you to include the version on generated Statements of Work or other deliverables.

Permissions

The Versions (projects.versions) permission under Settings > Roles controls access:

• View: See the list of project versions and their details.
• Manage: Create manual versions and revert the project to a previous version.