A time-and-materials (T&M) ticket can describe real work, in full, and still go nowhere on a pay application. The labor is recorded. The work was done. Yet that ticket is not connected to the change order work it belongs with, and it is not carried into the billing in a way a reviewer can follow. It is present as a row of data, and stranded at the same time.
That is the problem EX-03, Unlinked Tickets, is about. This article explains that check in plain language: what a link is, why a ticket loses it, why a careful reader can miss the problem, and where EX-03 sits in a set of seven checks.
What a link does for a ticket
A ticket on its own is a record of work. A link is what places that record inside the rest of the packet. It ties the ticket to the change order side of the job, so the work on the ticket can be followed into the amounts put forward for billing.
With that connection, a reviewer can move from the ticket to the related change order record, and from there toward the pay application, and see that the pieces belong together.
Without it, the chain stops at the ticket itself. The ticket may be filled in, but there is nothing in the packet that it is attached to. It leaves the billing admin with a question the ticket alone cannot answer: where does this work belong, and under what was it approved to be billed?
Why tickets become unlinked
In paste-based billing, ticket data, change order data, and pay application data are handled as separate sets. The connection between them has to survive every paste, sort, and update between the field record and the finished packet.
A ticket can be pasted into a billing file while the change order data it refers to is pasted elsewhere, or is not pasted in at all. A ticket can be added late, after the change order list for that cycle has been assembled, so the new row arrives without the record it should sit under. A reference can be carried in a form that does not match the related record in the other set, so the two records sit in the same packet and still do not connect.
None of those steps has to look like a mistake when it happens. Each paste can look complete on its own. The missing connection becomes visible only when the sets are read together, as one packet, and each ticket is asked whether it is tied to something else in that packet.
Why reading the ticket does not reveal it
A person reviewing a ticket reads its content: the work description, the labor, the materials, and the fields that describe the work. Read that way, an unlinked ticket can look entirely ordinary. Nothing inside the row has to look wrong for the connection outside the row to be missing.
That is the central point of EX-03. The fault is not inside the ticket. The fault is between the ticket and everything else. A review that stays inside each record can pass over a missing connection again and again, because the thing that is missing is a relationship, not a word or a number in the row.
The reader asks what the ticket says. A check for unlinked tickets asks what the ticket is connected to. A packet can pass the first question and fail the second.
Where EX-03 sits in the seven checks
EX-03 is one of seven checks in the Construction Control workbook:
EX-01 Duplicate Tickets. A COUNTIF check on ticket IDs. If the same ticket ID appears more than once, the count shows it. Stated plainly: a renumbered ticket is NOT caught by this check, because a renumbered ticket carries a different ID.
EX-02 Missing Fields. An ISBLANK check, which looks for blank fields in the pasted data.
EX-03 Unlinked Tickets. The check covered in this article, which looks at tickets that are not connected to the rest of the packet.
EX-04 COR Without Backup. A SUMIF and ABS check that works with an ORPHANED_COR result, for change order records without backup behind them.
EX-05 is a totals comparison. It uses SUMIF totals. It is NOT a status match.
EX-06 Missing from Pay App. The billing gap check, built on Approved amounts and ABS variance, for approved work that is missing from the pay application.
EX-07 Billed Not Equal Approved. A check for amounts billed that are not equal to the amounts approved.
The separation matters. A blank field is EX-02, not EX-03. A duplicate ID is EX-01, not EX-03. A totals difference is EX-05, and a billed amount that differs from an approved amount is EX-07. EX-03 keeps its attention on one narrow thing: the connection, or the missing connection, between a ticket and the packet around it.
EX-03 is about linkage in the pasted data, as the data stands in the workbook. It does not decide whether work was performed well, whether a change should have been directed, or whether a reviewer will accept a packet.
How the workbook is used
The Construction Control workbook is $39. It is a macro-free workbook for desktop Excel. Data is brought in by pasting, using 4 CSV templates. There is no importer.
If you want to work on the record-keeping side first, start with the free guide to a change order log template:
https://ty-square-csv-preflt-2026-10.pages.dev/articles/change-order-log-template
A free checklist PDF is linked from the guide.
A ticket that records finished work but is connected to nothing is hard to bill from a packet. Putting the connection question on a checklist, as its own separate question, is how that stranded row gets found while the packet is still in your hands.
This is from Construction Control, maker of the workbook.
Top comments (0)