BCWS, BCWP and ACWP are the traditional names for the three core earned value data elements now commonly called PV, EV and AC. Budgeted Cost for Work Scheduled (BCWS) equals Planned Value (PV). Budgeted Cost for Work Performed (BCWP) equals Earned Value (EV). Actual Cost of Work Performed (ACWP) equals Actual Cost (AC).
The terminology changed, but the underlying concepts and calculations did not. Whether a report uses BCWS BCWP ACWP or PV, EV and AC, it should compare the budgeted value of planned work, the budgeted value of completed work and the actual cost of that completed work at the same status date.
BCWS BCWP ACWP compared with PV, EV and AC
- BCWS = PV: The time-phased budget for work scheduled through the status date.
- BCWP = EV: The budgeted value of work actually completed through the status date.
- ACWP = AC: The actual cost incurred for the work completed through the status date.
The NASA program planning and control glossary identifies BCWS as Planned Value and BCWP as Earned Value. Similarly, the Department of Energy overview of earned value management defines the three elements by their relationship to planned work, completed work and actual cost.
The shorter terms are easier to use in management discussions. However, the traditional acronyms remain common in EVMS documentation, legacy reports, contract data environments and software. For example, Deltek materials continue to use BCWS, BCWP and ACWP alongside plain-language descriptions such as planned value and earned value.
What each earned value term measures
BCWS or Planned Value
Budgeted Cost for Work Scheduled represents the authorized budget assigned to work that should have been completed by a specific point in time. It comes from the time-phased Performance Measurement Baseline (PMB).
Suppose a control account has a Budget at Completion (BAC) of $2 million. The baseline calls for $700,000 of that budgeted work to be complete by the end of June. Therefore, the cumulative BCWS or PV at the June status date is $700,000.
PV is not the current forecast and does not represent actual spending. Instead, it answers a baseline question: How much budgeted work did we plan to accomplish by now? For more detail on establishing the time-phased plan, see how to build a robust Performance Measurement Baseline.
BCWP or Earned Value
Budgeted Cost for Work Performed measures the budgeted value of the work actually completed. It answers: How much of the planned budget have we earned through verified accomplishment?
BCWP does not show what the work cost. Instead, it values completed work using the approved budget and the applicable earned value technique. Those techniques may include weighted milestones, fixed formulas, units complete, percent complete, level of effort or other methods supported by the organization’s EVMS.
For example, a $100,000 work package using a 50/50 technique earns $50,000 when it starts and the remaining $50,000 when it finishes. It does not earn value continuously based only on elapsed time. Therefore, the selected technique and objective completion criteria can materially affect reported EV.
ACWP or Actual Cost
Actual Cost of Work Performed represents the cost incurred for the work completed during the reporting period or cumulatively through the status date. Labor charges, material costs, subcontractor costs, indirect costs and other applicable charges may contribute to AC, depending on the accounting structure and reporting requirements.
ACWP contains no budgeted value. It answers a different question: What did the performed work actually cost?
Program-controls teams must align AC with EV by accounting period, scope and organizational structure. Otherwise, cost performance can look artificially favorable or unfavorable. For example, earned value posted before a major supplier invoice or accrual may temporarily overstate the Cost Performance Index (CPI).
How the three values produce EVM variances
The three data elements become useful when analysts compare them. BCWP or EV sits at the center of both primary performance comparisons.
Schedule variance and SPI
- Schedule Variance: SV = BCWP − BCWS, or EV − PV
- Schedule Performance Index: SPI = BCWP ÷ BCWS, or EV ÷ PV
A negative SV or an SPI below 1.00 indicates that the program earned less budgeted value than planned through the status date. A positive SV or an SPI above 1.00 indicates that it earned more value than planned.
However, EVM schedule variance is expressed in budget units, usually dollars or labor hours. It does not directly show how many calendar days a milestone will slip. Therefore, the scheduler must also evaluate critical and near-critical paths, forecast dates, remaining duration and network logic.
Cost variance and CPI
- Cost Variance: CV = BCWP − ACWP, or EV − AC
- Cost Performance Index: CPI = BCWP ÷ ACWP, or EV ÷ AC
A negative CV or CPI below 1.00 indicates that the completed work cost more than its budgeted value. A positive CV or CPI above 1.00 indicates favorable cost performance.
For a deeper discussion of management interpretation, see what CPI and SPI tell program managers. Analysts developing completion forecasts can also review TCPI, VAC, ETC and advanced EVM measures.
Fictional program example
Consider the Falcon Ridge communications subsystem, a fictional development effort. At the September status date, its cumulative data shows:
- BCWS/PV: $1,000,000
- BCWP/EV: $800,000
- ACWP/AC: $900,000
The schedule variance is $800,000 minus $1,000,000, which equals negative $200,000. The SPI is 0.80. In budget terms, the team earned 80 cents of value for every dollar of work it planned to complete.
The cost variance is $800,000 minus $900,000, which equals negative $100,000. The CPI is approximately 0.89. Therefore, the program earned about 89 cents of budgeted value for each actual dollar spent.
This combination shows both schedule and cost pressure. However, it does not explain the cause. The program team should examine the underlying control accounts, work packages and schedule activities. Possible drivers might include late engineering releases, supplier delays, technical rework or actual costs recorded before the corresponding accomplishment earned value.
The Integrated Master Schedule (IMS) should provide the time-based explanation that the EVM metrics cannot. In particular, the scheduler should identify whether the delayed work drives a contractual milestone or has enough float to recover without affecting program completion. See the complete guide to the DoD Integrated Master Schedule for the broader schedule integration context.
Why both acronym sets still appear
Organizations often use PV, EV and AC in executive briefings because the terms communicate their purpose directly. Meanwhile, cost systems, data exports, legacy procedures and training materials may still use BCWS, BCWP and ACWP.
For example, the Deltek Cobra earned value reference defines BCWS as the budget for scheduled work and identifies it as Planned Value. It also uses BCWP and ACWP in CPI, CV and forecast calculations. Therefore, a Cobra analyst may work with the traditional acronyms even when the customer’s dashboard uses PV, EV and AC.
The key is consistency. A program should define its terminology in procedures, report instructions and data dictionaries. In addition, analysts should verify whether each value is current-period, cumulative or at-completion data before comparing reports.
Common interpretation mistakes
Treating EV as actual cost
EV is a budgeted measure of accomplishment. AC is the recorded or accrued cost of that accomplishment. A program can earn $500,000 of value while spending either $400,000 or $650,000.
Using PV as the latest forecast
PV normally comes from the approved PMB. A current schedule forecast may show later dates while the baseline value remains in its original time period. Moving budget merely to eliminate a variance can undermine baseline integrity unless the change follows authorized change-control procedures.
Reading schedule variance as calendar time
An SV of negative $200,000 does not mean the program is a specific number of days late. It shows the budgeted value of the accomplishment shortfall. The IMS must determine the effect on milestone dates and the critical path.
Comparing values from different cutoff dates
PV, EV and AC must use a consistent reporting cutoff. Mixing a current schedule update with prior-period actual costs can create misleading CPI and SPI results.
Earning value without objective evidence
Reported progress should follow the approved earned value technique and completion criteria. Subjective progress claims can overstate BCWP, especially on long-duration work packages with unclear outcomes.
Are these terms contractual requirements?
The acronym set alone is not a contractual requirement. A contract may require an EVMS, specific reports, particular data formats or customer-defined terminology. Those requirements depend on the applicable clauses, agency policy, contract value, acquisition type and program tailoring.
FAR Subpart 34.2 addresses when the federal government requires EVMS for major development acquisitions and allows agencies to apply EVMS to other acquisitions under their procedures. When applicable, FAR 52.234-4 requires the contractor to use an EVMS compliant with the referenced EIA-748 guidelines and submit reports required by the contract.
DoD contracts may apply separate DFARS provisions and clauses. Therefore, teams should review the actual solicitation or contract, Contract Data Requirements List, applicable data item descriptions, EVMS system description and customer instructions. Do not assume that terminology used on a commercial dashboard satisfies a contractual reporting requirement.
Practical takeaway for program-controls teams
When reviewing an earned value report, translate the labels into three questions:
- PV or BCWS: What budgeted work should be complete?
- EV or BCWP: What budgeted work is actually complete?
- AC or ACWP: What did that completed work cost?
Next, compare EV with PV for schedule performance and EV with AC for cost performance. Finally, trace significant variances into the control accounts, work packages and IMS activities that explain the result.
The acronyms may differ, but the management logic remains the same. EVM integrates scope, schedule and cost so the team can identify performance problems early, understand their causes and develop credible corrective actions. Readers who need the broader framework can continue with the complete guide to Earned Value Management or the focused explanation of what an Earned Value Management System is.
Frequently asked questions
Is BCWP the same as earned value?
Yes. Budgeted Cost for Work Performed is the traditional term for Earned Value. Both represent the approved budget assigned to completed work.
Is BCWS the same as planned value?
Yes. Budgeted Cost for Work Scheduled and Planned Value both represent the time-phased budget for work scheduled through a defined date.
Is ACWP the same as actual cost?
Yes. Actual Cost of Work Performed is commonly shortened to Actual Cost. It represents the cost incurred for performed work.
Which terminology should a program use?
Use the terminology required by the contract, customer data instructions and approved EVMS procedures. If no specific convention applies, PV, EV and AC are generally easier to explain, while BCWS, BCWP and ACWP may align better with existing systems and legacy reports.