M3.2 — Budgeting & Cost Baselines

M3.2 — Budgeting & Cost Baselines

1. Practical outcome

By the end of this section, the learner should be able to turn an approved estimate and authorised project scope into a controlled cost budget and time-phased cost baseline that can be used to plan, measure and govern project cost performance. They should be able to allocate budget to the project control structure, define accountable ownership, distinguish base budget from contingency or reserve, phase budget in a way that reflects the delivery plan, reconcile cost and schedule assumptions, distinguish the cost-control baseline from cash flow and current forecast, and preserve an approved reference so that later variance and authorised change remain visible.

The objective is not to spread an approved total across months until the curve looks plausible. It is to create an authorised financial model of the delivery plan: what scope the project is funded and authorised to control, where that budget sits, when the associated work is planned to be accomplished, who can act on it, and what rules govern movement after approval.

A useful question throughout this Knowledge Area is: “If the forecast changes tomorrow, can management still see what budget was authorised, where it was held, when the work was planned, and why any movement in the baseline was approved?”

2. Core concepts

Estimate, budget, cost baseline, forecast and funding are related but different

Project cost control uses several financial views that are often confused. The terminology differs between organisations, but the underlying questions are distinct. M3.1 estimates what defined scope is expected to cost. M3.2 establishes what cost is authorised for control and when that authorised budget is planned to support delivery. M3.5 later asks what the work is now forecast to cost. Finance and treasury may separately ask when cash or funding is required.

A project can therefore be within its approved budget but forecasting an overrun, or it can have an adequate total budget but a near-term funding or cash-flow problem. Those are different management conditions and should not be hidden inside one number.

The budget should inherit the scope integrity of the estimate

Budget allocation begins with authorised scope. Every material budget element should have a clear scope home through the WBS, CBS or control-account structure established in M1.1 and M1.2. A cost baseline cannot be integrated if one team is budgeting one scope definition while the schedule or estimate uses another.

The approved estimate from M3.1 is an important input, but the authorised budget does not have to be numerically identical to every working estimate snapshot. Governance may approve challenge reductions, specific allowances, contingency or other reconciled adjustments. The essential requirement is that any estimate-to-budget difference is explicit, approved and traceable rather than hidden.

Budget ownership should sit where meaningful control can occur

A budget is most useful when somebody has enough authority and information to control the associated work. Many organisations use control accounts or equivalent management points that connect WBS scope, responsible organisation, schedule and budget. The label is less important than the principle: budget should be assigned at a level where performance can be understood and corrective action can be taken.

Budget can be decomposed below that point into work packages, planning packages or other controlled components. Future authorised work may initially be held at a higher level where detail is not yet mature, but it should not remain indefinitely in vague buckets that prevent accountability or performance measurement.

Base budget, contingency and management reserve need visible boundaries

Organisations use the words contingency, reserve and management reserve differently, so the Open Standard should not impose one universal accounting model. The control principle is that defined-scope budget and uncertainty provision should be distinguishable and governed. Management should be able to see what amount is allocated to planned work, what amount is held for recognised uncertainty, where it is held, who can authorise its use and whether drawdown changes the cost baseline.

Where an organisation uses management reserve outside the performance or control baseline but within total authorised project budget, that boundary should be explicit. Where contingency is distributed within work packages, the risk or uncertainty it covers should also be explicit. The same uncertainty should not be funded twice through hidden allowances and separate reserve.

For formal EVM, use the PMB and reserve boundaries explained in M5.3. The Reference Project’s general owner contingency examples do not automatically represent a contractor’s EVM management reserve.

Reserve is not a mechanism for erasing poor performance. If a package overruns because productivity was weak, transferring reserve merely to remove the variance can destroy the distinction between authorised uncertainty response and delivery performance.

Time-phasing should represent the planned delivery model

A total budget is not yet a useful cost baseline. It must be time-phased in a way that reflects when the authorised work is planned to be accomplished or incurred under the project’s control method. The schedule is therefore a major input to cost phasing.

For discrete work, budget should normally follow the planned accomplishment of the work rather than an arbitrary straight-line spread. For labour-driven work, a resource profile can provide the phasing. For quantity-driven work, planned installed quantities can drive the curve. For procurement, manufacturing or design packages, approved weighted milestones or other measurable stages can be used.

If earned-value or another integrated performance method is used, the time-phased budget for discrete scope should support the planned-value logic of that method. M5.3 teaches integrated cost and schedule performance; M3.2 establishes the cost baseline that later analysis depends on.

