Cost value reconciliation on a live project
What cost value reconciliation looks like on a governed record, and the checks a reader can run for themselves.
Cost value reconciliation is the kind of thing a construction project usually argues about after the fact, from memory, with the evidence spread across inboxes and spreadsheets. CONSTRUX treats it as a record: every change to it is an append-only, hash-chained event on the golden thread, written before it is acknowledged, so the question "what did we know, and when" has an answer rather than an opinion.
Where it goes wrong
The failure is rarely a missing number. It is a number that exists in three places and agrees in none of them — the site diary, the commercial report and the board paper each telling a slightly different story about cost value reconciliation, with nobody able to say which was true on the day it mattered. By the time the disagreement surfaces it is a dispute rather than a decision, and a dispute is priced by whoever kept the better record.
How CONSTRUX handles it
Earned value, CVR and where the margin actually went. CPI and SPI with three EAC scenarios, cost-value reconciliation that shows margin erosion line by line, and an S-curve built from the programme rather than drawn by hand.
Payment cycles that refuse to be paid twice. Application, certification, payment notice and settlement with statutory dates calculated for you. The applicant cannot certify their own work, over-certification and overpayment are refused outright, and every withheld sum carries its reason.
AI spend you can see before it is spent. Every AI call is routed, reserved, executed and only then billed — prepaid, hard-capped and attributed per engine. An empty wallet stops the call rather than producing an invoice.
A record you can replay is a record you can rely on.
What you can check for yourself
None of this asks for trust. Replay reconstructs a project from its own history and reports a root hash; a document issued from the platform carries a content hash that lets anybody verify a document against what was issued; and every AI-assisted step names the engine that produced it and the records it read. If cost value reconciliation matters on your projects, the demo environment runs the whole cycle on a seeded programme — open it, run it, and read the record it leaves behind.
See the record being made rather than described.
Launch the demo environment