Differentiating 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 Planned Dates are the dates that the Project Owner defines as the start and the end dates of the tasks. 

When the task is first created, the Planned, Projected, and Estimated Dates should typically match. Some exceptions exist. 

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.
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

You or the Project Owner can manually modify the Planned Dates on a task.
However, you cannot manually modify either the Estimated nor the Projected Dates of tasks. They are both calculated by 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 also influences the Projected and Estimated Dates of the task.

Here are some scenarios when the Projected Dates of tasks are changed during the life of a project: 

  • 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
  • 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
  • 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

In comparison with the scenarios described above for the Projected Dates, the Estimated Dates always reflect the real analysis by the system on when the task will start or complete regardless of the Constraint or Commit Dates.


This information should be included in the MAIN Dates articles for Projects, Issues, and Tasks - part of the Phase 3 project for Documentation. This should not remain as a TTT article. 

Issue where the answers for this article are:

This article last updated on 2018-03-02 20:40:23 UTC