Cost Aggregation and Cost Baseline
Cost aggregation rolls the work package estimates up the project's work breakdown structure. The project manager sums the packages in their control account and then the accounts up to the project total. The schedule sets how this total spreads over time. Once approved, this time-phased budget becomes the cost baseline. The project manager then compares actual costs against it. The PMBOK Guide groups these operations in the Develop Budget process, which also checks each period's spending against the funding limits.
Goal
According to the PMBOK Guide, the Develop Budget process aggregates the estimated costs of the activities or work packages of the work breakdown structure to establish an authorised cost baseline.
The estimates state what each package costs. They do not say how much the project spends in each quarter or which amount the actual costs are compared against. The technique answers both questions. The sponsor relies on it to approve the budget and release the funding for each period.
Cost aggregation sums the estimates at each level of the work breakdown structure. Funding limit reconciliation compares the planned spending of each period with its limit. The PMBOK Guide adds supporting tools: expert judgment, reserve analysis, historical information review and financing (securing the funds, often from outside the organisation).
The process delivers the cost baseline by control account and by period. It also delivers the total and periodic funding requirements. It updates the cost estimates, the schedule and the risk register.
The technique starts from finished work package estimates. Bottom-up estimation is their usual source. The technique ends when the sponsor approves the baseline. Earned value management then measures progress against this baseline.
Usage
When to use it
- Work package estimates complete: turn them into a time-phased budget for approval.
- Earned value management planned: supply the planned value of each control account for each period.
- Funding by annual credit or in tranches: check that the planned spending of each period fits within the amount available.
- HERMES project management plan due: produce the cost plan and the approved budget that this outcome contains.
- End of a phase or new funding tranche: rebuild the baseline for the rest of the project.
- Approved change to scope, schedule or funding: re-aggregate the affected control accounts and update the baseline.
- Work contracted to a supplier: include the contract price in the control account that carries this work.
When not to use it
- Order of magnitude needed before any breakdown of the work (feasibility study, initiation phase): price the whole project with top-down estimation or parametric estimation.
- Agile budget set by team capacity: the spending of each period is known in advance; set the budget first and adjust the scope with time boxing and budgeting.
Description
The elements
The work package is the lowest level of the work breakdown structure. It carries an estimate and a unique identifier. These identifiers form a code of accounts used to summarise costs, schedule and resources.
The control account groups two or more work packages. In it, scope, budget and schedule are integrated and compared with the earned value. The GAO, which audits federal programmes for the US Congress, places the account at the intersection of the work breakdown structure and the project's organisation chart. One unit of the organisation is accountable for its work. Accounting books the actual costs to it.
The planning package sits between the control account and the work package. Its content is known and its activities remain to be detailed. Its budget enters the sum of the account.
According to the PMBOK Guide, the cost baseline is the approved version of the time-phased project budget. It excludes the management reserve. It changes only through change control. Together with the scope and schedule baselines, it forms the performance measurement baseline that earned value management uses.
The funding requirements derive from the baseline. They break down into total requirements and requirements per quarter or per year. The total funding required equals the cost baseline plus any management reserve. Funding often arrives in uneven tranches. The requirements can name the source of each amount.
The financial management plan sets the rules of the calculation: the unit of measure, the level of precision for rounding, the accepted level of accuracy (for example ±10%), the code of each control account and the control thresholds for variances.
| Amount | Content | Status | Use |
|---|---|---|---|
| Sum of the estimates | The estimates of the work packages and planning packages aggregated by control account | Unapproved intermediate calculation | Starting point of the budget |
| Cost baseline | The sum of the estimates spread over time, with the contingency reserve when the organisation places it there | Approved; changed through change control | Comparison with actual costs; planned value for earned value management |
| Initial budget | Reserves managed implicitly: the cost baseline plus the management reserve. Reserves managed explicitly: the estimates alone. | Approved; management releases the management reserve at its discretion | Basis of the total and periodic funding request |
The sequence
The steps synthesise the tools and the glossary of the PMBOK Guide and the process that the GAO describes.
- Gather the package estimates, their basis, the work breakdown structure, the schedule and the rules of the financial management plan.
- Sum the estimates by control account, then up to the project total.
- Place the contingency reserve according to the organisation's scenario and keep the management reserve out of the baseline.
- Spread each cost into the period in which the schedule places its work.
- Compare the spending of each period with its funding limit and shift the work that exceeds it.
- Derive the total and periodic funding requirements.
- Have the cost baseline approved.
- Hand the baseline over to monitoring and control, which measures progress against it.
Gather the inputs
The scope baseline provides the work breakdown structure and its dictionary. The schedule provides the dates. The risk register and the reserve analysis provide the reserves. The contracts provide the suppliers' prices.
Before summing, the project manager checks that every package carries an estimate and that every estimate belongs to a single package. A package without an estimate is missing from the total. An estimate attached to two packages counts twice. The project manager also checks that all the estimates use the same unit and the same precision.
Sum by control account
The addition is mechanical. The choice of accounts calls for judgement, because their level sets the level of detail of the tracking. A single account per phase buries the variance of one package in the phase total. One account per package multiplies the reports without informing the sponsor any better. Each account has a manager. The GAO calls this role the control account manager. The control account manager answers for the work, the budget and the variances of the account.
The financial management plan gives each account a code linked to the organisation's accounting. An invoice booked to this code falls into the same account as its budget. Without a common code, comparing the actual costs with the budget requires sorting the entries by hand.
Place the reserves
The contingency reserve enters the baseline when the organisation manages its reserves implicitly. It stays apart when the organisation manages them explicitly. Reserve analysis describes these two scenarios of the PMBOK Guide and sizes the reserves. The financial management plan records the chosen scenario. Without it, two revisions of the baseline cannot be compared. In the baseline, the contingency reserve carries its own line at the level of the control account or of the project whose risks it covers. The project manager places it in the period in which these risks can occur. The management reserve stays out of the baseline in both scenarios.
Spread over time
In the schedule, each activity carries the code of its package. The cost of the package therefore follows the dates of its activities. Labour follows the workload of the resources assigned to the activities. Material counts in the period of its delivery. The price of a supplier contract follows its payment milestones. The project manager spreads a planning package over the period that the schedule reserves for it.
The cumulative amounts per period trace an S-curve. Spending rises slowly at the start, accelerates during execution and slows at the end. A budget spread in equal parts over the months ignores the schedule. The reconciliation then compares the limit with amounts that nobody will spend on those dates.
Reconcile spending with the funding limits
The project manager compares the planned spending of each period with the limit of that period. When the planned spending departs from the limit, the project manager sometimes reschedules work to level out the rate of expenditure. Resource levelling and smoothing apply the same logic to people and equipment.
The financial management plan states whether the limit counts payments or costs incurred. The project manager spreads the supplier packages on the same basis. Without this rule, a package invoiced in year 2 for work done in year 1 can fall on the wrong side of the limit.
The limit takes several forms. Some annual budgets forbid any carryover to the following year. A budget allocation can separate capital expenditure (CapEx) from operating expenditure (OpEx). An external funder can set its own conditions.
In the Swiss federal administration, the Federal Finance Administration distinguishes two credits. The budget credit (Voranschlagskredit) authorises an administrative unit to spend for the stated purpose and within the approved amount during the budget year. The commitment credit (Verpflichtungskredit) sets the amount up to which the Federal Council may enter into commitments for a specific purpose. It is required in principle for commitments that extend beyond the budget year. The Federal Council can decide on a credit carryover (Kreditübertragung): it then moves an unused balance to the following year. The balance must result from a delay in the project. The carried-over share serves this project only. The budget credit plays the role of the PMBOK Guide's funding limit per period.
When spending exceeds the limit, the project manager first looks for work to shift without moving the end date. The project manager imposes a date constraint on each shifted activity, recalculates the schedule and checks the critical path with the critical path method. A shifted critical activity pushes back the end of the project. When no shift fits within the limit, the sponsor decides: more funding in the period, a reduced scope or a later end date.
The project manager then resumes the sequence at step 2. A reduced scope changes the sums of the accounts. A later end date changes the spread over time. Increased funding changes the limit of the reconciliation.
Derive the funding requirements
The periodic requirements follow the time-phased baseline. The funding cycle sets whether they run by year or by quarter. The organisation decides in which period it requests the management reserve.
Obtain approval
The sponsor approves the cost baseline. HERMES places the cost plan and the approved budget in the project management plan. In the project management plan, HERMES asks for the estimates with their accuracy and the reserves that follow from them. The project management plan is adapted at the close of each phase for the next phase.
Hand over to monitoring
The Monitor and Control Finances process then receives the baseline and keeps it current. One of its tools is earned value management, which reads the planned value of each account at each status date from the baseline.
The GAO lists the triggers for updating the baseline: a contract modification, a funding stream that shifts or is restricted, a change in rates, a change in scope or schedule, a revision of the acquisition strategy and a management decision. It recommends recording each change in detail.
In an adaptive approach
According to the PMBOK Guide, an iterative approach flattens the spending curve. The project then uses a time-phased budget and assesses funding continuously. In an agile approach, the sponsor can allocate the budget for one quarter and revise it each quarter according to the work done. The baseline then covers the horizon of the funding granted. When the budget equals the capacity of the team multiplied by its cost per period, time boxing and budgeting replace aggregation.
Pitfalls
The front-loaded baseline
According to the GAO, a front-loaded baseline gives the work of the early periods a disproportionate share of the budget. The work of the later periods then lacks budget. The defect hides problems until it is too late to correct them. The project manager compares the share of the budget in each period with the share of the work that the schedule places there.
The rubber baseline
The GAO uses the term rubber baseline for a baseline that the project keeps shifting toward actual spending to hide variances. The variances disappear early and reappear when correcting them becomes difficult or even impossible. Only an approved change justifies updating the baseline.
The outdated baseline
A baseline that is slow to incorporate approved changes becomes outdated. The variances measured against it no longer reflect reality. The earned value data lose their meaning. An approved change enters the baseline in the same period as it enters the schedule.
The undistributed budget that lingers
The GAO uses the term undistributed budget for the holding account of new work. The amount moves to a control account as soon as that work is planned in detail. The GAO asks for it to be distributed as soon as possible. Some of the sources it consulted set a period of 60 to 90 days. An amount attached to no control account has no manager and counts in no progress measurement.
AI considerations
A language model turns a schedule export into a baseline matrix: one row per work package grouped by control account, one column per period, the totals and the cumulative total. It makes addition errors on large tables. The analyst redoes the totals in the spreadsheet. The analyst checks that the row total, the column total and the sum of the estimates plus the contingency reserve agree.
The model proposes shifts to bring a period under its limit. It ignores the dependencies and the resource availability that the export does not contain. The scheduler tests each proposal in the scheduling tool. The tool recalculates the critical path and the end date.
The model compares the history of baseline revisions with the variances. It flags the accounts whose baseline moved just after a variance as rubber baseline candidates. The control account manager explains each case.
The sponsor approves the baseline and arbitrates between funding, scope and time. Budgets, contract prices and accounting data stay out of online services whose terms of use the organisation does not control.
Examples
The baseline matrix shows the reconciliation with an annual limit. A federal office replaces its case management application over six quarters. Its contracts run beyond the budget year and in principle require a commitment credit. The commitment credit covers the total funding requirement. The budget credit covers the requirement of each year: it authorises CHF 450'000 for year 1. The office manages its reserves implicitly: the contingency reserve enters the baseline. The contingency reserve of CHF 52'000 covers the risks of the data cutover in quarter 5. The illustrative amounts are in thousands of CHF.
| Control account | Package | Q1 | Q2 | Q3 | Q4 | Q5 | Q6 | Total |
|---|---|---|---|---|---|---|---|---|
| Concept | A. Requirements analysis | 60 | 60 | |||||
| B. Architecture | 30 | 60 | 90 | |||||
| Implementation | C. Development | 40 | 100 | 100 | 240 | |||
| D. Data migration | 20 | 110 | ||||||
| Contingency reserve (data cutover) | 52 | 52 | ||||||
| Deployment | E. Training | 50 | 30 | 80 | ||||
| F. Go-live | 20 | 50 | 70 | |||||
| Baseline per quarter | 90 | 100 | 120 | 80 | 702 | |||
| Cumulative baseline | 90 | 190 | 310 | 622 | 702 | |||
| Funding requirements | Year 1: 450 (budget credit: 450) | Year 2: 287 (252 plus 35 management reserve) | 737 | |||||
The shift affects only the migration, which still ends in quarter 5. The scheduler checked that the go-live keeps its date. The accounts of 150, 402 and 150 total 702. The quarters also total 702.
Visualisations
The cumulative curve sets the baseline against the funding step of each year.
Cost
| Phase | Level | Rationale |
|---|---|---|
| Preparation | Medium | A stable work breakdown structure, estimates per package, an up-to-date schedule and known funding limits. |
| Execution | Medium | The sum is mechanical in a tool. The spread and the reconciliation require back-and-forth with the schedule. |
| Documentation | Medium | The matrix by account and by period, the funding requirements, the approval decision, then the history of the baseline changes. |
Tools
A spreadsheet is enough for a project of a few dozen packages. One sheet holds the packages in rows and the periods in columns. Another holds the revision history.
Scheduling software (Microsoft Project, Primavera P6) loads the costs onto the activities. It produces the spread by period and the cumulative curve. It stores the baseline and compares it with the current schedule.
Earned value management tools (Deltek Cobra, for example) consolidate many control accounts. Enterprise resource planning systems (SAP Project System, for example) hold the budget by element of the work breakdown structure and link it to the accounting entries.
Sources
- PMI, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 8th ed., §2.4.1 (Funding, Financial constraints, Reserves and figure 2-25), §2.4.2.3 and figure 2-29, §2.4.2.4, §2.4.3, Section 4 (entries Cost baseline, Financial management plan, Project funding requirements and figure 4-1, Scope baseline), Section 5 (entries Cost aggregation, Earned value analysis, Financing, Funding limit reconciliation): the definition of Develop Budget, its inputs, its tools and its outputs; the cost baseline and the funding requirements; the control account and the planning package; the rules of the financial management plan; the financial constraints; the tailoring to iterative approaches.
- U.S. Government Accountability Office, Cost Estimating and Assessment Guide, GAO-20-195G, March 2020, chapter 18: the control account at the intersection of the work breakdown structure and the organisation chart; the undistributed budget; the defects of the baseline and the triggers for its update.
- Federal Finance Administration FFA, Kreditarten und Zahlungsrahmen (in German): the budget credit, the credit carryover and the commitment credit.
- Swiss Confederation, Federal Chancellery, HERMES 2022, Project Management Reference Manual, outcome 4.4.1.34 Project management plan and 7.4.5.3 Planning in traditional solution development: the cost plan and the approved budget in the project management plan; the estimates with their accuracy and their reserves; the adaptation of the plan to each phase.

