Construction Project Controls: Cost, Schedule, and Earned Value Management

Project controls is the discipline of measuring, monitoring, and managing the three primary variables of a construction project — scope, cost, and schedule — in an integrated way throughout the project lifecycle. Where project management focuses on directing the work, project controls focuses on tracking it: establishing baselines, measuring performance against those baselines, forecasting where the project will end up, and providing the data the project manager needs to make corrective decisions. On large commercial, infrastructure, and industrial projects, a dedicated project controls function is standard. On smaller projects, the same principles apply even if they're implemented by the PM directly rather than a specialist. Understanding how project controls works is essential for any project team seeking to deliver on budget and on schedule rather than discovering problems at closeout.

The Control Triangle: Scope, Cost, and Schedule

Every construction project is defined by three constrained variables — the "iron triangle" or "triple constraint" of project management:

Scope

What is being built — the full definition of work, specifications, and deliverables. Scope creep (uncontrolled expansion) is the primary driver of cost and schedule overruns. Every change to scope must be evaluated for its cost and schedule impact before authorization.

Cost

What the project costs — labor, materials, equipment, subcontracts, overhead, and profit. The cost baseline is the approved budget. Project controls tracks actual costs against the baseline and forecasts the final cost at completion.

Schedule

When the project will be done — the CPM schedule from NTP to substantial completion. The schedule baseline is the approved CPM. Project controls tracks actual progress against the baseline and forecasts the completion date.

The triangle is constrained: changing any one variable affects the others. Compressing the schedule (adding resources) increases cost. Cutting cost (reducing resources) extends the schedule or reduces scope. Adding scope with no budget or schedule adjustment creates a deficit. Integrated project controls makes these trade-offs visible — rather than allowing the team to make scope changes without understanding their cost and schedule consequences.

Earned Value Management: The Core Framework

Earned Value Management (EVM) is the industry standard methodology for integrating scope, cost, and schedule into a single performance measurement framework. Required on US federal projects over $20M (OMB Circular A-11), it is increasingly used on large private commercial and industrial projects. EVM works by assigning a dollar value to every unit of work — and then comparing what was planned to cost, what was actually accomplished (earned), and what was actually spent.

The Three Core Metrics

Planned Value (PV)
aka BCWS

The budgeted cost of work scheduled to be complete by a given date. The PV curve is the S-curve of the project budget over time — it represents what the project should have cost to this point based on the approved schedule. PV is derived from the baseline schedule and budget.

Earned Value (EV)
aka BCWP

The budgeted cost of work actually performed to date. EV is calculated by multiplying the percentage complete of each work package by its budgeted value. If a $100K work package is 60% complete, it has earned $60K — regardless of what was actually spent. EV represents the value of work actually accomplished in budget terms.

Actual Cost (AC)
aka ACWP

The actual cost incurred for the work performed to date — what has actually been spent. AC comes from the cost accounting system: labor hours × rates, invoices paid, committed purchase orders. AC answers "what did we actually spend?"

The Four Performance Indicators

Metric	Formula	What It Means	Healthy Value
Cost Variance (CV)	EV − AC	Positive = under budget; Negative = over budget. Measures cost performance for work done.	CV ≥ 0
Schedule Variance (SV)	EV − PV	Positive = ahead of schedule; Negative = behind schedule. Measures schedule performance in cost terms.	SV ≥ 0
Cost Performance Index (CPI)	EV ÷ AC	Efficiency of cost spending. CPI of 0.85 means you're getting $0.85 of work for every $1.00 spent.	CPI ≥ 1.0
Schedule Performance Index (SPI)	EV ÷ PV	Efficiency of schedule progress. SPI of 0.90 means the project is progressing at 90% of the planned rate.	SPI ≥ 1.0

EVM example: At month 6 on a $10M project: PV = $4.5M (what should have been spent per plan), EV = $3.8M (value of work actually done), AC = $4.2M (what was actually spent). Result: CV = −$400K (over budget), SV = −$700K (behind schedule), CPI = 0.90 (getting 90¢ per dollar), SPI = 0.84 (progressing at 84% of planned rate). The project is both behind schedule and over budget — and if the CPI holds, the final cost will be ~$11.1M instead of $10M.

Forecasting: Estimate at Completion (EAC)

The most actionable output of EVM is the Estimate at Completion (EAC) — a forecast of the total project cost at completion based on current performance. Several formulas exist; the most common in construction:

EAC = BAC ÷ CPI

Budget at Completion divided by CPI. Assumes current cost efficiency will continue for the remainder of the project. This is the most pessimistic forecast — if you're running at CPI 0.90, it projects that every remaining dollar will also only return 90¢ of work. On a $10M project at CPI 0.90: EAC = $10M ÷ 0.90 = $11.1M.

