Change orders: the paper trail that decides who pays

Change orders are where contract administration and payment administration collide. A CO modifies the contract sum for a specific line or set of lines. But the modification has to be tracked through the entire billing history: the original scheduled value, the approved CO amount, and the cumulative total for each affected line must all align with what's being billed this month. One missed entry and the financial picture on a line is quietly wrong for the rest of the project.

Pending vs. approved

The most common CO error in a pay application isn't mathematical - it's procedural. A contractor includes a pending change order in their current draw, billing against work that hasn't been formally approved. From the GC's perspective, the work is underway and the paperwork is a formality. From the owner's perspective, they're being asked to pay for a scope change that doesn't yet exist on paper. For a $100 million project where COs routinely run into six figures, getting the status right is a material risk control - not a clerical detail.

A pending CO billed as approved changes the cost basis for every subsequent application on that line. The error compounds.

The reconciliation that nobody does

At any point in a project, the sum of all approved COs on the register should equal the difference between the current contract sum and the original contract sum. In practice, COs are tracked in a spreadsheet maintained by the PM, pay applications are processed by the accountant, and the two documents drift apart over the course of the job. Reconciling them - checking that every approved CO on the register has been absorbed into the schedule of values and is being billed at the correct rate - is the kind of tedious, important work that is easy to skip when a draw deadline is looming.