Nothing sours an owner-contractor relationship faster than change orders. Not because scope never changes — on commercial work it almost always does — but because of how the change gets handled: verbally approved, vaguely priced, and reconciled months later in a stack of disputed paperwork. We run it differently, and the system we run on makes the honest way the easy way.
A change order is a document, not a conversation
In our workflow, a change order is a formal document, the same as a contract or an invoice. When something changes — an owner request, a field condition, a spec revision — it gets written up, priced at the line-item level, and sent for approval before the work proceeds. Once approved, it updates the job’s approved price automatically, and that revised number becomes the basis for everything downstream: the budget we manage against and every invoice that follows. There’s one set of numbers, and both sides are looking at it.
The system flags the need before anyone has to argue
Because we job-cost live, a cost overrunning its budget line shows up in red the day it happens. That flag forces the question early: is this a legitimate scope change, or is it our problem? If the owner changed something or the field revealed a genuine unknown, it becomes a documented change order while the facts are fresh. If we simply missed it in our estimate, that’s ours to eat — we don’t bill you for our own miss. Either way, the answer gets settled in days, not buried until closeout.
Every invoice shows the running math
Our progress invoices can display three columns on every line: the approved price, what’s already been invoiced, and what this invoice covers. An owner reviewing a pay application can see exactly how the current bill relates to the total — including approved change orders — without requesting a reconciliation. On cost-plus work, the system goes further and shows cost and fee separately, so our compensation is visible rather than blended into the numbers.
The software offers settings to condense that detail down. We generally point the other direction. Detail is what makes a pay application verifiable instead of just plausible.
What honest change management looks like in practice
- No work proceeds on a verbal change. Document first, signature, then work.
- Every change order is priced at the line-item level, not as a round number.
- Approved changes update the contract value in the system immediately — no side ledger.
- Invoices show approved price, previously invoiced, and current billing on every line.
- Our own estimating misses are our cost, not yours.
Change orders don’t have to be adversarial. They’re adversarial when the process is loose. Tighten the process and they become what they should be: a clear, documented agreement about a change in the work — and one more reason the closeout goes smoothly.
Originally shared on Tread Connection — our community for contractors who run their business on JobTread.