Lifecycle Templates
Control & DirectionLifecycle Templates define the sequence of phases that a project moves through from start to finish. Each template is a reusable blueprint that specifies the stages, their order, and the governance rules applied at each gate. Once created, templates can be assigned to projects so that every project of a given type follows the same structured process.
Lifecycle Templates integrate with Projects (template assignment), Lifecycle Builder (visual stage design), and Default Approvers (approval configuration per phase).
Template list
Navigate to Lifecycle > Lifecycle Templates to view all templates. The list displays templates in an editable table with columns for name, description, category, version, and active status. From this view you can create new templates, duplicate existing ones, manage versions, and toggle templates between active and inactive states.
Creating a template
Open the creation form
Click New Template from the lifecycle templates list page. This opens the template creation form.
Provide template details
Fill in the following fields:
| Field | Description | Required |
|---|---|---|
| Name | A descriptive title for the template (e.g., “Standard Security Project Lifecycle”) | Yes |
| Description | An explanation of when and how this template should be used | No |
| Category | A classification label to organize templates by type (e.g., “Compliance”, “Infrastructure”, “Incident Response”) | No |
Build the lifecycle stages
After saving the template, navigate to the Lifecycle Builder to define the stages. The builder provides a visual interface for adding, ordering, and configuring each phase.
Activate the template
Toggle the template to Active to make it available for assignment to projects. Only active templates appear in the project template selection dropdown.
Template versioning
Templates support versioning to allow controlled evolution without breaking projects that are already using a previous version. Each template tracks a version number that starts at 1 and increments with each new version. When you create a new version, the system creates a copy of the template with a parent link back to the original, preserving the full version history.
Projects that were assigned to a previous version continue using that version’s stage definitions. New projects can be assigned to the latest version. This ensures that in-flight work is not disrupted when lifecycle definitions are updated.
Duplicating templates
Use the Duplicate action to create a copy of an existing template as a starting point for a new one. The duplicated template receives a new name and is created in an inactive state so you can modify it before making it available. Duplication copies all stages and their configurations from the source template.
Default template
One template can be marked as the default for your tenant. When a new project is created without explicitly selecting a lifecycle template, the default template is applied automatically. Only one template can be the default at any time. Setting a new default replaces the previous one.
Active and inactive templates
Templates have an active flag that controls their visibility when assigning templates to projects. Active templates appear in the selection dropdown and can be assigned to new projects. Inactive templates are hidden from selection but remain in the system for historical reference. Projects already using an inactive template continue to function normally.
How templates attach to projects
When a project is created or edited, you select a lifecycle template from the available active templates. The template’s stages are applied to the project, creating the phase structure that governs the project’s progression. The project then tracks its current phase, records transitions between phases, and enforces any approval gates defined in the template’s configuration.
Permissions
Managing lifecycle templates requires the lifecycle:manage permission. Users with this permission can create, edit, duplicate, version, activate, and deactivate templates. Users with read-only access can view templates and their stage definitions but cannot make changes.