Study guide
20.1 Creating a Budget and Cost Types
APM Project Management Qualification PMQ
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Exam Format & Question Types 1.3 How to Study for APM PMQ
2 Life Cycles
2.1 Linear Life Cycles and Why Work Is Phased 2.2 Iterative and Hybrid Life Cycles 2.3 Project Life Cycles and Extended Life Cycles 2.4 Choosing a Life Cycle: Context, Culture, Strengths and Limitations
3 Governance Arrangements
3.1 Functional, Matrix and Projectised Structures 3.2 Governance Frameworks, Policies and Delegated Responsibility 3.3 Life-Cycle Impact on Governance and Limits of Financial Authority 3.4 Project Roles and Responsibilities 3.5 Project Manager and Project Sponsor Through the Life Cycle 3.6 Linking Projects to Organisational Objectives
4 Sustainability
4.1 Sustainability Responsibilities, Principles and Impact 4.2 Monitoring and Reporting Sustainability Measures
5 Business Case
5.1 Business Case Fundamentals and Analysis Tools 5.2 The Business Case as Baseline and Reviewing Change
6 Procurement
6.1 Procurement Strategy: Purpose and Contents 6.2 Supplier Selection and Negotiation 6.3 Features of Different Contractual Relationships 6.4 Supplier Reimbursement Methods
7 Reviews & Assurance
7.1 Reviews, Decision Gates, Benefits Reviews and Audits 7.2 What Gets Reported and Informing Decisions 7.3 Why Activities Are Re-Planned After a Review 7.4 Project Assurance
8 Transition & Benefits Management
8.1 Transition Requirements and Business-as-Usual Readiness 8.2 Knowledge Transfer and Agreeing the Transition Plan 8.3 Benefits Management: Identification to Realisation 8.4 Aligning and Communicating Benefits
9 Stakeholder Engagement & Communication
9.1 Stakeholder Analysis, Influence and Engagement 9.2 The Communication Management Plan and Its Benefits 9.3 Managing Stakeholder Expectations 9.4 Communication Methods and Tailoring the Message 9.5 Factors That Help and Hinder Communication
10 Conflict Resolution
10.1 Sources and Impacts of Conflict 10.2 Addressing Conflict and the Thomas-Kilmann Model
11 Leadership
11.1 Leadership, Motivation and Team Performance 11.2 Changing Leadership Styles for the Situation 11.3 Coaching, Mentoring and Emotional Intelligence
12 Team Management
12.1 Team Development Stages and Models 12.2 Characteristics and Benefits of Effective Teams 12.3 Leading Virtual and Hybrid Teams
13 Diversity & Inclusion
13.1 Diversity Characteristics and the Equality Act 13.2 Incorporating Diversity and Diverse Thinking 13.3 Conscious and Unconscious Bias and Fair Treatment
14 Ethics, Compliance & Professionalism
14.1 Continuing Professional Development and Competence 14.2 Sources of Specialist Advice and Standards 14.3 The Legal and Regulatory Landscape
15 Requirements & Solutions
15.1 Establishing Scope Through Requirements Management 15.2 Managing Scope Through Configuration Management 15.3 Solutions Development and Prioritisation
16 Quality Management
16.1 Quality Planning, Indicators and the Business Case 16.2 Quality Control and Success Criteria
17 Integrated Planning
17.1 The Integrated Project Management Plan: Format and Contents 17.2 Why an Integrated Plan Matters
18 Schedule Management
18.1 Defining Scope and Breakdown Structures 18.2 Dependencies and What Drives the Schedule 18.3 Re-Estimating and Schedule Optimisation
19 Resource Management
19.1 Determining Resource Requirements and Availability 19.2 Organisational Breakdown Structure and RACI 19.3 Categorising and Allocating Resources 19.4 Resource Smoothing and Resource Levelling
20 Budgeting & Cost Control
20.1 Creating a Budget and Cost Types 20.2 Earned Value and Cost Forecasting 20.3 Monitoring and Reporting Financial Performance 20.4 Closing Down Project Finances
21 Risk & Issue Management
21.1 Benefits of Risk and Issue Management and Contingency Planning 21.2 The Risk and Issue Management Processes 21.3 Proactive and Reactive Risk Responses 21.4 Governance in Risk and Issue Management
22 Change Control
22.1 The Change Control Process and Its Stages 22.2 What a Change Request Must Capture 22.3 Assessing Options and the Impact of a Change 22.4 Recommending Decisions and Updating Plans
20.1 Creating a Budget and Cost Types
Key Takeaways Explain This Topic AI
A budget is the approved, time-phased spending plan against which actual cost is controlled, not simply a total figure.
The cost breakdown structure aligns cost to the same decomposition as the work breakdown structure, which is what makes cost and progress comparable.
Fixed costs do not vary with the volume of work; variable costs do — so a scope cut does not reduce cost proportionally.
Direct costs are attributable to the project; indirect costs are shared overheads apportioned to it.
Contingency covers identified risk within the project manager’s control; management reserve sits above the baseline for the unforeseen and is released by governance.
Last updated: August 2026
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.
- Budget concept Meaning Why it matters
- Cost estimate Forecast of what work will cost Input to budget; not yet authority to spend
Budget / cost baseline Authorised amount for the defined scope (often with contingency treatment defined) Control baseline for variance and change
Funding / cash profile When money is available from finance A feasible budget can still fail if cash arrives too late
Forecast out-turn Current expected total cost at completion Updated as performance and risks evolve
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:
- Structure Primary question Budget role
- PBS What products? Costs often roll up to product or deliverable families
- WBS What work? Work packages are the usual estimating and control objects
- CBS What cost accounts/codes? Money is coded so actuals compare to budget by meaningful slice
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
- CBS design choice Control effect
- Aligned to WBS Easy earned value and package-level variance
- Aligned only to finance GL codes Easy corporate accounting; may obscure project package performance
- Too coarse Overruns hide inside large buckets
- Too fine Admin burden; noise instead of insight
- Consistent coding rules Actuals comparable over time and projects
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)
Type Behaviour Project examples Control implication
Fixed Does not change materially with activity volume (within a range) Project office rent for a set period; fixed software licence for the programme duration; some insurance premiums Changing output volume may not reduce these costs unless you cancel/renegotiate the commitment
Variable Changes with volume of work or output Materials per unit; contractor hours; cloud compute per transaction; travel per site visit Volume and productivity drive cost; good for unit-rate control
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)
Type Meaning Project examples Control implication
Direct Attributable clearly to a specific project/work package Site labour on package A; steel for building B; test environment hired only for this release Charge to the package; strong for bottom-up estimating
Indirect Shared or not uniquely attributable to one package Programme PMO overhead; shared tooling; corporate facilities recharges; some management salaries Need allocation rules; watch double-counting and unfair loading
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)
- Distinction Meaning
- Capital vs operating (CapEx / OpEx) Investment vs running cost — funding and approval routes may differ
Committed vs accrued vs paid Obligation raised vs cost recognised vs cash left the bank — status reports can look different
- Baseline budget vs forecast Authorised plan vs current expected out-turn
- 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.
Provision Typical purpose Typical ownership Inside cost baseline?
Contingency For identified risks (known unknowns) after risk analysis — funded responses and residual risk exposure Usually project (drawn under project risk/change rules) Often yes — part of the project budget for control, separately identified
Management reserve For unknown unknowns / unforeseen events beyond identified risk set Usually sponsor / senior governance above the project Often no — held outside the project performance measurement baseline
Key teaching points:
Contingency is not a slush fund for scope growth or poor estimating — it is risk-related (and should be traceable to the risk approach).
Management reserve is not free money for the project manager to spend without authority.
Using contingency for unauthorised scope bypasses change control and corrupts earned value baselines.
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):
Confirm authorised scope — WBS/PBS, exclusions, acceptance criteria, constraints.
Select estimating approaches appropriate to maturity of information (overview below).
Estimate by work package / cost account — labour, materials, equipment, services, travel, fees.
Classify and check — direct/indirect, fixed/variable, CapEx/OpEx if required; remove double counts.
Add risk-based contingency — linked to risk analysis; identify separately.
Time-phase the budget — map costs to the schedule for cash flow and performance measurement.
Reconcile to funding — annual budgets, grant rules, stage-gate funding releases.
Seek baseline approval from the correct financial authority; communicate the authorised CBS structure.
Establish actuals process — timesheets, purchase orders, accruals so control data is trustworthy.
Build quality check Question
Completeness Are all WBS packages that cost money represented?
Consistency Do schedule dates and resource plans match the cost phasing?
Transparency Is contingency separate from base estimate?
Authority Does total sit within the business case envelope and approval limits?
Controllability Can actuals be coded to the same structure?
Estimating approaches (overview level)
You need conceptual fluency, not deep statistical technique.
- Approach How it works Strengths Limits
- Analogous Use cost of a similar past project, adjusted Fast; useful early Accuracy depends on similarity
Parametric Unit rates × quantity (cost per m², per user, per story point with care) Scalable; good when parameters stable Bad parameters → systematic error
Bottom-up Estimate detailed work packages, then sum Most controllable; links to WBS/CBS Needs detail; time-consuming
Three-point (overview) Optimistic / most likely / pessimistic to reflect uncertainty Surfaces risk in the estimate Needs honest ranges; can be gamed
Vendor quotes / market data External prices for packages Reality-checked Scope clarity and validity period critical
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%":
Define the budget / cost baseline as authorised, structured money for scope.
Use CBS–WBS language to show control accounts map to work.
Classify relevant cost types (fixed/variable, direct/indirect) to explain what will actually change.
Separate base estimate , contingency , and management reserve conceptually.
Outline build steps and the need for authority and time-phasing.
Name suitable estimating approaches given information maturity.
That structure answers LO22a and sets up earned value and financial control in the next section.