A project can be within budget today and still be heading toward a significant cost overrun at completion. Current expenditure only shows what has happened so far; it does not reveal whether enough work has been completed for that spending or what the remaining work is likely to cost.
Effective cost control therefore looks both backward and forward. Project managers compare the approved baseline with actual costs and progress, investigate significant variances, update forecasts and take action before financial problems become harder to recover.
The basic cycle is Baseline → Track → Compare → Analyse → Forecast → Act → Control change.
Cost control in project management is the ongoing process of monitoring project expenditure and performance against an approved cost baseline, analysing significant variances, forecasting the expected final cost and taking corrective action where necessary.
It is not simply an exercise in spending less. Reducing expenditure can damage the project if the saving compromises required scope, quality or delivery.
Likewise, a project being below its planned expenditure does not automatically indicate strong cost performance. If only 40% of the work has been completed when 60% was scheduled, lower expenditure may simply reflect slower progress.
The Project Management Institute's Earned Value Management standard describes EVM as a methodology for integrating scope, schedule and resources, objectively measuring project performance and forecasting project outcomes.
The broader purpose of cost control is therefore to understand whether project resources are producing the expected result and whether the remaining work can still be delivered within an acceptable financial outcome.
.jpg)
These terms are closely related, but they answer different questions.
The important distinction is:
Budgeting establishes the financial reference point. Cost control uses that reference point during execution.
HAL's guide to Budgeting in Accounting explains the wider relationship between budgets, actual results, forecasts and variance analysis. Project cost control begins once the authorised project plan is being executed and management needs to know whether financial performance remains acceptable.
A cost baseline is the approved, time-phased financial reference used to evaluate project cost performance.
It should be connected with the project's authorised scope, work breakdown structure, schedule and budget. If those elements are poorly aligned, even accurate cost records can produce misleading performance reports.
The original estimate and the cost baseline are also not necessarily the same thing. An estimate forecasts expected cost during planning, while the approved baseline becomes the formal reference against which project performance is measured.
PMI's current EVM guidance stresses that performance measures are only useful when the underlying scope, WBS, schedule and budget are sound.
That is why cost control cannot compensate completely for a weak project baseline.
Looking only at invoices already posted to accounting gives an incomplete view of project exposure.
A useful cost-control system distinguishes several measures:
Budget is the authorised financial plan.
Actual cost is expenditure already incurred.
Committed cost can include approved purchase orders, contracts or other commitments that may not yet have become invoices.
Estimate to Complete (ETC) is the current forecast of what the remaining authorised work is expected to cost.
Suppose a project has a SAR 1 million budget and has spent only SAR 400,000. That can look comfortable until management discovers another SAR 250,000 is committed and the remaining work is forecast to require SAR 450,000.
Cost control therefore needs to look forward as well as backward.
Care is also required to avoid double-counting. A commitment should not simply be added to ETC if the remaining forecast already includes that committed expenditure.
Start with an authorised and usable reference point.
The cost structure should align with the project's scope, work packages and schedule closely enough that managers can determine where a variance is occurring. If the project budget exists only as one total figure, meaningful diagnosis becomes difficult.
Actual costs should be recorded quickly enough for management to act on them.
Depending on the project, they can include labour, materials, contractors, equipment, travel, software, licences and other project-attributable expenditure.
Delayed cost reporting creates delayed control. Discovering an overrun several reporting periods after the underlying work occurred leaves fewer options for correction.
A purchase order can create real project exposure before the supplier sends an invoice.
Tracking commitments helps managers understand how much of the remaining budget has effectively already been allocated. This becomes especially important on procurement-heavy or subcontractor-heavy projects.
Cost has limited meaning without progress.
If a project has spent 50% of its budget, management also needs to know how much of the planned work has actually been achieved.
This relationship between expenditure and accomplished work is the foundation of Earned Value Management.
Cost reviews should examine performance at useful levels rather than only the total project value.
Teams may compare current and cumulative costs by:
A project can appear on budget overall while one major work package is materially overspending and another has simply not started yet.
A number showing a variance does not explain why the variance occurred.
Possible causes include underestimated effort, supplier price changes, lower productivity, rework, scope changes, incorrect cost coding, schedule delay or timing differences between work and invoice recognition.
Management should identify the cause before deciding on corrective action.
The key forward-looking question is:
Given what we know today, what will this project cost when it finishes?
That requires an updated view of the cost still required to complete the remaining authorised scope.
A forecast that never changes despite changing project conditions is unlikely to remain useful.
Possible responses can include changing resource allocation, negotiating procurement, addressing rework, changing execution sequencing, resolving risks or formally evaluating a proposed scope change.
Cost control does not mean rewriting the baseline whenever results are unfavorable. If the authorised project itself changes, the baseline can be changed through the project's formal change-control process.
A basic budget-versus-actual comparison identifies whether expenditure differs from what was planned for a period or cost category.
Earned Value Management goes further by considering the value of the work actually completed.
In EVM:
Cost Variance (CV) = Earned Value (EV) − Actual Cost (AC)
A positive CV indicates that the budgeted value of completed work is greater than the cost incurred. A negative CV indicates that the project has spent more than the budgeted value of the work completed.
This is different from ordinary budget-versus-actual variance.
A project can spend less than originally planned while still have poor EVM cost performance if it has accomplished substantially less work than planned.
Earned Value Management connects three fundamental project measures.
PMI's August 2026 guide, Earned Value Management: A Guide to Reading the Numbers, emphasises that the real value of EVM comes from interpreting these figures rather than treating the formulas as an accounting exercise.
One commonly used measure is the Cost Performance Index:
CPI = EV ÷ AC
A CPI above 1.00 indicates favourable cost efficiency relative to the baseline. A CPI of 1.00 indicates alignment, while a CPI below 1.00 signals that the project is spending more than the budgeted value being earned.
For example, if:
EV = SAR 360,000
AC = SAR 450,000
then:
CPI = 360,000 ÷ 450,000 = 0.80
The project is currently earning SAR 0.80 of budgeted value for every SAR 1.00 of actual cost.
CPI identifies a performance signal. It does not tell management why the problem exists, so the underlying work still needs investigation.
Cost control becomes much more useful when it moves from explaining historical performance to estimating the final financial outcome.
Two important terms are:
Estimate to Complete (ETC): the current estimate of what the remaining authorised work will cost.
Estimate at Completion (EAC): the current estimate of the project's total cost when finished.
AACE International's Recommended Practice 80R-13 on Estimate at Completion defines the core relationship as:
EAC = AC + ETC
This approach allows the project team to use actual expenditure to date plus a fresh assessment of the remaining work.
EVM can also provide performance-based forecasts. If the current cost efficiency is expected to continue, one commonly used relationship is:
EAC = BAC ÷ CPI
where BAC is Budget at Completion.
The formula should not be selected mechanically. If the conditions that caused past cost performance have changed, a detailed bottom-up ETC may provide a more useful forecast than simply extending the historical CPI.
Consider a project with a Budget at Completion of SAR 1,000,000.
At the current review date:
The cost variance is:
CV = EV − AC
SAR 450,000 − SAR 540,000 = −SAR 90,000
The project has therefore spent SAR 90,000 more than the budgeted value of the work completed.
Its CPI is:
CPI = EV ÷ AC
SAR 450,000 ÷ SAR 540,000 = 0.83
If that cost efficiency were expected to continue:
EAC ≈ BAC ÷ CPI
SAR 1,000,000 ÷ 0.83 ≈ SAR 1.20 million
That does not mean the project will inevitably cost SAR 1.20 million. It tells management that current performance points toward a material overrun if the underlying conditions continue.
The project manager should now investigate why costs are high, determine whether those causes will persist and prepare an updated ETC before deciding what corrective action is appropriate.
Not every project requires the same control method.
Budget-versus-actual analysis provides a straightforward view of recorded expenditure against plan. Commitment tracking adds visibility into expenditure that has been contracted but may not yet appear in actual costs.
Variance analysis helps identify where project performance differs from expectations, while trend analysis shows whether that performance is improving or deteriorating over several reporting periods.
Earned Value Management is useful where reliable progress measurement can be connected with scope, schedule and cost. ETC and EAC forecasting then shift attention from what has already happened toward the likely final outcome.
Change control prevents additional scope from entering the project financial plan without the corresponding decision and authorisation, while cost-to-complete reviews reassess the remaining work using the latest project conditions.
The right approach depends on project size, risk and available data. A small internal project may not need a formal EVMS, while a large capital programme may require substantially more rigorous controls.
Project teams should keep the major cost measures conceptually separate.
These measures should not be added together blindly.
For example, a supplier purchase order may already be included in the current ETC. Adding the same commitment again would overstate forecast project cost.
Clear reporting rules are therefore just as important as collecting the numbers themselves.
Scope and cost are closely connected.
A useful change process follows:
Change identified → Cost and schedule impact assessed → Approval decision → Baseline updated if authorised → Performance measured against revised baseline
The key principle is that the baseline changes because an authorised change has changed the plan, not because actual performance has become worse than expected.
If management simply increases the baseline every time the project overruns, the variance disappears from the report without the underlying performance improving.
Forecasts and baselines therefore serve different purposes.
The forecast can change whenever current expectations change. The baseline should change only through controlled authorisation.
A cost-control dashboard should focus on information that helps managers act.
Smaller projects may need only a subset of these measures. More metrics do not automatically create better cost control if nobody uses them to make decisions.
Cost problems can originate before execution or emerge as the project progresses.
Common causes include unrealistic original estimates, scope creep, uncontrolled changes, lower productivity, rework, supplier-price increases, excessive resource usage, schedule delay, poor procurement, untracked commitments and risk events.
Reporting errors can also create apparent cost problems. Incorrect coding may move expenditure into the wrong project or work package, while delayed invoices can temporarily make performance appear better than it really is.
Cost control cannot repair an unrealistic estimate by itself. Its value is in exposing emerging financial problems early enough for management to respond.
One of the most common mistakes is treating “under budget” as automatically positive.
A project can appear under budget simply because it is behind schedule and has not yet incurred the expenditure associated with work that should already have been completed.
Other mistakes include:
Effective cost control is less about producing more reports and more about identifying exceptions early enough to change the outcome.
✓ Approved baseline has been confirmed
✓ Scope and WBS align with the budget
✓ Actual costs are current
✓ Commitments are captured
✓ Costs are assigned to the correct work packages
✓ Progress is measured consistently
✓ Significant variances are investigated
✓ Estimate to Complete is current
✓ Estimate at Completion is reviewed regularly
✓ Pending changes remain visible
✓ Approved changes update the baseline correctly
✓ Corrective actions have named owners
✓ Cost risks are reviewed
✓ Forecast and baseline remain separate
✓ Material cost information reaches the right stakeholders
Cost control becomes harder when scope and schedules are maintained in one system, actual financial information in another and budgets or forecasts in separate spreadsheets.
HAL Project Management supports project organisation, scheduling, planning and project-stage visibility. HAL Accounting provides the accounting environment for financial transactions, supplier activity, receivables, purchase orders and reporting.
HAL's existing Budgeting in Accounting guide also describes how HAL's Budget Manager can compare budget values with actual income and expenditure for general budgets, Customer Jobs and Financial Centres.
These capabilities can support a more connected project-control environment, but software does not determine why a variance occurred or what management response is appropriate. HAL should also not be treated as a formal PMI-compliant Earned Value Management System unless that capability is explicitly established for the required use case.
For contractors specifically, HAL's separate Construction Cost Management guide covers procurement, subcontractors and other construction-specific cost-control issues in greater depth.
Effective project cost control connects the approved financial plan with what the project is actually accomplishing:
Baseline → Actuals and commitments → Progress → Variance → Forecast → Corrective action → Controlled change
The objective is not merely to explain where money has already gone. It is to identify whether current performance threatens the final project outcome while there is still time to respond.
HAL Project Management and HAL Accounting can help businesses bring project and financial information into a more connected operating environment. To explore how HAL could support your project-management and financial workflows, book a demo.
Cost control is the ongoing process of measuring project financial performance against an approved baseline, analysing significant differences, forecasting the likely final cost and taking action where necessary.
Cost management covers the broader lifecycle of estimating, budgeting and controlling project costs. Cost control is the execution-stage process of monitoring performance and influencing the financial outcome after a baseline has been approved.
In Earned Value Management, Cost Variance is calculated as CV = EV − AC. A negative value indicates that actual cost exceeds the budgeted value of the work completed.
A Cost Performance Index below 1.00 means the project is currently spending more than the budgeted value it is earning. The cause still needs to be investigated before corrective action is chosen.
Estimate at Completion, or EAC, is the current forecast of the project's total cost when all authorised work is finished.
The budget or BAC is the approved financial baseline. EAC is the project's latest forecast of what it is now expected to cost at completion.
There is no universal frequency. Reviews should reflect project size, pace, risk and reporting needs; fast-moving or financially sensitive projects may require more frequent monitoring than smaller, stable projects.
.jpg)
.jpg)