An expected finish is a date the scheduler enters when they know when work will end, for example from the foreman’s estimate, rather than updating remaining duration by hand. In Primavera P6 it takes effect only when the project’s Use expected finish dates option is on. The calculation then sets the remaining work so the activity finishes on the expected finish.
Worked example
Illustrative: Rough-in plumbing, level 3 started last week and the foreman says it’ll be done Friday. Instead of working out the remaining duration, the scheduler enters Friday as the expected finish. With the option on, the next calculation finishes the activity on Friday and moves its successors to match. If the option is off, the date is stored but ignored.
How it interacts with constraints
Measured in P6 23.12.1:
- On work not started, an expected finish drops the early side of Finish On or After, Finish On and Mandatory Finish. The work starts from its logic and finishes on the expected finish.
- On work under way, the late side of Start On or Before, Start On, Mandatory Start and Mandatory Finish no longer applies. Finish On and Finish On or Before still cap the late dates.
- Work whose finish an expected finish holds has no free float.
Common mistakes
- Entering expected finishes with the option off, then wondering why nothing moved.
- Leaving an old expected finish in place after the work slips. It keeps pulling the forecast to a date nobody believes.
- Entering an expected finish on a milestone. os.construction doesn’t apply it there and warns.
How os.construction handles it
Expected finish dates come in from XER and P6 XML, are kept on the activity and go back out on export, and Use expected finish dates is a project setting. The engine follows P6 23.12.1 on the constraint interactions and free float above, measured on probe projects. It doesn’t apply an expected finish to milestones, and warns when one is set. See P6 compatibility.
FAQ
Is an expected finish a constraint?
Not formally, but it acts like one: the activity is fitted to finish on that date. It interacts with real constraints, and in P6 it can override the early or late side of some of them.
Why does an activity with an expected finish show no free float?
P6 gives no free float to work whose finish an expected finish holds, because the date is fixed by the entry rather than by its successors.