Why Do Your Change Orders Never Make It Onto the Invoice?
Q: How do I stop losing money on unbilled change orders in my remodeling business?
Change orders go unbilled because the change happens in the field and the invoice is built in the office, with nothing carrying it between. Fix the handoff, not memory: add a capture step that turns a verbal yes on site into a written, priced, logged change before the crew starts the work.
Because the change happens on the job site and the invoice gets built in the office. Nothing carries the change from one place to the other. That gap is where the money falls out. It is a handoff problem, not a memory problem. Fix the handoff and the billing fixes itself.
Most owners try to fix this by telling the crew to "remember to write it up." That never works. You cannot fix a broken process with better intentions. You fix it with a capture step that turns a verbal yes in the field into a written, priced, logged change before the crew touches the work.
A change order is a profit leak nobody schedules
Scope creep is the slow version of this leak. The client asks for one small thing, then another. Each one feels too small to bill. By the time the job is done, the extra work added up to real money, and the contractor never saw it happening. The Contractor Success Forum calls this exact pattern out: the scope drifts, and accepting the changes to be "the good guy" is a top reason builders are not profitable every year (Contractor Success Forum).
The fast version is the one that gets approved and still never gets billed. Siteline, a construction billing platform, names the cause plainly. The field team does the extra work but never tells the office in time, so the change order never makes it onto an invoice (Siteline). The work got done. The cost got eaten. Nobody decided that on purpose.
Why the change never reaches the invoice
Walk the path a change takes. A client points at a wall on Tuesday. Your lead says "yeah, we can do that." The crew frames it Wednesday. The invoice goes out three weeks later, built by someone who was never on that job site and never heard about the wall.
The verbal yes lived in one person's head. It never got written down. It never reached the person who bills. The handoff had no rails, so the change fell off the track. This is not a people problem. Your crew is good. The information path is broken.
The three-step capture system
You do not need software for this. You need a documented step that every change passes through, the same way every time. Map it on paper first. Run it by hand on the next ten changes. Then, and only then, point the simplest tool at the proven steps.
Step 1: Capture it in the field, same day, one channel. The moment a client asks for something outside the contract, it goes into one place. A shared note, a job-management entry, a photo with a caption. Not three different text threads. One channel the office checks. The rule for the crew is simple: if it was not in the contract, it gets captured before you build it.
Step 2: Price it and write it before the work starts. No work on a change until it is written and priced. This is the step that protects the margin and the relationship at the same time. The client sees the number before the saw comes out. Nobody argues about a price after the work is done, because the work did not start until the price was agreed.
Step 3: Log it where the invoice gets built. The written change lands in the same place the final invoice pulls from. Now the person billing cannot miss it, because it is sitting in their workflow, not in a text thread on someone's cracked phone screen.
Three steps. Capture, price, log. The change cannot disappear because every step hands it to the next one on purpose.
Decide who can say yes, and how it gets written
Your system needs one more rule: who is allowed to approve a change. A construction attorney group puts the legal version of this best. The best defense against scope creep is a contract that spells out who can authorize changes and how they must be documented (Bean, Kinney & Korman).
Put that in your contract and your field process. One or two named people can approve a change. Every change gets written before work starts. Now a verbal approval from a client to a framer in passing does not commit you to free work. It routes to the person who can say yes and write it up.
If your change orders live in verbal approvals and text threads, that is a documentation gap with a known fix. Book a systems consult at gofirstconsulting.com and we will map your change-order path in 45 minutes and show you where it leaks.
The math on one missed change a job
Run the arithmetic on your own numbers. Say you miss one change worth $1,500 on a job. Say it happens on half your jobs. Say you run 20 jobs a year. That is ten missed changes, $15,000 a year, walking out the door on work your crew already performed.
That is illustrative math, not a claim about your shop. Plug in your real change value and your real job count. The number is almost always bigger than owners expect, because the small ones never felt worth chasing, and the small ones are most of them.
Build the system once, keep the margin forever
You will not remember to bill change orders by trying harder. You will bill them by building a path that carries every change from the field to the invoice without depending on anyone's memory. Map it, test it by hand, then run it the same way on every job.
That is the GO First way to fix any leak. Document the process first. Prove it works with a clipboard. Then find the simplest tool to run it. The tool is the last step, not the first.
Questions builders ask about billing change orders
What is the single biggest reason change orders go unbilled? The field-to-office handoff. The change gets approved on site but never reaches the person who builds the invoice (Siteline). Capture it in one channel the day it happens and that gap closes.
Should I bill small change orders or let them go to keep the client happy? Bill them, written and priced before the work starts. Letting small changes go is how scope creep quietly eats your year (Contractor Success Forum). A client who sees the price up front rarely fights it.
Do I need software to capture change orders? No. Map the capture, price, and log steps on paper and run them by hand first. Once the process works, the simplest tool that matches it is enough. Software on top of a broken process just breaks faster.
How do I stop verbal approvals from committing me to free work? Name in your contract who can approve a change and require it in writing before work starts (Bean, Kinney & Korman). A framer hearing "just add it" is not an approval until it routes to the right person and gets written.
If your change orders keep slipping through the cracks, that is a process you can fix this month, not a personality flaw on your crew. Book a systems consult at gofirstconsulting.com and we will map the fix together.
By Grant Fuellenbach, Founder of GO First Consulting.