Send the client one page every billing cycle that lists every change order on the job — pending, approved and rejected — with the original contract, the approved changes and the revised contract total at the bottom. Do that from the first change to the last, and the final invoice holds nothing the client has not already seen added up. Most final-bill disputes are not about whether a change was approved. They are about changes the client approved one at a time and never saw as a sum.
Most guidance on change order log construction treats the log as an internal file — a spreadsheet the PM keeps so the office knows what is signed. That is half its value. The other half comes from the client reading it every month, next to the invoice. The construction change order process covers how a single change gets raised, priced and signed. This piece is about what happens to all of them together.
Why a client who signed every change is still shocked
Here is an illustration. A $412,000 remodel runs seven months, and over that time the client signs fourteen change orders. An added outlet run at $640. A header upgrade at $1,850. A tile allowance overage at $3,200. A relocated vent stack at $2,400. Then ten more like them. None feels large on the day it is signed. Each one was approved on a phone, in the driveway or in a reply to an email. Together they add $41,300.
The number in the client's head is still $412,000. It is the number from the contract signing, from the bank draw schedule and from the conversation at the kitchen table. Then the final invoice arrives, built on $453,300. The client does not dispute any single change. They dispute the total. The argument starts with 'nobody told us it was that much.' That is technically false and practically true.
Nobody on either side acted in bad faith. The builder documented every change. The client approved every change. What neither of them did was look at the running sum. So the first time it appeared was on the bill that closes the job — the payment the client finds easiest to withhold, at the point where they have the least goodwill left.
What goes on the log
Give each change order one row. Number the rows in sequence and never renumber them. The columns:
- CO number and date raised — CO-007 stays CO-007 even if it is rejected
- Description in plain words — 'Relocate kitchen vent stack 4 ft east to clear new island', not 'Plumbing revision'
- Cause — owner request, unforeseen condition, design change or allowance overage
- Status — pending, approved or rejected, with the date the status changed
- Amount — the priced figure, or 'pricing' if no price exists yet
- Schedule impact in working days, including zero
- Approved by — the name, and how: signed in the portal, signed on paper or confirmed by email
- Billed to date against that change
Under the rows, add a summary block that never moves:
- Original contract sum
- Approved changes to date
- Revised contract total
- Pending changes — the total exposure if every one is approved
- Billed to date, and the balance remaining on the revised total
The revised contract total is the line that does the work. The final invoice will be built on that number, so the client should have watched it change every month.
Why pending and rejected lines stay
Pending lines show the client what might be coming before it arrives. Say the log shows $9,800 pending in month four. The client can still drop the upgraded fixtures before they are ordered. Rejected lines are the record of a decision. They settle the conversation in month eight, when the client remembers agreeing to the wider pantry door. Delete a rejected change and that record goes with it.
Send it every billing cycle, with the invoice
If the client has to ask for the log, they will never read it. Attach it to every progress bill. Send it on the same day, in the same format, whether or not anything changed that month. If progress billing runs monthly against a schedule of values, the log goes out with each pay request. The revised contract total on the log should match the contract sum on the pay application.
- Close out the month's changes. Move signed ones to approved, mark the rejections and price anything still showing 'pricing'.
- Check the log's revised contract total against the contract sum on the invoice. If the two differ, fix it before anything goes out.
- Send the invoice and the log together, with one sentence on what moved — 'Two changes approved this month, $4,150; revised contract now $431,600.'
- Flag any pending change older than two billing cycles and ask for a decision by a specific date.
- Keep a copy of the version you sent. The log as of each invoice date is the record of what the client was shown.
That last step matters if the job ever ends in a dispute. The question will not be whether a change existed. It will be whether the client knew about it. A dated log sent with every invoice answers that question.
What changes once the client sees the sum
Decisions move earlier. A client who watches approved changes climb past $20,000 by month three starts asking whether the next upgrade is worth it. At that point the answer can still change what gets built. Without the log, the same conversation happens at closeout, when every dollar is already spent.
Allowance overages stop hiding. Clients forget overages more easily than any other change, because picking a finish felt like a choice, not a change. Give each overage its own line on the log, with the cause marked as an allowance overage. That ties it back to the number set at signing, which is where allowances in construction contracts are won or lost.
The final invoice becomes arithmetic. A client who has received eight logs has seen the revised contract total eight times. The final bill is just the last number in that series. If there is an argument at closeout, it is about workmanship or punch items — not about money nobody saw coming.
Where the log fails
The log only reports what is on it. These three gaps cause most of the failures:
- Changes that never got entered. A request made on site and done the same week never reaches the log, so it shows up on the final bill as a stranger. The fix is a rule: no work starts on a change until it has a CO number, even if it is only pending. Verbal change orders fail for exactly this reason.
- Pending changes that sit. A change that has been pending for four months has really been either approved by conduct or quietly rejected. The log should say which. Old pending lines are where the surprises collect.
- A log kept apart from billing. When the change log lives in one spreadsheet and the invoice lives in another system, the two totals drift apart. A client who spots the difference stops trusting both.
Suppose work is done on a change the client never approved, and it first appears as billed on the final invoice. The builder is now collecting on a decision the client never made. Get the signature, or carry the change as pending exposure on every log until you have it. Billing it for the first time at closeout is the most reliable way to turn a $3,000 change into a withheld final payment.
Keeping the log without a second spreadsheet
In BuilderSolve, each change order is a record with its status, amount, cause and approval history. An audit trail shows who changed what and when. The log is a view of those records, not a separate file, so the revised contract total updates as soon as a change is approved. The client sees the same log in the branded portal and approves or rejects pending changes there. Budget vs. actual picks up approved changes, so the office sees margin on the revised contract rather than the original. The change orders feature page shows how this works in detail.
Here is what it does not do. BuilderSolve reads QuickBooks one way. Invoices stay in QuickBooks, which remains the book of record. That means checking the log total against the invoiced contract sum is still a step someone has to perform. The AI assistant can draft a change order from a daily log entry that mentions extra work. A person still approves or rejects that draft before it reaches the log or the client.
Some offices do not have the hours to close out changes and send the log every cycle. In that case the BuilderSolve finance team does the work — change orders, AR and QuickBooks — priced against the role it replaces.
What to do before the next bill goes out
- On your largest active job, pull every change into one numbered list — the signed ones, the pending ones, the rejected ones and the ones only discussed.
- Add the summary block: original contract, approved changes, revised total and pending exposure.
- Send it with the next invoice, with a one-line note saying it will come with every invoice from now on.
- On the next job that starts, do the same from change one.
On a job already underway, the first log may lead to a hard conversation. It will be a smaller one than the conversation at closeout.
Common questions
What is a change order log in construction?
A change order log is a numbered list of every change on a job — pending, approved and rejected. Each line shows the amount, cause, schedule impact and approval date. A summary at the bottom shows the original contract, approved changes and revised contract total. Kept internally, it tracks what is signed. Sent to the client with every bill, it stops the final invoice from being a surprise.
What columns should a change order log have?
At minimum, a change order log needs these columns: CO number, date raised, plain description, cause, status, amount, amount billed to date, schedule impact in days, and who approved it and how. Under the rows, add a summary with the original contract sum, approved changes, revised contract total, pending exposure and balance remaining. Clients most need to see the revised contract total.
How often should you send a change order log to the client?
Send it with every billing cycle, on the same day as the invoice, even in months when nothing changed. Clients rarely read a log they have to ask for. A monthly log lets the client watch the revised contract total move in steps. The final invoice is then the last number in a series they have already seen, not a new figure.
Should rejected change orders stay on the change order log?
Yes. A rejected change records that the client was offered something and declined it. Deleting the line removes the evidence of that decision. That evidence is exactly what you need when a client later remembers agreeing to the work. Keep the CO number, mark the change rejected with the date and leave it in the sequence.
Does a change order log replace signed change orders?
No. The log summarizes change orders but does not authorize them. Each change still needs its own signed document showing scope, price and schedule impact. The log's job is to show the client all of those decisions together, with a running contract total. That way no single approval is ever seen in isolation.