Cash flow and cost-control phasing may legitimately differ

A supplier may require an advance payment before manufacture, a retention may be paid after acceptance, or invoices may be raised at contractual milestones that do not match physical progress. The cash/payment profile therefore does not automatically equal the time-phased control budget.

Where the organisation uses accrual accounting, cost-incurrence timing may also differ from cash payment timing. M3.3 addresses commitments, actuals and accruals. M3.2 should establish the planned control reference and, where useful, a separate cash or funding profile so management can see both without confusing them.

Schedule and cost baseline should tell the same delivery story

If the schedule says installation occurs in Months 15–18 while the cost baseline earns almost all installation budget in Month 6, the project should investigate the inconsistency. There may be a legitimate commercial explanation for early payment, but that explanation belongs in the cash or commitment view rather than silently distorting the performance-control baseline.

Conversely, a schedule extension can create additional cost exposure even if the cost baseline has not changed. That effect belongs initially in the forecast. The project should not move baseline budget merely because forecast dates have slipped.

Forecast movement is not budget movement

The approved cost baseline answers what was authorised and planned. The current forecast answers what the work is now expected to cost. If productivity deteriorates or a supplier price increases, the forecast may move above budget. That variance is management information. Rewriting the budget to match the forecast would remove the signal that cost control is intended to provide.

Budget and baseline should change only under defined authority. Approved scope change, reserve drawdown, reallocation, controlled future-work replanning or a formal rebaseline may legitimately alter the reference. A routine forecast update does not itself authorise a baseline change. Apply M6.3’s distinction between forecast revision, rolling-wave/internal replanning and formal reprogramming; do not change the reference merely to remove adverse variance.

Budget transfers require governance and history

Projects sometimes need to transfer budget between work packages or control accounts. Some transfers may be delegated management actions; others may require formal change approval. The project should define authority thresholds, permitted reasons, effective dates and how history is preserved.

A transfer should not create or remove total authorised budget unless an authorised change permits it. It should also not disguise the cause of a variance. Good governance records the source, destination, reason, approving authority and the relationship to scope, risk or change.

Funding constraints can influence delivery without redefining the cost baseline

A project may have an approved total budget but insufficient funding in a particular financial period. That can force resequencing or create schedule risk. The response should be explicit: management may change the plan, secure additional funding or accept the consequence. The cost baseline, funding profile and schedule should then be reconciled through the appropriate governance rather than treated as if they are the same thing.

3. Step-by-step method — how to establish a controlled cost budget and baseline

1. Confirm the authorisation and budgeting purpose. Identify the decision that has approved the project or package, the authorised total, the effective date, the price basis and any conditions. Establish whether the budget is for project control, investment approval, contract control, annual funding or another purpose. Do not assume all financial totals answer the same question.

2. Confirm the authorised scope and estimate basis. Start from the approved scope, WBS and the estimate/Basis of Estimate developed in M3.1. Reconcile any differences between the estimate used for approval and the latest estimate. Identify scope, assumptions or allowances that management accepted, rejected or changed during authorisation.

3. Establish the cost-control architecture. Define the WBS/CBS/control-account structure at which budget will be owned and reported. Confirm identifiers, accountable managers and mapping to the schedule. Avoid inventing a parallel budget structure that cannot reconcile to the rest of project controls.

4. Define the budget categories and reserve rules. State how the organisation distinguishes base budget, package contingency, project contingency, management reserve, undistributed budget or equivalent categories. Record who owns each category and what approval is required to move it.

5. Reconcile the authorised total before distribution. Create a simple control equation showing how distributed budget and held reserve reconcile to the total authorised project budget. Any gap, overlap or unexplained allowance should be resolved before baselining.

6. Allocate base budget to scope. Distribute budget to WBS elements, control accounts and work packages at a level that supports responsibility and performance control. Check that every material scope element has a cost home and that no scope has been funded twice.

7. Assign accountable ownership. Identify the manager or team responsible for controlling each budget element. Confirm that the owner has enough authority and visibility to influence scope, resources, procurement or delivery. Avoid assigning nominal ownership to people who cannot act on the cost drivers.

8. Map budget to schedule work. Connect budgeted work to the activities, milestones or planning packages that deliver the scope. The mapping does not need to be one budget line per activity, but it should be clear enough to support time-phasing, progress measurement and later variance analysis.

9. Select the phasing basis for each work type. Choose a method that reflects planned accomplishment: quantities, resource loading, weighted milestones, planned procurement/manufacturing stages, LOE resource profiles or another defensible basis. Document exceptions.

