Intro
Primavera P6 Training Insights from Ecostar Plan
One of the most common statements we hear during Primavera P6 training sessions is:
“In P6, if the duration is 1.4 days it shows 1 day, and if it’s 1.6 days it shows 2 days.”
While that observation appears correct, it often leads to a dangerous misunderstanding of how Oracle Primavera P6 actually works.
The reality is that Primavera P6 does not round durations in its calculations. It only rounds what you see on the screen.
Understanding this distinction is essential for planners, schedulers, project controls engineers, and project managers who rely on accurate schedule analysis.
The Key Misunderstanding
Many users assume that because Primavera P6 displays a rounded value, that is the value being used by the scheduling engine.
It is not.
Primavera P6 stores and calculates durations using precise values, typically based on hours. The software then converts those values into days according to the activity calendar and displays them according to the formatting settings of your layout.
In other words:
- Calculations use the actual stored duration.
- Display settings determine what you see.
These are two completely different things.
What You See vs What Primavera P6 Calculates
When a Duration column is configured to display zero decimal places, Primavera P6 applies standard mathematical rounding for display purposes.
| Actual Duration Stored | Displayed Duration |
|---|---|
| 1.4 days | 1 day |
| 1.5 days | 2 days |
| 1.6 days | 2 days |
Looking at the screen, it appears that P6 has converted 1.4 into 1 and 1.6 into 2.
However, internally:
- 1.4 remains 1.4
- 1.5 remains 1.5
- 1.6 remains 1.6
The scheduling logic has not changed.
The activity relationships, float calculations, critical path analysis, and forecast dates are still based on the precise duration values.
Why This Creates Confusion
This misunderstanding becomes particularly problematic when teams perform schedule reviews or compare Primavera P6 outputs with Excel calculations.
Because Primavera P6:
- Calculates using hours
- Converts values using the assigned calendar
- Displays values according to layout formatting
you can easily encounter situations where:
- Two activities both appear as “1 day” but finish at different times
- Activities with apparently identical durations behave differently
- Float values seem inconsistent
- Critical path calculations appear incorrect
In reality, the calculations are correct. The displayed values are simply hiding the precision behind them.
A Practical Example
Imagine two activities:
Activity A: 1.4 days
Activity B: 1.49 days
If your layout displays zero decimal places, both activities will show as:
1 day
Yet the scheduling engine still recognises a difference between them.
This difference can affect:
- Early and late dates
- Total float
- Resource loading
- Progress calculations
- Forecast completion dates
For major infrastructure, construction, engineering, and energy projects, these seemingly small differences can become significant when accumulated across hundreds or thousands of activities.
The Real Risk
The problem is not Primavera P6’s rounding behaviour.
The problem is believing the rounded value is the actual value.
This often leads to:
Incorrect Progress Assessments
Teams may assume activities have identical durations when they do not.
Misunderstood Float Values
Small float differences can disappear when displayed in whole days.
Misinterpretation of Critical Activities
Activities that appear identical may have different criticality due to hidden decimal values.
Excel vs Primavera P6 Discrepancies
Many reporting disputes occur because Excel calculations are performed on displayed values while Primavera P6 uses stored values.
Best Practice for Professional Planners
At Ecostar Plan, we recommend the following Primavera P6 best practices:
Display Durations with Two Decimal Places
This immediately improves transparency and reduces misunderstanding during schedule reviews.
Review Float in Hours
Float analysis is often far more meaningful in hours than in rounded days, particularly on detailed project schedules.
Use Rounded Days Only for Stakeholder Communication
Senior stakeholders typically do not need decimal-level detail. However, planners should always perform analysis using precise values.
Never Adjust Logic Based on Rounded Visuals
If something looks unusual, investigate the underlying values before changing durations, relationships, or constraints.
Why This Matters for UK Project Controls Teams
Across the UK construction, infrastructure, rail, utilities, defence, and energy sectors, Primavera P6 remains one of the most widely used planning tools.
Yet many schedule issues arise not because the software is wrong, but because users misunderstand how the software presents information.
A planner who understands the difference between stored values and displayed values can make better decisions, produce more reliable forecasts, and avoid unnecessary reporting disputes.
This is one of the many practical topics covered in Ecostar Plan’s Primavera P6 training courses, where we focus not only on software functionality but also on the planning principles that drive successful project delivery.
Final Thought
Primavera P6 is extremely precise.
The software does not round durations for scheduling calculations—it only rounds what you see on screen.
If you base planning decisions on what appears to be true rather than what is actually being calculated, the schedule will eventually expose the difference.
Professional planning is not about trusting the display.
It is about understanding the logic behind it.
Looking to Improve Your Primavera P6 Skills?
Ecostar Plan provides practical Primavera P6 training, project controls coaching, and schedule review services for organisations and planning professionals across the UK and internationally.
Whether you are new to Primavera P6 or looking to strengthen your project controls capability, our training focuses on real-world scheduling challenges and industry best practices that can be applied immediately on live projects.
