The core issue is the ambiguity of using the single "Planning" status for two distinct project states: waiting for team capacity (backlog) and actively being prepared for execution. Creating a custom "Backlog" status introduces a clear, sequential stage in the project lifecycle. This allows projects created from templates to be placed in the "Backlog" status initially. Once the team has capacity and begins active preparation, the status can be changed to "Planning." This provides an unambiguous, system-driven way for the team to differentiate between the two states, directly resolving the stated confusion.

A. Load the project template once the team has bandwidth to start on the project.

This approach avoids creating a backlog, which contradicts the requirement that projects are created for the year and wait until the team has capacity.

B. Create projects but leave the roles in place without assigning users.

Staffing status (assigned vs. unassigned roles) is separate from the project's lifecycle status. This does not resolve the confusion over whether a project is in a backlog or being actively planned.

1. Adobe Experience League Documentation - Create or edit a status: This document explains the process and purpose of creating custom statuses. It states

"You can create custom statuses to match the workflows in your organization." Creating a "Backlog" status is a direct application of this functionality to define a specific workflow step.

Source: Adobe Workfront Documentation

"Create or edit a status

" Section: "Create a custom status."

2. Adobe Experience League Documentation - System project statuses: This document defines the default "Planning" status. Its intended use is for when "the project is being planned and prepared." Using it for a pre-planning backlog overloads its meaning

justifying the need for a separate

custom status for the backlog phase.

Source: Adobe Workfront Documentation

"System project statuses

" Section: "Planning."

3. Adobe Experience League Documentation - Customize unlocked system statuses: This guide details how administrators can tailor statuses to fit their organization's needs. It reinforces the principle that Workfront's status system is designed to be flexible and adapted to specific processes

such as implementing a backlog stage before the standard planning stage.

Source: Adobe Workfront Documentation

"Customize unlocked system statuses."