KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesMastering Project Cost ManagementProject Delivery · Principles of Project ManagementLesson 22/58← PrevNext →
GuidePublished 13 Aug 20267 min readBy Kevin Joginproject managementproject deliveryprinciples of project managementcost
On this page

Ask about this page

KEVOS AIMastering Project Cost Management

KEVOS knowledge first · trusted web sources when needed

Home/ Project Delivery/ Principles of Project Management

KEVOS® Project Delivery Handbook

Mastering Project Cost Management

Why Cost Management Is the Make-or-Break Discipline A practical KEVOS handbook for project delivery teams.

7 min read1,422 words Guide 22 of 57Reviewed 2026-08-13
In this handbook article
  1. Why Cost Management Is the Make-or-Break Discipline
  2. What Is Project Cost Management?
  3. How It Works: The Cost Management Lifecycle
  4. Phase 1 — Plan Cost Management
  5. Phase 2 — Estimate Costs
  6. Phase 3 — Determine Budget
  7. Phase 4 — Control Costs
  8. The Earned Value Toolkit
  9. Worked Example
  10. The Pitfalls: Where Cost Management Goes Wrong
  11. Key Takeaways

Source and edition context

Source basis: This handbook article is adapted from the supplied file(s): 23. Mastering Project Cost Management.md.

Interpretation rule: Named scenarios, schedules, percentages, monetary values and thresholds are source examples or illustrative proposals unless an identified authority, contract or approved baseline makes them mandatory.

PMI edition context: The supplied notes primarily teach fifth- and sixth-edition process groups and knowledge areas. PMI currently publishes the PMBOK® Guide—Eighth Edition, which retains the principles and performance-domain foundation while presenting evolved, non-prescriptive process guidance. Historical counts in this article remain for source/course context, not as a claim about the current edition.

Why Cost Management Is the Make-or-Break Discipline

Every failed project tells a cost story. Sometimes it is the story of an estimate that was wishful thinking dressed in a spreadsheet. Other times it is the story of a budget that existed on paper but was never connected to the rhythm of real expenditure.

Derek Lidow, reflecting on years of project failures at International Rectifier, identified resource allocation as one of his five critical "Ducks" that must be aligned before any project launches. His argument is stark: projects frequently fail not because the team lacked talent or commitment, but because the necessary resources were never secured — or worse, were promised and then quietly redirected elsewhere. Sponsors, he observed, routinely "make unrealistic promises and overcommit resources because they believe that success springs from doing more with less." The predictable result is cost overrun, schedule collapse, and team demoralisation.

The PMBOK framework addresses this reality head-on by structuring cost management into four disciplined phases. Understanding these phases — and the human behaviours that undermine them — is the difference between a project that delivers value and one that haemorrhages money.


What Is Project Cost Management?

Project cost management encompasses the processes required to plan, estimate, budget, finance, fund, manage, and control costs so that the project can be completed within the approved budget.

The PMBOK identifies four core processes:

Process Phase Purpose
Plan Cost Management Organising & Preparing Establish policies, procedures, and documentation for managing costs
Estimate Costs Organising & Preparing Develop approximations of monetary resources needed
Determine Budget Organising & Preparing Aggregate estimated costs to establish an authorised cost baseline
Control Costs Carrying Out the Work Monitor project status, update costs, and manage changes to the baseline

Core Principle: A cost estimate is not a price. Estimating asks "how much will this cost us to deliver?" Pricing asks "how much will we charge?" Confusing the two is a common and dangerous error.


How It Works: The Cost Management Lifecycle

Phase 1 — Plan Cost Management

Before a single dollar is estimated, the project team must agree on how costs will be managed. The Cost Management Plan establishes the rules of the game: what estimating methods will be used, how budgets will be structured, what variance thresholds trigger corrective action, and how changes are formally controlled.

Inputs include the Project Management Plan, Project Charter, enterprise environmental factors, and organisational process assets. The outputs flow into a single, governing document — the Cost Management Plan.

Phase 2 — Estimate Costs

Cost estimating is inherently uncertain. The PMBOK acknowledges this by recognising different levels of accuracy tied to different project phases:

Project Phase Estimate Type Typical Accuracy
Concept Order-of-magnitude ±30%
Concept Preliminary ±20%
Development (early activities) Definitive ±5%
Development (later activities) Definitive ±10%
Post-tender Fixed price Contractually bound

The progression from rough to refined is not optional — it reflects the reality that uncertainty decreases as information increases. Graham Winch's research on construction projects models this beautifully: at inception, virtually nothing is known about the completed asset; at handover, virtually everything is known. The project process itself is fundamentally an information flow that converts uncertainty into certainty over time.

Process and relationship map
Time →
Level →
Uncertainty (High)
Uncertainty (Low)
Information Possessed (Low)
Information Possessed (High)
Key Decision Points
Relationship details
FromRelationshipTo
Uncertainty (High)leads toU2
U2leads toU3
U3leads toU4
U4leads toUncertainty (Low)
Information Possessed (Low)leads toI2
I2leads toI3
I3leads toI4
I4leads toInformation Possessed (High)
U3leads toKey Decision Points
I3leads toKey Decision Points
Time →leads toU2
Level →leads toUncertainty (High)

