Sign in

Blog · Territory, capacity and quota planning · Finance and FP&A teams

Project cost management: estimate, budget and control

Connect project estimates, approved budgets, actual costs, and open commitments. Follow a worked project example with spreadsheet formulas, reconciliation checks, and clear review responsibilities.

The short answerProject cost management estimates the resources needed for an agreed scope, establishes an approved budget, and compares actual and expected spending with that baseline. Track costs by work package, include remaining commitments without double counting invoices, and update the cost to finish. Investigate forecast overruns while the team can still change the outcome.

Project cost management connects the estimate for an agreed scope, its approved budget, and the latest expected final cost. Compare actual spending, remaining commitments, and uncommitted work by work package so an overrun has a location, an explanation, and an owner.

A report showing actuals against the full budget is only a starting point. It can look comfortable while most of the budget is already committed or the work is behind schedule.

Define what the project must deliver

Start with the business scope and divide it into work packages that someone can own. For a warehouse change, these might be design, equipment, and launch. Use the same package codes in the estimate, budget workbook, purchasing export, and ledger extract.

Record the cost boundary: internal labor, supplier costs, freight, installation, taxes where applicable, and any agreed allocation of shared costs. State the currency, accounting basis, and reporting cutoff. Finance should resolve expense versus capitalization treatment outside the management summary.

Cost needs the context of delivery. The US Department of Energy describes earned value management as integrating cost, schedule, and technical scope. A basic cost report does not become an earned value system merely because it compares spending with budget; it still needs reliable information about work accomplished.

Put the recurring rules and responsibilities in a cost management plan. That document governs the comparison; the process here shows how to run it.

Estimate, challenge, and approve the baseline

Estimate each package from identifiable quantities and rates. Supplier quotes, internal labor hours, and installation assumptions should have dates and source references. For an estimating worksheet with quantity in B2 and unit rate in C2:

=B2*C2

Review the assumptions with the package owner. Separate known scope from uncertainty, document any allowance, and make clear which costs require a later decision. An unsupported lump sum cannot explain whether a later change comes from price, volume, or scope.

Once approved, save the baseline version and its approval date. Keep the original baseline, approved changes, and current approved budget distinguishable. A forecast is the team's latest expectation; it does not authorize additional spending or replace the approved budget.

Assign the baseline across reporting periods if the project needs a monthly spending comparison. A full-project budget should not be treated as the amount expected to have been spent at an interim cutoff.

Bring actuals and commitments to the same cutoff

Use a ledger or project-cost export for actuals, an open purchase-order report for remaining commitments, and the package owners' latest estimate for work not yet committed. Include document references so procurement and finance can investigate differences.

Aggregate each file separately before combining it at work-package level. In an Actuals sheet, assume project code is column A, work package B, posting date C, and cost amount D. With the selected project in J1, cutoff date in J2, and package code in A2:

=SUMIFS(Actuals!$D:$D,Actuals!$A:$A,$J$1,Actuals!$B:$B,$A2,Actuals!$C:$C,"<="&$J$2)

This returns cumulative actuals through the cutoff for that project and package. Microsoft's SUMIFS documentation explains the multiple-criteria summation used here. Covirage is not affiliated with Microsoft or Google.

Use the same cutoff and package codes for the commitment report. Confirm that its “open” balance excludes the portion already included in actuals or accruals. Do not add original purchase-order values to booked invoices.

Work the forecast by package

A US distributor reviews a warehouse project at its October cutoff. The following illustrative amounts are cumulative project figures in USD. Open commitments and uncommitted remaining work are separate, nonoverlapping amounts.

Forecast final cost = Actual costs + Remaining open commitments + Uncommitted cost to finish

Forecast overrun = Forecast final cost - Approved budget

Place the columns below in A through H:

Work package Budget (USD) Actual (USD) Open commitment (USD) Uncommitted remainder (USD) Forecast final (USD) Overrun (USD) Overrun / budget
Design 30,000 27,000 0 4,000 31,000 1,000 3.3%
Equipment 50,000 32,000 18,000 2,000 52,000 2,000 4.0%
Launch 20,000 8,000 5,000 9,000 22,000 2,000 10.0%
Total 100,000 67,000 23,000 15,000 105,000 5,000 5.0%

For row 2, calculate forecast, dollar overrun, and percentage overrun:

=SUM(C2:E2)
=F2-B2
=IF(B2>0,G2/B2,"Check budget")

Copy down and calculate the total percentage from total overrun divided by total budget. Percentages are displayed to one decimal place using unrounded calculations.

Actuals of $67,000 alone do not show the exposure. Adding $23,000 of remaining commitments and $15,000 of uncommitted work gives a $105,000 forecast, or $5,000 above the $100,000 budget.

The checks are explicit: package budgets sum to $100,000; actuals to $67,000; commitments to $23,000; and uncommitted work to $15,000. The forecast also reconciles as $100,000 + $5,000 = $105,000. Each source total must tie to the project-filtered export before the team interprets the variance.

Turn the differences into decisions

Ask each owner what changed: scope, supplier price, labor effort, timing, or an omitted assumption. Design needs an explanation for its remaining work; equipment needs confirmation of the extra uncommitted cost; launch has the largest percentage overrun. These are investigation questions, not proof of poor execution.

Agree an action, an owner, and a review date. Possible actions include challenging a quote, changing an unapproved scope item, or updating an estimate after new information. Cost control examples examine individual interventions; the project management report shows how to communicate the overall position. Apply RAG status only against documented thresholds.

Where it goes wrong

  • Double counting commitments. Original order value plus actual invoices overstates the forecast.
  • Missing accruals. Work received but not posted makes actual spending look artificially low.
  • Replacing the baseline. Overwriting budget with forecast removes the comparison the report exists to make.
  • Treating delay as savings. Lower spending may mean less work has been completed.
  • Unmapped costs. A project total can reconcile while costs sit in the wrong work packages; review exceptions as well as totals.

Compare your project files in Covirage

Upload your approved budget, project-cost export, and remaining commitment schedule, or bring a Google Sheet. Covirage maps the columns, its tools compute and check the comparisons, and the external AI model explains the differences with every figure traced to its rows. Create a free Covirage account, which takes about a minute, then set up your business and bring a sample of your own data.

See project cost control for the supporting business use.

Questions people ask

What are the main steps in project cost management?

Define the scope and work packages, estimate their costs, approve a budget, record actual spending, and update the remaining cost. Review differences with the people responsible for delivery and document approved changes rather than silently replacing the original budget.

Are purchase orders the same as actual project costs?

No. A purchase order records an agreed purchase, while actual costs reflect the accounting treatment of work or goods received. Use the remaining open commitment alongside actuals, with accruals and invoices reconciled so the same cost does not appear twice.

Does spending below budget mean a project is healthy?

Not necessarily. Work may be delayed, invoices may be missing, or a large purchase may still be open. Compare spending with the work completed and the latest cost to finish before treating an apparent underspend as a saving.