Schedule Compression Index (SCI) in EVM 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="#the-formula">The Formula</a></li><li><a href="#visualising-schedule-compression">Visualising Schedule Compression</a></li><li><a href="#worked-example-30m-rail-depot-refurbishment">Worked Example: £30M Rail Depot Refurbishment</a></li><li><a href="#why-this-metric-matters-in-construction">Why This Metric Matters in Construction</a></li><li><a href="#sci-threshold-guide">SCI Threshold Guide</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 Schedule Compression Index measures how fast you need to work compared to how fast you planned to work. It's the ratio of remaining planned duration to remaining actual duration available. When the number drops below 1.0, your team has to execute the remaining work faster than the original programme assumed, and every tenth of a point below 1.0 means more risk, more pressure, and usually more cost.</p><p>It's one of those metrics that doesn't get enough attention in UK construction. Most teams track <a href="/en/earned-value/definitions/schedule-performance-index">SPI</a> and leave it there. But SPI tells you how efficient progress has been so far. The Schedule Compression Index tells you what's required going forward. Different question. Often a more useful one.</p><p>This metric is part of the <a href="/en/earned-value/definitions">earned value definitions glossary</a>. For the broader schedule performance framework, see the <a href="/en/earned-value/cpi-spi">CPI and SPI formula page</a>.</p><h2 id="the-formula">The Formula</h2><div class="ge-formula-box ge-anim"><span class="ge-formula-label">Formula</span><code>Schedule Compression Index = Remaining Planned Duration / Remaining Available Duration</code></div><p>Or equivalently:</p><p><strong>SCI = (Planned Duration - Elapsed Time) / (Revised Forecast Duration - Elapsed Time)</strong></p><p>An SCI of 1.0 means the remaining work can be done at the originally planned pace. Below 1.0, the work needs to happen faster than planned. Above 1.0, there's slack, you could go slower and still finish on time.</p><h2 id="visualising-schedule-compression">Visualising Schedule Compression</h2><pre class="ge-ascii-diagram ge-anim">BASELINE PROGRAMME ├──────────────────────────────────────────────┤ Month 1 Month 12 Month 24 Start Planned Finish NOW (Month 8) ├────────┤ Elapsed ├─────────────────────────────────────┤ (8 mo) Remaining Planned = 16 months CURRENT FORECAST ├────────┤ Elapsed ├───────────────────────────────────────────┤ (8 mo) Remaining at Current Rate = 18.3 months Forecast Finish: Month 26.3 SCI = 16 / 18.3 = 0.874 The remaining work must be executed at 114% of the original planned pace (1 / 0.874) to finish on the original date.</pre><p>That number, 114%, is what matters. It means every month from now on needs to deliver 14% more progress than the programme assumed. On a complex construction project with weather windows, resource constraints, and interface dependencies, that's a tall order.</p><h2 id="worked-example-30m-rail-depot-refurbishment">Worked Example: £30M Rail Depot Refurbishment</h2><span class="ge-worked-label">Worked Example</span><div class="ge-callout ge-anim"><p><strong>Scenario:</strong> A £30M NEC4 Option C rail depot refurbishment, 24-month programme starting April 2024. At the end of month 8 (November 2024), the commercial team assesses the schedule position.</p><p><strong>Elapsed time:</strong> 8 months <strong>Remaining planned duration:</strong> 24 - 8 = 16 months <strong>Progress achieved:</strong> 28% complete (<a href="/en/earned-value/definitions/earned-value">EV</a> = £8.4M) <strong>Progress expected by month 8:</strong> 33% (<a href="/en/earned-value/definitions/planned-value">PV</a> = £9.9M) <strong><a href="/en/earned-value/definitions/schedule-performance-index">SPI</a></strong> = £8.4M / £9.9M = 0.848</p><p>At current performance, the remaining 72% of work at SPI 0.848 will take: Remaining forecast duration = 16 months / 0.848 = 18.9 months</p><p><strong>SCI</strong> = 16 / 18.9 = <strong>0.847</strong></p><p><strong>Interpretation:</strong> The team needs to execute at 118% of the planned production rate (1/0.847) for every remaining month to hit the original completion date. That's not impossible, but it's aggressive, especially on a refurbishment project where access constraints tend to get worse, not better, as work progresses.</p><p>The project director's question becomes: can we realistically sustain 118% of planned pace for 16 straight months? If the honest answer is no, it's time to discuss programme extension or acceleration measures. On this job, the acceleration estimate came back at £1.8M for additional shifts and weekend working. The LD rate was £45,000 per week. With 2.9 months of likely delay, that's roughly £565,000 in LDs versus £1.8M to accelerate. The numbers made the decision easy: take the delay, manage the LDs.</p></div><h2 id="why-this-metric-matters-in-construction">Why This Metric Matters in Construction</h2><p>The Schedule Compression Index surfaces a question that SPI alone can't answer: is recovery realistic?</p><p>An SPI of 0.85 sounds bad, and it is. But it doesn't tell you whether recovery is feasible. SCI does. An SCI of 0.95 means you only need to work 5% faster than planned, achievable on most projects. An SCI of 0.70 means you need to work 43% faster. That's not recovery. That's fantasy.</p><p>I've seen project teams present recovery programmes showing impossible compression ratios without ever calculating the SCI. They'll promise to make up six months in twelve by "increasing resources" without quantifying what that actually requires. SCI forces honesty. When the number says you need 140% of planned pace and you've never achieved more than 105%, the conversation changes.</p><h2 id="sci-threshold-guide">SCI Threshold Guide</h2><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>SCI Range</th><th>What It Means</th><th>Typical Action</th></tr></thead><tbody><tr><td><strong>> 1.05</strong></td><td>Ahead of plan, surplus duration available</td><td>Monitor normally. Consider resequencing to capitalise.</td></tr><tr><td><strong>0.95 to 1.05</strong></td><td>On track, minor compression at most</td><td>Normal management. Small adjustments may recover any gap.</td></tr><tr><td><strong>0.85 to 0.94</strong></td><td>Moderate compression needed</td><td>Increase resources on critical path. Review sequencing for gains.</td></tr><tr><td><strong>0.75 to 0.84</strong></td><td>Significant compression</td><td>Formal acceleration plan required. Cost the options vs LD exposure.</td></tr><tr><td><strong>< 0.75</strong></td><td>Severe compression</td><td>Recovery likely unrealistic at planned scope. Negotiate programme extension or scope reduction.</td></tr></tbody></table></div><h2 id="common-mistakes">Common Mistakes</h2><p><strong>1. Confusing SCI with SPI.</strong> They're related but answer different questions. SPI looks backward (how efficient has progress been?). SCI looks forward (how fast must we go from here?). You can have an SPI of 0.90 with an SCI of 0.95 if you're early in the project with plenty of duration remaining. Late in the project, the same SPI produces a much worse SCI because there's less time left to recover.</p><p><strong>2. Not updating the forecast duration.</strong> SCI requires an honest forecast of remaining duration. If you keep using the original planned finish date when the programme clearly shows a later completion, your SCI is meaningless. Use the current forecast, not the contractual date.</p><p><strong>3. Ignoring the cost of compression.</strong> An SCI of 0.85 tells you compression is needed, but not what it costs. Acceleration typically comes with premium rates, overtime, weekend working, additional plant, expedited materials. Always cost the compression before committing to it. On NEC4, acceleration is a separate agreement under clause 36, and the cost is the Contractor's to bear unless the PM agrees otherwise.</p><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>How is the Schedule Compression Index different from SPI?</h3><p><a href="/en/earned-value/definitions/schedule-performance-index">SPI</a> measures how efficiently you've delivered progress to date (backward-looking). SCI measures how fast you need to deliver the remaining work to finish on time (forward-looking). A project at month 3 of 24 with SPI of 0.80 has an SCI of roughly 0.94, plenty of time to recover. The same SPI at month 20 of 24 produces an SCI around 0.36, hopelessly compressed. Same SPI, vastly different recovery picture.</p><h3>What SCI value makes recovery unrealistic?</h3><p>Below 0.75 on most construction projects. That means executing 33% faster than planned for every remaining month. Some projects can sustain that briefly, a week or two of overtime, but maintaining it for months across multiple work fronts isn't realistic. Once you're below 0.75, the conversation should shift from "how do we recover?" to "what's our extension of time position?"</p><h3>Can SCI improve during the project?</h3><p>Yes. If you accelerate production and start delivering above the planned rate, SCI rises. It's a dynamic metric that responds to actual performance changes. That's its value. It tells you in real time whether your recovery actions are working.</p><h3>Is SCI used in NEC4 contracts?</h3><p>Not explicitly. NEC4 doesn't reference earned value metrics. But SCI is invaluable for programme management under clause 31/32, particularly when justifying acceleration proposals or demonstrating that an <a href="/en/earned-value/definitions/accepted-programme">Accepted Programme</a> is no longer achievable. The number gives commercial weight to what would otherwise be a subjective argument about programme feasibility.</p></article></div>