EAC = AC + (BAC − EV)

Actual cost plus remaining work at budget rates. Assumes the overrun to date was a one-time event and remaining work will be performed at budgeted rates. More optimistic than the CPI method. Used when there's a clear, identified cause of the past overrun that won't recur.

EAC = AC + [(BAC − EV) ÷ (CPI × SPI)]

Composite forecast. Weights both cost and schedule performance in projecting the remaining work cost. Used when both cost and schedule inefficiency are expected to affect future performance. This is the most conservative — and most realistic — forecast when the project is behind on both dimensions.

The gap between EAC and the Budget at Completion (BAC) is the Variance at Completion (VAC) — the projected overrun or underrun at project end. Tracking VAC monthly and understanding its trajectory is the primary early warning system for budget problems.

The S-Curve and Cash Flow Forecasting

The S-curve is the cumulative plot of planned value (PV), earned value (EV), and actual cost (AC) over the project timeline. It takes the characteristic S-shape because spending is slow at project start (mobilization, early work), accelerates through the middle (peak construction), and tapers at the end (closeout). The S-curve provides a visual representation of project health:

• AC above PV and EV: Over budget relative to work accomplished. Cost performance issue.
• EV below PV: Behind schedule. Schedule performance issue.
• EV below PV with AC above PV: Both behind schedule and over budget. The most problematic position.
• EV above PV with AC near PV: Ahead of schedule and on budget. The ideal position.

Cash flow forecasting extends the S-curve forward, projecting monthly expenditures through project completion based on the remaining schedule. Owners use cash flow forecasts to manage construction loan draws; GCs use them to plan working capital requirements and manage the timing of sub payments. The forecast is updated monthly as actual performance data comes in and the remaining schedule is revised.

Integrated Change Control

One of the most important functions of project controls is integrated change control — ensuring that every change to scope is evaluated for its cost and schedule impact before it is authorized, and that the baseline is updated when changes are approved. Without integrated change control, the baseline becomes meaningless: actual performance is compared against an outdated plan, and the project appears to be performing better or worse than it actually is.

The integrated change control process:

Change request initiated (RFI response, owner directive, unforeseen condition).

Impact analysis: estimate cost change, evaluate schedule impact on CPM critical path, identify resource requirements.

Change order submitted to owner for approval. See construction change orders for the full process.

Upon approval: update the cost baseline (BAC), update the schedule baseline (approved revision), update the EVM performance measurement baseline.

All future EVM calculations use the updated baseline — the change is now part of the plan, not a variance.

Reporting Cadence

Effective project controls requires a consistent reporting rhythm. Standard cadence on large projects:

Frequency	Report Type	Audience / Content
Daily	Daily report + manpower log	Field team, PM. Crew counts by trade, work completed, weather, issues. See daily report post.
Weekly	Schedule look-ahead + cost tracking	PM, superintendent. 3-week look-ahead, labor cost vs. budget by trade, open RFIs/submittals affecting schedule.
Monthly	EVM report + forecast update	Owner, PM, project executive. PV/EV/AC, SPI/CPI, EAC, VAC, S-curve, change order log, cash flow forecast. This is the primary controls deliverable.
Quarterly	Trend analysis + risk update	Senior management, owner. CPI/SPI trends, risk register review, revised completion forecast, pending change order exposure.

The Project Controls Engineer

On projects over ~$50M, a dedicated project controls engineer (PCE) manages the controls function. The PCE role includes:

• Establishing and maintaining the WBS (Work Breakdown Structure), CBS (Cost Breakdown Structure), and EVM performance measurement baseline.
• Loading the CPM schedule into scheduling software (Primavera P6 is the industry standard on large projects; Microsoft Project on smaller ones) and maintaining schedule updates.
• Collecting percent-complete data from field superintendents and sub PMs monthly.
• Running EVM calculations, updating S-curves, producing the monthly controls report.
• Maintaining the change order log and updating the budget baseline for approved changes.
• Providing the PM and project executive with early warning indicators when CPI or SPI trends signal a trajectory problem before it becomes a crisis.

On smaller projects without a dedicated PCE, the PM performs all these functions — often less rigorously. The cost of a project controls function on a large project (0.5–1.5% of project cost) is easily justified by the cost avoidance from early detection of schedule and budget problems.

Scope gaps in your documents corrupt your controls baseline from day one

EVM and project controls only work when the scope baseline is complete and accurate. When construction documents have gaps and missing details, change orders accumulate that inflate the budget baseline and mask true cost performance. SheetIntel reviews plan sets before bid to identify the scope ambiguities that generate change orders, helping your controls baseline reflect actual project scope rather than a growing list of additions. First review is free.

Try SheetIntel Free →