Track change orders across plans, contracts, and invoices

A change order is one of the few project events that touches everything at once: the design, the contract, the schedule, and the money. It usually survives as a line item and an email thread. The change gets agreed in the field, captured in a message, and entered as a number, and the link back to the affected plan detail and the cost code is left to somebody’s memory. Months later, nobody can cleanly say what the change altered or why the cost moved the way it did. The problem is almost never the change itself. It is the disconnection around it.

That disconnection has a price, and it compounds. Productivity beats plan on roughly 60% of projects when change stays at or under 5% of contract value, and in the same analysis, productivity never once beat plan once change crossed 20%.^[1] Change is not a side effect of building. It is the thing most likely to decide whether the job makes money, which is a strange thing to track in an inbox.

Why change orders go wrong

Walk a typical change from start to finish and you can see where the thread breaks. A field condition does not match the plans. Someone writes it up, often as an RFI. A clarification comes back. Scope moves. A number gets agreed and entered into the schedule of values, and a cost code gets charged. Each of those steps lives in a different place: a photo, a message thread, a marked-up detail, an accounting line. The change order at the end is a summary that has quietly cut itself loose from everything that produced it.

That break lands differently depending on where you sit. For an owner, it means initialing changes without the full story, trusting that the number reflects work that actually moved. For a builder, it means an impact that was never tied to the budget showing up late, usually at the worst possible draw, when retainage is already thin. For the architect, it means a change that may have wandered off from design intent with no clean record that it did. The contract has a formal change process for exactly these moments, with notice clocks and signatures.^[2] The process is sound. What it does not do on its own is keep the change wired to the plan, the clause, and the cost once the email chain scrolls off the screen.

Brad connects the change to the detail, the clause, and the cost

Brad reads the change order alongside the rest of your connected project, the way a project engineer would if they had time to read everything. It ties the change to the plan detail and CSI MasterFormat spec section it modifies, the contract language it implicates, and the cost code it lands on. The change becomes something you evaluate in context rather than a number you initial and hope about.

Because the project’s documents and conversations are already in one place, Brad can show the surrounding story without anyone reassembling it. The field condition that prompted the change. The RFI or clarification that backed it. The marked-up detail. The approval that closed it. The change order stops being an island and becomes the visible center of a thread you can actually follow, from the original conflict to the dollar figure in the schedule of values.

Cost impact that surfaces now, not at the draw

The expensive version of a change order is the one whose cost nobody connected until the money was due. Bad project data drove an estimated $88.69 billion of avoidable rework in 2020, about 14% of all rework that year, much of it the cost of decisions made against information that was stale, scattered, or simply lost.^[3] A change whose impact is tied to its cost code the day it is agreed is a change you can price against the budget while you still have room to act on it.

Ask Brad in plain language. “What’s the running cost of changes on the curtain wall?” “Which approved changes aren’t reflected in the last draw?” You get the list back with the affected detail and the cost code on each one, over the same email and text threads your team already uses. No new dashboard to log into, and no Friday spent assembling the change log by hand for Monday’s owner meeting. The schedule of values and the change record stay in agreement because they are reading from the same connected picture.

A traceable record that holds up at closeout and in a dispute

The connected thread is what saves you a year later, once memory has gone soft and the paperwork is all you have. Someone asks why a detail got built the way it did, or whether the added cost was ever authorized. With Brad, the originating condition, the RFI, the cited clarification, the change, and the approval are already sitting together. No reconstruction job, no folklore about what was decided around April.

This is not a small benefit. The most common cause of construction disputes is a party failing to understand or comply with its contract obligations, and those disputes are not cheap to lose. A sourced, dated change trail, each change tied to the clause it implicates and the approval that closed it, is the difference between a defensible timeline and a room full of people arguing from memory.^[4] The same record that makes a draw package easier to assemble is the record that holds when the change gets questioned in earnest.

Where Brad stops and your process starts

Brad connects and surfaces change order information from your project’s documents and messages. It does not replace your contract’s formal change process, your accounting system of record, or the contractual notice clock you still have to mind. It makes all three run from a connected, verifiable picture instead of a pile of forwarded emails. A person owns every approval and every dollar figure. Your project’s content stays yours, and each workspace is walled off from every other one. If you have specific requirements about how change order and cost data get handled or retained, ask us and we will walk you through exactly how it works.

You will not stop changes from happening; building is a sequence of them. What you can change is whether each one stays connected to the detail it altered, the clause it implicates, and the cost it carries, or floats off as a number you initial and hope about. Track the connection, not just the line item, and the change order stops being the thing you reconstruct under deadline.