10. Time-phase discrete work. Profile budget over the period in which the scope is planned to be accomplished. Reconcile the curve with schedule dates, productivity and resource assumptions. Avoid straight-line phasing unless the work genuinely follows a roughly uniform pattern.

11. Time-phase procurement and commercial packages carefully. Separate planned accomplishment from payment terms. A deposit, milestone invoice or retention can affect cash earlier or later than the work is physically earned. Maintain a separate cash/payment profile where that distinction matters.

12. Time-phase indirect and support cost. Use the planned resource or service profile for management, logistics, temporary facilities, project controls and other indirect work. Check that support cost does not continue beyond the schedule without explanation and that LOE is not used to mask discrete delivery performance.

13. Integrate contingency and reserve without double counting. Identify which uncertainty is held at package, control-account or project level and how it will be released or drawn down. Reconcile with M4 risk information and the M3.1 BoE so the same uncertainty is not funded in several places.

14. Reconcile cost baseline, schedule and funding views. Compare the time-phased control budget with scheduled work, expected commitments/cost-incurrence and funding/cash needs. Differences can be legitimate, but material differences should have an explicit reason and owner.

15. Perform baseline quality and affordability checks. Review scope coverage, ownership, time phasing, reserve treatment, schedule alignment, funding constraints, totals and control-account reconciliation. Challenge large early/late peaks, unexplained unallocated budget and phasing that appears driven by reporting convenience.

16. Obtain approval and preserve the authorised version. Record what budget and cost baseline were approved, by whom, when and with what conditions. Preserve the exact approved version and its underlying mapping/assumptions so that later performance can be compared with a stable reference.

17. Define movement and transfer rules. Document how approved change, reserve drawdown, internal budget transfer, forecast change and rebaseline are treated. Specify authority limits, evidence requirements and how prior versions remain recoverable.

18. Operate the baseline as a control reference. Use the approved phasing in later performance and variance analysis. Update the forecast when evidence changes, but do not automatically rewrite the budget. When authorised budget movement occurs, record the reason, source, destination, effective date and approval so management can reconstruct the history.

4. Worked Reference Project example — Community & Learning Centre

The Community & Learning Centre Reference Project has a fixed approved budget of 50 million CU and a 24-month delivery period. M3.2 turns that authorised total into a controlled cost architecture and time-phased baseline. The values below are illustrative learning allocations within the fixed 50 million CU project total; they do not change the canonical project scope.

Step A — reconcile the approved project budget

The first control test is arithmetic and structural: the distributed amounts plus project-held contingency equal 50.0m CU. The second test is conceptual: each amount has a defined scope owner and reserve boundary. The project should be able to explain what the 3.0m CU central contingency is intended to cover and why the 0.089m CU held within WBS 1.4 does not cover the same uncertainty.

Step B — reconcile M3.1 estimate to the Technology budget

M3.1 produced a current defined-scope estimate of 3.711m CU for WBS 1.4 Digital & Technology Systems before project-level contingency or reserve. The budgeting decision authorises 3.8m CU for the package. The 0.089m CU difference is not left unexplained: in this worked example it is an explicitly approved package contingency for two residual uncertainties that remain within the authorised technology scope. The BoE and risk record identify those uncertainties so they are not also funded from the central 3.0m CU reserve without a deliberate decision.

The base control budget available for planned technology work is therefore 3.711m CU. The 0.089m CU package contingency is held separately until its drawdown criteria are met. This prevents the planned-value or performance curve from assuming that contingency will automatically be earned simply because time passes.

Step C — time-phase the base control budget

The important lesson is that the control-budget curve and cash/payment curve can both be correct while looking different. If management used the payment curve as physical planned value, the project would appear to earn disproportionate performance before installation and testing occur. If treasury ignored the payment curve and looked only at planned accomplishment, the project could face a cash requirement it had not prepared for.

Step D — link the cost baseline to the schedule

The technology schedule places procurement and manufacture before on-site installation, followed by configuration, integrated testing and user acceptance. The cost baseline should therefore show the same broad sequence. If the schedule is later updated and installation is forecast three weeks late, the current cost forecast may also change because indirect support, supplier attendance or resource timing changes. The approved cost baseline, however, remains the reference unless the project approves a baseline change.

This distinction matters during performance review: “the forecast is now 4.05m CU” and “the authorised budget is 3.8m CU” can both be true. The 0.25m CU adverse forecast is information that management must understand; it is not an instruction to move the budget.

