Planned Value (PV) is the budget assigned to work scheduled by a set date. In construction, it gives teams a baseline for comparing progress with the plan. See how PV differs from earned value and actual cost, and how that gap can signal a schedule delay.

Multiple Choice

In earned value management, what does Planned Value (PV) represent?

Planned Value is the authorized budget for the work that is scheduled to be performed by a given date. It represents the value, in currency, of the plan—what the project baseline says should have been completed by that point (often called the Budgeted Cost of Work Scheduled). It is not the actual money spent (that’s the actual cost incurred) and it’s not the value of work actually completed (that’s earned value). It’s also not the total project budget (that’s the Budget at Completion). For example, if the baseline plan calls for $200,000 of work to be completed by the end of the month, the Planned Value at that date is $200,000. If only $150,000 of work is actually completed by then, earned value would be $150,000, and you’d have a Schedule Variance of EV minus PV, which in this case would be -$50,000, indicating you're behind in value terms.

Planned Value in Construction: The Budgeted Cost of Scheduled Work

A construction project runs on more than concrete, steel, and labor. It also runs on a plan: what work should be done, when it should happen, and how much of the budget is assigned to it. Earned value management turns that plan into measurable figures. One of its key measures is Planned Value (PV), the authorized budget for the work scheduled to be completed by a specific date.

Put simply, PV answers this question: According to the project plan, how much work should have been done by now, expressed in budgeted dollars? It does not show how much the contractor has spent, or how much work is actually finished. That distinction matters when project leaders need a clear view of cost and schedule performance.

What Planned Value tells you

Planned Value is tied to the project’s approved cost and schedule baseline. The baseline lays out the work, its timing, and the budget assigned to each part. As time passes, the budget for the work scheduled up to a given point becomes the PV for that date.

The measure is also known as Budgeted Cost of Work Scheduled (BCWS). The name sounds formal, but the idea is straightforward: it’s the budgeted value of the work the plan says should be complete by now.

For example, imagine a project baseline that schedules $200,000 worth of work by the end of the month. The project’s PV at month-end is $200,000. That figure remains tied to the plan, even if the crew finishes less work, finishes more work, or spends more than expected. PV is a reference point—not a report of what actually happened.

That fixed reference gives project teams a way to compare the schedule with real progress. Without it, “we’re a bit behind” can mean almost anything. A budget-based measure gives that impression a clearer frame.

Planned Value is not the same as spending

Construction teams often need to keep three related figures separate:

  • Planned Value (PV): The budgeted value of work scheduled by a given date.

  • Earned Value (EV): The budgeted value of work actually completed by that date.

  • Actual Cost (AC): The amount actually spent on the work completed by that date.

These measures can sound similar, but they answer different questions. PV asks what the plan called for. EV asks what work has been completed, valued using the approved budget. AC asks what that completed work cost in real dollars.

Say a project has a PV of $200,000 at month-end, but crews have completed only $150,000 worth of budgeted work. The EV is $150,000. If the team has spent $165,000 to complete that work, AC is $165,000.

Each number tells part of the story. The gap between PV and EV points to schedule performance. The gap between EV and AC points to cost performance. Mixing them up is like comparing a delivery schedule with a fuel bill: both matter, but they don’t measure the same thing.

How PV helps show schedule performance

A common earned value measure is Schedule Variance (SV):

SV = EV − PV

Using the example above:

SV = $150,000 − $200,000 = −$50,000

The negative result means the project has completed $50,000 less work, in budgeted-value terms, than the baseline scheduled by that date. In plain language, it’s behind schedule relative to the plan.

That doesn’t necessarily mean the project is exactly a certain number of days late. SV measures the difference in the budgeted value of work, not calendar days. A $50,000 shortfall could come from several activities with different durations and importance. Project managers should look at the schedule itself to understand the cause and likely effect.

The related Schedule Performance Index (SPI) gives another view:

SPI = EV ÷ PV

With EV of $150,000 and PV of $200,000, the SPI is 0.75. In value terms, the project has completed 75 cents of work for every dollar’s worth of work planned by that date. An SPI of 1.0 means earned value matches planned value; above 1.0 means more budgeted work has been completed than planned by that point.

These figures are useful signals, not full explanations. A low SPI might reflect a delayed material delivery, a late design decision, a weather disruption, or a sequence of smaller issues. The number points to a gap; the team still needs to investigate what caused it.

How PV supports cost control, too

PV is mainly a schedule reference, but it also helps teams make sense of cost performance. For example, comparing EV with AC shows whether completed work cost more or less than its budgeted value.

Cost Variance (CV) = EV − AC

If EV is $150,000 and AC is $165,000, CV is −$15,000. The project spent $15,000 more than the budgeted value of the completed work. That’s a cost concern, even though the schedule comparison tells a separate story.

Here’s where careful reading matters: a project can be behind schedule and under budget, or ahead of schedule and over budget. One measure cannot tell the whole story. PV, EV, and AC work best as a set, much like separate instruments on a dashboard. Looking at only one may give a misleading impression of the project’s health.

The baseline is the backbone

Planned Value is only as useful as the baseline behind it. If the schedule is unrealistic, or the budget hasn’t been assigned clearly to scheduled activities, PV may offer a poor comparison. A baseline should reflect approved scope, timing, and budget assumptions. When a project has an authorized change, the baseline may need to be updated through the organization’s change-control process.

That doesn’t mean teams should revise the baseline every time work slips. Doing so can blur the difference between the original plan and what actually happened. Changes should be documented and handled consistently, so reports remain meaningful over time.

For construction finance professionals, this connection between scope, schedule, and cost is especially important. A job-cost report may show where money went, while the schedule shows when work was expected. Earned value management links those views by assigning budgeted value to work over time. It can help project managers, controllers, and executives discuss performance using a shared set of definitions.

A clear reference point, not a crystal ball

PV doesn’t predict the future, and it doesn’t reveal the reason for a delay on its own. What it does provide is a clear, budget-based picture of what the project plan expected to have accomplished by a specific date.

That distinction is the heart of the measure. Planned Value is not actual cost, not completed work, and not the total budget for the project. It is the authorized budget for scheduled work—the plan translated into dollars over time.

When PV is read alongside EV and AC, the team gets a more useful view of performance: what should have happened, what did happen, and what it cost. In a complex construction job, that simple separation can prevent a lot of confusion.