20.1 Creating a Budget and Cost Types

Budgeting on the APM PMQ

Budgeting and cost control (learning objective 22, Area D) is how the project converts agreed scope and estimates into an authorised cost baseline, then monitors, forecasts, and closes money responsibly. This section covers creating a budget, including the Cost Breakdown Structure (CBS), cost types, contingency versus management reserve, and estimating approaches at overview level. The next section covers earned value, financial reporting, and financial close.

Weak exam answers treat the budget as a single number the sponsor once approved. Strong answers explain structure (CBS linked to WBS), classification of costs, risk money treated transparently, and governance of the baseline.

Exam frame: Budgeting is integrated with scope and schedule. Money without mapped work is uncontrolled; work without funded cost accounts is a commitment the organisation has not authorised.

What a project budget is

A project budget is the approved, usually time-phased allocation of money to deliver the authorised scope within defined constraints. It is more than a total: it is a control tool that says how much may be spent, on what categories or work packages, and often when cash is expected to flow.

The cost baseline (budget for control) should align with the scope baseline (WBS/products) and schedule baseline (when work happens). That is the financial face of integrated planning.

Cost Breakdown Structure (CBS) and the WBS link

A Cost Breakdown Structure (CBS) hierarchically organises project costs into accounts or codes used for estimating, approval, charging actuals, and reporting. It answers: How do we structure the money so we can manage it?

CBS ↔ WBS (and PBS)

Recall the breakdown family from schedule and scope teaching:

Integration rule: every significant WBS work package that consumes money should map to one or more CBS cost accounts, and every major CBS account should map back to authorised work (and, where useful, products). Orphan cost codes and unfunded work packages both destroy control.

Authorised scope (PBS products)
        ↑ created by
WBS work packages  ←—— estimate effort/materials
        ↑ funded and controlled via
CBS cost accounts / budget line items  ←—— time-phased cost baseline

Why CBS design matters

Organisations often use a project coding structure that maps WBS elements to corporate cost codes. For PMQ, stress traceability from work to money, not a branded software tool.

Scenario A — CBS not linked to WBS

A systems project budgets £2.4m under three finance headings: "hardware," "software licences," and "professional services." The WBS has twelve work packages including data migration and training. Actual spend hits professional services hard, but nobody can see whether migration or training is overrunning. Correct practice: structure the CBS (or a control account layer) so migration and training are separate cost accounts mapped to their WBS packages, while still rolling up to finance codes for the general ledger.

Cost types: fixed, variable, direct, indirect

PMQ expects you to recognise cost types so estimates and control actions make sense.

Fixed vs variable (cost behaviour)

Semi-variable / stepped costs exist in practice (a second supervisor hired after a headcount threshold). In answers, classify the dominant behaviour and note the range.

Direct vs indirect (attribution)

Overhead is often used for organisational indirect costs allocated to projects. Be precise: indirect to a work package may still be direct to the project (for example a dedicated project manager salary charged wholly to one project).

Other useful distinctions (exam vocabulary)

Scenario B — fixed cost mistaken for variable

A sponsor demands a 20% scope cut and expects a 20% cost cut. Half the budget is fixed licences and a leased project office already contracted for twelve months. The PM should re-estimate: variable costs (contractor days, materials) may fall; fixed commitments may not, unless contracts are renegotiated (often with exit cost). Explain cost behaviour, not only total percentage.

Contingency vs management reserve (conceptual)

Risk money is a classic PMQ trap. Treat the concepts clearly even when organisations use different labels.

Key teaching points:

1. Contingency is not a slush fund for scope growth or poor estimating — it is risk-related (and should be traceable to the risk approach).
2. Management reserve is not free money for the project manager to spend without authority.
3. Using contingency for unauthorised scope bypasses change control and corrupts earned value baselines.
4. As risks retire or crystallise, contingency should be reviewed and potentially released or reinforced under governance.

Scenario C — contingency used for gold-plating

A team uses "risk contingency" to fund extra reporting dashboards that were never in scope and never risk-assessed. That is scope change without control, not risk management. The correct path is a change request with cost, time, and benefit impact — funded from approved change budget or a revised baseline, not silent contingency drawdown.

Building a budget — practical steps

A defensible budget build typically follows this logic (wording varies by organisation):

1. Confirm authorised scope — WBS/PBS, exclusions, acceptance criteria, constraints.
2. Select estimating approaches appropriate to maturity of information (overview below).
3. Estimate by work package / cost account — labour, materials, equipment, services, travel, fees.
4. Classify and check — direct/indirect, fixed/variable, CapEx/OpEx if required; remove double counts.
5. Add risk-based contingency — linked to risk analysis; identify separately.
6. Time-phase the budget — map costs to the schedule for cash flow and performance measurement.
7. Reconcile to funding — annual budgets, grant rules, stage-gate funding releases.
8. Seek baseline approval from the correct financial authority; communicate the authorised CBS structure.
9. Establish actuals process — timesheets, purchase orders, accruals so control data is trustworthy.

Estimating approaches (overview level)

You need conceptual fluency, not deep statistical technique.

Progressive elaboration: early budgets may rely more on analogous/parametric totals; later phases shift to bottom-up package estimates. Re-estimating is normal professional practice, not failure.

Scenario D — top-down target vs bottom-up reality

Finance issues a top-down target of £1.0m. Bottom-up WBS estimates total £1.15m base plus £0.08m contingency. The PM must not silently cut package estimates to force a match. Present the gap with options: descope, phased delivery, different methods, extra funding, or accepted risk — under sponsor decision. A forced fake baseline destroys cost control later.

Putting LO22a together for exam answers

When a scenario involves overspend risk, unclear budgets, or "just cut 10%":

1. Define the budget / cost baseline as authorised, structured money for scope.
2. Use CBS–WBS language to show control accounts map to work.
3. Classify relevant cost types (fixed/variable, direct/indirect) to explain what will actually change.
4. Separate base estimate, contingency, and management reserve conceptually.
5. Outline build steps and the need for authority and time-phasing.
6. Name suitable estimating approaches given information maturity.

That structure answers LO22a and sets up earned value and financial control in the next section.