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.
In this handbook article
- Why Cost Management Is the Make-or-Break Discipline
- What Is Project Cost Management?
- How It Works: The Cost Management Lifecycle
- Phase 1 — Plan Cost Management
- Phase 2 — Estimate Costs
- Phase 3 — Determine Budget
- Phase 4 — Control Costs
- The Earned Value Toolkit
- Worked Example
- The Pitfalls: Where Cost Management Goes Wrong
- Key Takeaways
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.
Relationship details
| From | Relationship | To |
|---|---|---|
| Uncertainty (High) | leads to | U2 |
| U2 | leads to | U3 |
| U3 | leads to | U4 |
| U4 | leads to | Uncertainty (Low) |
| Information Possessed (Low) | leads to | I2 |
| I2 | leads to | I3 |
| I3 | leads to | I4 |
| I4 | leads to | Information Possessed (High) |
| U3 | leads to | Key Decision Points |
| I3 | leads to | Key Decision Points |
| Time → | leads to | U2 |
| Level → | leads to | Uncertainty (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.
Relationship details
| From | Relationship | To |
|---|---|---|
| Activity Cost Estimates | leads to | Cost Aggregation |
| Cost Aggregation | leads to | Work Package Budgets |
| Work Package Budgets | leads to | Control Account Budgets |
| Control Account Budgets | leads to | Project Cost Baseline |
| Reserve Analysis | leads to | Project Cost Baseline |
| Management Reserves | leads to | Total Project Budget |
| Project Cost Baseline | leads to | Total 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:
A negative CV means the project is over budget — you have spent more than the value of the work completed.
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
$100 \quad \text{(10% over budget)}$$
$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.
| Category | PV (Planned Value | EV (Earned Value | AC (Actual Cost |
|---|---|---|---|
| Week 1 | 250 | 200 | 300 |
| Week 2 | 500 | 450 | 600 |
| Week 3 | 750 | 800 | 900 |
| Week 4 | 1000 | — | — |
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.
