A performance measurement baseline, or PMB, is the time-phased budget plan used to measure the execution of authorized project or contract scope. It integrates scope, schedule, resources, and budget so the program can compare planned value, earned value, and actual cost at each status date.
The PMB is not simply a copy of the Integrated Master Schedule (IMS), the contract value, or the original cost estimate. Instead, it is the approved value of scheduled work distributed across control accounts, work packages, and planning packages. It also includes applicable higher-level planning and undistributed budget.
For a program using an Earned Value Management System (EVMS), the PMB provides the reference point for calculating schedule and cost variances. Without a credible PMB, earned value results may be mathematically correct but operationally misleading.
What Is a Performance Measurement Baseline?
The performance measurement baseline represents how the program plans to accomplish all authorized work. NASA defines the PMB as the time-phased budget plan for accomplishing authorized life-cycle scope. Similarly, the Department of Energy describes it as the numeric representation of the same execution plan contained in the resource-loaded IMS.
Therefore, the schedule and budget systems should tell the same story. If an activity moves in the baseline schedule, its planned budget should follow the approved timing. Likewise, work should not appear in the cost system without corresponding scope and schedule detail.
The PMB becomes the basis for planned value, historically called Budgeted Cost for Work Scheduled (BCWS). As work progresses, the team compares planned value with earned value and actual cost. The resulting variances show whether the program is accomplishing work when planned and within its assigned budget.
The NASA earned value management tutorial provides a straightforward illustration of how time-phased planned value forms a PMB.
What the PMB Includes
A credible PMB rests on an integrated technical, schedule, and budget plan. Although implementation details vary by organization and contract, its core structure usually includes the following elements.
Authorized scope organized by the WBS
The Work Breakdown Structure (WBS) defines the products, services, and other work that the program must accomplish. The PMB should cover the complete authorized scope without gaps or duplication.
The WBS also provides a common structure for connecting the statement of work, IMS, control accounts, budgets, actual costs, and performance reports. For more detail on this integration, see how to structure an IMS using the WBS.
Control accounts
A control account is a management control point where scope, schedule, and budget come together. A Control Account Manager (CAM) accepts responsibility for planning and executing that work.
Each control account normally contains one or more work packages and, when needed, planning packages. The program assigns budgets and objective performance measurement techniques at this level or below.
Time-phased work and planning package budgets
Work packages define near-term work in enough detail to schedule, budget, and measure it. Planning packages hold future control-account scope that the team cannot yet plan in sufficient detail.
Both forms of budget belong in the PMB. However, the team should detail planning packages through its rolling-wave planning process before the work begins. Planning packages should not become indefinite holding areas for unresolved scope.
Summary-level planning packages and undistributed budget
A Summary-Level Planning Package (SLPP) may hold far-term authorized work that has not yet been assigned to a control account. Undistributed Budget (UB), meanwhile, holds budget for authorized scope that has not yet been distributed to control accounts or other appropriate planning elements.
UB is part of the PMB even though it has not yet been fully time-phased at the control-account level. Programs should distribute it promptly once they have enough information to assign responsibility and plan the work.
Applicable indirect budgets
The PMB may also include indirect budgets, depending on the contractor’s accounting structure and EVMS implementation. The treatment must remain consistent with the organization’s approved procedures and the way indirect costs are collected and reported.
What the PMB Does Not Include
Several amounts commonly discussed in program controls do not form part of the PMB:
- Management Reserve (MR): Budget held for management control of unplanned but in-scope work. MR sits outside the PMB until management authorizes its use and assigns it to planned work.
- Profit or fee: The PMB is a cost-based management plan, not the total contract price.
- Actual costs: Actual Cost (AC) records what the program spent. It is compared with the PMB but does not become part of it.
- Estimate at Completion (EAC): The EAC forecasts the expected final cost. It may differ from the baseline budget because the EAC reflects current performance and remaining conditions.
- Out-of-scope work: Work outside the existing contract scope requires contractual authorization before it can enter the contract baseline.
The distinction between the PMB and MR is especially important. At the contract level, the normal budget relationship is:
Contract Budget Base = Performance Measurement Baseline + Management Reserve
When an approved Over-Target Baseline (OTB) exists, the applicable relationship changes because Total Allocated Budget exceeds the Contract Budget Base. An OTB is a formal reprogramming action, not routine replanning.
How the PMB Supports Monthly Program Control
During each accounting period, the program statuses the IMS at an established data date. The cost system then determines how much budgeted work was planned and how much was accomplished through that date.
- Planned Value (PV) comes from the time-phased PMB.
- Earned Value (EV) represents the budgeted value of completed work.
- Actual Cost (AC) records the cost incurred for that work.
- Schedule Variance (SV) equals EV minus PV.
- Cost Variance (CV) equals EV minus AC.
For example, a program that planned to earn $10 million but earned only $8 million has a negative $2 million schedule variance. If it spent $9 million to earn that $8 million, it also has a negative $1 million cost variance.
These are budget-based indicators. Schedule variance expressed in dollars does not directly show how many days a milestone may slip. Therefore, managers should review EVM results alongside critical and near-critical path analysis in the IMS. The article on how the IMS supports earned value management explains that relationship further.
For a comparison of the variance calculations, see schedule variance versus cost variance.
A Practical PMB Example
Assume the fictional Falcon Sensor Development contract has a Negotiated Contract Cost of $60 million. The contracting officer also authorizes $2 million of unpriced work, producing a Contract Budget Base of $62 million.
The contractor retains $4 million as Management Reserve based on identified program risk. As a result, the initial PMB totals $58 million:
- $52 million distributed to control accounts
- $3 million in summary-level planning packages
- $3 million in undistributed budget
- $4 million in Management Reserve outside the PMB
At the sixth monthly status date, the PMB shows $18 million of planned value. The program has earned $16.5 million and recorded $17.2 million in actual cost.
- Schedule Variance = $16.5 million minus $18 million = negative $1.5 million
- Cost Variance = $16.5 million minus $17.2 million = negative $700,000
The negative schedule variance tells management that the program accomplished less budgeted work than planned. However, the scheduler still needs to inspect the IMS. A late software integration activity on the critical path presents a different completion risk than several late, noncritical documentation tasks with adequate float.
Meanwhile, the CAM should update the Estimate to Complete (ETC) based on remaining work, resource rates, technical conditions, and schedule forecasts. The ETC is a forecast and should not be forced to equal the remaining baseline budget. See Estimate to Complete explained for additional guidance.
How Programs Establish a Credible PMB
Developing a PMB requires more than loading budget into an earned value tool. The planning team should complete a traceable sequence:
- Define the complete authorized scope.
- Organize the scope using the contract WBS.
- Assign responsibility through the organizational structure and control accounts.
- Build a logically connected IMS for the authorized work.
- Estimate labor, material, subcontract, and other required resources.
- Establish control-account, work-package, and planning-package budgets.
- Select objective earned value techniques suited to the type of work.
- Time-phase the budget in alignment with the IMS.
- Reconcile the distributed budget, UB, PMB, MR, and Contract Budget Base.
- Approve the plan and place it under formal change control.
Schedule dates and cost-system time phasing should reconcile at the appropriate level. Otherwise, the program may report planned value before work can occur or after the schedule says it should finish.
A PMB also needs a defensible basis of estimate, documented assumptions, clear calendar rules, realistic resource availability, and defined measurement methods. For a more detailed development process, see how to build a robust performance measurement baseline.
The Integrated Baseline Review Tests PMB Realism
An Integrated Baseline Review (IBR) is a joint assessment of whether the baseline can support successful execution. It is not merely a presentation of baseline totals or an EVMS software demonstration.
Federal Acquisition Regulation 34.202 states that, when EVMS is required, the Government conducts an IBR to examine the realism of the technical content, budgets, resources, and schedules. The review also considers whether the PMB can support project execution and cost objectives.
On DoD contracts containing DFARS 252.234-7002, the clause requires the Government to schedule applicable IBRs as early as practicable and conduct them no later than 180 calendar days after contract award, significant option exercise, or major modification. The Government and contractor assess scope coverage, schedule logic, resources, and inherent risks.
However, teams should always read the solicitation, contract, Contract Data Requirements List, and agency procedures. IBR timing, reporting detail, and tailoring can vary by agency and acquisition.
Contractual Requirements Versus Good Practice
A PMB is not automatically a contractual requirement on every federal contract. The contract must invoke the applicable EVMS requirement, clause, data item, or agency-specific direction.
Under current DoD policy, DFARS 234.201 applies EIA-748-compliant EVMS requirements to cost or incentive contracts and subcontracts valued at $20 million or more. At $50 million or more, the Cognizant Federal Agency must have determined the EVMS acceptable. Below $20 million, application is optional and risk-based. DoD policy discourages applying EVMS to firm-fixed-price contracts and requires an approved waiver before doing so.
Those thresholds and policies do not replace the signed contract. Acquisition rules can also change. Therefore, proposal and execution teams should verify the current solicitation provisions, contract clauses, agency policy, and tailoring before defining compliance obligations.
Even when a contract does not require formal EVMS, a time-phased and controlled baseline can still improve internal management. In that situation, using PMB concepts is a management practice rather than a claim of contractual EIA-748 compliance.
Maintaining the Baseline Without Hiding Performance
A baseline should remain stable enough to preserve meaningful performance trends. However, stability does not mean the program can never change it.
Valid baseline changes may include authorized contract modifications, distribution of UB, approved use of MR, controlled detail planning, corrections of material errors, and formal reprogramming. Each change needs appropriate authorization, documentation, and reconciliation.
By contrast, a team should not move baseline dates or budgets simply because work finished late or cost more than planned. That practice erases variance instead of managing it. It also prevents leadership from distinguishing original planning assumptions from the current forecast.
The baseline and forecast serve different purposes:
- The baseline records the approved execution plan against which performance is measured.
- The current schedule forecast shows when the remaining work is now expected to occur.
- The EAC shows the current expected final cost.
Programs need all three views. A baseline without a realistic forecast hides future consequences, while a forecast without a stable baseline removes accountability.
Common PMB Failure Modes
- Incomplete scope: Authorized requirements appear in the statement of work but not in the WBS, IMS, or control-account plans.
- Schedule and budget misalignment: Planned value occurs in different periods from the activities that drive the work.
- Excessive undistributed budget: Scope remains unassigned long after the program has enough information to plan it.
- Weak earned value techniques: The program uses subjective percent-complete assessments for work that supports objective measurement.
- Unrealistic resource assumptions: Multiple control accounts plan to use the same limited personnel or facilities at the same time.
- MR inside the PMB: Management Reserve becomes time-phased planned value before the program authorizes its use.
- Baseline equal to forecast: The team continually resets baseline dates to current expectations and eliminates visibility into schedule variance.
- Uncontrolled retroactive changes: Prior-period budgets or earned value change without a documented and authorized reason.
These problems weaken both EVM analysis and schedule execution. More importantly, they reduce management’s ability to identify emerging risk early enough to take corrective action.
Performance Measurement Baseline FAQ
Is the PMB the same as the IMS?
No. The IMS provides the networked schedule for accomplishing the work. The PMB adds the time-phased budget used for performance measurement. However, the two should remain fully aligned.
Is Management Reserve part of the PMB?
No. MR sits outside the PMB. Once management authorizes MR for specific in-scope work and assigns the budget to a control account, that assigned budget becomes part of the PMB.
Is the PMB the same as the Budget at Completion?
At the total contract level, Budget at Completion generally represents the total PMB budget. At lower WBS or organizational levels, BAC represents the budget assigned to that element. Teams should follow the definitions and reporting rules in their EVMS procedures and contract data requirements.
Can the PMB change after the IBR?
Yes, but changes require formal control. Authorized scope changes, rolling-wave planning, UB distribution, MR use, error correction, and approved reprogramming may change the PMB. Poor performance alone does not justify erasing historical variance.
Why does the PMB matter to schedulers?
The PMB connects activity timing to performance budget. A scheduler’s logic, calendars, durations, status, and forecast dates directly affect when planned value appears and how management interprets schedule performance. Therefore, schedule quality is central to PMB credibility.