Expected Finish is a date field available at the activity level in P6 (activity table only) and P6 Professional (activity table and activity details). This field can be used when updating your schedule to indicate when you expect ongoing activities to be completed. This can be very useful when you are involved in a project where the team gives you the date they expect to finish the work instead of the time they need to complete it. This is a widespread situation on a project. This may be because it is more natural for the human brain to come out with a date rather than calculate the time\/effort necessary to reach that date.<\/p>\n
The Main Benefits of Expected Finish<\/strong> As a project manager, it will make it easier to get the progress information during schedule updates and possibly reduce the time you usually spend on that task.<\/p>\n Also, one of the positive effects of using Expected Finish dates is that it helps induce a commitment from your team or your contractors regarding the dates they give you at every progress meeting.<\/p>\n Finally, unlike the Remaining Duration, the Expected Finish date does not require to be changed on every update cycle. Unless there is a change in \u201cin-progress\u201d activities, you can leave the Expected Finish date as it is and let P6 automatically update the remaining duration for you. This is particularly interesting in the case of Master Schedules because they carry many activities with long durations (several weeks to several months) with shorter update cycles (weekly or monthly).<\/p>\n How to Update A Schedule Using Expected Finish Dates<\/strong><\/p>\n The following example explains how to update activities in P6 depending on what has occurred since the last update.<\/p>\n Figure. 1<\/i> shows the status of the schedule as per the last update (March 1st<\/sup>), with the update period in yellow and a new Data Date on April 1st<\/sup>.<\/p>\n Status of activities as per the last update<\/p><\/div>\n The table below summarizes the actions to perform in P6 depending on the status of activities since the last update.\u00a0<\/span><\/p>\n Figure 2 show<\/i>s the schedule after activities have been updated, Data Date has been changed, and the schedule was recalculated. Note that the Expected Finish date on Activity D did not require to be updated, and P6 automatically calculated the Remaining Duration to reach that date.<\/p>\n
\n<\/p>\n![\"Status](\"https:\/\/www.projectp.com\/ppblog\/wp-content\/uploads\/2014\/04\/Figure11.png\")
<\/a>\n\n
\n Status<\/span><\/span><\/i><\/b><\/td>\n Action<\/span><\/span><\/i><\/b><\/td>\n<\/tr>\n \n Activity A: The activity started and finished<\/span><\/span>\u00a0<\/span><\/td>\n Set Actual Start and Actual Finish<\/span><\/span><\/i><\/td>\n<\/tr>\n \n Activity B: The activity started but has not finished<\/span><\/span><\/td>\n Set Actual Start and Expected Finish<\/span><\/span><\/i><\/td>\n<\/tr>\n \n Activity C: The activity was already started and has been finished<\/span><\/span><\/td>\n Set Actual Finish<\/span><\/span><\/i><\/td>\n<\/tr>\n \n Activity D: The activity was already started and is still pending<\/span><\/span><\/td>\n Update Expected Finish if necessary<\/span><\/i><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n