The Record Everyone Agrees On

Construction's commercial problem isn't a lack of systems. It's a lack of agreement

Most construction payment disputes are not finance problems. They begin at the point of work, when the supplier's record of what was delivered and the contractor's record of what was received do not match. The gap is not a missing system. It is a missing agreement, and it sits between companies rather than inside them.

The agreement gap, defined: the difference between what a supplier records as delivered and what a contractor records as received, which stays invisible until the payment claim is submitted, often weeks after the work was done.

Walk into any head contractor's commercial team and you won't find a shortage of software. There's an ERP. There's a project controls system. There's a scheduling tool, a procurement module, a data warehouse and a reporting stack on top of it. The suppliers have their own: weighbridge systems, batching plants, fleet telematics, payroll and enterprise bargaining agreement (EBA) interpretation engines.

None of it is the problem.

The problem is that every one of those systems holds one company's version of the truth. The supplier knows what it says it delivered. The contractor knows what it says it received. The principal knows what it was told. And nobody finds out where those versions differ until the claim lands, often weeks after the work was done, when the crew has moved on, the plant is on another job, and the only person who can settle the question is a commercial manager with a stack of paper and a deadline.

That's not a systems gap. It's an agreement gap. And you can't close it by adding another system inside your own four walls, because the disagreement doesn't live inside your four walls. It lives between companies.

"Payment delays are often treated as a finance problem, but it generally starts earlier in the process," says Docketbook CEO Mark Shepherd-Smith. "If the order or the dockets are unclear or misaligned, the payment process is already under pressure."

Where Agreement Breaks Down: The Order, The Docket And The Claim

Commercial reality in construction is decided at three moments: the order, the docket and the claim. If all three are agreed by both parties as they happen, there is nothing left to reconcile at month-end. If any one of them is agreed only after the fact, the dispute is already in the system.

Docketbook is built to deliver agreement at the three points where commercial reality is actually decided: the order, the docket and the claim. Get agreement at all three and the month-end argument doesn't happen, because there's nothing left to argue about.

The Order: Agreed Up Front

The order is where the commercial terms get locked in, not argued over later. Scope, rates and units are shared with the supplier, and the supplier accepts them. That acceptance matters: it means both parties are working from the same rate schedule before a wheel turns.

It also does something quieter but just as important. The order maps the supplier's resources to your purchase order lines, so everything that follows - every docket, every claim line - arrives already coherent to your ERP. No translation layer. No reinterpretation by someone in accounts.

The Docket: Agreed At The Point Of Work

The docket is captured on site as the work happens: time-stamped, GPS-located, signed on the spot, and visible to every party the moment it's raised. Not a photo of a piece of paper emailed the next morning. Evidence.

Suppliers come onto the network three ways, and all three produce the same shared record:

For labour hire and plant hire, Smart Dockets add interpretation at the point of capture. A Smart Docket is a docket that applies the relevant pay and charge rules as it is raised, rather than leaving them to be worked out later. A worker enters start, finish and break; the ruleset applies the enterprise bargaining agreement (EBA) or non-EBA agreement, allowances, minimum charges and wet weather conditions, and produces a docket that is commercially accurate on the day, not reinterpreted three weeks later by two parties reaching two different numbers.

The Claim: Three-Way Matched Before It's Submitted

Because the order and the dockets are already shared, the claim reconciles against them automatically. What matches, matches, and nobody touches it. What doesn't, surfaces immediately as an exception, while the crew is still on site and the answer is still fresh.

The supplier prepares the claim already matched against the order lines and approved docket quantities. It arrives pre-reconciled and ready to approve. That's the difference between a claim that moves and a claim that stalls.

For the full mechanics of how the order, docket and claim reconcile against each other, see the complete guide to digital dockets for construction.

How One Shared Record Makes Productivity Real

Most projects build productivity reporting and commercial reporting from separate data, so the two never agree. When the docket is the source for both, daily costs and invoice reconciliation tell the same story, and the month-end surprise disappears.

