Task Progress Status overview
Adobe Workfront determines the Progress Status of a task by looking at the progression of the task across its timeline. You can configure Workfront to determine the Condition of a project based on the value of the Progress Status of the tasks. For more information about configuring the Condition of the project, see the article Overview of Project Condition and Condition Type.
Criteria that determine the Progress Status of tasks
For information about the Progress Status of a project, see Project Progress Status overview.
For information about tracking the progress of your tasks, see Task Tracking Mode overview.
The following criteria determine the Progress Status of a task:
A task is considered On Time when all the Planned Dates match the Projected Dates. This Progress Status could also mean that the project is ahead of schedule and the Projected Dates could be before the Planned Dates.
For more information about Projected Dates, see Overview of the Projected Completion Date for projects, tasks, and issues.
For more information about task Planned Completion Date, see the following articles:
A task is considered At Risk when the Estimated Completion Date is later than the Planned Completion Date and later than the Projected Completion Date. This can happen when a task has a constraint of Must Finish On or Must Start On but the percent complete or the predecessor relationships of the task show that it cannot finish or start on the specified dates.
Setting the Task Constraint to Must Finish On manually sets the Planned Completion Date to a specific date. The Projected Completion Date in this case matches the Planned Completion Date. In the case of this constraint, Workfront analyzes the task to calculate when it will finish based on the percent completed. This calculation is stored as the Estimated Due Date. If the Estimated Due Date is after the Projected Completion Date, the task is considered at risk of being late.
Setting the Task Constraint to Must Start On manually sets the Planned Start Date to a specific date. The Projected Start Date in this case matches the Planned Start Date. In the case of this constraint, Workfront analyzes the task to calculate when it will start based on its predecessor relationships. This calculation is stored as the Estimated Start Date. If there is an enforced predecessor that will not allow the task to start on the specified Start Date, then the Estimated Start Date can be after the Projected Completion Date. The task is considered at risk of being late.
Note: Typically, Estimated Dates match Projected Dates except for when Must Start On or Must Finish On are used. In these cases, Estimated Dates continue to calculate based on percent complete and other factors (predecessor relationships), while the Projected Dates are forced to match the Planned Dates which have been set manually.
A task is considered to be Behind when the Estimated Completion Date is later or equal than the Planned Completion Date and sooner than the Projected Completion Date.
The Projected Completion Date is a real-time view of when the task will be completed based on prior progress. Though the task was started late, it is not considered late yet, because the Planned and Projected Completion Dates are still in the future, and the task might still be completed on time.
Note: The Behind and At Risk Progress Statuses are almost identical. However, At Risk indicates there are some forced Task Constraints (Must Finish On, Must Start On, Fixed Dates) on one or both of the Planned Dates. If there are no forced constraints on the task, the Projected Dates are the same as the Estimated Dates and reflect the system calculation of the Completion Date based on the current progress of the task. The task is not considered late yet, because the Planned and Projected Completion Dates are still in the future, and the task might still be completed on time.
For more information about the Projected and the Estimated Dates, see Differentiate between Projected and Estimated Dates.