Skip to main content
Every project sits in a lifecycle stage. Workspace admins and project access-group admins advance the project from one stage to the next. The advance modal lists the criteria for that step. Lifecycle stages are not a compliance checklist. Checklists come from governance frameworks you activate and scope to projects. You complete those requirements in Governance mode; you advance stages from the project’s lifecycle controls.

​
Lifecycle stages

Projects move through these stages, in order: If you cannot advance the project, the control shows this tooltip: Only workspace admins or project access-group admins can advance projects. See Roles and permissions and Access groups.

​
Advance from Intake

From Intake, the Advance to Development modal asks you to Assign an owner and Score risk.
  • If there is no owner, the modal shows No owner assigned.
  • If risk is not scored, it shows Risk has not been assessed. Use Score risk. If a score already exists, use Rescore.

​
Development and Staging gates

From Development, the Advance to Staging modal lists:
  • Set up development mode — development mode, not the Development lifecycle stage
  • Push your first commit
  • Integrate system
  • Configure development tests — Add a development test / Configure tests. See Tests configuration
From Staging, the Advance to Production modal lists:
  • Set up monitoring mode — monitoring mode
  • Connect a data source
  • Connect to deployment
  • Configure monitoring tests — Add a monitoring test
These labels are the criteria in the modal. They are not the same items as a framework’s project checklist.

​
Retire a project

From Production, the Retire project modal moves the project to Retired.

​
Overrides and audit

If a listed criterion is unmet, you can still continue with Override unmet criteria. Confirm I understand and want to override, enter a Reason, then choose Advance. While the request runs, the button shows Advancing…. You must provide a Reason to override.