How to Track Change Orders So the Work Actually Gets Billed

A crew hits an obstruction that wasn't on the drawings. The superintendent calls the owner's rep, who says keep going, we'll sort it out. The crew loses a day and a half working around it. Everyone on site knows it was extra. Three months later the progress claim goes out at the original contract value, the estimator who priced the extra has moved to another job, and the day and a half quietly becomes a gift.

Nothing dramatic happened. Nobody argued. The change just fell through a gap in the process, and on most jobs there are three gaps it can fall through: the change was never priced, it was priced but never approved in writing, or it was approved and then never made it onto an invoice. Every dollar of change order margin you lose goes out one of those three doors. Tracking is how you close them.

One log, and someone who owns it

The fix is not sophisticated. It is a single change order log per project, one line per change, and one named person responsible for keeping it current. Not "the project team." A person.

The log needs fewer columns than most templates suggest. For each change: a number, a one-line description, the date you identified it, the date you gave written notice, the quoted value, the current status, the approval reference, and the invoice it was billed on. That last column is the one almost every log is missing, and it is the one that makes the log worth keeping. A log that ends at "approved" tells you the paperwork went well. It cannot tell you whether you got paid.

Status should be a short, fixed list: identified, notice given, priced, submitted, approved, in dispute, billed, closed. If your log has changes sitting in "priced" for six weeks, that is not a tracking failure, it is a follow-up failure, and now you can see it.

Know which kind of change you're holding

Under CCDC contracts, which cover a large share of Canadian commercial work, there are two distinct instruments and they carry different risk. A change order is issued after the price and time adjustment are agreed: you quoted, they accepted, everyone signs. A change directive tells you to proceed with the work before the price is agreed, with the money sorted out later.

The distinction matters for tracking because a change directive is an IOU with no number on it yet. The work is authorized, so your crews are covered, but the value is still an open negotiation, and your records from the field are the only leverage you will have in that negotiation. Any change proceeding under a directive should be flagged in the log and should trigger daily cost tracking on its own cost code: labour hours, equipment hours, materials, tickets signed by the owner's representative where you can get them. If you wait until the negotiation to reconstruct costs from memory and fuel receipts, you will settle low.

Most contracts also set a window for giving written notice of a change or a claim, often measured in working days from when you knew about the condition, and the window is usually shorter than the pace of a busy project. Courts have enforced these clauses against contractors who did the work but sent the paperwork late. The exact number lives in your contract; the operational rule is simpler. Notice is free and silence is expensive, so the log's "notice given" date should never be blank for long.

No paper, no extra work

The most reliable way to lose change order value is to start extra work on a verbal okay. It feels cooperative in the moment. It converts your negotiating position from "agree on the price or the work doesn't happen" to "pay me what you think is fair for work you already have."

The field fix is a short written confirmation the superintendent can produce in two minutes: a text or email that says, as discussed, we are treating the obstruction at gridline C as a change, we will proceed on your direction and track costs, written confirmation to follow. That is not a contract document, but it is a dated record that both sides understood this was extra, written the same day, and it beats a recollection from six months later in any dispute. Site staff will actually do this if the template is sitting in their phone. They will not draft formal correspondence from a muddy pickup.

Tie the log to the billing cycle

A log that gets updated "when things calm down" is a diary, not a control. The way to keep it honest is to bolt it to something that already happens every month: the progress claim.

Before each claim goes out, the person who owns the log and the person who prepares the billing sit down for fifteen minutes and answer two questions. Which approved changes are not yet on an invoice, and why not? And which changes are stuck at the same status as last month? The first question recovers money directly. Approved-but-unbilled is pure leakage, work you fought for and then forgot to collect. The second question surfaces the quiet ones: the quote the consultant never responded to, the directive whose costs stopped being tracked when the foreman rotated off.

This rhythm matters more in BC right now than it used to. Prompt payment legislation has passed and is coming into force once the regulations land, and it will put invoices on statutory clocks, with defined windows to pay or formally dispute. Changes that live in email threads and site memories do not survive contact with that kind of regime. Changes that live in a numbered log with notice dates and approval references do.

Spreadsheet or software? Mostly the wrong question

Every search result for change order tracking wants to sell you a platform, and the platforms are fine. Linking approved changes straight into job costing and billing genuinely closes the unbilled gap, and on a large project with dozens of changes in flight, that integration earns its keep.

But the tool is downstream of the habit. A shared spreadsheet with the columns above, owned by one person and reviewed before every billing, will outperform an expensive platform that nobody updates. We have seen the reverse too: software bought to fix a tracking problem that was actually a responsibility problem, and the licence fee just made the gap more expensive. Fix the habit first. Then, if the volume justifies it, buy the tool that automates the habit you already have.

Where to start Monday

Pick one active project. Build the log from the contract file and the email trail, which will take an afternoon and will almost certainly turn up at least one approved change that never got billed. Assign an owner. Put the fifteen-minute review on the calendar the day before the next progress claim. That is the whole system.

If you would rather have a second set of eyes on it, this is the kind of thing Manara does. We look at how changes actually move through your jobs, from the site to the invoice, and set up controls your team will keep using after we leave. The first conversation is a free discovery call, and if the fix really is one spreadsheet and a calendar entry, we will tell you that.