Key estimating techniques include:

  • Analogous Estimating — using data from similar past projects as the basis for the current estimate
  • Parametric Estimating — multiplying a known quantity by a historical cost rate (e.g., cost per square metre)
  • Bottom-Up Estimating — estimating each work package individually and aggregating upward through the WBS
  • Vendor Bid Analysis — using competitive quotations to validate internal estimates

Phase 3 — Determine Budget

Budgeting transforms the cost estimate into an authorised cost baseline — the time-phased spending plan against which all future performance is measured.

Process and relationship map
Activity Cost Estimates
Cost Aggregation
Work Package Budgets
Control Account Budgets
Project Cost Baseline
Reserve Analysis
Management Reserves
Total Project Budget
Relationship details
FromRelationshipTo
Activity Cost Estimatesleads toCost Aggregation
Cost Aggregationleads toWork Package Budgets
Work Package Budgetsleads toControl Account Budgets
Control Account Budgetsleads toProject Cost Baseline
Reserve Analysisleads toProject Cost Baseline
Management Reservesleads toTotal Project Budget
Project Cost Baselineleads toTotal Project Budget

Key Distinction: The cost baseline includes contingency reserves allocated to known risks. The total project budget adds management reserves for unknown risks. Understanding this layered structure is essential for honest reporting.

Cost budgets must be time-phased to reflect the expected cash flow profile of the project. This produces the characteristic S-curve — slow spending during early planning, accelerating through implementation, and tapering during finalisation.

Phase 4 — Control Costs

Cost control is where planning meets reality. It involves comparing actual expenditure against the baseline, analysing variances, and taking corrective action when the project drifts.

The most powerful tool in this phase is Earned Value Analysis (EVA).


The Earned Value Toolkit

Earned Value Analysis rests on three fundamental measurements:

Metric Full Name What It Measures
EV (BCWP) Budgeted Cost of Work Performed Value of work actually completed
PV (BCWS) Budgeted Cost of Work Scheduled Value of work planned to be completed by now
AC (ACWP) Actual Cost of Work Performed Actual money spent on work completed

From these three values, two critical variance indicators emerge:

CV=EV−ACCV = EV - AC

A negative CV means the project is over budget — you have spent more than the value of the work completed.

SV=EV−PVSV = EV - PV

A negative SV means the project is behind schedule — you have completed less work than planned.

Worked Example

Consider a task with a 4-week duration and a $1,000 budget. At the end of Week 3:

  • 80% of work is complete → EV = $800
  • 75% of the schedule has elapsed → PV = $750
  • Actual spend is $900 → AC = $900

$CV=800−900=−CV = 800 - 900 = -100 \quad \text{(10% over budget)}$$

$SV=800−750=+SV = 800 - 750 = +50 \quad \text{(ahead of schedule)}$$

The project is delivering work faster than planned but spending too much to do it. This is a classic pattern that demands investigation — often the root cause is overtime, premium material procurement, or scope creep absorbed without formal change control.

Earned Value Analysis — Week 3 Snapshot
CategoryPV (Planned ValueEV (Earned ValueAC (Actual Cost
Week 1250200300
Week 2500450600
Week 3750800900
Week 41000——

The Pitfalls: Where Cost Management Goes Wrong

1. Confusing accuracy with precision. A budget calculated to the nearest cent from a ±30% estimate is precisely wrong. Match the level of detail to the level of certainty.

2. Ignoring lifecycle costs. The cheapest construction option may carry the highest maintenance burden over 30 years. As the PMBOK notes, extra design effort that increases project costs may generate substantial operations savings — but only if the project manager is willing to advocate for this trade-off.

3. Treating the budget as fixed from day one. Lidow's resource prioritisation model reminds us that only critical projects have truly fixed objectives and timing. For important projects, either objectives or timing are variable. For desirable projects, all elements are variable. Budgets must reflect this reality.

4. Failing to time-phase the budget. A lump-sum budget tells you nothing about cash flow. Without a time-phased baseline, earned value analysis is impossible and variance detection is delayed until it is too late to act.

5. No formal change control. Scope changes that are absorbed informally — without adjusting the budget baseline — guarantee a negative cost variance at completion. Every approved change must flow through to the cost baseline.


Key Takeaways

  • Project cost management spans four processes: Plan, Estimate, Budget, and Control.
  • Estimate accuracy improves as the project progresses from concept (±30%) to detailed design (±5%).
  • The cost baseline is time-phased and excludes management reserves; the total project budget includes them.
  • Earned Value Analysis uses three measurements (EV, PV, AC) to derive cost and schedule variance in real time.
  • Cost management is inseparable from resource management — Lidow's Duck Alignment Theory reminds us that resources must be secured before work begins, not wished into existence after commitments are made.
  • Winch's information flow model explains why estimates become more accurate over time: certainty replaces uncertainty as the project progresses.

Continue learning

Execution Monitoring And ControlMonitoring and Controlling Projects11 min readLifecycle HandbookOrganising and Preparing the Project11 min readFrameworks Processes And ControlsThe Ten Project Management Knowledge Areas9 min readLifecycle HandbookFoundations of Project Management9 min read

Prepared for the KEVOS® Knowledge Library. Apply the governing contract, approved project method and current standards to live work.

Continue learning

Project Scheduling, Gantt Charts and the Critical PathGuide · Principles of Project ManagementNEXT LESSON →Planning Project QualityGuide · Principles of Project ManagementMastering the Work Breakdown StructureGuide · Principles of Project ManagementDeveloping a Project Human Resource PlanGuide · Principles of Project Management
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®