Blog
News
Beyond Performance Indicators: Better Interpreting CPI and SPI in Complex Infrastructure Projects
ByPhilippe Amilton Rego, 2026-03-16, 7:00
6 minutes
Philippe Amilton Rego, P.Eng., M.Eng.
Senior Project Controls Engineer
Montréal, Canada
Senior Project Controls Engineer
Montréal, Canada
Based on observations drawn from professional practice, this article reflects on the interpretation of the CPI and SPI indices in complex infrastructure projects and their role in governance discussions and decision-making.
Introduction
In major infrastructure projects, performance indices derived from Earned Value Management (EVM), particularly the Cost Performance Index (CPI) and the Schedule Performance Index (SPI), are widely used to monitor project performance.
These indicators have proven their value. They allow teams to compare the actual progress of a project with what was planned and to quickly detect certain cost or schedule variances.
In several large-scale infrastructure projects to which I have contributed over the past years, these indicators systematically appear in monitoring discussions, performance reports, and governance reviews. However, experience shows that their interpretation often requires going beyond a purely mechanical reading of the indices.
In complex project environments—particularly in public infrastructure programs involving multiple contracts, numerous stakeholders, and delivery horizons extending over several years—the interpretation of these indicators can become more delicate.
In practice, the reading of CPI and SPI may be influenced by several factors: the structure of the schedule, the timing of cost recognition, changes in the critical path, and the methods used to measure and credit progress.
The objective of this article is not to question the relevance of CPI and SPI, which remain essential tools. Rather, it aims to share observations from professional practice and propose a more contextualized interpretation of these measures in complex infrastructure projects.
CPI and SPI: Essential Tools… but to Be Read with Discernment
In its simplest form, Earned Value Management compares three elements:
-
the planned value of the work
-
the earned value of the work completed
-
the actual costs incurred
The CPI measures cost efficiency, while the SPI reflects progress relative to the planned schedule.
In a relatively stable environment, these indices provide a quick overview of the project's status. A CPI below 1 may signal cost overruns, while an SPI below 1 may indicate a schedule delay.
In large infrastructure projects, however, operational reality is often more nuanced. In some cases, the indices reflect structural effects (schedule design, credit rules, cost recognition) as much as actual field performance.
The Particular Dynamics of Major Infrastructure Projects
Public infrastructure projects often share certain characteristics: long timelines, numerous interfaces, interdisciplinary coordination, and complex contractual structures. Planning typically spans several years and requires the synchronization of many stakeholders.
In such contexts, project progress is not always linear. Some phases generate significant planned progress, while others mobilize teams intensively with little measurable progress in terms of earned value (for example: preparation, integration, coordination, or validation activities).
Furthermore, in multi-contract environments, cost recognition mechanisms and invoicing structures may create temporary misalignment between actual work progress and costs recorded in financial systems.
These factors can influence the interpretation of CPI and SPI if they are analyzed in isolation.
The Interpretation Limits of CPI
CPI is often perceived as a direct indicator of financial performance. In practice, in major infrastructure programs, several elements can influence its interpretation.
Certain preparatory activities may generate significant costs before measurable progress is recognized in the earned value system. Conversely, some phases may generate significant progress with relatively low costs.
The structure of deliverables, billing mechanisms, and milestone definitions can also influence how value is credited to the project.
Scope changes can also affect the interpretation of performance indices. In large infrastructure projects, introducing new activities, modifying deliverables, or adjusting the initial plan may temporarily affect indicator readings without necessarily reflecting a true deterioration of performance.
Another sometimes underestimated factor concerns progress measurement for continuous monitoring activities. Activities related to quality assurance, sustainability, compliance management, or coordination may span long durations. If progress measurement criteria are not clearly defined (or remain highly subjective), earned value may become less representative of the actual status of work.
In such cases, CPI may appear artificially favorable (or unfavorable), not because costs are drifting, but because the credited progress does not accurately reflect reality.
Therefore, a CPI temporarily below 1 does not necessarily indicate financial drift. It may simply reflect a mismatch between cost recognition and value crediting methods. In practice, CPI analysis benefits from being complemented by a review of contractual context, deliverable structure, and progress measurement rules.
The Particular Case of SPI
SPI is probably the indicator most sensitive to project structure.
In complex projects, schedule progression strongly depends on the critical path and the activities composing it. However, earned value does not always directly reflect the logic of the critical path.
It is therefore possible for a project to display a relatively favorable SPI while critical activities are under pressure. Conversely, a temporarily weak SPI may coexist with a relatively stable schedule situation if the affected activities are not on the critical path.
In my experience, SPI interpretation becomes truly useful when combined with schedule analysis, particularly:
-
the position and stability of the critical path
-
the consumption of schedule float
-
the proximity of near-critical paths
-
the schedule’s sensitivity to delays or resource constraints
In some contexts, organizations also use complementary approaches (for example, practices inspired by Critical Chain methods) to better manage buffer consumption and schedule robustness.
The key point, however, is not to reduce schedule analysis to a single indicator.
Critical Path: Understanding Where the Real Risk Lies
Critical path analysis remains one of the most powerful tools for understanding the real dynamics of a project.
While CPI and SPI provide a synthetic measure, schedule analysis helps identify where schedule risks truly lie.
A project may display relatively stable indices while critical buffers are gradually shrinking. Conversely, apparent index deviations may result from planned adjustments, structural schedule effects, or progress crediting methods.
This does not mean performance indices are useless—quite the opposite. They provide an excellent starting point. However, their interpretation benefits from being combined with a careful review of the schedule and an understanding of the mechanisms producing the numbers.
Toward an Integrated Interpretation Framework
In complex infrastructure projects, indicators become particularly valuable when interpreted within a broader framework.
This approach can be understood as an integrated interpretation framework, where CPI and SPI are analyzed alongside critical path behavior and project operational context.
Such a framework may consider:
-
CPI and SPI indicators
-
critical path evolution
-
float consumption
-
contract and deliverable dynamics
-
operational project context
The objective is to transform indicators into decision-support tools, rather than simple “traffic lights” displayed on dashboards.
In many organizations, project controls teams play a key role in this interpretation, transforming indicators into meaningful decision-support information for governance bodies. Their role is to contextualize trends, explain limitations, and help decision-makers ask the right questions at the right time.
Implications for Professional Practice
The observations presented in this article suggest that performance indices should be interpreted within a broader analytical framework, particularly in major infrastructure programs.
Several practical actions can help:
-
interpreting CPI and SPI alongside critical path and schedule dynamics
-
ensuring progress measurement rules (especially for continuous activities) are clear, consistent, and auditable
-
considering contractual mechanisms and cost recognition practices when analyzing performance
-
integrating contextual interpretation into governance discussions beyond the simple “score” of indicators
-
strengthening the role of project controls teams in explaining trends and presenting decision options
In multi-contract environments and large infrastructure programs, this approach helps improve the quality of performance analysis and supports more informed decision-making.
Conclusion
CPI and SPI remain fundamental project management tools. They provide a structured measure of performance and allow early detection of certain trends.
However, in complex infrastructure programs, their interpretation often needs to be placed within a broader context. Schedule structure, critical path evolution, contractual dynamics, and cost recognition mechanisms can all influence the reading of these indicators.
The objective is not to replace these tools but to use them with discernment and complement them with the appropriate analyses at the right time.
In advanced project phases, limitations of these indices may also appear in cost forecasting exercises, sometimes leading organizations to rely more on direct estimation of remaining work. This topic alone would merit deeper analysis.
When combined with careful schedule analysis and operational context awareness, performance indicators become powerful governance and decision-support tools.
In complex infrastructure projects, performance indices should not be interpreted as automatic verdicts but rather as signals inviting deeper analysis of the project's operational context.
In major infrastructure programs, where decisions may carry significant financial and operational consequences, this contextualized interpretation directly contributes to improving the robustness of organizational decision-making.
Author Biography
Philippe Amilton Rego, P.Eng., M.Eng., is a Senior Project Controls Engineer based in Montréal. He has over 14 years of international experience in planning, performance analysis, and governance of major infrastructure projects, particularly in the transportation sector and complex public programs.
His work focuses on performance indicator analysis, interpretation of cost and schedule trends, and supporting governance bodies in managing highly complex projects.
