Cost control · Software category
Construction cost tracking software,
and what separates it from accounting.
Cost tracking software exists to answer a question your ledger cannot, which is where this job is heading while you can still change it. This page covers what the category does, the real difference between accounting-level cost visibility and live job cost control, the six things worth looking for, the questions to ask a provider, the honest limits, and how VIABUILD holds budget against committed against actual on every job.
01 / The direct answer
What construction cost tracking software does
Construction cost tracking software takes the budget your job was priced at, records what you have committed through purchase orders and what suppliers have actually invoiced, compares the three per cost code, and carries that forward into a view of where the job will finish. Construction cost management software and job costing software name the same category, and cost tracking software for construction is the same thing again with the words reordered.
The reason the category exists as something distinct from accounting is timing. A ledger is accurate about what has been billed, and billing lags the decision that caused it by weeks. Cost control is about the window in which a number can still be influenced, which means counting a commitment on the day the order is placed. The reference for the discipline itself is cost control, and it works with or without software. This page is about the software category, which is a separate question.
One neighbouring category is worth naming so you can tell the two apart while shortlisting. Cost control looks forwards and is judged on how early it warns you. Job costing looks backwards and downwards, attributing every dollar to the job that caused it accurately enough to reconcile against the ledger, and it is judged on whether the accountant accepts it. Most products lean one way. That side is covered on job costing software.
02 / The distinction
Accounting cost visibility and live job cost control
This is the decision underneath most searches in this category, because a builder who already has tracking categories in their accounting system is reasonably asking what else there is to buy. Six differences that matter.
The ledger tells you what was billed
Accounting software is complete, accurate and behind. It records the invoices that have arrived and been coded. On a build that runs for nine months, the invoice for a decision made in March lands in May, so the ledger is describing a job you can no longer change.
Cost control tells you what you are exposed to
A purchase order is a commitment. The money is spent in every sense that matters the moment the order is placed, weeks before an invoice exists. A cost position that only counts invoices systematically understates where the job actually sits, and it understates it most at the point where a decision would help.
The ledger is organised for tax
Accounts are structured by account code and reporting period because that is what they are for. Job cost is structured by cost code and work package, per job, because that is the shape a builder makes decisions in. Tracking categories help, but they are a reporting overlay, not a job cost structure.
Cost control compares against a budget
The point is not the number, it is the gap. Cost tracking software exists to hold the estimate you won on next to what has been committed and billed, and to make the difference visible per line while the line can still be influenced.
The ledger looks backwards, control looks forwards
The question a builder actually needs answered is where this job will finish, not where it has been. That requires cost to complete on the remaining work and a forecast final cost, which are estimates, not records, and no accounting system produces them.
They are not competitors
A builder needs both. The ledger is the source of truth for what has been billed and paid, the statutory record, and the thing an accountant works in. Cost tracking software is the operating view of the job. The useful arrangement is that they connect, not that one replaces the other.
03 / Before you buy
Six things to look for
All six are testable in a trial on a real job. The second one, committed cost captured at the purchase order, is the one that most reliably separates the category from job-coded accounting.
The budget arrives from the estimate
If the job budget has to be re-keyed from an estimate that lives somewhere else, it will be entered once and never reconciled again, and every later comparison is against a number nobody trusts. Ask how the estimate becomes the budget, and what happens when the estimate is revised before contract.
Committed cost captured at the purchase order
The single most important behaviour in the category. Commitment happens when the order is placed, not when the invoice arrives, so a system that only counts invoices is telling you where the job was, not where it is. If a product describes committed cost vaguely, ask exactly which event moves that column.
Cost to complete on the remaining work
Budget minus spent is arithmetic, not a forecast, and it is wrong on every line where the remaining work is not proportional to the remaining budget. Real cost to complete asks what finishing the rest will cost. Ask whether the tool supports a judged figure per line and who is expected to maintain it.
A forecast final cost you can act on
Committed plus actual plus cost to complete gives a forecast of where the job lands, which is the number that decides whether to chase a variation or change a supplier. A tool that stops at budget versus actual leaves the most useful figure to a spreadsheet.
Variance surfaced without being asked
The failure mode of every cost report is that it is correct and unread. Alerts on drift, at a threshold you set, turn cost control from a monthly ritual into something that interrupts you when it matters. Ask what triggers a notification and who receives it.
Cost codes that match how you actually price
Your estimate, your purchase orders, your invoice coding and your reporting all have to share one structure, or the comparison is between different things. Ask whether you can bring your own cost code structure, and whether changing it later breaks history on live jobs.
One structural point sits behind all six. A cost position is assembled from the estimate, the purchase orders, the supplier invoices and the approved variations, so a cost tracking tool is only as current as its connection to those four. A standalone cost tracker gives you a good structure to type numbers into, and the typing is the part that stops happening in March. A cost module inside the system that already holds the estimate, the orders and the invoice coding reads them directly. Decide which of those you want before comparing feature lists, because it determines whether the numbers stay current after the first busy month.
04 / The conversation
Questions worth asking a provider
Six questions with specific answers. The first one is the most diagnostic in the whole category, so ask it early and watch the demonstration rather than accept the description.
- 01
Which event moves a cost from committed to actual
Ask for the precise sequence, purchase order raised, goods received, invoice received, invoice matched, invoice approved, bill posted. Watch it happen with real documents. This one answer tells you more about whether a tool does job cost control or just job-coded accounting than any feature list will.
- 02
Show me a job where the forecast changed this week
Not a demo dataset built to look tidy. Ask what the forecast final cost was seven days ago, what it is now, and what caused the move. If the product cannot answer that, the forecast is a static field someone types in rather than a number the system maintains.
- 03
Where do the actuals come from and who codes them
Supplier invoices have to reach the right job and the right cost code, and that job is either automated, done by your admin, or done by your bookkeeper in a different system entirely. Find out which, because that labour is the real ongoing cost of cost tracking and it rarely appears in the subscription price.
- 04
How does this sit alongside my accounting system
Whether costs flow one way, both ways, or not at all, and what your bookkeeper has to change. If the answer is that you enter bills twice, you have bought a reconciliation job. If it is a real integration, ask specifically what syncs and what does not.
- 05
What happens when a variation changes the budget
A budget that cannot move as approved variations are added stops matching the contract by the third month, and the variance reporting on top of it becomes noise. Ask how an approved variation adjusts the budget, and whether the original estimate stays visible underneath as a baseline.
- 06
What is the total cost and can I get my job cost history out
Price the shape you actually have, per user, per job and per active project produce very different bills for a builder with six live jobs and four office staff. Then ask what exports, in what format. Historic job cost is the raw material of your next estimate, so it is worth more to you than to anyone else.
05 / Honest limits
What cost tracking software cannot do
Four limits, and being clear about them changes what you expect from an implementation.
It cannot fix a bad estimate. Cost tracking compares against a budget, and if the budget was optimistic at tender then the software will report accurately and early that the job is losing money. That is worth knowing, but the cause sits upstream in estimating and the handover into the budget, not in the tracking tool. It cannot capture what is not entered. Committed cost exists only if purchase orders are genuinely raised in the system before the order is placed, and that habit is the real implementation project. A product with excellent commitment tracking and a team that still orders by text message produces the same invoice-only picture as a spreadsheet.
It cannot forecast without judgement. Cost to complete is an estimate about work not yet done, and the automatic default of budget minus spent is wrong precisely on the lines where a builder needs it to be right. Software maintains the structure and the arithmetic; a person supplies the number. And it does not make the decision. A forecast four per cent over budget is the start of a conversation about scope, a variation or a supplier, and no tool has a view on which of those is correct. Cost tracking software is an instrument, and any vendor presenting it as a solution to margin erosion rather than an early warning of it is overclaiming.
06 / How VIABUILD does it
Cost control as one module, not a separate cost app
Cost control in VIABUILD is one module of the Construction Operating System for residential builders, on the same data model as the rest of the job. It holds three numbers live on every job, the budget that comes from the estimate you won on, what has been committed through purchase orders, and what suppliers have actually invoiced. Because the modules share one data model, those figures are not re-keyed here. Purchase orders drawn from the budget move the committed column, and supplier invoices that Oryn reads and codes in accounts payable fill in the actuals as they arrive.
On top of that sits variance flagging. Oryn watches each cost line against budget and flags drift at 2, 5 and 10 per cent, so the thing that reaches you is a two per cent problem rather than a twenty per cent explanation. The same coded actuals feed the WIP and margin view across every active job, and bills sync to Xero with tracking categories so the ledger and the job view agree without a month-end reconciliation.
What we do not claim. VIABUILD does not improve your estimate, does not raise purchase orders you did not raise, and does not decide what to do about a forecast it flags. The full feature detail is on cost control, and the working routine, which is worth tightening before changing any software, is in the builder cost tracking guide.
07 / FAQ
Common questions.
Construction cost tracking software holds the cost position of each job against its budget while the job is running. In practice it does five things. It takes the budget, usually from the estimate the job was won on, and breaks it into cost codes. It records committed cost as purchase orders and subcontract packages are raised, before any invoice exists. It records actual cost as supplier invoices are coded and approved. It compares those three figures per cost line and surfaces the variance. And it supports a forward view, cost to complete on the remaining work and a forecast final cost for the job. Construction cost management software and job costing software describe the same category from slightly different angles, the first emphasising the control loop and the second emphasising the record.
They answer different questions and a builder needs both. Accounting software is the ledger. It records what has been invoiced, what has been paid and what is owed, it is the statutory record, and it is where your accountant works. It is complete and it is behind, because an invoice arrives weeks after the decision that caused it. Cost tracking software is the operating view of the job. It compares a budget against committed and actual cost per cost code, and it counts a purchase order as exposure on the day it is raised. Tracking categories in an accounting system will get job-level reporting out of the ledger, which is genuinely useful, but they do not give you a budget to compare against, committed cost before invoicing, or a forecast final cost. The right arrangement is that the two connect rather than that one replaces the other.
A spreadsheet works while one person can hold the job in their head, which is a real situation and not a failure. What breaks it is volume and delay rather than complexity. The sheet is updated when there is time, so it is accurate about a job as it was a fortnight ago. Committed cost is usually missing entirely because nobody enters purchase orders twice. Invoices are coded in the accounting system and then re-coded in the sheet, so the two disagree and the reconciliation becomes a monthly job. And each new job starts as a copy of the last one, so the structure quietly drifts. The value of software here is not better arithmetic, it is that committed cost gets captured at the moment of ordering and the numbers stop being re-keyed. The underlying discipline is set out in the cost control reference and works on paper too.
Committed cost is money you have agreed to spend but have not yet been billed for, chiefly through purchase orders and subcontract packages. It matters because it is the difference between knowing where a job sits and knowing where it sat. When you place a $40,000 framing package, the exposure is real from that moment, but an invoice-based view of the job will show nothing for weeks. That gap is exactly where a builder would still have choices, so a cost position that ignores commitment is at its least accurate at the point it would be most useful. Any tool being evaluated for construction cost tracking should be able to show committed cost as its own column, updated when an order is raised. The full explanation is in the committed costs reference.
Cost to complete is what it will cost to finish the remaining work on a cost line, and it is a judgement rather than a calculation. Software can offer a default, usually budget minus committed and actual, and that default is reasonable on lines where the remaining work really is proportional to the remaining budget. It is wrong on the lines that matter most, where the job is 80 per cent through the budget and 40 per cent through the work. That is why good tools let a person override the figure per line and record who set it and when. The honest position is that the software maintains the arithmetic and the structure, and a supervisor or estimator supplies the judgement. A product presenting a fully automatic cost to complete as fact is presenting a guess with a confident interface. See cost to complete and forecast final cost for the mechanics.
Four limits worth being clear about. It cannot fix a bad estimate. If the budget it compares against was wrong at tender, the software will tell you accurately and promptly that you are on track to lose money, which is useful but is not cost control. It cannot capture what is not entered. Committed cost only exists if purchase orders are actually raised in the system, and the discipline of ordering through the tool is the real implementation project, not the configuration. It cannot forecast without judgement, as above. And it does not make the decision. Knowing a job will finish four per cent over is the beginning of a conversation about scope, a variation or a supplier, and the software has no view on which of those is right. Any vendor presenting cost tracking as a solution rather than an instrument is overclaiming.
Cost control is one module of VIABUILD, the Construction Operating System for residential builders, rather than a separate cost app. It holds three numbers live on every job, the budget that comes from the estimate you won on, what has been committed through purchase orders, and what suppliers have actually invoiced. Because every module shares one data model, those figures are not re-keyed, purchase orders draw down the committed column and supplier invoices that Oryn reads and codes in accounts payable fill in actuals as they arrive. Oryn watches each cost line against budget and flags drift at 2, 5 and 10 per cent, so a two per cent problem is visible rather than a twenty per cent one being explained later. Bills sync with Xero using tracking categories, so the ledger and the job view agree without anyone reconciling a spreadsheet at month end. Full detail is on the cost control feature page.
08 / Keep reading
Keep reading on job cost
The references behind budget, committed, actual and forecast, the working guides, and the product pages.
See the blowout while it is still small.
VIABUILD holds budget against committed against actual live on every job, fed by the estimate, the purchase orders and Oryn-coded supplier invoices, with drift flagged at 2, 5 and 10 per cent. One module of the operating system, synced to Xero.