The customer walks the job and says, “While you’re here, can you also do this?” The lead says sure. They talk through it. Maybe they agree on a rough number. The crew does the work, does it well, and the customer is happy.
Weeks later, the final invoice goes out. The extra work isn’t on it.
Nobody lied. Nobody was careless, exactly. Everybody knew the customer approved the extra work. That’s the problem. Everybody knowing does not get it onto the invoice.
What the owner thinks is wrong
“Somebody forgot to tell the office.” Usually true. But if it keeps happening with different people on different jobs, it’s not a memory problem. It’s a missing step.
Tracing the trip
A change order has to make a trip from a conversation to money. Here’s the path and the usual breaks:
- The customer asks. On site, by text, on a call to the owner’s cell. Already three different entry points.
- Someone agrees. Often verbally. Sometimes with a price, sometimes “we’ll figure it out.”
- It gets written down. Or it doesn’t. This is the biggest break. If the approval only lives in two people’s memories, it’s fragile from here on.
- It gets attached to the job. The office needs to know it exists, which job it belongs to, and what was agreed.
- The job budget changes. Extra work means extra labor and materials. If the budget doesn’t change, the job looks over budget for no reason, and nobody trusts the report.
- It reaches billing. Someone has to turn it into a line on an invoice, at the agreed price.
- The customer sees it and recognizes it. If the approval was clear, this part is easy. If it wasn’t, it turns into an awkward conversation months later.
Every step depends on the one before it. Lose it at step 3 and steps 4 through 7 never happen.
What I’d investigate
I’d take a few recent jobs and ask the people involved: was there extra work on this job? Then I’d look for it everywhere it should be: a written approval, the job file, the budget, the invoice. The pattern of where it disappears tells me what to fix.
I’d also ask the crew lead what happens when a customer asks for something extra. Not what’s supposed to happen. What actually happens. The answer is usually honest and usually useful.
What’s underneath it
There’s no moment where the field conversation turns into a record the office can act on. Field and office run on different channels. The field runs on conversation. The office runs on paperwork. Change orders live right in the gap between them.
What I’d change
- Capture the approval at the moment it happens. Simple. A short form on a phone, a text template, a photo of a signed note. What it is, rough price or “price to follow,” customer’s okay, date.
- Log it to the job right away. One place, not a text thread.
- Give it an owner. One person whose job is to make sure every logged change order reaches the budget and the invoice.
- Check it before the final invoice. A quick “any change orders on this job?” review before anything goes out.
What I’d leave alone
The crew’s willingness to say yes. Customers love a crew that can handle “while you’re here.” I don’t want to turn that into a bureaucratic fight. I just want the yes to leave a trail.
The tradeoff
There’s a small pause in the field to document, and some customers may feel it’s a little more formal. Most customers prefer clarity. Nobody enjoys a surprise line on an invoice, and nobody enjoys finding out later that the work they asked for was a “favor” that hurt the job.
The bigger point
This is one of the clearest places where work turns into money or doesn’t. The work happened. It just never finished the trip. Change orders are one of the pieces Job Cost Ready connects, alongside labor, materials and subs, so the job report reflects what actually happened on the job.
To start: pull your last five finished jobs. Ask whether any had extra work. Then see how many of those made it onto the invoice.
