COST CONTROL
Construction cost control software for Australian head contractors
What cost control means on a commercial job, why the margin number is usually a month old, and what the docket-to-claim workflow has to look like for it to be current. Written for the project manager or contract administrator who runs the job, in the words used on site.
What cost control means on a commercial job
Every construction project has a contract above it and a budget below it. The contract above is the revenue contract: what the client has agreed to pay, on what terms, with what retention held and what liquidated damages attached. The budget below is what you expect to spend delivering it, broken into budget lines by trade and by cost type, each tagged with a cost code.
Margin is the difference between what the job has earned under the contract and what it has cost so far. Cost control is the discipline of knowing that number while the job is running, with enough confidence to act on it: to push a variation before the work is done rather than after, to notice a trade package running hot before its supplier invoices arrive, to claim everything the contract lets you claim.
The accounting system does not do this. It records invoices once they exist. Cost control works one step earlier, on the site records and the commitments that will become those invoices, and on the contract terms that decide what each of them is worth.
Why the margin number lags on a live project
On most commercial jobs the cost report comes out two or three weeks after the month closes, and it is already out of date on the day it is issued. Three lags cause it.
Dockets arrive late and get coded later. A docket is the daily record of who worked, what plant ran and what materials went in. On paper it sits in a ute until Friday, then in a tray until someone keys it, and only then does it get a cost code. Until it has one, the cost it represents does not exist anywhere the job can see it.
Cost is incurred long before it is invoiced. Concrete poured in week two is invoiced in week six. The gap is an accrual, and if nobody estimates it the cost report understates spend and overstates margin every month. Most teams accrue by hand, from memory, at month end.
Scope changes have no record. A verbal yes on site is a variation that cannot be claimed. A missed time extension is a missed defence against liquidated damages. Neither shows up in a cost report because neither was ever written down.
A faster report does not fix any of these. Capturing each record once, at the point it happens, with its cost code attached, does.
The docket-to-claim workflow
The commercial workflow a head contractor already runs is also the evidence chain for the margin number. It has four steps, and each one substantiates the next.
- Docket. The crew records the labour, plant and materials that went into a piece of work, on the day, against a cost code. An engaged contractor submits theirs; your own forces go in the site diary.
- Assess. The contract administrator checks each docket against the contract: the right classification, the right rate for that date under the schedule of rates, hours that match the diary. Approve, reprice or reject.
- Claim. Approved dockets are priced into the period's payment claim under the Security of Payment Act, against a reference date that starts the statutory clock. Work outside the original scope goes through a variation, with its own approval, before it can be claimed.
- Certificate. The other party responds with a payment certificate stating what they will pay and why any amount is disputed. Issued late, the claim is taken to be approved in full. Retention is held on the certified amount and released at practical completion and at the end of the defects period.
Run on paper, each step is a re-keying of the one before it, and the substantiation packet for a disputed claim takes days to assemble. Run as one record that moves through four states, the claim is the sum of its approved dockets and the packet already exists.
What the software has to do
Whatever tool you use for this, the requirements are set by the workflow above, and a tool that skips any of them leaves the margin number where it was.
- One cost-coded spine. Revenue and cost on the same cost codes, so a docket, a purchase order and a claim line all roll up to the same budget line without a mapping sheet in between.
- Capture at the source. The docket is created by the people who did the work, on the day, from wherever they are. A docket keyed from paper a week later is a week of lag built in.
- Rates that know the date. A labour classification is worth a different amount after an award increase or a contract rate revision. Pricing a docket means pricing it at the rate that applied on the day the work was done.
- A forecast that comes from the plan. Cost to complete is the remaining work on the program at its budgeted cost, so a slip on the critical path changes the forecast that day. A cost-loaded program is how a schedule delay becomes a margin signal.
- Your internal rates stay yours. What the work costs you is the most sensitive number on the job. The internal rate card must be invisible to the parties above you and the contractors below you, enforced by the system rather than by who remembers to hide a column.
- Australian by default. State-by-state Security of Payment timeframes, the public holiday calendar of the state the project is in, GST on claims and certificates, and the vocabulary used on commercial work here.
Where tectm sits
tectm is construction cost control software built around that workflow for Australian head contractors. The head contract and the subcontracts sit on one cost-coded spine. Dockets come in from the site, including from a phone, and are assessed against date-effective contract rates. Approved dockets price into payment claims; certificates, retention, back charges and liquidated damages sit on the revenue side of the same job. A cost-loaded critical-path program carries the forecast, and projected margin is what the revenue loading nets against the cost loading, per cost code, today.
Contracts are read on upload by Tectus, which extracts the rates, retention terms and milestone dates with the clause and page each one came from, and answers questions about them the same way. Substantiation packets are generated on demand from the records already in the system. Internal rate cards are locked to the organisation that owns them at the database itself.
It runs on the desktop today, with dockets and the site diary also on the phone. It is not a document store, not a compliance checklist and not built for residential work. Access is by invitation: there is no public sign-up, and the first step is a conversation about one of your projects.
Questions people ask before they ask about a product
What is construction cost control software?
Software that keeps a running comparison between what a project has earned under its contract and what it has cost so far, and shows the gap as margin while the job is still going. The accounting system tells you what has been invoiced. Cost control tells you what has happened on site, whether or not an invoice exists for it yet, and what the rest of the job is going to cost.
How do head contractors track margin on a live job?
On most jobs, monthly. The contract administrator collects the dockets, the accountant posts the invoices, a quantity surveyor estimates the accruals, and a cost report comes out two or three weeks after the month closes. By the time it says a trade package is over, the overrun has been running for six weeks.
Tracking it live means every cost record carries a cost code the moment it is created, so it rolls up against its budget line that day, and the forecast to complete comes from the program. Nobody updates a spreadsheet at month end to produce it.
What is the docket-to-claim workflow?
The chain of evidence from work done to money claimed. A crew records the labour, plant and materials that went into a piece of work on a docket. The head contractor assesses that docket against the contract rates and either approves it, reprices it or knocks it back. Approved dockets are priced into a payment claim for the period, the other party responds with a payment certificate, and anything outside the original scope goes through a variation instead. Each step is a record that substantiates the next one.
Why is our cost report always a month behind?
Because the inputs arrive late and get coded late. Paper dockets sit in a ute until Friday. Supplier invoices land weeks after delivery, so cost incurred is only known once it has been accrued by hand. A variation agreed verbally on site has no record until somebody writes it up. None of that is fixed by a faster report. It is fixed by capturing each record once, at the point it happens, with its cost code attached.
Is this the same as job costing in our accounting system?
No. The two sit next to each other. Accounting software records transactions once they exist: invoices in, invoices out. Cost control works one step earlier, on the commitments and the site records that will become those invoices, and on the contract terms that decide what you can claim for them. Retention, variations, back charges and Security of Payment timeframes are contract matters, and a general ledger has no field for any of them.
Do our subcontractors have to change how they submit dockets?
Only in where the docket goes. The content is what it has always been: who worked, on what, for how long, with which plant and materials. In tectm an engaged contractor submits that from a phone on site, or the head contractor keys it from the paper copy. Either way it lands against a cost code and against the contract rates for that date, so the assessment happens on the record itself, with nothing re-keyed.
Does it handle the Security of Payment Act timeframes?
The claim and certificate cycle is built around them. A payment claim is made against a reference date, the response window for the payment certificate runs from there, and a certificate issued late or not at all is the risk the workflow exists to make visible. Each state has its own Act with different windows; the dates on a project follow the state the work is in. tectm records and tracks the process. It does not give legal advice on a particular claim.
Is it built for Australian contracts?
Yes. Australian states and territories, state-by-state Security of Payment legislation, the public holiday calendar of the state the project is in (so a Perth job is not priced on a Sydney calendar), GST on claims and certificates, and the contract forms and vocabulary used on commercial work here: dockets, schedule of rates, retention, practical completion, defects liability, liquidated damages.
Who is it not for?
Residential builders, and anyone whose main need is a document store or a scheduling tool on its own. tectm does run a critical-path program, but the program is there because it is cost-loaded and drives the forecast. It is also invitation-only at the moment: there is no public sign-up, and the first step is a conversation about one of your projects.
Every term above is defined in the construction glossary.