The Budget Structure
Every EVMS program has a hierarchical budget structure. Understanding this structure is essential for every CAM because it defines the boundaries within which you plan, execute, and report. The structure flows from the contract price down to the individual work package.
| Component | Definition | Who Controls It |
|---|---|---|
| Contract Price | The total negotiated value including cost, fee/profit, and any incentive provisions. | Contracting Officer |
| Contract Budget Base (CBB) | Contract price minus fee/profit. This is the total budget available for work. CBB = PMB + MR. | Program Manager |
| Management Reserve (MR) | Budget held outside the PMB for emerging work within general contract scope. Not allocated to any control account. | Program Manager |
| Performance Measurement Baseline (PMB) | The time-phased budget plan. PMB = Distributed Budget + Undistributed Budget. | Baseline Change Control |
| Undistributed Budget (UB) | Budget associated with authorized scope changes that have not yet been allocated to control accounts. | Program Manager |
| Distributed Budget | Budget allocated to control accounts. This is where the CAM lives — the sum of all work package and planning package budgets. | CAM (within CA) |
The fundamental equation: CBB = PMB + MR = (Distributed Budget + UB) + MR. This equation must always balance. If it does not, the baseline has an integrity problem.
Management Reserve Rules
Management reserve is one of the most misunderstood elements in EVMS. It is not a slush fund, not a contingency for known risks, and not a way to hide budget problems. It has strict rules that every CAM must understand.
✅ Proper Use of MR
- Funding scope growth within the general contract boundaries
- Addressing complexity increases that could not have been anticipated
- Supporting emergent requirements identified during execution
- Replenishing a control account where original budget was insufficient due to scope underestimation
- Each MR allocation has a documented scope justification
- MR log maintained with running balance and traceability to scope
❌ Improper Use of MR
- Covering cost overruns caused by inefficiency (that is a variance, not a scope issue)
- Adding budget to eliminate a negative cost variance
- “Feeding” control accounts to keep CPI above 1.0
- Funding work that was always in scope but was under-budgeted
- Using MR without documented scope justification
- Allocating MR retroactively to cover past-period performance
💡 How Much MR Is Enough?
Industry norms range from 5% to 15% of the PMB, depending on program maturity and risk. A development program early in its lifecycle might hold 10–15%. A production program might hold 3–5%. The key is that MR should decrease over time as uncertainty resolves. If MR is growing, something is wrong — either the program is receiving excess budget or management is hoarding reserve instead of addressing known problems.
Undistributed Budget and Distribution
When a contract modification adds new scope and budget, that budget typically enters the system as undistributed budget (UB). It sits in the PMB but has not yet been allocated to control accounts. The CAM’s role is to work with program control to plan the new scope and receive the appropriate share of UB into their control accounts.
Scope Change Authorized
A contract modification or internal change adds new authorized scope and budget. The budget enters UB pending detailed planning and distribution.
Planning and Allocation
CAMs plan the new work within their control accounts. Work packages are defined, budgets are time-phased, and resources are loaded. The total distributed amount must equal the UB being allocated.
Baseline Change Request
A formal baseline change request (BCR) documents the distribution of UB into control accounts. This changes the distributed budget and reduces UB, but the PMB total remains unchanged.
UB Should Trend to Zero
UB is a temporary holding area. Budget should not sit in UB for extended periods. If UB is persistently high, scope changes are being authorized faster than they are being planned — a risk to baseline integrity.
Over-Target Baseline (OTB) and Over-Target Schedule (OTS)
Sometimes a program reaches a point where the current baseline is no longer a meaningful standard of measurement. The EAC significantly exceeds the CBB, and no realistic corrective action can close the gap. When this happens, the program may implement an over-target baseline.
| Concept | Description | Key Requirement |
|---|---|---|
| OTB | A budget baseline that exceeds the CBB. The program formally recognizes it needs more budget than the contract provides to establish a meaningful measurement baseline. | Customer notification and approval. Historical cost/schedule data must be preserved. |
| OTS | A schedule baseline that extends beyond the contractual completion date. The program formally recognizes the work will take longer than contracted. | Same governance as OTB. Must maintain traceability to original dates. |
| Reprogramming | The process of restructuring the PMB to establish a new, realistic baseline. May involve eliminating existing variances and resetting cumulative data. | Joint customer-contractor decision. Typically documented in a formal reprogramming agreement. |
An OTB is not a failure — it is an honest recognition that the current baseline cannot serve its measurement purpose. Continuing to measure against a meaningless baseline is worse than implementing an OTB, because it produces data that no one trusts and no one acts on.
Baseline Maintenance Best Practices
The PMB is a living document, but it must change through controlled processes. A baseline that changes without discipline becomes meaningless. A baseline that never changes becomes irrelevant. The CAM’s job is to maintain the right balance.
| Practice | Description | Frequency |
|---|---|---|
| Rolling Wave Conversion | Convert planning packages to work packages as work approaches. Internal replanning within the CA — does not change the PMB total. | Ongoing, typically 3–6 months ahead |
| Internal Replanning | Reschedule remaining work within the CA to reflect updated execution plans. Budget may shift between periods but total CA budget does not change. | As needed, with PM awareness |
| Formal Reprogramming | Changes to the PMB that affect total CA budget, scope, or schedule milestones. Requires baseline change control approval. | Only through formal BCR process |
| Retroactive Changes | Changes to past-period BCWS or BCWP. Prohibited under EVMS guidelines except in limited corrective circumstances. | Rare and heavily scrutinized |
💡 The Rubber Baseline Problem
If the baseline changes every month to match actuals, it is not a baseline — it is a mirror. A meaningful baseline must be stable enough to reveal variances. The question is not “does the variance look bad?” but “is the baseline still a valid measurement standard?” Only change the baseline when the plan has genuinely changed, never to cosmetically improve performance metrics.
🎯 The Bottom Line
The PMB is the measurement standard against which all performance is judged. It is built from the bottom up through work package budgets, controlled through formal change processes, and protected by management reserve for genuine scope growth. Understanding the relationship between distributed budget, UB, MR, and the CBB is fundamental to the CAM role. Next: Performance Measurement — how to apply EV techniques to actually measure progress against this baseline.
Stop reading, start modeling
Model your process flow, run simulations, optimize staffing with TOC math, and test your knowledge with 107 interactive checks — all in one platform.