The Fifth Change Order
You know which change order took the margin on the last hall you closed out. It was not the big one. It was the fifth small one — a re-routed duct run, approved on a call, buried three weeks deep in a report nobody re-derived from what was actually installed.
## The reconciliation you already know At close-out the schedule of values said one thing, the field said another, and the trail between them was spreadsheets, RFIs, and whoever still remembered the call. The crew that made the change was two projects gone. So someone rebuilt the history from memory and email search, the way it gets rebuilt on every job, and the number that came out was defensible and not quite the same as the one that went in. None of that is a failure of your people. **It is the unit of record.**
## What a cost code cannot tell you A cost code can tell you what was spent. It cannot tell you where. Every reconciliation rebuilds the where from memory, and every project pays that tax again. The voxel ledger is designed to change the unit: a cost event attaches to the place it happened — the room, the run, the rack row — and that place carries its own history. What sits at that voxel is one record — the design intent, the materials, the field verification — which we call BOX. The trail is not assembled afterwards because **the place is the trail.** When the duct run above the electrical room is re-routed, the cost of that change sits on that room, traceable to the decision that caused it. That changes what stays and what goes — and what stays is everything you already run.
One place, one trail.
## Your systems stay where they are This is not a reporting layer over the same spreadsheets. Your schedule of values, your RFI log and your coordination model stay where they are; the ledger binds their events to the building. Every decision, every cost event, every schedule slip is attributed to a voxel, and that voxel's history is the audit trail rather than a reconstruction of one. **What you already run keeps running.** What changes is that its events now have an address.
The schedule of values tells you what you billed. The voxel ledger is built to tell you what happened, where, and why — without anyone remembering which Tuesday call approved it.
What that buys is not a faster close-out on this project. It is a record that answers the where on every project after it, so the fifth change order is visible the week it happens and not the quarter after.
## Walk a change order on a real model Request a demo and follow one change from decision to voxel on a migrated data-center model. [Request a demo](/contact/)