Undistributed budget is budget for authorized work that has not yet been assigned to a control account, summary-level planning package, or lower-level Work Breakdown Structure (WBS) element. In an Earned Value Management System (EVMS), it serves as a temporary holding category while the program identifies the responsible organization and develops an executable scope, schedule, and budget plan.
Undistributed budget, commonly abbreviated as UB, belongs to specific work scope. Therefore, it forms part of the Performance Measurement Baseline (PMB). However, the program cannot measure performance against UB while it remains undistributed because the budget has not been time-phased into an executable plan.
The practical rule is simple: use UB to preserve budget traceability for newly authorized scope, then distribute it as soon as the program can plan that scope responsibly.
What Is Undistributed Budget in EVMS?
The Defense Acquisition University Earned Value Management Gold Card describes UB as budget for specific work scope or contract changes that have not been planned. Similarly, the Department of Energy describes it as budget applicable to authorized effort that has not yet been distributed below the project level.
Three characteristics define undistributed budget:
- The work is authorized. UB should not contain speculative, out-of-scope, or unauthorized effort.
- The work is identifiable. The program knows the scope or change associated with the budget, even though detailed planning remains incomplete.
- The assignment is temporary. The program intends to transfer the budget to control accounts or other appropriate planning elements.
For example, a contracting officer may authorize a major engineering change before the program completes its detailed impact assessment. The contractor can place the budget associated with that change in UB. Next, the program evaluates the affected WBS elements, identifies the responsible Control Account Managers (CAMs), updates the Integrated Master Schedule (IMS), and distributes the budget.
UB is not a pool of uncommitted money. Instead, each amount should remain traceable to the authorized scope that created it.
Where Undistributed Budget Sits in the Baseline
Undistributed budget is part of the Performance Measurement Baseline. At a high level, the Contract Budget Base consists of the PMB plus Management Reserve (MR). The PMB, in turn, contains both distributed and undistributed budget.
- Distributed budget has been assigned to control accounts or appropriate higher-level planning elements.
- Undistributed budget belongs to authorized scope but has not yet been assigned to those planning elements.
- Management Reserve remains outside the PMB and supports management of in-scope risks and unplanned effort.
NASA guidance similarly states that the PMB includes control account budgets and, where applicable, budget assigned to higher-level WBS elements and UB. Its program planning and control glossary also distinguishes UB from Management Reserve and other budget categories.
Because UB is not time-phased at the holding level, it does not create planned value or a basis for earning value. Once the program transfers the budget into an authorized, scheduled plan, it can establish planned value and apply an appropriate performance measurement technique.
Undistributed Budget vs Management Reserve
Teams often confuse UB and MR because both may appear above the control account level. However, they serve different purposes.
Undistributed budget has specific scope
UB connects to known, authorized work. The program may still need to determine who will perform the work or how it will fit into the baseline. Nevertheless, the underlying scope already exists.
Management Reserve does not have specific assigned scope
MR is budget held by the contractor for management control of in-scope risks and unplanned effort. It does not belong to a defined control account task when established. In addition, MR sits outside the PMB until management authorizes its use and assigns it to appropriate scope.
Therefore, a program should not move authorized change budget into MR merely because the change remains difficult to plan. Likewise, it should not use UB as a substitute for risk-based MR.
A useful diagnostic question is: Can the program identify the authorized scope associated with this budget? If yes, but the budget has not reached a control account or other appropriate planning element, it may qualify as UB. If no specific scope exists and the budget supports management of future in-scope risk, it may be MR, subject to the contractor’s approved EVMS processes.
UB vs Summary-Level and Control Account Planning
Not all future work that lacks detailed work packages belongs in UB. The correct category depends on how far the program has progressed in assigning responsibility and defining the plan.
Summary-level planning package
A Summary-Level Planning Package (SLPP) contains far-term work that the program can assign to a reporting-level WBS element but cannot yet assign to a control account. An SLPP is not UB because the program has distributed the budget to a defined planning element.
Planning package
A planning package contains future work already assigned to a control account. The CAM owns the scope and budget, but the team cannot yet plan it as detailed work packages. See what a planning package means in EVMS for a closer look at that distinction.
Work package
A work package represents near-term, executable work within a control account. It should have defined scope, schedule dates, budget, and an appropriate earned value technique. The relationship between these planning levels is covered further in Control Account vs Work Package.
In short, UB means the program has not completed the initial distribution. A planning package means it has assigned the work to a CAM but has not finished detailed planning.
How Programs Distribute Undistributed Budget
The exact workflow depends on the contractor’s EVMS description, contract requirements, change-control process, and customer direction. However, a disciplined distribution generally follows these steps.
- Confirm authorization. Identify the contract modification, change order, internal authorization, or other approved source of the scope.
- Record the UB transaction. Enter the budget in a controlled log with the source, amount, effective period, associated scope, and approval reference.
- Analyze the scope. Determine which WBS elements, organizations, control accounts, and contract deliverables the change affects.
- Develop the schedule plan. Add or revise IMS activities, logic, durations, resources, and milestones as needed.
- Assign responsibility. Identify the CAMs and performing organizations that will execute the work.
- Allocate the budget. Transfer budget from UB to control accounts or, where appropriate, summary-level planning packages.
- Time-phase the plan. Align the budget with the scheduled work and expected resource use.
- Reconcile the records. Confirm that the UB log, change-control records, cost system, schedule, and customer reports agree.
These steps should operate as one integrated baseline-change process. A budget transfer without corresponding scope and schedule updates creates an incomplete plan. Likewise, adding schedule activities without authorized budget can distort performance measurement.
Fictional Program Example
Assume the Government authorizes a $4.8 million sensor redesign on the fictional Falcon Ridge avionics program. The modification defines the required capability, but the contractor needs several weeks to complete make-or-buy analysis and detailed planning.
The program initially records $4.8 million in UB and ties the entry to the authorized modification. The change team then identifies four affected areas:
- $600,000 for systems engineering;
- $2.7 million for sensor hardware;
- $900,000 for software integration; and
- $600,000 for qualification testing.
After the change board approves the plan, the program transfers each amount to the appropriate control account. The CAMs establish work packages and planning packages, while the scheduler integrates the work into the IMS. The team also verifies that procurement lead times, software dependencies, and test-facility availability support the budget phasing.
Once the full $4.8 million has been assigned, the UB balance for the modification becomes zero. The budget did not disappear or increase during the transfer. Instead, it moved from a temporary holding category into an executable baseline plan.
Why Undistributed Budget Matters to Schedulers
UB may appear to be a cost-system concern, but it has direct schedule implications. A large or aging UB balance often indicates that authorized scope has not reached the IMS and control account plans.
Consequently, schedulers should review UB during baseline-change meetings. They should ask which activities, milestones, interfaces, and resources will represent the associated scope. They should also verify that the schedule change follows the same authorization and approval path as the budget change.
However, UB itself should not become a generic placeholder activity in the IMS. It is a budget category, not a scheduling technique. The schedule should represent the actual authorized work as soon as the team can define it at the appropriate level.
This integration supports reliable earned value data because the schedule provides the timing and sequencing behind the budget plan. For more detail, see how the IMS supports earned value management.
Contractual Requirements vs Good Practice
Undistributed budget requirements depend on the contract, agency, applicable clauses, Contract Data Requirements List, and approved EVMS description. They do not apply identically to every federal contract.
For covered DoD contracts, DFARS 252.234-7002 requires the contractor to use an EVMS that meets the applicable system criteria. The clause does not establish a universal number of days for clearing UB.
When the Integrated Program Management Data and Analysis Report (IPMDAR) is contractually required, the IPMDAR Implementation and Tailoring Guide directs contractors to provide the amount of budget applicable to contract work that has not yet been distributed in the baseline. It also addresses the Estimate at Completion (EAC) for the scope associated with UB.
As a management practice, programs should clear UB in a reasonably timely manner. However, the acceptable timeframe depends on the size and complexity of the change, near-term work authorization, negotiations, planning maturity, and the contractor’s documented process. A team should not present an internal target, such as 30 or 60 days, as a universal regulation unless the contract or governing procedure establishes that target.
Common Undistributed Budget Mistakes
- Treating UB as discretionary budget. Every UB entry should remain tied to authorized scope.
- Leaving budget in UB after planning is complete. This weakens baseline visibility and may hide work that should reside in control accounts.
- Starting work without an executable baseline. Actual costs may accumulate before the team establishes planned value and a method for measuring performance.
- Using UB as Management Reserve. UB has scope; MR does not have specifically assigned scope when held.
- Confusing budget with funding. Budget establishes a performance target. Funding governs financial authority and cash availability. The two require separate controls.
- Failing to reconcile logs and reports. The UB balance should agree across change records, the EVMS cost tool, and contractual reporting.
- Distributing budget without schedule integration. A control account budget that lacks corresponding IMS logic and timing does not create a credible performance plan.
The Department of Energy’s EVMS metric specifications emphasize traceability, control, reconciliation, and timely distribution. Although DOE assessment methods do not automatically govern DoD contracts, they illustrate sound controls for reviewing UB.
Frequently Asked Questions
Is undistributed budget part of the PMB?
Yes. UB belongs to authorized scope and forms part of the PMB. Management Reserve remains outside the PMB.
Can a program earn value against UB?
Not while the budget remains in the undistributed holding category. The program must first assign and time-phase the budget within an executable performance plan.
Is UB the same as Authorized Unpriced Work?
No. Authorized Unpriced Work describes authorized scope whose final price has not yet been negotiated. Budget for that effort may initially enter UB, but the terms describe different concepts.
How long can budget remain undistributed?
No single clearing period applies to every program. The contract, approved EVMS procedures, agency guidance, and nature of the change determine the applicable expectations. Programs should still distribute UB promptly enough to support meaningful planning and performance measurement.
Does UB affect the Budget at Completion?
UB is part of the authorized performance budget structure, but it has not yet been assigned to detailed performing elements. Analysts should understand how their reporting system presents UB when interpreting Budget at Completion and related totals.
Practical Takeaway
Undistributed budget is a controlled bridge between authorization and executable planning. It protects budget traceability while the program determines where the work belongs. However, it should remain temporary.
Program-controls teams should monitor each UB entry by source, scope, owner, age, value, and planned distribution date. They should also reconcile the balance monthly and connect each transfer to approved scope and IMS changes. When managed well, UB helps preserve an accurate baseline without forcing immature work into detailed control account plans too early.