By Cassandra Mascarenhas, Product & Marketing Strategist, Projx - a project delivery platform for leading client-side property development and capital works teams
Published on September 6, 2026
A capital works project typically involves four distinct cost roles: the Quantity Surveyor (your client-side cost advisor), the Estimator (the builder's pricing specialist), the Cost Controller (delivery-stage tracking), and the Project Accountant (financial governance and compliance). Each serves a different function at a different stage of the project. Confusing them, or assuming one covers another's ground, creates real gaps in cost oversight.
If you're a property developer or capital works manager, understanding who does what helps you build the right team, ask better questions, and know when something is being missed.
The Quantity Surveyor (QS) sits on your side of the project. They're your cost planner and commercial advisor, engaged from the earliest feasibility stage through to final accounts.
The Australian Institute of Quantity Surveyors (AIQS) describes the QS as a professional working across cost estimating, cost planning, and contract administration. The modern QS isn't just measuring quantities. They're helping you understand what a project should cost, where the commercial risks sit, and whether the numbers you're being presented with are reasonable.
If you're a developer or asset owner, the QS is working for you. That's the most important thing to understand about the role.
Their involvement typically runs across the full project arc:
The QS and the numbers: A QS advising the client on a $20 million capital project might be reviewing a builder's progress claim and querying $180,000 in variations, because their job is to make sure you only pay for what was agreed. That's client-side cost management in practice.
The role has evolved. It's less about manual measurement and more about commercial judgment, particularly on capital works programs where scope changes constantly and the financial exposure is significant.
For a deeper look at how cost data flows from the QS through to client reporting throughout delivery, our blog on financial reporting in property development and capital works covers what structured reporting looks like at each stage.
The Estimator is the builder-side counterpart to the QS. Before a project gets to construction, the builder needs to price it. The person doing that pricing is the Estimator.
Where your QS is working out what a project should cost from your perspective, the Estimator is working out what it will cost the builder to deliver, and what margin to put on top.
Both roles often work from the same documents: the same drawings, the same specifications, the same scope. But they're asking different questions. The QS is asking: "How much do we think this will cost based on past projects?" The Estimator is asking: "What will be our price to deliver the works based on current subcontractor pricing?"
As an asset owner or developer, you won't manage the Estimator directly as they work for the builder or head contractor. But understanding what they do helps you interpret a tender. When a QS tells you a bid looks high, or flags that a contractor has priced a provisional sum conservatively, they're applying the same lens the Estimator used - just from the other side.
Similarly, during construction, the estimator for the Head Contractor often prepares variation orders which then gets reviewed by the Quantity Surveyor on behalf of the Client/Principal.
The Cost Controller enters the picture during project delivery. Their job is to track what's being spent against what was budgeted, identify variances early, and give the project team the information they need to respond before a cost problem becomes a cost crisis.
This role is typically found on larger or more complex capital works programs such as infrastructure projects, multi-stage developments and government capital programs, where the scale and financial complexity warrant a dedicated person monitoring the numbers in real time. On smaller projects, the QS or project manager often absorbs this function.
The Cost Controller:
The Cost Controller tracks not just "what have we spent?" but "where is this heading?" That forward-looking view is what makes the role valuable.
On programs where structured project cost controls are in place, the Cost Controller is usually the first person who knows when something is trending off track. The project manager might not know yet. The finance team definitely doesn't know yet. The Cost Controller does because they're watching the numbers week by week.
Cost planning vs cost control: Cost planning happens before construction - it's the QS's domain. Cost control happens during delivery - it's the Cost Controller's domain. They're sequential, not interchangeable. On well-run capital programs, both exist. On smaller projects, the QS often carries both.
The Project Accountant is the financial governance and compliance arm of the project. Where the QS and Cost Controller are focused on project cost management, the Project Accountant is focused on making sure the financial records meet corporate or government reporting requirements.
Like the Cost Controller, this role is most commonly found on larger projects with significant financial complexity, external funding obligations, or multiple stakeholders requiring formal financial reporting. On smaller capital works projects, these functions are typically handled by the organisation's finance team rather than a dedicated project accountant.
Their focus is the financial record of the project: invoices, payments, accruals, commitments, cash flow forecasts, and formal financial statements. They sit between the project delivery team and the finance function, translating project cost data into reporting that meets organisational accounting standards.
This matters particularly at the end of a project. When costs need to be capitalised, assets need to be classified, and the finance team needs a clean set of records to work from, the Project Accountant is the person who makes that handover possible.
As we covered in our article on fixed asset cost classification in capital works, getting cost records structured correctly during delivery is what makes that process clean rather than chaotic.
The QS and Cost Controller both work on the owner side, both deal with project costs, and both produce reports. But they're doing different things at different stages. Confusing them means you end up with gaps, either in how the budget was built, or in how it's being tracked during delivery.
The most common gap in practice: the QS prepares a strong pre-contract cost plan, then moves on to the next job once construction starts. Nobody picks up the cost control function. The project manager approves monthly invoices but doesn't have a current forecast. Costs drift. By the time the overrun is visible, it's too late to do much about it.
That gap is a single-project problem. On a capital program running 10 or 15 projects at once, it compounds. Even if each project has someone watching its numbers, the bigger question becomes: can you see across all of them? Which projects are tracking well? Which are burning through contingency? Where does the real financial risk sit across the portfolio?
Projx is built for owner-side and client-side project delivery teams - the same people these cost roles serve.
Projx gives QS firms, capital works managers, and development teams a structured environment where cost data is captured consistently - committed costs, forecasts, variations, contingency - across every project, in the same format. That means a Cost Controller running reports across a 10-project program gets comparable data, not a patchwork of different spreadsheet structures.
It's not just about the reports themselves. It's about the data integrity that makes those reports trustworthy. That's what you're getting: a structured dataset that means your cost roles can do their jobs, instead of spending half their time reconciling information that should already line up.
A Quantity Surveyor is your client-side cost advisor. They work across feasibility, cost planning, tender, and final accounts. A Cost Controller focuses specifically on the delivery stage, monitoring actual expenditure against budget and updating forecasts in real time. On well-resourced capital programs, both roles exist and hand off to each other. On smaller projects, the QS often absorbs the cost control function, but the two are distinct disciplines.
Cost planning happens before construction begins. It's the process of establishing a reliable budget based on design information, market conditions, and risk allowances. Cost control happens during delivery. It's the ongoing tracking of actual costs against that budget, updating forecasts, and flagging variances. The QS typically leads cost planning; the Cost Controller leads cost control. Both are essential to a well-run capital program.
A dedicated Cost Controller is most common on larger or more complex programs - typically infrastructure, multi-stage developments, or government capital programs where the scale and reporting obligations justify the role. On smaller projects, cost control is often absorbed by the QS or project manager. The threshold isn't a fixed dollar figure; it's about whether the financial complexity of the program warrants dedicated real-time monitoring.
A Project Accountant manages the financial records and compliance obligations for the project, such as invoices, payments, accruals, commitments, cash flow forecasts, and formal financial statements. Their focus is making sure the financial data meets corporate or government reporting requirements, and that cost information is properly structured for capitalisation and asset classification at project completion. The role is most common on larger projects with significant external reporting obligations.
On a well-structured capital works program, cost management is typically shared across roles: the QS manages cost planning and commercial oversight, the Cost Controller tracks actuals and forecasts during delivery, and the Project Accountant handles financial governance and compliance. On smaller programs, these functions are often carried by fewer people — sometimes just a QS and a project manager. What matters is that each function is being performed, regardless of how many roles cover it.
For more on how Projx supports client-side project delivery teams across property development and capital works programs, see how owner-side teams use Projx
Last updated on September 6, 2026
© 2026 Copyright. All Rights Reserved.
