How to Track Construction Change Orders Without Losing Revenue

A change order is easy to recognize as paperwork and harder to manage as a revenue process. For a commercial subcontractor, the financial path does not end when a change is identified or even when a proposal is sent. The path is potential work → priced → submitted → approved → billed → paid.

If ownership cannot see where each open change sits on that path, the business may perform legitimate extra work while the financial follow-through depends on email, memory and periodic cleanup.

1. Give every change one record

Start as soon as a potential scope change is identified. The record does not need to imply that the customer owes the amount yet. Its job is to preserve the issue, the project context and the next action.

A practical record includes the project, change reference, short description, responsible internal owner, proposed or expected amount, estimated cost, current status and the dates that matter. If the amount changes during negotiation, keep the approved amount separate from the submitted amount.

2. Use status names that describe the financial stage

Status should tell ownership what has to happen next. A small set of stages is usually clearer than a large list: potential, pricing, submitted, approved, billed, paid and rejected or closed.

The key distinction is between submitted and approved. Submitted revenue is an exposure that requires follow-up. Approved revenue can appropriately flow into the revised contract value for the owner-level project view.

That distinction is one of the foundations of change-order tracking for subcontractors.

3. Put dates on the handoffs

Without dates, an open change order is just a list item. Record when it was identified, priced, submitted, approved and billed. Those timestamps let you measure aging and separate a normal waiting period from an item that deserves attention.

You do not need one universal aging threshold for every customer. Instead, define what “normal” looks like for your operation and contracts. When an item exceeds that expectation, surface it as an exception rather than asking the team to remember it.

4. Track financial exposure, not only count

Ten open changes do not necessarily matter more than two large ones. Ownership should be able to see the dollar value and, when useful, estimated gross profit attached to aging changes. That creates a better priority queue.

For example, an owner may choose to review all submitted changes older than the expected response window, then sort by gross-profit exposure. The system is not declaring that the amount will be recovered; it is telling ownership where attention is economically meaningful.

5. Separate approval from billing

An approved change can still leak operationally if nobody ensures it enters the next billing cycle. Treat approval as a handoff, not a finish line. The record should show whether the approved amount has been billed and who owns that step.

Once billed, the change becomes part of the accounts-receivable control process. The original change-order record can retain its history while the invoice follows the cash path.

6. Connect changes to project profitability

Approved changes should update the revenue side of the current job view. Potential or merely submitted changes should stay visible without silently inflating the revised contract value.

That gives project profitability a cleaner financial story: original contract + approved changes compared with the cost view the company actually manages.

7. Review exceptions, not every line

A good control system reduces review burden. Ownership should not have to read the entire change log every morning. Build exception views for conditions such as submitted items whose follow-up date has arrived, approvals older than expected, approved changes not yet billed and billed changes that have become overdue receivables.

This is the central StandardArc idea: visibility only matters if it creates action.

A simple weekly change-order review

1. Capture all newly identified changes and assign an owner.
2. Confirm every open item has a current status and next action.
3. Review submitted items by age and financial exposure.
4. Move approved items into revised project revenue.
5. Confirm approved changes have entered billing.
6. Follow billed changes into receivables until collected.

The contractual notice, documentation and approval requirements for a specific project still govern the rights of the parties. This framework does not replace those procedures. It creates an owner-level financial control path around them.

For the broader system, see Revenue Control for Commercial Subcontractors.