Construction Control

Construction Control — Articles

Why Doesn't My Pay Application Match My Change Orders?

The pay application is built from the schedule of values. The change orders live in their own log. The tickets live in a third place. At billing time those records get compared — by you before you submit, or by the reviewer after — and the comparison is where the month slows down: a change order whose amount doesn't match the application, an approved amount that never made it onto the application at all, a pending figure that its own backup doesn't support.

Each mismatch has a mechanical cause. The numbers are produced at different times, from different documents: a change-order request written from an estimate, tickets that accumulate behind it as the work runs, an approval that lands at its own figure, and billing typed from whichever version was on the desk. The divergence sits in one of three places. Here is each one, and the check that catches it before the application goes out.

1. The pending COR doesn't match its own tickets

A change-order request is written early, from an estimate, before the work is done. Then the work runs — more hours than the estimate carried, an added material run, a second day on site — and the tickets accumulate behind the COR at their own total. Nobody updates the COR figure to match, because the COR is already written and the tickets are still arriving.

While that COR is pending, the figure under review is the COR figure, and its support is the ticket total. If the two disagree, the disagreement is what gets reviewed. The fix is a comparison, made while the COR can still be corrected: for every pending change-order request, add up the tickets linked to it and compare the total to the COR amount. Any difference gets explained or corrected now — not discovered after the COR has been billed at the unsupported figure.

2. The approved COR never reached the pay application

This mismatch is an omission, and omissions don't show up in any single entry. The change order was approved, the approval was filed, and the schedule of values never got a line for it. Every line that is on the application can be perfectly correct; the error is the line that isn't there.

Example: COR-06 is approved at $1,700. The approved change-order list includes it. The pay application's schedule of values has no line carrying the COR-06 ID. The work is done, the approval is documented, and the money is never asked for — and nothing in either document, read alone, looks wrong.

The check is a comparison of lists, ID by ID: take the approved change-order list and confirm that every approved COR ID appears in the pay application's schedule of values (column B on the workbook's Pay App SOV sheet). An approved ID with no line is approved work that isn't being billed.

3. The billed amount doesn't match the approved amount

Approval can land at a figure different from the one the COR was written at. The COR goes in at one amount; the approval comes back at a negotiated figure, lower or higher. Billing, though, gets typed from the version on the desk — which can be the original COR draft rather than the approval. The application then bills an amount that the approval doesn't support, or underbills the amount it does.

Example: COR-07 was approved at $765. The pay application bills $865 against it. Both numbers have paper behind them — the $865 from the COR as written, the $765 from the approval — and the $100 difference sits unexplained between two documents that were each correct when they were created.

The check: for every schedule-of-values line tied to an approved change order, compare the billed value against the approved value, line by line. They should be the same number. Where they differ, one of the two documents is out of date, and the approval is the one that governs.

The manual pass, in one sitting

The three checks above are one pass over the same three records, in this order:

  1. Pending CORs vs their tickets. Total the linked tickets behind each pending COR; compare to the COR amount.
  2. Approved COR IDs vs the pay application. Every approved ID present as a line on the schedule of values.
  3. Billed values vs approved values. Each billed line equal to its approved figure.

The pass depends on the tickets being linked to their change orders first — a ticket linked to no COR, and a COR with no tickets behind it, break the comparisons before they start. It also depends on the records being current: a comparison run against a stale COR log just certifies the stale numbers.

Where the workbook fits — and where it doesn't

That pass is a reconciliation: tickets to change-order requests to the pay-app schedule of values, compared in both directions. It is also the part we built a tool for. Construction Control is an Excel worksheet for use alongside your AIA G702/G703 that runs that reconciliation and flags seven exceptions by name: Duplicate ticket, Missing fields, Unlinked ticket, COR without backup, Pending COR vs ticket mismatch, Approved COR missing from pay app, and Approved COR vs billed value. The three mismatches above are the last three checks on that list. The Missing fields check covers a ticket's Date, Scope, Labor hours, and Loaded $/hour.

Be clear about the boundaries. One column on the pay-app side — column D, prior completed dollars — is typed in manually, so the workbook checks the numbers it is given, not numbers it gathers itself. It does not check G702/G703 totals. It does not approve change orders. And it does not make a GC pay.

One mismatch it cannot see at all: a change order billed before it was approved. EXAMPLE SCENARIO — NOT WORKBOOK OUTPUT: COR-09, at $2,900, billed while still pending. Each of the seven checks compares values, links, and fields; none of them compares billing against approval timing. It does not flag change orders billed before approval.

If you want the pass in printable form, our Pay App Pre-Submission Checklist is a free one-page PDF covering these comparisons. And if running them by hand is the part that eats your billing time, the workbook is the Construction Control Subcontractor Pay App Bridge. One-time purchase: $39. No subscription. Requires desktop Microsoft Excel.

The underlying principle is the same one behind every item on this list: a mismatch between the pay application and the change orders is cheapest to find while both documents are still on your desk — at the comparison, not after it.

Before your next application