Cost Performance Index and Schedule Performance Index in Construction: What Earned Value Metrics Actually Mean for Indian Project Managers — with Worked Examples in ₹
Key facts at a glance
- Cost Performance Index = Earned Value ÷ Actual Cost. Below 0.95 = meaningful cost overrun in progress.
- Schedule Performance Index = Earned Value ÷ Planned Value. Below 0.90 = 10%+ behind schedule, Liquidated Damages risk growing.
- PMBOK finding: a Cost Performance Index set by month 3 of a project rarely changes by more than 10% at completion
- Most Indian MSME contractors track cost and schedule separately — neither Earned Value metric is ever calculated
- Estimate at Completion = Budget at Completion ÷ Cost Performance Index — your projected total final cost if current performance holds
- VentureVitals calculates Cost Performance Index and Schedule Performance Index per project from live procurement and progress data
In this guide
- What is CPI and how to calculate it (with Indian ₹ example)
- What is SPI and what it tells you about delay risk
- How to calculate all EVM metrics on a real Indian project
- CPI and SPI benchmark thresholds for construction
- Why most Indian MSMEs do not measure CPI or SPI
- What tools calculate CPI and SPI for Indian construction
CPI and SPI are the two most important numbers in active construction project management. They are not complicated. They require no special software to calculate manually. And the vast majority of Indian MSME construction companies — from ₹30 Cr contractors to ₹300 Cr developers — have never calculated either on a single project.
This is not a knowledge gap. Every project manager in India has heard of Earned Value Management. The problem is a data gap: CPI requires knowing how much work has been completed (Earned Value) and how much has been spent (Actual Cost) in the same system, at the same time. These two numbers live in different departments, on different tools, and often with different update frequencies. Until someone reconciles them — which, in monthly reporting cycles, means they are 3–4 weeks stale by the time anyone reads them — neither number is reliable.
This guide explains what CPI and SPI actually mean, shows you how to calculate them with real Indian project values, tells you what the benchmarks say about when a project is in trouble, and explains the structural reason most Indian contractors cannot produce these numbers on demand.
What is CPI (Cost Performance Index) in construction?
CPI (Cost Performance Index) = Earned Value ÷ Actual Cost. It measures how much work you are completing per rupee spent. CPI = 1.0 means exactly on budget. CPI = 0.95 means you are spending ₹100 to get ₹95 of work done — a 5% overrun compounding each period. CPI = 1.05 means you are completing ₹105 of work per ₹100 spent — under budget. Example: a ₹2 Cr office fit-out is 35% complete (EV = ₹70 lakhs) but has spent ₹75 lakhs (AC). CPI = 70/75 = 0.933 — the contractor is spending ₹100 for every ₹93.30 of completed work, a 6.7% cost overrun visible in month 4. On a ₹2 Cr project this is ₹5 lakh overspent already; on a ₹20 Cr project at the same CPI it would be ₹50 lakhs overspent before the month-end report is reviewed.
Sources: PMBOK 7th Edition (Section 4.5 — Earned Value Management); IS 15883 Part 1 (Project Management Guidelines for Construction, Bureau of Indian Standards).
CPI = EV ÷ AC
where EV (Earned Value) = % Work Completed × Budget at Completion (BAC)
and AC = Actual Cost to Date (all expenditure incurred)
Cost Variance (CV): CV = EV − AC
Negative CV = cost overrun; Positive CV = under budget
Estimate at Completion (EAC): EAC = BAC ÷ CPI
Your projected total final cost if current CPI holds for the rest of the project
The EAC formula is the one that should be on every Indian contractor's weekly review. On a ₹20 Cr project running at CPI 0.93 in month 4, EAC = ₹20 Cr ÷ 0.93 = ₹21.5 Cr. The contractor is projecting a ₹1.5 Cr overrun right now, visible in the data, 4 months into the project — not in the month-end report when 12 months have passed and the overrun is irreversible.
What is SPI (Schedule Performance Index) and what does it tell you about delay risk?
SPI (Schedule Performance Index) = Earned Value ÷ Planned Value. It measures how efficiently the project is progressing through the planned schedule. SPI = 1.0 means exactly on programme. SPI = 0.88 means progress is at 88% of the planned rate — for every 10 planned weeks, only 8.8 weeks of progress is made. SPI below 0.90 means more than 10% behind schedule — at this level, without a formal recovery plan, the completion date will be missed and LD exposure is growing. Example: planned to be 40% complete at month 4 (PV = ₹80 lakhs), but only 35% complete (EV = ₹70 lakhs). SPI = 70/80 = 0.875. On a ₹150 Cr portfolio of 12 projects, one project at SPI 0.875 with a CPWD contract worth ₹40 Cr and 12 weeks of planned completion remaining = approximately 10–11 weeks additional delay expected = ₹4–4.4 Cr LD exposure building.
Sources: PMBOK 7th Edition (Section 6.6 — Schedule Control); IS 15883 Part 1; CPWD GCC clause 2 (Compensation for Delay).
SPI = EV ÷ PV
where PV (Planned Value) = % Planned Complete × Budget at Completion
Schedule Variance (SV): SV = EV − PV
Negative SV = behind schedule; Positive SV = ahead of schedule
Predicted Additional Delay:
Expected Remaining Duration = Planned Remaining ÷ SPI
Predicted Delay = Expected Remaining − Planned Remaining
How to calculate all EVM metrics on a real Indian construction project
To calculate EVM you need: Budget at Completion (BAC) = contract value; Planned Value (PV) = % planned complete × BAC; Earned Value (EV) = % actual complete × BAC; Actual Cost (AC) = total expenditure to date (POs raised + invoices paid). Then CPI = EV/AC; SPI = EV/PV; CV = EV−AC; SV = EV−PV; EAC = BAC/CPI. Data sources: % actual complete from progress tracking and daily site logs; AC from purchase orders and actual payments. The challenge for Indian MSMEs: these two sources are maintained by different teams. Finance tracks expenditure in Tally; site tracks progress in WhatsApp. Reconciling them requires a joint monthly exercise — meaning EVM data is always 3–4 weeks stale when it is finally assembled. VentureVitals connects procurement (PO data = AC proxy) and progress tracking (% complete = EV base) in the same system, calculating CPI/SPI continuously. Sources: PMBOK 7th Edition; IS 15883 Part 1.
Sources: PMBOK 7th Edition (Earned Value Management — all metrics); IS 15883 Part 1 (Project Management Guidelines for Construction, Bureau of Indian Standards).
Worked Example: ₹2 Cr Commercial Office Fit-Out, Bengaluru
Project details: ₹2 Cr fit-out, 20-week programme, private sector FIDIC-based contract.
Month 4 measurement:
BAC = ₹2,00,00,000 (₹2 Cr)
Planned % complete at month 4 = 40% → PV = ₹80,00,000
Actual % complete = 35% → EV = ₹70,00,000
Actual expenditure to date = ₹75,00,000 → AC = ₹75,00,000
Calculated metrics:
CPI = 70 ÷ 75 = 0.933 (spending ₹100 to get ₹93.30 of work)
SPI = 70 ÷ 80 = 0.875 (progressing at 87.5% of planned rate)
CV = 70 − 75 = −₹5,00,000 (₹5 lakh cost overrun)
SV = 70 − 80 = −₹10,00,000 (₹10 lakh worth of work behind schedule)
EAC = 2,00,00,000 ÷ 0.933 = ₹2,14,36,228 (projected final cost = ₹2.14 Cr if CPI holds)
Interpretation: At month 4, this project is already projecting a ₹14.4 lakh overrun. At SPI 0.875, with 16 weeks of work planned remaining, the expected additional duration is 16 ÷ 0.875 = 18.3 weeks — meaning approximately 2.3 weeks additional delay. On a FIDIC contract with ₹80,000/day LD, that is ₹12.9 lakh exposure building.
CPI and SPI benchmark thresholds for Indian construction projects
From PMBOK and PMI EVM practice standard: CPI above 1.05 = exceptional (under budget); 1.00–1.05 = on track; 0.95–1.00 = marginal, monitor weekly; 0.90–0.95 = meaningful overrun, corrective action required; below 0.90 = significant overrun, recovery plan needed; below 0.85 = crisis. SPI above 1.00 = ahead of schedule; 0.95–1.00 = on schedule; 0.90–0.95 = slightly behind, monitor and recover; below 0.90 = behind schedule, LD risk growing; below 0.85 = significant delay, formal recovery plan required. Critical PMBOK finding: a CPI established by the end of 20% of project duration rarely changes by more than 10% at completion. CPI of 0.88 at month 4 of a 20-month project predicts a final overrun of approximately 10–15% of contract value with high probability. Sources: PMBOK 7th Edition; PMI Practice Standard for EVM (2nd Edition, 2011).
Sources: PMBOK 7th Edition (Section 4.5); PMI Practice Standard for Earned Value Management, 2nd Edition (2011); IS 15883 Part 1.
| Metric | Value Range | Status | Action |
|---|---|---|---|
| CPI | > 1.05 | Exceptional | Monitor — verify % complete is not inflated |
| CPI | 1.00–1.05 | On Track | Continue current approach |
| CPI | 0.95–1.00 | Marginal | Weekly monitoring; investigate cost drivers |
| CPI | 0.90–0.95 | Overrun | Corrective action plan required this week |
| CPI | < 0.90 | Crisis | Major scope/cost review; client communication |
| SPI | > 1.00 | Ahead | Monitor — maintain resource levels |
| SPI | 0.95–1.00 | On Schedule | Continue; monitor for emerging slippage |
| SPI | 0.90–0.95 | Slipping | Recovery plan; evaluate resource increase |
| SPI | < 0.90 | At Risk | Formal recovery plan; assess LD exposure now |
Why most Indian construction MSMEs do not measure CPI or SPI
Three structural reasons: (1) Data silos — cost tracking in Tally or Excel (finance team); progress tracking in WhatsApp and site reports (project team). Nobody reconciles the two into EVM terms because it requires agreeing on '% complete' for each work item, which is contested between site-team optimism and finance-team conservatism; (2) No time-phased baseline — EVM requires a Performance Measurement Baseline (PMB), a week-by-week plan of % complete. Most Indian MSME projects have a completion date but not a formal programme with weekly milestones; (3) No integrated tool — Tally (for AC) and Excel (for % complete) are not connected. The reconciliation requires a manual joint exercise. VentureVitals connects procurement PO data (AC proxy) and daily progress tracking (% complete = EV base) in one system, calculating CPI/SPI continuously rather than monthly. Sources: PMBOK 7th Edition; IS 15883 Part 1; field observation of Indian MSME construction practice.
Sources: PMBOK 7th Edition (Performance Measurement Baseline); IS 15883 Part 1; PMI Practice Standard for Earned Value Management (2011).
What tools calculate CPI and SPI automatically for Indian construction projects?
For automatic CPI/SPI calculation, a tool must: track actual expenditure per project (POs, invoices, payments); track actual physical progress (% complete, milestone status, daily logs); maintain a time-phased baseline (planned value per period); calculate EV = % complete × BAC and AC from procurement data. Primavera P6 and MS Project track schedule but not actual cost against live procurement. Procore has cost tracking but is enterprise-priced and not configured for CPWD/FIDIC BOQ-based contracts. VentureVitals calculates CPI/SPI per project from the same procurement and progress data — PO lifecycle provides AC; progress tracking provides % complete; variance analysis module displays both metrics with corrective action recommendations when either drops below 1.0. For spot calculations: use the free CPI/SPI calculator at logicleap.in. Sources: VentureVitals codebase (variance-analysis.tsx, purchase-orders.tsx, progress-tracking.tsx); PMBOK 7th Edition.
Sources: VentureVitals AI codebase (components/sections/variance-analysis.tsx); PMBOK 7th Edition; PMI Practice Standard for Earned Value Management.
Calculate your project's CPI and SPI right now. Enter your BAC, actual % complete, planned % complete, and actual cost to date.
Free CPI / SPI Calculator →Or see how construction CEOs use VentureVitals to track CPI/SPI across a portfolio of 5–50 projects automatically — updated from live data, not monthly reports.
Related reading
Liquidated damages in Indian construction contracts — complete guide (ICA 1872 s.74, CPWD, FIDIC)
VentureVitals AI — complete platform for Indian construction MSMEs