Differentiate between Projected and Estimated Dates
There are several types of dates that show the timeline of tasks between when they can start and when they can complete. The following are some dates that display the timeline of tasks:
- Planned Start and Planned Completion Dates
- Projected Start and Projected Completion Dates
- Estimated Start and Estimated Due Dates
- Actual Start and Actual Completion Dates
This article describes the differences between the Estimated and the Projected Dates for projects.
When the task is first created, the Planned, Projected, and Estimated Dates should typically match. Some exceptions exist.
For more information on the project, task, and issue dates in Adobe Workfront, see Overview of the Project, Task, and Issue dates in Adobe Workfront.
Overview of Planned Dates
The Planned Dates are the dates that the Project Owner defines as the start and the end dates of the tasks. You or the Project Owner can manually modify the Planned Dates on a task.
Overview of Actual Dates
When a task is first created, it has no Actual Dates because it has not started nor completed yet.
Overview of Projected and Estimated Dates
During the life of a project, the Projected and Estimated Dates are more in line with the reality of the project, as they take into account what can influence the actual start and end of a task. This causes them to change from the Planned Dates.
Consider the following when working with Projected and Estimated Dates on tasks:
-
You cannot manually modify either the Estimated nor the Projected Dates of tasks. They are both calculated by Adobe Workfront.
-
When you create a task, the Projected and the Estimated dates should be identical and they should illustrate the actual times when the tasks can start or end.
Certain updates that you make to tasks directly affect the values of the Projected and Estimated Dates.For example, if the user starts or completes a task, the task displays Actual Start and Completion Dates which influence the Projected and Estimated Dates of the task. Also, if an assignee on the task modifies the Commit Date, this date influences the Projected Date of the task.
Difference between Projected and Estimated Dates
The difference between Projected and Estimated Dates is:
-
Projected Dates are affected by a user making the following updates on the task:
- Add a Constraint Date by adding a fixed Task Constraint
- Add a Commit Date
-
Estimated Dates only take into account the real progress on a task in a given point in time.
Example: If we have a task that has a Planned Start Date of September 20 and a Planned Completion Date of September 24, and it has Must Finish On Constraint, the Projected Completion Date September 24. This task has a Duration of 4 days.
The Estimated Completion Date is calculated based on the current progress of the work on the task. So, if today is September 23 and the task has not started yet, the Estimated Completion Date is September 27 (it should be completed after 4 days, assuming that the work is started today).
If the task is 50% completed today, the Estimated Completion Date is on September 25 (it should be completed after 2 days which is half of the Duration of the task).
Understand when Projected Dates update on tasks understand-when-projected-dates-update-on-tasks
The Projected Dates can either match other task dates, or they are a calculation done by Workfront that takes into consideration the real-life progress of the task.
The following list displays several scenarios when the Projected Dates of tasks are changed during the life of a project depending on what happens in real life to the task:
-
When a task is marked as Complete:
Projected Dates = Estimated Dates = Actual Dates
-
When a task has an Actual Start Date:
Projected Start Date = Estimated Start Date = Actual Start Date
-
When a task does not have an Actual Start Date, but there is a forced constraint on the Planned Start Date (Must Start On) that is in the future:
Projected Start Date = Constraint Date
For information about Constraint Date, see Glossary of Adobe Workfront terminology.
-
When a task does not have an Actual Start Date and the task does not have a forced constraint date:
Projected Start Date = the next available date in the future that falls within working schedule
-
When the assignee updates the Commit Date:
Projected Completion Date = Commit Date
For information about Commit Date, see Commit Date overview.
-
When the task does not have an updated Commit Date and the task has a forced constraint (Must Finish On) for the Planned Completion Date that is in the future:
Projected Completion Date = Constraint Date
-
When a task does not have an updated Commit Date, a forced constraint date in the future, or it has a Constraint Date in the past:
Projected Completion Date = system calculation for the Completion Date based on the current progress and the work left to be done
Understand when the Estimated Dates update on tasks understand-when-the-estimated-dates-update-on-tasks
In comparison with the scenarios described above for the Projected Dates, the Estimated Dates always reflect Workfront’s real analysis of when the task will start or complete regardless of the Constraint or Commit Dates.
What influences the timeline of a task
The following are some examples of what can influence the real timeline of a task:
-
Task progress in relation to the Planned Dates and to the current day
-
Percent complete of the task so far
-
Predecessor relationship
-
Predecessor progress
-
User allocation
note note NOTE User allocation can influence the Estimated Completion Date of a task if they affect the speed with which the task can be completed. For example, if the task Duration Type is Effort Driven, you can make the task complete sooner by adding assignees. As a result, the Estimated Completion Date changes.