Primavera P6 Expected Finish vs Microsoft Project
Many planners focus on logic, durations, and progress percentages when updating schedules. However, one small feature difference between Primavera P6 and Microsoft Project can significantly affect forecasting accuracy: the Expected Finish field.
The Primavera P6 Approach
Primavera P6 includes a dedicated Expected Finish field for activities that are already in progress.
When a supervisor provides a realistic completion date for an ongoing activity, P6 automatically recalculates the Remaining Duration required to achieve that date.
Example
- Data Date: 10 May
- Expected Finish: 20 May
P6 automatically adjusts the Remaining Duration so the activity finishes on 20 May.
This allows field intelligence to directly influence the schedule forecast.
The result is a schedule that reflects current site reality rather than relying solely on the original duration assumptions.
How Microsoft Project Handles It
Microsoft Project does not include a native Expected Finish field that behaves the same way.
Although planners can create a custom date field called “Expected Finish”, it remains informational unless additional automation is developed.
Entering a date into a custom field:
- Does not recalculate Remaining Duration
- Does not update forecast logic
- Does not influence schedule calculations
The planner must manually adjust Remaining Duration to achieve the desired forecast.
Why This Difference Matters
The distinction is not simply a software feature.
It affects how project teams update and control schedules.
In Primavera P6:
- Site teams can provide realistic finish dates
- Forecasts immediately reflect field expectations
- Schedule pressure becomes visible
- Recovery actions can be assessed earlier
In Microsoft Project:
- Expected completion dates often remain external notes
- Forecast updates depend on planner intervention
- Schedule changes may be delayed until manual adjustments are made
The Debate Among Project Controls Professionals
The topic generates strong opinions among planners.
Supporters of Expected Finish argue that supervisors know the reality of the work and should provide completion commitments based on actual site conditions.
Others believe excessive use of Expected Finish can introduce hidden contingency and reduce forecasting discipline if not properly controlled.
The key point is that Expected Finish should generally be used for activities already in progress, not as a substitute for planning logic on future work.
Recommended Practice
For activities in progress:
- Capture Actual Start
- Record Physical Percent Complete
- Obtain a realistic Expected Finish or Remaining Duration
- Review impacts on the critical path
For activities not yet started:
- Maintain logic-driven scheduling
- Avoid unnecessary date overrides
- Let network logic determine forecast dates
Final Thoughts
Both Primavera P6 and Microsoft Project are powerful scheduling tools, but they support forecasting in different ways.
Understanding how Expected Finish interacts with Remaining Duration helps planners create forecasts that better reflect project reality and support informed decision-making.
Want to improve your planning and project controls skills?
Ecostarplan provides Primavera P6 training, Microsoft Project training, schedule reviews, and project controls consulting for professionals and organisations seeking better forecasting and schedule performance.