Step E — demonstrate reserve drawdown and baseline change

Assume one of the specifically identified technology uncertainties materialises and the authorised response requires 0.060m CU. Under the worked project rules, the Technology Lead submits evidence linking the event to the approved package contingency. The appropriate authority approves a 0.060m CU drawdown. The project records the source, reason, approving authority and effective date, and reallocates that amount from held package contingency into the relevant work-package budget.

The package-authorised total remains 3.8m CU; what changes is the distribution between held contingency and planned work. If a client-requested scope change adds new technology and needs another 0.200m CU from an owner-held project reserve, confirm that its rules permit that use and obtain the scope and funding approvals. This is not permission to fund added contract scope from contractor EVM management reserve. Neither transaction is a forecast increase caused by poor productivity.

Step F — perform baseline-readiness challenge

Before approval, the learner should be able to trace a selected cost element from authorised scope to estimate line, WBS/CBS code, accountable owner, schedule activity or milestone, time-phased budget and reserve treatment. They should then reconcile the WBS totals to 50.0m CU and explain why the control-budget, cash and current-forecast curves are different where they legitimately diverge.

A useful management statement would be: “The project has an authorised budget of 50.0m CU, of which 47.0m CU is allocated to delivery scope and 3.0m CU is held centrally for governed uncertainty. The Technology package is authorised at 3.8m CU, with 3.711m CU in the base control budget and 0.089m CU held as package contingency. Its cash requirement is front-loaded relative to planned accomplishment because of supplier payment terms. Any forecast movement will be reported against this baseline rather than absorbed into it automatically.”

5. Interpretation and professional judgement

Budgeting is not simply an accounting distribution exercise. The practitioner must decide whether the financial control model represents how the project will actually be delivered, whether authority sits at a useful level, whether uncertainty is visible, and whether the time-phased baseline can support meaningful performance analysis later.

How detailed should the budget structure be?

Detailed enough to expose material cost drivers, responsibility and scope boundaries, but not so detailed that every minor transaction becomes a control account. The appropriate level normally follows the level at which managers can act and performance can be interpreted.

Should the budget always equal the latest estimate?

No. The budget is the authorised control position and the forecast is the current expectation. A difference can be legitimate, but it should be understood. If the latest forecast exceeds budget, management needs to know why and decide what action or change is appropriate.

When is straight-line phasing acceptable?

Only when the underlying work is genuinely expected to progress at a broadly uniform rate or where a proportionate LOE method justifies it. Straight-line phasing should not be a default shortcut for discrete delivery.

How should procurement be phased?

Separate physical or performance-control phasing from contractual cash/payment timing. A deposit is not automatically physical accomplishment, and a retention payment after acceptance does not mean the work was only completed when cash was paid.

Where should contingency sit?

There is no universal answer. The project should choose a governance model that reflects accountability and uncertainty. The critical test is that contingency is visible, linked to a defined purpose or risk class, not double counted, and released only under controlled authority.

What if management wants to move budget to remove a variance?

Challenge the reason. Legitimate transfer, scope change or reserve drawdown can alter distribution, but moving budget solely because a package is overspending turns the baseline into a moving target and weakens performance information.

How should annual funding limits affect the baseline?

Funding constraints are real delivery constraints and should be visible in schedule and cost planning. If funding forces resequencing, the plan may need formal revision. Do not simply reshape the cost baseline to fit a funding profile without addressing the delivery consequence.

What should happen to authorised but immature future scope?

Use a governed higher-level or planning-package budget until detail is mature enough for lower-level control. Progressive elaboration is legitimate; permanent ambiguity is not. The budget should become more specific as scope and schedule definition improve.

How should an internal transfer be judged?

Ask whether the scope changed, whether total authorised budget changed, whether the transfer is within delegated authority, whether it removes a meaningful variance and whether it affects performance-history comparability. Record the decision so later users can reconstruct it.

What is the strongest test of baseline quality?

Whether the baseline supports decisions. A manager should be able to see what scope is funded, when it was planned, who controls it, where uncertainty is held, what variance means and what authority is required to change the reference.

Questions the practitioner should be able to answer

·       What approved decision and estimate created this budget?

·       What scope is included in each budget element and how does it map to the WBS/CBS?

·       Who is accountable for each material budget element?

·       Which amounts represent base work, package contingency, project contingency or reserve?

·       What uncertainty does each reserve category cover and who can authorise drawdown?

