Critical Path Length Index (CPLI) Explained

<div class="ge-article-wrapper"> <nav class="ge-toc" aria-label="Table of contents"> <p class="ge-toc-label">In this article</p> <ul class="ge-toc-list"> <li><a href="#why-spi-isnt-enough">Why SPI Isn't Enough</a></li> <li><a href="#the-cpli-concept-visually">The CPLI Concept Visually</a></li> <li><a href="#cpli-interpretation-table">CPLI Interpretation Table</a></li> <li><a href="#worked-example-18-month-highway-programme">Worked Example: 18-Month Highway Programme</a></li> <li><a href="#cpli-vs-spi-when-they-disagree">CPLI vs SPI: When They Disagree</a></li> <li><a href="#common-mistakes">Common Mistakes</a></li> <li><a href="#frequently-asked-questions">Frequently Asked Questions</a></li> </ul> </nav> <article class="ge-article-body"> <p>The Critical Path Length Index (CPLI) answers a question that <a href="/en/earned-value/definitions/schedule-performance-index">SPI</a> can't: can this project actually finish on time? SPI tells you how fast you're earning value relative to the plan. CPLI tells you whether the remaining programme duration, including whatever float you have left, is physically sufficient to deliver the remaining critical path work. It bridges the gap between earned value schedule metrics and proper CPM scheduling.</p> <p><strong>CPLI = (Critical Path Length + Total Float) / Critical Path Length</strong></p> <p>Or, expressed differently:</p> <p><strong>CPLI = (CP Remaining Duration + Total Float) / CP Remaining Duration</strong></p> <p>A CPLI of exactly 1.0 means you'll finish on time with zero float remaining. Below 1.0, the maths says you can't finish on time without crashing or fast-tracking. Above 1.0, you have buffer.</p> <p>CPLI is part of the <a href="/en/earned-value/definitions">earned value definitions glossary</a>. For related schedule metrics, see the <a href="/en/earned-value/cpi-spi">CPI and SPI page</a>.</p> <h2 id="why-spi-isnt-enough">Why SPI Isn't Enough</h2> <p>Here's the problem with SPI alone. SPI compares earned value against planned value, both expressed in pounds, not time. A project with SPI of 0.95 is earning value 5% slower than planned. But that doesn't tell you whether the critical path has been affected or whether you've just fallen behind on non-critical work that has float.</p> <p>I've seen projects with an SPI of 0.88 finish on time because the delayed work was off the critical path. I've also seen projects with an SPI of 0.97 finish three months late because a single critical activity slipped and nobody noticed until the float was gone.</p> <p>CPLI fixes this by going directly to the programme. It doesn't care about earned value or budgets. It looks at the critical path length, compares it to the available time, and gives you a binary answer: enough time or not enough time.</p> <h2 id="the-cpli-concept-visually">The CPLI Concept Visually</h2> <pre class="ge-ascii-diagram ge-anim"> PROJECT PROGRAMME – 18 Month Duration (390 working days) Planned completion: Day 390 Today: Day 240 (month 11) CRITICAL PATH (remaining): ├─────────────────────────────────────────────────┤ │ Remaining CP activities = 165 days │ └─────────────────────────────────────────────────┘ AVAILABLE TIME: ├─────────────────────────────────────────────────┤ │ Calendar days remaining to planned completion │ │ = 390 - 240 = 150 working days │ └─────────────────────────────────────────────────┘ TOTAL FLOAT on critical path: -15 days (Critical path extends 15 days beyond the planned completion) CPLI CALCULATION: ┌─────────────────────────────────────────────────┐ │ │ │ CPLI = (CP remaining + Total Float) │ │ ───────────────────────────── │ │ CP remaining │ │ │ │ = (165 + (-15)) │ │ ────────────── │ │ 165 │ │ │ │ = 150 / 165 │ │ │ │ = 0.909 │ │ │ │ RESULT: Project CANNOT finish on time. │ │ Need to compress 15 days from the critical path.│ │ │ └─────────────────────────────────────────────────┘ </pre> <p>When total float is negative, CPLI drops below 1.0. The further below 1.0, the more compression you need. A CPLI of 0.909 means you need to find 15 days of compression on a 165-day remaining critical path, roughly a 9% acceleration. That's achievable with additional resources or revised sequencing. A CPLI of 0.75 means you need 25% acceleration. That's almost certainly unrealistic without a fundamental replanning exercise.</p> <h2 id="cpli-interpretation-table">CPLI Interpretation Table</h2> <div class="ge-table-wrap ge-anim"><table class="ge-table"> <thead> <tr> <th>CPLI Value</th> <th>What It Means</th> <th>Practical Implication</th> </tr> </thead> <tbody> <tr> <td><strong>> 1.10</strong></td> <td>Significant positive float</td> <td>Comfortable. But check whether the programme is realistic, excessive float sometimes means the baseline wasn't properly resource-loaded.</td> </tr> <tr> <td><strong>1.01 to 1.10</strong></td> <td>Adequate float buffer</td> <td>Healthy. Normal operational range.</td> </tr> <tr> <td><strong>1.00</strong></td> <td>Zero float</td> <td>On the wire. Any delay to a critical activity will cause late completion.</td> </tr> <tr> <td><strong>0.95 to 0.99</strong></td> <td>Minor negative float</td> <td>Recovery likely possible through overtime, weekend working, or minor resequencing.</td> </tr> <tr> <td><strong>0.90 to 0.94</strong></td> <td>Moderate negative float</td> <td>Recovery needs a formal plan, additional resources, parallel working, or scope adjustment.</td> </tr> <tr> <td><strong>< 0.90</strong></td> <td>Severe negative float</td> <td>Completion date is unrealistic without fundamental changes. Consider revising the programme baseline, negotiating an extension, or accepting delay damages.</td> </tr> </tbody> </table></div> <h2 id="worked-example-18-month-highway-programme">Worked Example: 18-Month Highway Programme</h2> <span class="ge-worked-label">Worked Example</span> <div class="ge-callout ge-anim"> <p><strong>Scenario:</strong> An 18-month (390 working day) NEC4 Option C highway improvement programme in South Wales. At month 11 (day 240), the project planner runs a CPM schedule update and feeds the results into the CPLI calculation.</p> <p><strong>Programme status at day 240:</strong></p> <ul> <li>Original programme duration: 390 working days</li> <li>Working days elapsed: 240</li> <li>Working days remaining to planned completion: 150</li> <li>Critical path remaining duration: 165 working days</li> <li>Total float on critical path: -15 days</li> </ul> <p><strong>CPLI = (165 + (-15)) / 165 = 150 / 165 = 0.909</strong></p> <p>The critical path extends 15 days beyond the planned completion date. The project can't finish on time at the current rate.</p> <p><strong>Root cause analysis:</strong> The planner traces the negative float to two sources:</p> <ol> <li><strong>Structures package</strong>, Pier 2 foundation redesign added 8 working days to the critical path. This is a compensation event under clause 60.1(1), the Project Manager changed the Works Information. The CE entitlement should include a time extension that recovers 8 of the 15 days, resetting CPLI to approximately 0.955.</li> <li><strong>Surfacing package</strong>, Late delivery of binder course material from the supplier added 7 working days. This is a Contractor risk, no CE entitlement unless the delay was caused by a Client action.</li> </ol> <p><strong>Recovery plan for the 7 Contractor-risk days:</strong></p> <ul> <li>Weekend working on surfacing (2 days recovered, cost: £45,000 in weekend premiums)</li> <li>Parallel working on kerbing and surfacing instead of sequential (3 days recovered, minimal cost)</li> <li>Overtime on drainage tie-ins (2 days recovered, cost: £18,000)</li> <li><strong>Total recovery: 7 days. Estimated cost: £63,000.</strong></li> </ul> <p><strong>Revised CPLI after CE and recovery:</strong> (165 + (-15) + 8 + 7) / 165 = 165 / 165 = <strong>1.00</strong></p> <p>Back to zero float. Not comfortable, but the completion date is achievable.</p> </div> <h2 id="cpli-vs-spi-when-they-disagree">CPLI vs SPI: When They Disagree</h2> <p>This is where it gets interesting. CPLI and SPI can tell completely different stories.</p> <div class="ge-table-wrap ge-anim"><table class="ge-table"> <thead> <tr> <th>Scenario</th> <th>SPI</th> <th>CPLI</th> <th>What's Happening</th> </tr> </thead> <tbody> <tr> <td>Non-critical work delayed</td> <td>0.88</td> <td>1.05</td> <td>Value earned is behind plan, but all the delay is on non-critical activities. Completion date is safe.</td> </tr> <tr> <td>Critical path slipped, offset by early non-critical work</td> <td>1.02</td> <td>0.94</td> <td>Earning value faster than planned overall, but the critical path has slipped. SPI masks the problem.</td> </tr> <tr> <td>Both align</td> <td>0.91</td> <td>0.93</td> <td>The delay is broad-based, both critical and non-critical work are behind.</td> </tr> <tr> <td>SPI healthy, CPLI dropping</td> <td>0.98</td> <td>0.96 → 0.93 → 0.90</td> <td>SPI looks fine because non-critical progress keeps the ratio up. But the critical path is progressively slipping. This is the dangerous scenario, SPI gives false comfort.</td> </tr> </tbody> </table></div> <p>The fourth scenario is the one that catches people out. I've sat in monthly progress meetings where the project manager reports SPI of 0.97 and everyone's relaxed. Meanwhile, the critical path has lost three weeks of float over the last quarter and nobody's tracking CPLI. By the time SPI catches up to reality, it's too late.</p> <p>Track both. Always.</p> <h2 id="common-mistakes">Common Mistakes</h2> <ol> <li><strong>Not updating the programme before calculating CPLI.</strong> CPLI is only as good as the CPM schedule it's based on. If the Accepted Programme hasn't been updated since month 3 and you're now at month 11, your critical path data is fantasy. On NEC4, clause 32.1 requires the Contractor to show on each revised programme the actual progress achieved. Hold them to it. Otherwise CPLI is meaningless.</li> <li><strong>Using total project float instead of critical path float.</strong> CPLI specifically uses the total float on the critical path. Not the float on random non-critical activities. If your scheduling software reports multiple float values, make sure you're using the right one. The critical path, by definition, has the least float (usually zero or negative). Using the float on a non-critical chain gives you a falsely optimistic CPLI.</li> <li><strong>Ignoring CPLI because "we don't do earned value."</strong> CPLI doesn't require earned value data. It uses programme data, critical path length and total float. You can calculate CPLI on any project with a CPM schedule, regardless of whether you're running EVM. If you're producing an Accepted Programme under NEC4, you already have the inputs. Use them.</li> <li><strong>Treating CPLI as static.</strong> CPLI should be recalculated at every programme update. A CPLI of 1.05 in month 6 can become 0.88 by month 12 if critical activities are slipping. Plot CPLI over time alongside <a href="/en/earned-value/definitions/schedule-performance-index">SPI</a>, the trend tells you more than any single data point.</li> </ol> <div class="ge-product-note ge-anim"> <p><strong>How Gather helps.</strong> Gather's AI reads your site diaries daily and maps progress against your cost-loaded programme, giving you accurate earned value data without manual spreadsheet updates. <a href="https://gatherinsights.com/contact">Book a demo</a> to see it working on a live NEC4 project.</p> </div> <h2 id="frequently-asked-questions">Frequently Asked Questions</h2> <h3>What does a CPLI below 1.0 mean?</h3> <p>A CPLI below 1.0 means the remaining critical path work takes longer than the time available to planned completion. The project cannot finish on time without compressing the critical path, through additional resources, parallel working, overtime, or scope reduction. For example, a CPLI of 0.95 means you need to compress the critical path by 5%. A CPLI of 0.85 means 15% compression, which is rarely achievable without fundamental changes to the delivery strategy.</p> <h3>How is CPLI different from SPI?</h3> <p><a href="/en/earned-value/definitions/schedule-performance-index">SPI</a> measures schedule performance using earned value data (SPI = EV / PV), it tells you how fast you're earning value relative to the plan. CPLI measures schedule feasibility using programme data, it tells you whether enough time remains to complete the critical path. SPI can be misleading because it includes non-critical work. A project can have SPI of 0.98 (looks healthy) but CPLI of 0.88 (critical path has slipped badly). CPLI is the more reliable predictor of whether the project will finish on time.</p> <h3>Can CPLI be calculated without earned value?</h3> <p>Yes. CPLI uses only programme data: critical path remaining duration and total float. You don't need EV, AC, PV, or any other earned value metric. If you have a CPM schedule with a defined critical path and float calculation, you can calculate CPLI. This makes it useful even on projects that don't formally implement <a href="/en/earned-value">earned value management</a>.</p> <h3>What is a healthy CPLI range?</h3> <p>For UK construction projects, a CPLI between 1.02 and 1.10 is healthy, enough float to absorb minor delays without threatening the completion date. A CPLI of exactly 1.0 means zero float, which is uncomfortable but manageable if you're monitoring weekly. Below 0.95 requires a formal recovery plan. Below 0.90, the completion date is almost certainly unachievable without either crashing the programme (expensive) or negotiating a time extension.</p> </article> </div>