Change order tracking: closing the gap between field and accounting

The cost of a change order is not just the scope it adds. It is the time the information spends between the field and accounting, during which it is invisible to cost control.

On most sites, a change is triggered in conversation. A go-ahead is given verbally, then by text, then eventually by email. Someone starts the pricing. The approval takes a few more days. By the time the change order reaches accounting, three weeks have passed—and the work may be substantially complete.

Where the workflow loses control

The trigger is informal. Verbal and text go-aheads are not tracked in any system. Changes that are eventually accepted begin as private conversations between a site supervisor and a subcontractor or owner’s rep. If the conversation is not captured, pricing work begins without a formal record.

Pricing sits in disconnected files. A project manager assembles a change order estimate in a spreadsheet, pulling from previous bids, subcontractor emails, and supplier quotes. This work is not connected to the project management or accounting system. If the change is modified before approval, multiple versions circulate.

Approval confirmation loops back through email. Approval arrives in an inbox, gets forwarded, and someone manually updates the project budget and notifies accounting. Each handoff introduces delay and the risk that the update does not happen at all.

Accounting receives incomplete information late. The amount posted to the cost-control ledger often differs from what was estimated, because revisions happened in email and never made it to the formal record.

The core problem: same information, different places

Every change order involves the same data—description, scope, value, approval status, and the relevant project codes—entered into at least three places: the estimate, the project record, and accounting. Each re-entry takes time. Each creates a version that may diverge from the others.

A better workflow structure

A cleaner process has four stages:

1. Capture the trigger. A short structured form—submittable from a phone—records the change description, who requested it, the date, and the relevant project. This becomes the record that everything else references.

2. Route for pricing. The captured trigger routes to the estimator automatically, with the project context attached. No searching for the email thread.

3. Route for approval. The completed estimate routes to the owner or owner’s rep with a clear approval interface. Approved changes return a status that updates the project record.

4. Push to accounting. Approved changes push the relevant codes and value to the accounting system without re-entry. The cost-control ledger reflects approved changes within hours, not weeks.

The right implementation depends on the systems already in use—Procore, Sage, Viewpoint, or others—and what is missing between them. The goal is not to replace those systems. It is to connect them at the points where information currently moves through email, texts, and memory.

Related: which construction workflow to automate first and where margin is lost between site and office.

---

If change orders in your operation spend weeks moving through email before reaching accounting, describe the current process to us. We will map the friction and show you where a targeted connection could close the gap.