Checklist
Schedule Health Checklist
Purpose
A quick technical read on whether a programme is sound — before its dates are trusted.
Who it’s for
Planners and controls reviewers checking any Primavera P6 programme.
When to use it
On any baseline or update you need to rely on.
Key areas covered
- Logic, leads & lags
- Constraints & float
- Durations & dates
- Critical-path tests
- CPLI & BEI
Related framework Baseline Integrity →
A DCMA-based read on whether a programme is technically sound — before its dates are trusted. Thresholds are common industry guides; adapt them to your project.
Logic & network
- Missing logic ≤ 5% (activities without a predecessor and successor)
- Leads (negative lag) = 0
- Lags ≤ 5% of relationships
- Finish-to-start relationships ≥ 90%
Constraints & float
- Hard constraints ≤ 5% and justified
- High float (> 44 days) ≤ 5%
- Negative float = 0, or explained and being recovered
Durations & dates
- High duration (> 44 days) ≤ 5%
- No invalid dates (actuals in the future / forecasts in the past)
- Resources assigned where the method requires
Progress & critical path
- Missed tasks within tolerance
- Critical-path test passes (a deliberate large delay moves the finish)
- CPLI ≈ 1.0 or better
- BEI ≈ 0.95 or better