Why your change orders take two weeks to hit the books

The delay is almost never the accountant. It’s the four handoffs between the foreman’s photo and the invoice line.

Erica GarmanPrincipal, operations6 min read

The short answer

Change orders take two weeks to reach the books because the work sits in queues, not because anyone is slow. A typical change order crosses four handoffs - field capture, PM review, office data entry, accounting posting - and each one adds a wait state measured in days. Cutting the queue to a single source of truth that every other system reads from routinely takes the cycle from 12–14 days to under 48 hours.

Key takeaways

  • Queue time, not work time, is 90% of a change order's lifecycle.
  • Four handoffs is the industry norm; each adds 1–4 days of waiting.
  • Pick one artifact as the source of truth and make every system read it.
  • Measure days-to-post weekly - it moves before revenue does.

A change order starts as a conversation on a slab and ends as a line on an invoice. In most contracting businesses those two events are separated by four handoffs, three tools and at least one person who is on a roof.

When we map it on a whiteboard the pattern is always the same: the field captures it fast, the office waits for paperwork, and accounting waits for the office. Nobody is slow. The queue is slow.

Where the two weeks actually goes

We time-stamp every hop for a month. The work itself - writing the description, pricing it, keying it - adds up to about 40 minutes. Everything else is waiting.

Typical change order lifecycle, 14-day baseline
StageWork timeWait timeOwner
Field captures scope8 min0–1 daysForeman
PM reviews and prices20 min2–4 daysProject manager
Office keys into ERP7 min3–5 daysCoordinator
Accounting posts + bills5 min2–4 daysController

40 min

Actual work per change order

13.2 days

Median time to post

4

Handoffs between field and invoice

The three failure modes

  1. 01No named owner. When two people can do the step, neither does it today.
  2. 02Re-entry as the integration. Every re-key is an excuse to wait for a batch.
  3. 03Approval by inbox. Email is a queue with no visibility and no SLA.
Crew reviewing scope changes on a jobsite
Capture happens in minutes on site. Everything downstream is queue design.

“We didn't hire anyone or buy anything. We deleted two handoffs and change orders started posting the same week.”

VP Operations, 180-person mechanical contractor

The fix: one artifact, many readers

Choose the artifact that gets created first and closest to the truth - usually the field-captured change order with photos, scope and rough quantities. Everything else reads from it. Pricing appends, it doesn't recreate. Accounting posts from it, it doesn't re-type it.

Frequently asked

How long should a change order take to hit the books?
Under 48 hours from field capture to posted cost is achievable for most contractors. Best-in-class teams post same-day because pricing appends to the original field record instead of recreating it.
Do we need new software to fix change order delays?
Usually not. The majority of the delay is queue time caused by unnamed owners and duplicate data entry. Naming a single owner per step and eliminating one re-key typically cuts the cycle in half before any purchase.
What metric should we track?
Median days from field capture to posted cost, reviewed weekly. It's a leading indicator - it improves weeks before billings and cash collection do.
Erica Garman

Erica Garman

Principal, operations · Tie In

Keep reading

All resources →

Only get emails when it matters

Get the next field note

The jobsite is noisy enough. We keep your inbox clean and only send a short note when we publish something worth your time.