Projects in Altus progress through a defined lifecycle, typically represented as a stage-based workflow (also known as a Business Process Flow).

Each stage represents a phase in the project lifecycle (e.g. Planning, Execution, Closing) and may include checklists, approvals, or conditions that must be completed before progressing.

Important:
These lifecycle workflows are configured and tailored by your organisation or implementation partner, and may vary from simple manual processes to fully governed, automated workflows.

Always refer to your organisation’s internal governance guidelines if your process behaves differently.

Where This Is Performed

• At the top of the Project form (stage indicator with dots)

Advancing to the Next Stage (Default Behaviour)

In a typical configuration:

1. Locate the current stage at the top of the project (highlighted with a dot)
2. Select the current stage
3. Review the checklist panel that appears
4. Complete or mark required items
5. Select Next Stage

How Stage Progression Works

Stage progression can vary depending on configuration:

• ✅ Manual progression
• • Complete checklist → Click Next Stage
• ⚙️ Semi-governed
• • Certain fields or checklist items must be completed before progressing
• 🔒 Fully governed / automated
• • Stage progression may:
  • • Require formal approval
    • Be locked until criteria are met
    • Progress automatically once approved
• 📩 Notifications
• • Email or task notifications may be triggered depending on configuration

Moving Backwards in the Lifecycle

You can revisit earlier stages if required:

• Select a previous stage and click Set Active, or
• Use the Back button (if available)

Important:

• You can move backward through stages
• However, resetting a project back to the very beginning may require admin access

End-State Limitations

Once a project reaches the final stage:

• It may be marked as Closed / Completed
• Re-activation or reopening may require:
• • Admin access, or
  • Backend/system changes

Project Status (Separate from Lifecycle)

Important:
Advancing the lifecycle stage does not always automatically update the Project Status.

You should:

• Update the Project Status manually (e.g. to Closed or Completed) from the header

Unless:

• Your organisation has configured this to happen automatically

Lifecycle Configuration (How It Is Defined)

• Lifecycle workflows are centrally managed in Power Apps
• The lifecycle applied depends on the Project Type selected at project creation

👉 This means:

• Different project types may have different stages
• Checklist requirements and approvals may vary

Understanding Duration Indicators

The lifecycle also displays timing indicators:

• “Active for X months/weeks” (project level)
• • Shows how long the project has been active
• Stage duration indicators
• • Show how long the project has been in each stage

👉 These help:

• Identify bottlenecks
• Highlight stages requiring follow-up

Key Considerations

• Lifecycle progression is governed by your organisation’s process
• Checklist requirements may vary significantly
• Not all projects follow the same lifecycle
• Some stages may require approval before progressing
• Status updates may need to be done manually

Tips

• Always complete checklist items before progressing
• Use stage duration indicators to identify delays
• Confirm your organisation’s governance rules if unsure
• Ensure Project Status is aligned with lifecycle stage
• Engage stakeholders early if approvals are required