In property development and capital works projects, the terms“committed cost” and “agreed cost” are used interchangeably.

But, they shouldn’t be.

For example - it’s possible to have works be committed priorto costs being agreed and vice versa.

Confusing these terms can cause financial mismanagement, budget blindspots and awkward conversations.

In this article, we explain why the best client-side project teamsmake the distinction between a commitment and an agreement, and howthis improves their cost control and reporting.

‍

What are Committed Costs?

In the property and construction industry, ‘committed works’ iswhen the Client instructs a Vendor to do something - whether that’sproviding a good or service.

A committed cost is the cost associated with those works.

The instruction from the Client to the Vendor can be the form of:

• A signed contract
• A Superintendent’s Direction
• A Purchase Order
• An Email Confirmation
• Or sometimes just a “go ahead” on site even before all paperwork has been finalised

Once the works are committed, the Client may be legally obligated topay the costs associated with the works, regardless of whether theworks are carried out or not. That’s because the Vendor may beacting on the representations and might be out of pocket if theClient reneges.

In other words, committed costs are financial obligations the projecthas already taken on, even if the invoices haven’t landed yet.Think of it as: the money spoken for, whether or not it’sactually left the bank account.

“But sometimes, works can be committed without costs beingsubmitted be the vendor”.

Fair point - we’ll get to this in a bit.

But first…

‍

What are Agreed Costs?

The best way to understand an agreed cost is to first understand the“cost journey”. These are the ‘steps’ (or cost positions) aparticular cost goes through before becoming agreed. The costpositions are:

• Anticipated Cost: this is an estimate or forecast of how much the works might cost
• Submitted Cost: this is the costs issued by the vendor for the works
• Assessed Cost: this is the cost considered ‘fair and reasonable’ by the Project Manager or Quantity Surveyor
• Agreed Cost: this is the final cost agreed between the Client and Vendor for the works (sometimes after a bit of argy-bargy).

Yay! Our cost has made it all the way along its journey. It’s gonethrough all the proper checks, assessments, recommendations,endorsements, etc., and is ready to be paid to the Vendor once theworks are completed.

But until someone instructs the Vendor or raises a PO, it’s justremains as an agreed cost without any financial obligation to pay.

‍

Why the Distinction Matters

The property and construction industry is unique in that they allowfor the following scenarios:

• Works are committed, without a cost being submitted: For example, the Head Contractor identifies some asbestos behind a switchboard which needs to be removed. They are unable to provide a cost for the removal works. To avoid delaying the works, the Superintendent directs the works on the Clients’ instruction.
• Works are committed, but submitted costs are not agreed: For example, the Head Contractor submits a cost to remove the asbestos, and is subsequently instructed to proceed with the removal works under a Superintendent’s Direction with “costs to be agreed”.
• Submitted costs are agreed, but works are not committed: For example, the Client agrees that the cost to remove the asbestos is reasonable but decides not to do it now.

Given these are common scenarios, project managers and quantitysurveyors should be given the option to classify works so they canaccurately track and report costs on projects.

Clear separation gives project stakeholders a clearer picture of theproject’s financial position:

• Clients can spot committed costs still waiting for approval and push them through the chain.
• Project Managers can see approved costs not yet committed and follow up any instructions.
• Finance teams can avoid overstating budgets by only allocating what’s truly approved.

It’s the difference between thinking you have money to spendand knowing exactly where the money’s going.

‍

How Projx Clears It Up

Legacy systems like spreadsheets don’t cater for this distinctionso project teams consider committed costs and agreed as aone-and-the-same. These legacy systems blur committed and agreedcosts into the same bucket, which makes cost reporting - well,blurry.

Other cost reporting systems do not allow for costs to be classifieddifferently.

Projx does.

Projx introduces a clear cost journey: Anticipated→ Submitted → Assessed → Agreed.

Furthermore, Projx provides a toggle for costs to be classified aseither Committed or Uncommitted.

It’s not one or the other with Projx - it’s both.

That means project teams can:

• Instantly filter to see all committed costs awaiting approval.
• Track where each cost sits in its lifecycle, so nothing slips through the cracks.

The result? A transparent, flexible cost management process thatshows who approved what, when it was committed, and what still needsaction.

‍

‍

‍The Payoff

Committed and agreed costs might sound similar, but treating them asone and the same is a recipe for confusion.

• Committed = what vendors have been instructed to deliver
• Agreed = the approved costs with the associated works

When projects keep those states distinct, clients, PMs, and financeteams all get clearer insights, smoother workflows, and strongerbudget control.

And with Projx making that distinction front and centre, teamsfinally get what they’ve been missing: a cost view that reflectsreal-world project dynamics, not just tidy accountingcategories.