·       Does distributed budget plus held reserve reconcile exactly to the authorised total?

·       What schedule activities or milestones drive each major period of cost-baseline phasing?

·       Which work packages use quantity, resource, milestone or LOE phasing and why?

·       Where do cash/payment timing and performance-control phasing differ?

·       Are those differences documented and understood by finance and delivery teams?

·       Does current schedule timing still tell the same story as the approved cost baseline?

·       What is the latest cost forecast and how does it differ from budget?

·       Which movements are forecast changes and which are approved baseline changes?

·       What budget transfers have occurred and can their causes and approvals be reconstructed?

·       Are funding constraints affecting delivery or phasing?

·       Can the full baseline be reconciled back to the approved 50m CU total and forward to the records used for performance analysis?

A useful practitioner test is: “If I see an adverse cost variance, can I determine whether it comes from timing, performance, scope change, estimate/forecast movement, reserve treatment, coding or a genuine change to the authorised baseline?”

6. Practice diagnostic

Use this table to challenge the quality of the approach or deliverable. The rows consolidate the most important recurring red flags and checks; they are prompts for professional judgement rather than a substitute for the method above.

7. Try-it-yourself practical exercise

Using the Community & Learning Centre Reference Project, build and challenge a simplified cost budget and baseline. The exercise should demonstrate control architecture, time phasing and governance rather than simply producing a monthly spreadsheet.

1. Starting from the fixed 50m CU authorised project budget, allocate 47m CU across the six Level-1 WBS elements and retain 3m CU as a governed project-level contingency/reserve. Explain the rationale for the distribution.

2. For one Level-1 WBS element, define at least four lower-level control packages and assign accountable owners. Show how the package budgets map to WBS/CBS and responsibility structures.

3. Choose one package and reconcile its M3.1 estimate to the amount authorised as budget. Identify and explain any difference rather than forcing the numbers to match silently.

4. Define which budget is base work, which is package contingency and which remains held at project level. Write the drawdown authority and evidence rule for each held amount.

5. Map at least ten representative schedule activities or milestones to the selected package budget and identify the phasing basis for each work type.

6. Create a 12-period time-phased cost-control baseline for the package. Use at least two phasing methods, such as resource loading, planned quantities or weighted milestones.

7. Create a separate 12-period cash/payment profile for the same package that includes one advance payment and one retention or delayed payment. Explain why the two curves differ.

8. Introduce a three-week schedule delay without changing scope. Update the current cost forecast assumptions and explain why the approved cost baseline does or does not move.

9. Introduce a 0.10m CU productivity-driven forecast overrun. Show the variance against budget and explain why reserve should not automatically be used to remove it.

10. Introduce one approved risk event that qualifies for contingency drawdown. Record the source, destination, rationale, approval and effective date and show the before/after budget distribution.

11. Introduce one approved scope change funded from project-level reserve. Demonstrate how the new budget, schedule and baseline history remain traceable.

12. Introduce three deliberate defects: a cash curve used as planned value, a duplicated contingency allowance, and an unallocated budget amount with no owner. Identify and correct all three during a baseline-readiness review.

13. Reconcile all WBS totals, reserve balances and time-phased values back to the authorised 50m CU project total.

14. Prepare a one-page cost-baseline narrative explaining scope/budget ownership, time-phasing basis, reserve treatment, funding/cash differences, current forecast relationship and change rules.

What good performance looks like

The exercise is successful when the learner can demonstrate that the budget is authorised, traceable to scope, owned, time-phased to a credible delivery plan, reconciled to the total and governed after approval. They should be able to explain why cash, forecast and control-baseline curves differ; distinguish reserve drawdown from performance overrun; and preserve a visible audit trail of budget movement. A spreadsheet that adds to 50m CU but cannot explain those relationships is not sufficient.

8. Bridge to capability

The How-to teaches how approved cost becomes a controlled budget and time-phased baseline. At APPLIED and above, capability assessment should test whether the practitioner can establish or maintain that position under realistic schedule, funding and reserve constraints. Reconciled allocations, ownership, phasing and authorised transactions should substantiate the result. Supporting work products are illustrative and should be assessed with the practitioner’s reasoning. Sample learning questions illustrate the judgement at each recognition level; they are discussion prompts rather than validated assessment items.

Learning question: Do you understand how authorised cost becomes a time-phased control baseline?

Capability question for APPLIED and above: Can you demonstrate a reconciled cost baseline while keeping budget, forecast, cash, reserve and approved change distinct?