Skip to main content
Home Solutions Approach About Blog
Book a call →
← All Articles
Construction & Trades

Unbilled Change Orders: How Contractors Stop Doing Extra Work for Free

The super agrees to move a wall. The electrician adds circuits the drawings missed. The roofing crew replaces rotted decking nobody knew was there. The work gets done and the job closes out.

Then nobody bills for it.

Unbilled change orders are one of the quietest leaks in construction and the trades. The labor and material costs are real, but the paperwork stalls somewhere between the field, the project manager and billing. By the time anyone notices, the PM has moved on and the customer remembers things differently.

The fix is not more software. It is a simple change order process where every change has an owner, a stage and a next step, from the moment someone in the field says "yes" to the day the money arrives.

Why change orders slip through

Most contractors have a change order form. The leak is everything around it:

None of this is about effort. The gap is that no one system and no one person owns the change from start to finish.

Eight things every change log entry needs

Whether you track changes in job-management software, a CRM or a shared spreadsheet, every change needs the same eight pieces of information:

  1. Job and customer — the project, plus who you bill (owner, GC or property manager).
  2. Change number — one running number per job so nothing gets counted twice or skipped.
  3. What changed and why — a plain description, plus the reason: owner request, design change, unforeseen condition or field direction.
  4. Who asked for it — the name of the person who directed the work, and the date.
  5. Proof — photos, a signed T&M ticket, an email, or a marked-up drawing.
  6. Price and status — the amount, and whether it is still an estimate or has been approved.
  7. Owner — one person on your side accountable for moving it forward. Usually the PM. Not "the office."
  8. Next action and date — "send pricing by Friday" or "follow up with the GC on Tuesday," not "pending."

A change without an owner or a next date is not in your pipeline. It is a favor.

Stages that match how changes actually move

Use a short, fixed list of stages so anyone can look at the log and see where the money is stuck:

StageMeaning
Field requestSomeone asked for extra or different work; logged, not yet priced
PricedCost and schedule impact worked up internally
SubmittedPricing sent to the customer; waiting on approval
ApprovedSigned or approved in writing
On billingAdded to the schedule of values or the next invoice / pay app
PaidPayment received for the change
Rejected / disputedCustomer said no, or the amount is in dispute; reason logged

Watch Submitted and Approved most closely. Changes stuck in Submitted are waiting on your customer. Changes stuck in Approved are waiting on you, and that is the most expensive delay because the work is often already done.

For help writing stage definitions your team will actually use, see CRM stage definitions.

Five field-to-office rules

Most unbilled change orders start in the first 24 hours. These rules close that window:

  1. Log it the same day. Any extra work directed in the field gets a log entry before the crew leaves site, even if it is just a photo and two sentences.
  2. Get a name and a signature. A signed T&M ticket or a confirming email from the person who directed the work beats a verbal "go ahead" every time.
  3. Check your contract's notice rules. Many contracts set a deadline and a required format for giving written notice of extra work. Make sure PMs know what yours say.
  4. Price within a set number of days. Pick a target your team can hit, and make the change log show anything that has gone past it.
  5. Hand off when people change. When a PM or super leaves a job, their open changes get reassigned by name before they go.

The weekly change log review

Thirty minutes a week, run by operations or the senior PM:

  1. Changes in Field request with no price yet — assign a date or kill them.
  2. Changes in Submitted past your follow-up window — call the customer, not just email.
  3. Changes in Approved not yet On billing — fix these first.
  4. Changes with no owner or no next date — assign both.
  5. Rejected or disputed changes — log the reason so you can spot patterns by customer or GC.

Before every pay application or invoice

Before any progress billing goes out, check three things:

Where a CRM fits

Your estimating software builds the number. Your job-management and accounting systems run the project and send the invoice. A CRM for contractors does a different job: it holds the customer relationship and the history behind it. That includes which GCs approve changes quickly, which customers dispute them, and how much change work each account brings in over time.

When leadership cannot answer "how much approved change work is not billed yet?" without calling three PMs, the systems are not talking to each other. See what revenue leakage looks like for the broader picture.

When the checklist is not enough

A change log and a weekly review will surface the leak. They will not fix systems that do not share information, or a closeout process that finds unbilled work only after the final invoice.

That is what Desert West Digital's construction and trades work starts with: following real jobs from bid to change order to invoice and showing where work gets done but not billed. See the construction and trades page for scope.

FAQ

What are unbilled change orders?

Unbilled change orders are extra or changed work that your crews performed but that never made it onto an invoice or pay application. Usually the work was approved verbally, priced late, or approved in writing but never added to billing.

How do contractors track change orders?

Use one change log per job with the same fields every time: change number, description and reason, who requested it, proof, price, status, an owner and a next action date. Review the log weekly and before every bill goes out.

Who should own a change order: the field, the PM or the office?

The field captures it, but one person, usually the project manager, should own each change from request to payment. The office or billing team adds approved changes to the invoice, but the PM stays responsible until it is billed.

Should change orders live in the CRM or in job-management software?

Pricing and project details usually belong in your estimating or job-management system, and invoices in accounting. The CRM is where the customer relationship and history live. The key is deciding which system owns which step, so nothing falls in the gap between them.

What should we do with work that was done but never approved?

Log it, gather the proof you have (photos, T&M tickets, emails), and submit pricing as soon as possible. Check your contract for notice requirements, and flag it so it does not disappear at closeout.

Ready to see where change work is slipping?

If approved changes are missing from pay apps, or nobody can say how much extra work is still unbilled, start with the CRM & Revenue Systems Audit — $3,500 fixed. Desert West Digital follows real bids, jobs and change orders from first inquiry to paid invoice in the systems you already use, and shows where work stalls, gets re-typed or never gets billed. You get written findings, a ranked fix plan and a recorded video walkthrough.

The full $3,500 audit fee is credited toward your retainer if you start within 30 days of delivery. It can be spread across your first three months. Unused credit has no cash value and ends if the retainer is cancelled.

Construction & trades overview → See the audit and retainer options → Book a free 30-minute fit call →

No prep required for the first call. Bring one job where change work went unbilled and one question about your change log that nobody can answer quickly. That is enough to talk through what is broken and what to fix first.