Change Order Form vs. Ticket Backup: When a COR's Linked Tickets Total $0
A change order request can sit on the log with an amount, a status, and a place in the billing — and have nothing standing behind it. No ticket amounts in the billing data add up under it. When a reviewer asks the standard question — show me the backup — the data cannot point anywhere, because in the pasted records, the backup is not there.
This is a different failure from a missing ticket. The change order side of the packet looks finished. It is the space underneath it that is empty.
Why a COR ends up with nothing behind it
Change order data and ticket data usually arrive by different roads. The COR is entered from the signed change order form. The tickets come from the field, in batches, through exports and pastes of their own.
The two sets meet only if a ticket's link entry names the COR it belongs to. That meeting can fail quietly. Tickets get pasted under a different reference than the one the COR carries. A batch of tickets for the work is still sitting in an inbox when the COR goes onto the log. Or the tickets are in the file, but their amounts stand at $0 while pricing is still being worked out — present as rows, absent as dollars.
Each set can look complete on its own. The COR list is tidy. The ticket list is long. Read together, one question exposes the gap: for this COR, what do its tickets add up to?
What the EX-04 check actually does
EX-04 COR Without Backup is the check for this problem in the Construction Control workbook. Its mechanism is a sum, and it can be stated in full.
For each change-order request, the workbook uses SUMIF to add the totals of every pasted ticket whose link entry names that request. Then it compares that sum against the request's own amount. If the linked tickets total $0 while the request's amount is not $0, the request is flagged ORPHANED_COR, and the Exception Report counts the flagged requests and totals their amounts.
Here is the shape of it, with invented COR numbers and amounts for illustration:
| COR | COR amount | Tickets linked to it | Linked ticket total | Flag |
|---|---|---|---|---|
| COR-201 | $1,850 | 3 tickets | $1,850 | — |
| COR-202 | $2,400 | none in the data | $0 | ORPHANED_COR |
| COR-203 | $960 | 2 tickets, each $0 | $0 | ORPHANED_COR |
COR-201 is what backup looks like in data: the tickets under it add up. COR-202 is the empty case — no ticket in the pasted data names it. COR-203 is the case worth pausing on, and it leads directly to what this check does and does not see.
The limits, stated plainly
EX-04 tests whether linked tickets total $0. It does not test whether tickets exist.
COR-203 above has tickets. They are linked. They are named in the data. The check flags the request anyway, because their total is $0 — and that is correct behavior for the question being asked, which is about amounts standing behind an amount. A flag on a COR with tickets is not the check misfiring; it is the check reporting that, in dollars, nothing is behind the request yet.
Two more edges, so the flag is never over-read. A change-order request whose own amount is $0 is not flagged by this check, with or without tickets — there is no amount asking for backup. And the check reads the pasted billing data only. Signed ticket copies in a project folder, a superintendent's binder, or an email thread are outside the workbook. An ORPHANED_COR flag means there is no backup in the billing data; it does not claim no backup exists anywhere. The flag tells you where to go look — it does not do the looking, and it cannot judge whether backup you find is signed, complete, or acceptable to the reviewer who asked for it.
Read that way, the flag is a worklist, not a verdict: these are the requests that will stall the moment someone asks for their tickets, while the packet is still in your hands.
How EX-04 fits the seven
EX-04 is one of seven checks in the workbook. EX-01 counts duplicate ticket IDs by exact match — and stated plainly, a ticket renumbered under a different ID counts once and is not flagged. EX-02 flags tickets with Date, Scope, Labor hours, or Loaded $/hr blank — exactly those four fields. EX-03 flags a ticket with no change-order reference in its link column. EX-05 compares a pending change-order request's amount against the total of its linked tickets — an amount comparison, not a status match. EX-06 flags an approved change-order request with no billing line on the pay application's Schedule of Values — absence only; it does not compare amounts. EX-07 flags an approved change-order request whose billed-to-date differs from its approved amount.
The checks divide the packet by the kind of question being asked. EX-04's question is the backup question: what stands behind this amount?
Where to go from here
If you want the record-keeping structure first, the free guide to building a change order log template is here:
https://ty-square-csv-preflt-2026-10.pages.dev/articles/change-order-log-template
The free pay-application checklist is a separate listing, here:
If you want the checks themselves, the Construction Control workbook is $39 — a macro-free Excel workbook for desktop Excel with 528 formulas, including EX-04 and the six other checks named above. Data goes in by pasting from four CSV templates; there is no importer. It is a worksheet for use alongside your AIA G702/G703 — it does not replace them.
Disclosure: this article was drafted with AI assistance. It is from Construction Control, maker of the workbook.
Top comments (0)