Change-order management is the process of capturing a change in scope on a construction project, pricing it, getting it approved, and billing it before the project closes out. A change order — often abbreviated CO — is a formal modification to the original contract: additional work, deleted work, a material substitution, a schedule change, or a condition discovered in the field that nobody could have priced at bid time.
Every commercial installation contractor lives on change orders. The original contract is the baseline; the change orders are where the real margin moves. A clean change order is the most profitable work a contractor does all year — the customer already trusts the crew, the crew is already mobilized, the price has less competitive pressure than the original bid. And change orders are also the single most reliably unbilled work in the trade. The money is rarely lost on the job site. It dies in the gap between when the work happened and when somebody remembered to write it down.
That gap is what change-order management is supposed to close. Most of the tooling contractors use makes the gap wider, not narrower — because the change happens in the field and the billing happens in the office, and the two run on different systems that don't talk.
What actually triggers a change order
On a commercial install, change orders come from a small number of recurring sources, and naming them is the first step to catching them. The first is discovered conditions — the crew opens a wall, pulls back a roof membrane, or scans a mechanical room and finds something the plans didn't show. Rotted decking under a re-roof, a panel that's already at capacity, conduit that has to be rerouted around structure that isn't where the as-built said it was.
The second is owner-directed changes — the customer or the GC asks for something different mid-project. More cameras at the loading dock. A different access-control reader at the executive entrance. Moving an AV head-end because the IT closet got reassigned. These are the friendliest change orders because the request is explicit, and they're still the ones that go unbilled most often, because the PM says "yeah, we can do that" from the truck and nobody writes a number down.
The third is design and coordination changes — an RFI comes back, a submittal gets revised, a trade above you moved their rough-in and now yours has to move too. The fourth is unit-price and quantity adjustments on contracts that bill by measured quantity rather than lump sum. Each of these is a different paperwork shape, and a real change-order workflow has to handle all of them without forcing the field to think about which category they're in.
Why the change order dies in email
The structural failure is almost always the same. The change happens in the field — that's where the work is. The person who sees it is a foreman or a PM standing on the roof or in the mechanical room. They know, in the moment, exactly what changed and roughly what it's worth. And the tool they have in their hand is a phone with a text thread and an email app.
So the change-order gets captured as a text to the office, or a photo with a caption, or a note the PM means to write up later. The office is running estimating in one tool, the project schedule in another, payroll in a third, and accounting in a fourth. Nothing forces the field note to become a priced change order, nothing forces the priced change order to get a signature, and nothing forces the signed change order to land on the next invoice. Every handoff is a place the change order can fall through, and on a busy commercial job there are four or five handoffs.
The result is predictable and it shows up at closeout. The PM goes to reconcile the job three months after the crew demobilized, finds six change orders that were done but never billed, and discovers that two of them are now too old to collect cleanly because the GC's pay application window closed. The work was real. The labor was paid — it ran through certified payroll like everything else. The margin just never made it onto an invoice.
What good change-order management requires
A change-order workflow that actually holds revenue has a small number of non-negotiable properties, and they all come down to closing the gaps between handoffs.
Capture has to happen where the change happens — in the field, on the device the foreman is already holding, in seconds, before the moment passes. If capture requires getting back to a laptop, capture doesn't happen. Pricing has to draw on the same assembly catalog and labor rates the original estimate used, so the change order is priced consistently with the contract and not re-guessed from scratch. Approval has to be fast and traceable — a signature from the PM and a counter-signature from the GC's representative, captured with a timestamp, so there's no he-said-she-said when the pay app gets reviewed.
And then the part everyone forgets: the approved change order has to flow into billing and into labor cost without anyone re-typing it. The whole point is that the signed CO becomes a line on the next invoice, and that the labor hours spent on the change get attributed to the change order rather than smeared across the base contract — because if you can't see what the change order cost you, you can't tell whether the change orders are actually making money or quietly subsidizing the customer.
Change orders versus residential supplements
It's worth naming a common confusion, because a lot of contracting software is built around the wrong one. On residential storm-chase and insurance-restoration work, the equivalent of a change order is the supplement — the contractor finds additional damage during demo, files the supplement with the insurance carrier, and the adjuster approves it before the work continues. That workflow is real, and the residential insurance-restoration tools built around it are the right call for that job. If your work is residential insurance restoration, supplement workflow is what you want, and Forge is not the tool for that — Forge is built for commercial installation contractors.
Commercial change orders run on a different mechanic entirely. There's usually no carrier in the loop. The PM signs from the truck, the GC's PM counter-signs the next morning, and the customer pays it through the next progress billing or pay application. There's no adjuster, no estimate-to-supplement back-and-forth, no carrier scope to negotiate. A workflow built for carrier supplements is an awkward fit for a commercial CO — which is part of why so many commercial change orders end up living in email instead, when the dedicated workflow doesn't match how the work actually moves.
How Forge handles change orders
Forge is the commercial contractor operating system built by Dominus Foundry — one AI-native platform that replaces the disconnected estimating, scheduling, CRM, documents, payroll, communication, and field-ops tools a commercial installation contractor would otherwise stitch together. We call the unified system the chest, and the reason change orders survive inside it is that there are no integrations to fall through. The modules share architecture, not API calls — what we call federation. The change order doesn't get handed from one vendor's tool to another's; it moves inside one system.
Change-order management lives in Treasury, the financial drawer of the chest — the same module that carries payroll, certified payroll and prevailing-wage filing, the recurring-revenue (RMR) ledger, and project billing. Because the change order is priced against the same trade assemblies the original estimate used, a CO is priced consistently with the contract rather than re-guessed. Because Treasury also owns labor cost and payroll, the hours a crew spends on a change order can be attributed to that change order, so the operator can see whether change orders are carrying margin or quietly leaking it.
The field-capture side runs through Forge's field ops and embedded communications — the dialer, SMS, call recording, and AI call summaries that live inside the same system rather than bolted on. The foreman who sees the change documents it from the field, on the same device, without switching tools. And where the change is a measured-quantity question — more roof area exposed than the plan showed, a longer cable run than the drawing implied — Hyperion, Forge's iPad and iPhone LiDAR spatial-scan instrument, turns an in-field scan into line-item quantities, so the change order is priced against the ground-truth geometry the crew walked through this morning rather than a number recalled from memory.
None of this changes the fact that change orders are work. The signature still has to be gotten, the GC's PM still has to counter-sign, the customer still has to pay. What changes is that the change order stops dying in the gap between the field and the office — because in one unified system, there is no gap. The work that was the most profitable and the most reliably unbilled becomes work that simply gets billed.
What it's worth getting right
Ask any commercial contractor what their unbilled change orders cost them last year and most can't tell you, which is itself the answer — if the number were visible, it would already have been collected. The change orders that get lost aren't lost because the work was disputed or the customer refused to pay. They're lost because the system that was supposed to carry the change order from the field to the invoice had a seam in it, and the change order slipped through the seam.
Change-order management, done properly, is not a feature you bolt onto a CRM. It's a property of having the estimate, the field capture, the labor cost, and the billing in the same place — so that a change captured on the roof at 9 a.m. is a priced, signable line item by lunch and a billed line on the pay application by the end of the cycle. That's the difference between a change-order workflow and a change-order graveyard, and it's the difference unified architecture is built to make.