Unbilled Change Orders: Who Catches the Change When It Happens in the Field

The problem: Extra work gets requested on site and performed the same day, and the only person who knows it happened is standing in a trench with no responsibility for billing it.

The solution: Make capturing the change part of the moment it is agreed to, by the person who agrees to it, so the request reaches billing while the customer still remembers making it.

A customer walks the site on a Tuesday and asks for something. Move the panel six feet. Add two receptacles. Core one more penetration while you have the equipment here. The superintendent looks at it, decides it is an hour or a half day, and says yes, because saying yes is what keeps a customer and because arguing about a small thing on a Tuesday is how a good relationship goes bad.

The crew does the work. That is the end of the event as far as anyone on site is concerned.

Everything that would have turned it into revenue was supposed to happen after that, somewhere else, by someone who was not there and does not know it occurred.

The failure is a handoff, not a form

Most contractors have a change order process. There is a form, or a module in the project software, and a rule that says extra work requires an approved change order before it proceeds. The process is not the problem. The problem is that the process starts at a point the work has already passed.

Look at where the information actually has to travel. The event happens in the field, at the moment of the conversation. The person present is the superintendent or the foreman. The person who can bill it is in the office. Between those two points there is a handoff, and that handoff has no owner.

Ask a contractor who is responsible for capturing a change that happens in the field and the answers conflict in a revealing way. The superintendent believes he flags it when it is significant, and significance is his judgment. The project manager believes the superintendent tells him, and often he does, on the phone, in a conversation about six other things. The coordinator believes she raises the paperwork when the PM asks her to. Nobody believes it is their job to notice one that never got mentioned, because noticing an absence is not a task anybody can be assigned.

So the change is not dropped by a person failing at their duty. It is dropped in the space between three people who each did what they understood their duty to be.

Why the small ones are the expensive ones

There is a filter operating here, and it works backwards.

A $40,000 change gets captured. It is too big to absorb, the customer expects paperwork, and everybody knows to stop and write it up. The process works exactly as designed on the changes where the stakes make people careful.

The $3,000 change does not. It is under the threshold where anyone feels the need for formality, it is faster to just do it, and writing it up costs the superintendent a phone call and an argument he does not want. So the process reliably captures the changes that were never at risk and reliably misses the ones that were.

Then the second filter runs. Time passes. If the request reaches billing three weeks later, it is now a conversation about work the customer half remembers agreeing to, with no signature, no photograph, and no record beyond one person's recollection. At that point the PM makes a commercial judgment, and the judgment is almost always to eat it rather than damage the relationship over $3,000. That decision is defensible each time it is made. It is expensive because it is made repeatedly and never counted.

What makes it invisible

Unbilled field work has a property that makes it uniquely hard to see: the cost side records perfectly and the revenue side records nothing.

The labor hours land against the job through payroll, because the crew was on the clock and coded to that job. The material comes off a purchase order that has the job number on it. Every dollar of cost is captured accurately. The revenue that should have offset it was never entered, because it was never invoiced, because it was never asked for.

The result is a job that shows lower margin than it should for a reason that appears nowhere. No report can flag a missing invoice, because nothing in the business ever knew it should exist. There is no exception to raise. There is only a job that came in a little light, on a project everybody remembers as having gone fine.

What capture at the moment looks like

The fix is not more discipline, and it is not a stricter policy, because the policy is already stricter than the behavior and has been for years. The fix is to make capture take less effort than not capturing.

That means the moment of agreement is the moment of record. The superintendent, standing there, opens his phone, photographs what was asked for, records ten seconds of what the customer wants, and it becomes a draft change against that job with the date, the location, and the person who asked. He has not priced it, approved it, or committed to anything, and that is deliberate: pricing is not his job and he will not do it. He has done the one thing only he can do, which is record that it happened, while it is happening.

From there the responsibility becomes explicit rather than assumed. The draft lands with the project manager as an item that must be resolved. It gets priced, sent, and tracked, or it gets deliberately written off, but it is never simply forgotten, because it now exists as an open item on the job and open items are visible. Automation is what keeps that true without anyone maintaining it: the draft is created from the field capture, the pricing request goes to the PM, the follow-up chases the unsigned ones, and a change still sitting unresolved after five days raises its hand.

The important shift is small and specific. One person now owns one action at one moment. Everything downstream is a consequence of that.

A look at a general contractor

Consider a general contractor doing about $11 million a year, 25 to 30 active jobs, three project managers, a project coordinator, and field crews under four superintendents. The change order process is real and documented. Large changes go through it correctly.

Suppose the owner takes six completed jobs and asks each superintendent one question: what did we do on this job that we did not bid. Not from the paperwork, from memory and from the daily logs. You would expect the list to be longer than the change order register on every one of the six, and you would expect the difference to sit almost entirely below $10,000 a ticket.

Extrapolated across the year, fifteen captured-nowhere changes at an average of $6,000 is around $90,000 of revenue that was earned and delivered and never invoiced. It is a better dollar than most, because the cost was already incurred and absorbed, which means nearly the whole ticket would have dropped to margin.

The likely response is not a new policy. It is giving four superintendents a way to record a request in thirty seconds without pricing it, making one person accountable for resolving every draft, and accepting that some will be written off on purpose rather than lost by accident. A contractor doing this would expect the register to get longer within a couple of months, and to hear the phrase "we already did that one" less often at closeout.

How to start

1. Ask the field, not the file. Walk six finished jobs with the superintendents and ask what was done that was not bid. Compare against the change order register.
2. Sort the gap by size. If the misses cluster under $10,000, your process is fine and your capture point is wrong.
3. Name the owner of the moment. Decide who is responsible for recording a change at the instant it is requested. If the answer is more than one person, it is nobody.
4. Strip the field step down to recording. No pricing, no approval, no form. A photo, a location, a date, and who asked.
5. Make an unresolved draft visible. Anything captured and not priced within a week should surface on its own, or it will quietly become a write-off again.

The takeaway

Work you performed and never billed is the cheapest revenue available to you, because you have already paid for it. It goes missing not because your people are careless but because the one person who witnesses the change has no responsibility for capturing it and the people who could capture it were not there. Move the capture to the moment and the person, keep it to thirty seconds, and make sure someone owns every draft after that. Start by asking six superintendents what you built that you never charged for.