Skip to content
P6 Schedule Analytics

DCMA 14-point assessment

13. Critical Path Length Index (CPLI)

How efficiently the remaining critical path must run to finish on time.

Default threshold
At least 0.95
On the demo programme
FailCPLI = 0.937

Definition

CPLI = (critical path length + total float) ÷ critical path length, where the critical path length is the working days from the data date to the project finish.

How the app counts it

  • The float used is the float of the activity that finishes the project, not the lowest float anywhere, which an intermediate key date could set on its own.
  • If the file's stored dates weren't produced by a reschedule, the app falls back to the lowest float of any open activity and says so.
  • If the scheduled finish is before the data date, CPLI can't be calculated and the check fails with that explanation.

Thresholds, the counting basis and whether the check counts towards the score can all be changed. See settings.

Why it matters

Below 1.0 the remaining path can't absorb any delay: it has to run faster than planned to meet its date.

How to fix it in P6

  1. It reflects negative float at completion. Recover the path or record the delay; see Negative float.

Related