How to track change orders without losing money

Where the money actually goes

Ask a contractor what change orders cost them and you get a story about a client who would not pay. Look at the records and it is usually one of these four, none of which is about the client being difficult.

• NEVER CAPTURED. The ask happened on site, the work got done, and nothing was written. There is nothing to bill and nothing to argue with.
• CAPTURED BUT NEVER PRICED. It is on a list as "extra tile work, TBC". Six weeks later nobody remembers the scope well enough to price it honestly, so it gets rounded down or dropped.
• PRICED BUT NEVER APPROVED. The number exists in an email. The client never said yes in writing and the work went ahead anyway, which turns an invoice into a negotiation.
• APPROVED BUT NEVER FLOWED THROUGH. Signed, agreed, and still not on the budget line it belongs to - so the line reads over budget, the sub contract reads over-billed, and the job’s margin is wrong in your own reporting.

The fourth one is the quiet killer, because everything looks handled. The client is billed, the money arrives, and your own numbers still say the electrical line blew its budget by eleven thousand dollars - so the next job gets estimated off a figure that was never true.

Capture at the moment of the ask

The only reliable capture is the one that happens while somebody is standing there. It does not have to be a form. It has to have four things: what was asked, who asked, the date, and a photo of the condition if there is one.

1. 1The moment the ask happens, write it down on the job - not in a personal notebook, not in a text thread.
2. 2Photograph what is there now. On a dispute six months later, the before photo does more work than the paragraph.
3. 3Say out loud, then and there: "that is outside the contract, I will price it and send it over." This one sentence prevents most of the arguments that follow.
4. 4Get it priced within a day or two, while the scope is still fresh and before the trade has moved on.
5. 5Send the price for written approval and do not start until it comes back.

Price it while you can still say no

A change order priced after the work is done is not a price, it is an invoice with a story attached. Before the work starts you have leverage and the client has a choice, which is exactly what makes the number credible. After it is built, you are asking somebody to pay for something they already have.

Price the whole impact, not just the labour and materials: the trade that has to come back a second time, the two days the schedule moves, the inspection that has to be re-booked. Those are real costs that are invisible on a line-item quote, and they are the ones that turn a "small" change order into a loss.

Approval that counts

Whatever your contract says about written change orders, what protects you in practice is a record that shows three things together: an amount, a scope, and an affirmative response from somebody with authority. An email reply saying "ok go ahead" under a quoted number does that. A signature on a form does it better. A verbal yes on site does not do it at all, however sincere it was.

Two practical rules. First, the approval must name the amount - "approved" under an email thread with three numbers in it is ambiguous by design. Second, approval and the record of the work are different acts: recording that a change happened is not the same as the client accepting it, and a system that collapses them into one step will eventually book an agreement nobody made.

Make it flow through to the money

This is the step that spreadsheets almost never get right, because it is three edits in three places and a person has to remember all of them.

The reversal half matters as much as the addition. A change order that is approved, folded into a budget, and then cancelled has to take its money back out of every one of those places. Anywhere this is done by hand, it is done once and remembered as done forever.

A tracking system that works, with or without software

If you are doing this on paper or in a sheet, these are the columns that earn their place. Anything else is decoration.

• Number and date raised - sequential, never reused.
• Who requested it, by name.
• Scope, in one sentence a stranger could understand a year later.
• Amount, and whether it is an addition or a deduction.
• Status: pending, approved, rejected, withdrawn - with the date it changed.
• Who approved it, and where that approval is recorded.
• The budget line it raises.
• The sub contract it raises, if any.
• The client invoice it went out on.

The last three are what turn a log into a control. A log with only the first six tells you what was agreed; it does not tell you whether the money ever arrived where it was supposed to go.

How SyteNav handles it

In SyteNav a change order carries the budget line it raises and, where relevant, the sub contract it belongs to. Approving it adds the amount to that line and folds it into that sub’s contract; un-approving, rejecting or deleting it takes the amount straight back out, because the budget figure is derived from the change order rather than copied from it. There is nothing to reverse by hand and no way to count it twice.

An approved change order that names neither a line nor a contract still counts in the job total, and the budget tab lists it under "Not on a budget line" with a picker to file it - because money in a total that is not on a row is exactly how a job stops adding up. And when a pay application refuses a line for being billed past its scheduled value, the words "change order" in that message open the form with the overage and the right line already filled in.