Infrastructure and road contractors build along a line rather than within a boundary. Work is organised by chainage, executed in layers that each require testing before the next covers them, and delivered largely by plant and machinery whose utilisation determines whether the job makes money. Government departments, public authorities and private developers are all important clients in this segment, contract durations are often long enough that input prices move materially, and access to the land itself is sometimes incomplete when work begins. With Pentoggle, an infrastructure contractor can describe its chainage structure, layers and plant records and generate the starting application around them.
Contract models vary and continue to evolve, covering item rate arrangements, engineering procurement and construction packages and annuity based structures, each allocating design, price and traffic risk differently. Terms differ by authority and by package, so build around the contracts you actually sign.
Many contractors already run Tally or a comparable system for accounting, which can handle job costing and project-level financials. What site teams often still manage outside that workflow is which stretch is at which layer, how many hours the paver ran last week, and how long a particular obstruction has been blocking work.
Key takeaways
- Chainage is the organising key. A record that does not carry a location on the line is much harder to connect to the rest of the project record.
- Plant utilisation is a major driver of margin on plant-intensive work, and idle hours rarely appear anywhere as a number.
- Fuel is a significant cost that can be usefully checked by comparing consumption against expected consumption for the work done.
- Layer work is concealed work at scale, so testing records have to be made before the next layer goes on.
- Obstructions outside your control can be a major source of delay, and entitlement usually depends on contemporaneous records rather than on being right.
Your project is a line, not a place
A building contractor organises everything by block, tower and floor. An infrastructure contractor has a dominant linear dimension, and every record in the business has to carry a position on it.
Progress is between chainages. Measurement is between chainages. A quality test can be tied to a layer between two chainages. Material consumption belongs to a stretch. A machine was working at a location. An obstruction blocks from one point to another. When all of these carry the same key, questions that are otherwise research become queries: what is the status of every kilometre, which stretches have passed testing at subgrade but not started on the next layer, where has the plant been for the last fortnight.
When they do not, each record lives in its own document. Progress is in the daily report, tests are in the lab register, machine hours are in an operator's log, and they are often combined only through the project manager's working view of the job. That works for one stretch and stops working once a package spans dozens of kilometres and several crews.
This is a modest structural decision with a large payoff, and it is the first thing worth getting right when building anything for this business. Chainage on every entry, recorded on a phone at the location, is what makes the rest possible. It also matches how measurement already works in this sector, where quantities come from cross sections and level books rather than from direct dimensions.
A major margin driver on many infrastructure projects is machine utilisation
Road and infrastructure work can be particularly plant intensive compared with many building projects. Batching and mix plants, pavers, rollers, graders, excavators and a tipper fleet represent both the capital and the running cost of the business, whether owned or hired.
A machine has hours available and hours it actually worked. The difference is the leak, and it is often invisible because the denominator is rarely recorded. A paver that ran four hours on a day it was available for ten did not fail dramatically. It waited for mix, or for the stretch to be cleared, or for an operator, and the day passed. Across a season this is a large number that never appears in any report.
Hired machinery makes it sharper still, because hire charges may accrue based on time rather than output, depending on the hire arrangement, so an idle hired machine can be a direct cash cost with nothing against it.
Fuel sits alongside. Fuel can be a significant consumable cost in this business, and a useful check is comparison. Fuel issued against a machine, set against the hours it ran and the output it produced, gives a benchmark against which actual consumption can be compared. A machine consistently consuming above expectation is a specific question about a specific machine, which is a far better position than a general suspicion about the fuel bill. As with material, the comparison indicates where to look rather than what happened, and the causes range from an ageing engine to haulage distances nobody accounted for.
Holding deployment, running hours, idle hours and fuel against each machine gives the plant fleet a management view that can be reviewed weekly. See equipment management for the maintenance side.
Many costly delays come from constraints outside your control
Infrastructure work can depend on the client, authorities or other parties providing access, approvals and other prerequisites before particular stretches can proceed.
Land and right of way may be encumbered on some stretches. Utilities may need shifting, which involves other agencies working to their own priorities. Approvals, drawings and forest or environmental clearances may be pending. Structures may need to be removed. Some of these may be outside the contractor's direct control, and they can stop or restrict work on the affected stretch while overheads, plant hire and mobilised crews continue running.
Whether that converts into an extension of time or any entitlement depends on the contract and on the facts, and that is a question for your contracts team or legal advisor rather than for general guidance. What is not in doubt is that any such case rests on records made at the time.
The records that matter are unremarkable. The date an obstruction was identified. The chainages affected. What was blocked. Who was notified and when, which is where this connects to the correspondence and notice record. What plant and crew were mobilised and unable to work. The date it cleared. Each entry takes a minute at the time and is nearly impossible to reconstruct afterwards, which is why so many contractors carry genuine entitlement they cannot evidence.
A hindrance record organised by chainage and date, sitting alongside the plant and labour deployment for the same days, gives a claim a contemporaneous documentary basis rather than leaving it dependent mainly on later correspondence and recollection. This is the same problem the MEP contractor page describes for firms working inside another trade's programme, in a form where the blocked area is measured in kilometres.
Layers behave like concealed work once the next layer covers them
Road construction proceeds in layers, each covering the last. Subgrade, granular layers and bituminous layers have applicable requirements for compaction, gradation, thickness and material properties, with testing and acceptance carried out according to the project specification before subsequent work covers the relevant layer where required.
Testing frequency is generally specified by the applicable contract specification, often by quantity, area, location or another defined sampling basis, which means the number of tests is itself a function of progress, and the records may form part of acceptance and payment documentation, depending on the specification and contract. Requirements differ by specification and authority, so build around what your contract requires.
The operational problem is familiar from other concealed work, with an additional twist. Once a layer is covered, additional verification may require methods such as core cutting, which can be destructive, time-consuming and disruptive. So the test record made at the time is the evidence, and it needs to carry the chainage, the layer, the date, the result and the reference to the sample. Where those records are kept in a lab register that is not connected to progress, two failure modes appear. Stretches proceed to the next layer without the previous test being traceable. And tests get repeated because the earlier result cannot be found, which costs time on the critical path for no reason.
Holding tests against chainage and layer, in the same place progress is recorded, closes both. Quality and inspection covers the broader workflow.
Escalation, where applicable, is money you have to compute and claim
Long-duration contracts may include provisions adjusting payment for movement in input prices such as fuel, bitumen, steel, cement and labour, usually by formula against published indices.
Where such a provision applies, the adjustment is computed for each bill from the quantities executed in that period and the relevant index values. It is arithmetic, it is tedious, and it is easy to defer. The consequence of deferring is that escalation gets claimed late, computed hurriedly, or claimed on fewer components than the contract allows.
Formulae, applicable indices and the components covered vary considerably by contract and authority, and index values are published on their own schedule, so the mechanics have to follow your specific contract rather than a standard template. What software contributes is holding the executed quantities by period in a form the computation can use, keeping the index values applied to each bill on record, and making the whole calculation reproducible when the client's engineer checks it. Computing escalation systematically makes it easier to identify and claim the amounts permitted by the contract.
The workflows an infrastructure contractor runs
- Measurement and Quantity Tracking, on chainage, cross sections and level books rather than direct dimensions.
- Construction Equipment Management, which for this business is close to the core of the operation.
- RA Billing and Retention, in departmental formats and including escalation where applicable.
- Construction Material Management, where bulk material and haulage distance dominate cost.
- Construction Quality and Inspection, covering layer-wise testing at specified frequency.
- Construction Progress Tracking, reported by stretch and layer.
- Construction Change Order and Variation, for deviations and extra items on departmental contracts.
- Construction Labour Management Software, across crews spread over a long site.
Why infrastructure contractors choose Pentoggle
Chainage on every record
Progress, tests, material, machines and obstructions all carrying the same location key, so they can be read together.
Plant hours and fuel together
Running hours, idle hours and fuel issued per machine, which is where the margin actually sits.
Hindrance recorded on the day
Obstruction, chainages affected, notification and resources idled, captured when it happens.
Layer-wise testing tied to progress
Test results held against the stretch and layer they belong to.
Sits around your accounting
Tally and comparable systems handle accounting, GST and job costing, and they stay where they are.
A useful number for an infrastructure business
Productive hours against available hours, by machine.
Turnover and progress describe output. This describes whether the asset base that produces the output is being used. For a plant-intensive business, it can materially affect whether a package earns its expected margin, and unlike many useful numbers it can be produced from records a site already keeps informally.
Read it per machine and per week. A fleet average conceals the problem, because the pattern is usually one or two machines waiting on something specific rather than a general inefficiency. Read it alongside the hindrance record, since machinery idle against a blocked stretch is a claim question rather than a productivity question, and the two need entirely different responses.
The number needs available hours recorded, not just running hours. Available hours should reflect the periods when the machine was actually available for productive deployment, with agreed exclusions such as planned maintenance or other non-available periods. That is the entry most operators' logs omit, and it is the one that makes the figure mean anything.
Ready to build software for your infrastructure business?
The road is measured in kilometres. A large part of your margin is reflected in machine hours.