How Construction Joint Ventures Control Costs Across Partner Companies

Large infrastructure is rarely built by one company. A railway line, a motorway section or a hospital is often delivered by a consortium: a joint venture, a project alliance or a temporary grouping of contractors. Each partner brings its own teams, suppliers and subcontractors. Together they answer to one client, one budget and often one funder.

That arrangement solves a capacity problem and creates a control problem. Money is spent by several companies, through several purchasing departments, on one shared budget. Someone has to know — every month, ideally every day — what was planned, what was committed, what was delivered, what was invoiced and what can be paid.

1. Why the usual tools fall short

Spreadsheets. Most consortiums start here. A shared workbook tracks the budget; purchase orders are approved by e-mail; site reports arrive as PDFs and are re-typed at the office. It works for a few weeks. Then versions multiply, formulas break, nobody can say who approved an order, and the real cost of a month is known six weeks after it ended.

One partner's ERP. The obvious next step is to run the project in the leading partner's system. But the other partners then work inside a competitor's tool, see only what that company chooses to show, and still keep their own books on the side. Every figure is entered twice, and trust in the shared numbers depends on one member of the group.

A general construction management suite. These are strong on documents, drawings and site coordination. They are usually built around one contractor and one set of books, and are less concerned with the question a consortium keeps asking: which partner committed this money, under which contract, and who is allowed to see it?

2. The ten things a consortium cost-control system must do

1. One budget, one cost-code structure. Every partner books against the same codes. The same code appears on purchase orders, daily site reports and invoices, so costs add up without mapping tables.
2. Open book on the budget, private perimeter on the rest. All partners should read the same budget figures. But each company should only see the orders, deliveries and invoices of its own part of the project — nothing merges, nothing leaks between firms.
3. Purchase orders that route themselves. An order should follow an approval circuit set by amount and by issuing company, not by whoever happens to be in the e-mail thread. Every order ties back to a contract or quotation.
4. Separation of duties by construction. Nobody approves their own order. Whoever signed an order does not approve its invoice. A subcontractor’s claim is never certified by the person who filed it.
5. Deliveries recorded once, on site. The daily site report — crews, machine hours, materials, work done — should be tied line by line to purchase orders, so approving the report is the goods receipt. Nothing is re-typed at the office.
6. Errors stopped at entry. A missing cost code, a quantity above the order or a unit that contradicts the budget should block the report on the day, not surface at invoice time.
7. Three-way matching of invoices. An invoice is checked against the order and against what was actually delivered. A discrepancy keeps it pending instead of letting it through.
8. Subcontractor payment applications handled as data. Monthly claims should be approved or rejected line by line, and only certified claims should count as earned value.
9. Earned value and month close. Planned, earned and actual cost side by side, month by month — and a closed month frozen as it stood, so the figures reported to the client can be reproduced later.
10. A trace of everything. Who approved what, and when, for every order, invoice and claim — because a consortium answers to a client, a funder and auditors, often in several languages.

3. What a shared system changes in practice

Cost becomes visible during the month, not after it. Each day shows what it cost and what it produced. An unprofitable day is visible the evening it happens, while there is still time to act.

Arguments move from people to records. "Who approved this?" and "was it delivered?" have answers in the system, with a date and a name. Photos from site, delivery notes and signed contracts are attached to the record they belong to.

The partners trust the same number. Because the system is neutral — owned by none of the contractors — the total on screen is the total everyone signed off.

4. How ControlWise approaches it

ControlWise is the cost and procurement control platform Hidacs built for construction consortiums. It follows the ten points above: one shared budget by cost code with monthly planning and earned value; purchase orders routed by amount and company; daily site reports tied to orders, where approval records the delivery; invoices matched and approved line by line by the validator named on the contract; subcontractor Applications For Payment certified line by line; per-company visibility; and a full activity log. It also covers the site paperwork that sits next to the cost — safety forms, certificate expiry, site photos — and works in English, French, Estonian and Finnish.

It is designed, developed and supported in Switzerland by Hidacs Sàrl, independently of any contractor. If you are setting up a consortium and want to see it, request a walkthrough.

5. Frequently asked questions