Where Construction Procurement Goes Wrong

A procurement manager opens three tender submissions for the same electrical package. One bidder priced the provisional sums separately, another buried them inside the unit rates, and the third quoted against a drawing revision that went out two days after the tender closed. On paper, all three numbers look comparable. In practice, none of them are pricing the same job.

This is not a rare mishap. It is the default outcome of a tendering process where three or four bidders are quietly working from three or four slightly different pictures of the same project.

Why tenders stop being comparable

Tender packages exist to let a head contractor compare bidders on equal footing, price, capability, safety management, and delivery timeline, side by side. That only works if every bidder is pricing identical information. In practice, incomplete tender packages routinely produce non-comparable tenders, because bidders price what they can see, not what was intended, and fill any gap with their own assumptions rather than confirmed facts. A scope defined across documents that quietly disagree with each other is a common source of dispute, and the contract's order-of-precedence clause, not either party's actual intention, ends up deciding who is right.

Missing design details, unclear responsibilities, or outdated specifications create uncertainty in pricing, and these gaps often lead to contingencies or post-contract disputes. Aditum Lawyers, on common scope of works pitfalls in Australian construction contracts, 2026

Why this happens on almost every project

Nobody issues a bad tender pack on purpose. It happens because design finalises on a different timeline than procurement needs it to. A trade package goes out before the drawings are locked because the programme cannot wait, addenda get issued piecemeal to whichever bidders happen to ask the right question, and by the time bids come back, four subcontractors are pricing four slightly different versions of the same job. Australia's construction industry compounds this: 98.5% of the country's 410,602 construction firms employ fewer than 20 people, and 91% are microbusinesses with under five employees. That means most bidders on any given tender have limited capacity to chase down ambiguity themselves, they price the gap and move on.

The cost of a gap nobody priced

A Sydney legal firm recently advised on a $2.8 million design and construct contract where the scope of works was little more than a marketing flyer and a handful of notes, with no reference to insulation ratings, paving, or data cabling. At handover, the builder argued those items were excluded. The dispute went to adjudication under Security of Payment legislation, cost both parties more than $150,000 in legal fees, and delayed occupation by over three months. The issue was never performance. It was a scope gap that nobody caught between tender and contract.

What good procurement actually looks like

The fix is not more paperwork, it is one version of the truth that every bidder prices against. That means a single, current set of drawings and specifications, addenda issued to every bidder simultaneously rather than piecemeal, a clarifications log every bidder can see, and a clear statement of what is included and excluded before a single quote comes back. When that discipline holds:

• Every bidder prices the same drawing revision, not whatever version happened to reach them first.

• Provisional sums, exclusions, and assumptions are visible before bids close, not discovered at handover.

• A tender comparison takes minutes, not days of manually normalising mismatched formats.

• The awarded contract references the same scope document the winning bid was actually priced against.

• Variations after award are the exception, not the predictable consequence of an ambiguous tender pack.

The Australian context

Construction procurement software exists to close this exact gap, but the tendering process in construction is still, on most Australian projects, a manual exercise in reconciling PDFs, spreadsheets, and email threads. With a construction sector this fragmented on the subcontractor side, the builder carries almost all the responsibility for keeping tender information consistent. That is the same coordination burden we cover in our piece on the real cost of subcontractor management failure, and the scope gaps that open at tender are frequently the same gaps that resurface later as disputed variations, a problem we cover in an upcoming post.

Both problems trace back to a wider pattern we explore in our companion piece on what a single source of truth actually means on a construction project.

The cost is never the process itself, it is what happens when different people are working from different versions of it.

Where Plexa fits

Plexa's Procurement module keeps every bidder working from the same current drawing set, the same addenda, and the same clarifications log, so a tender comparison is actually comparing like with like. When a package is awarded, the scope that was priced becomes the scope in the contract, not a document that has to be reconstructed after the fact from a marketing flyer and a few notes. The procurement manager comparing three tenders should be comparing three prices for the same job, not reconciling three different interpretations of what the job even was.

If you want to see how Plexa keeps tender packages consistent from issue to award, book a 30-minute demo with the Plexa team.