Template Status Tab

TABLE OF CONTENTS

• Adding or Editing Status Levels
• Field Definitions
• Best Practices

Managing Project Status Levels

Project status levels help teams track progress and provide visibility into key stages of work. Administrators can customize these statuses to align with internal workflows, notifications, and governance needs. This article explains how to add and edit the available status levels for a project.

Adding or Editing Status Levels

1. Navigate to the Project Settings for the project you want to configure.
2. Open the Status Tab section by clicking Show Advanced.
3. Add a new status or edit an existing one using the following options:

Field Definitions

• Name: The label or title of the status. This is what users will see when they select or view the project status.
• Notify: Determines whether an email notification prompt is displayed when this status is selected.
• Is Default: Defines the default status assigned to a project following submission. Only one status can be set as the default.
• Progress Next Stage: Automates progression in a stage-gate process when this status is selected. Example: Selecting “Approved” can automatically move the project into the next stage.
  
• Requires Reason Code: Users must provide a reason code when selecting this status. This is useful for statuses such as “On Hold” or “Cancelled,” where context is needed.
  
• Requires Message Popup: Displays a warning message when this status is chosen.
  • The warning text is configured in the text box associated with this option.
  • Example: Selecting “Cancelled” may show a pop-up reminder: “This action will stop all work associated with this project.”

Best Practices

1. Use clear, descriptive names for statuses so users understand their purpose.
2. Enable notifications for statuses that require stakeholder visibility (e.g., “Approved,” “Completed”).
3. Require reason codes for statuses that impact reporting or project tracking.
4. Add warning popups to prevent accidental selections of critical statuses.
5. Align the default status with your most common project starting point.