How to Set Up a Construction Change Order Process

Ask a construction owner where their margin went and you will hear the same answer more often than any other: work that got done and never got billed. A construction change order process is the system that stops that, and most companies do not have one. They have a habit, which is different, because a habit only works when the person who has it is standing there.

The short answer

A construction change order process is a written sequence for how a scope change moves from request to approval to invoice. It needs four things to work: a single person authorized to approve changes, a written record created before the work starts, a price attached at the moment of approval, and a link into billing so the change cannot be finished and forgotten. Companies leak margin when any one of those four is missing.

Key Takeaways

• Unbilled change orders are the most common source of margin loss in construction, and they are entirely preventable.
• Verbal approvals are not approvals. If it is not written before the work starts, you are betting on someone's memory months later.
• One authorized approver. Multiple approvers means no approver.
• Price the change at approval, not at completion. Pricing after the fact is negotiating from the weakest position you will ever be in.
• The process must connect to billing automatically, or approved changes still go uninvoiced.

Why this leak is so hard to see

Change order loss does not show up as a line item. It shows up as jobs that came in below the margin you estimated, spread across the whole portfolio, with no single project obviously to blame.

The sequence is always the same. A client asks for something on site. Your project manager, who is trying to be responsive and keep the job moving, says yes. The crew does it. Three weeks later somebody asks whether that was billed and nobody is certain. The PM remembers agreeing to it. The client remembers it differently. The work is already done, so you either eat it or start an argument you are unlikely to win.

Multiply that by every job. That is the leak, and it is why owners who tighten pricing still do not see margin improve. The pricing was never the problem.

The four requirements

One authorized approver. Decide who can say yes to a scope change and make it exactly one role, ideally with a dollar threshold above which it escalates to you. When three people can approve changes, what actually happens is that nobody owns the outcome and each assumes another handled the paperwork.

Written before work starts. This is the hard one culturally, because it feels like friction with a client who is standing right there. It is also the only part that matters legally and practically. A change order form, an email confirming scope and price, or an entry in your project software all count. A conversation does not.

Priced at approval. Whatever your markup convention is, apply it at the moment of approval. Pricing later means pricing after the client already has the work, which is the weakest negotiating position that exists.

Connected to billing. Approved and documented is still not invoiced. There has to be a mechanical link so the change appears in the next billing cycle without anyone remembering to move it there.

| Failure point | What it looks like | The fix |
|---|---|---|
| No single approver | Everyone says yes, nobody documents | Name one role with a dollar threshold |
| Verbal approval | "They told us to do it" | Written confirmation before work starts |
| Priced later | Negotiating after the work is done | Price attached at approval |
| No billing link | Approved, completed, never invoiced | Change orders flow into the billing cycle automatically |
| No log | Nobody can say how many are open | One running log per project |

The minimum viable version

You do not need software to start. You need a form and a rule.

1. The form. Project, date, who requested it, what changed, price, schedule impact in days, signature or written confirmation. Half a page.
2. The rule. No changed work begins until that form is confirmed. No exceptions, including for good clients, especially for good clients.
3. The log. One running list per project of every change order, its status, and whether it has been billed. Reviewed weekly.
4. The escalation. Anything above your threshold comes to you before it is approved.

That is the whole system. It fits on one page and it can be running by Friday. Software makes it faster later, but a company that cannot run this on paper will not run it in software either.

The schedule impact line nobody fills in

Most change order forms have a field for schedule impact and most of them are left blank or filled with a guess. That blank is where the second half of the loss lives.

A change that adds four days is not just a price. It pushes every downstream trade, potentially into overtime, and it moves your completion date, which may have liquidated damages attached to it. If you are not capturing schedule impact at approval, you are absorbing delay cost you agreed to without knowing it.

Make the field mandatory. If the honest answer is "we do not know yet," write that, and write when you will know.

How this connects to everything else

A change order process is a measurement system before it is a paperwork system. It tells you what you actually built versus what you estimated, which is the input to every other number you care about.

If job costing is where your margin visibility lives, change orders are the largest single variable feeding it. And if your team cannot execute a simple written rule consistently, that is usually an accountability structure problem rather than a process problem. Those two pieces are covered in construction KPIs every owner should track and how to build a construction org chart that works.

The cash side matters too, because an approved change order that bills next month is still cash you have already spent. Construction cash flow: why profit is not cash covers that gap directly.

For contract language, the American Institute of Architects publishes the standard construction contract documents most change order clauses are built from.

Rolling it out without a revolt

Field teams resist this, and their reason is legitimate: it feels like it slows down a client relationship they are managing in person. Two things fix that.

First, make it fast. If your form takes ten minutes, it will be skipped. If it takes ninety seconds on a phone, it will not.

Second, be explicit about what the process protects. It protects the PM from being blamed for a margin miss they did not cause, and it protects the client from a surprise invoice at the end. Framed as protection, it lands very differently than framed as compliance.

Give it sixty days and then look at how many change orders were logged versus how many you would have guessed. That gap is the number that ends the debate.

Where this gets solved faster

Most owners implement a version of this, watch it decay in three months, and conclude the team is the problem. It usually is not. It is that nobody was holding the standard once the owner stopped watching.

Real Construction Owners Mastermind exists for exactly that layer of problem. Foundations for newer companies, the Mastermind for owners in the $1 to $3 million range, and Champion for one-on-one work with Justin at the eight-figure level. Accountability over self-study, because self-study is what got most of these processes abandoned in the first place.

Book a complimentary business conversation and we will look at where your margin is actually going.