Once the order, the docket and the claim are a single shared record, something else becomes possible, and it's the part commercial teams tend to underestimate.

Your daily cost report and your invoice reconciliation start telling the same story.

Most projects run productivity reporting and commercial reporting on separate data. Site fills in a daily diary or a spreadsheet; finance reconciles invoices against orders. The two are assembled by different people from different sources, so they never quite agree and the difference only shows up at month-end, as a surprise.

When the docket is the source for both, that surprise disappears. The same captured data drives daily costs, production quantities, plant utilisation and the reconciled invoice. Supervisors can see what a day actually cost while they can still change tomorrow. Commercial managers can see committed cost as it accrues, not after it's booked. And because the data is structured and shared, it flows into Power BI or your data warehouse to sit alongside your other project metrics.

Accurate productivity isn't a separate module. It's what you get for free once everyone is working from one agreed record.

Why a Layer Between Companies Works Where Internal Systems Don't An ERP, a project controls system or a data warehouse can only ever hold one company's version of events. A disagreement between two companies cannot be resolved inside either one of them. That is why the record has to sit between businesses rather than inside one.

This is the distinction that matters most, and it's the one that gets missed.

Docketbook is not another system inside your business. You already have enough of those. It's the layer between businesses - the shared commercial ground where you and your supply chain transact, agree and reconcile.

That layer connects in both directions. It connects to your internal systems: ERP, accounting, project controls, analytics. And it connects to your suppliers' systems, so the data that already exists in their weighbridge, batching plant or hire system becomes your docket without anyone typing it twice.

The proof is in who's already on it. Head contractors including BMD, Laing O'Rourke and John Holland run projects on Docketbook. Major materials suppliers including Heidelberg Materials, Boral, Holcim, Adbri and Barro Group integrate directly, delivering product and surcharge information in near real time, effectively self-populating concrete and materials registers as loads are delivered. Coates connects hire orders and on-hire status through a cross-company dry hire process built over several years. Labour hire companies including Protech run interpreted daily dockets across company boundaries. And plant hire businesses of every size, from national fleets to single-machine owner-operators, raise dockets on the same network.

Every one of those connections was built once and works for everyone on the network. That's the compounding advantage of a layer that sits between companies rather than inside one.

Frequently Asked Questions

Why do construction payment disputes happen?

Most disputes start at the point of work rather than in finance. The supplier records what it believes it delivered, the contractor records what it believes it received, and the two records are never compared until the claim is submitted. By then the crew has moved on and the evidence is memory and paper.

Can an ERP or project controls system close the agreement gap?

No. An ERP holds one company's version of events, which is exactly the problem. It can record your position accurately and still leave you in dispute, because the disagreement is with another business and lives outside your systems. Closing it requires a record both companies can see and accept as work happens.

What is the difference between a site diary and a docket?

A site diary is an internal record of what a project team observed on a given day. A docket is a transactional record of work or materials delivered, agreed between two companies, that carries commercial consequence. A diary supports your position in a dispute. An agreed docket prevents the dispute.

How does docket data improve daily cost reporting?

When dockets are captured and agreed on site, the same data drives both the daily cost report and the invoice reconciliation. Supervisors see what a day actually cost while they can still influence the next one, and commercial managers see committed cost as it accrues rather than after it is booked.

The record everyone agrees on

Commercial certainty shouldn't arrive six weeks after the work. It should happen as the work happens.

One order, agreed. One docket, agreed at the point of work. One claim, matched before it's submitted. Shared. Live. Agreed by everyone who touches it.

That's the whole idea. Fewer disputes, faster approvals, real daily costs, and a supply chain that finally reads from the same page.

Docketbook. The record everyone agrees on.

See how the order, docket and claim work together on your own project data. A walkthrough takes 30 minutes and we'll use your workflow, not a demo dataset.

Book a walkthrough · Get started