Typed to Fit
17 November 2026
The subcontract on the middle school job runs 34 pages, and page 11 is the one that rewired your billing office: payment by monthly application against the schedule of values, submitted in the GC's payment system by the 25th.
So on the 23rd your clerk does something she does for no other customer. Your own system already priced the job's tickets the way it prices everything, one line per load. None of that can be sent. The GC doesn't take invoices on this job; he takes a pay application, and the pay application doesn't speak in your products. It speaks in his bid items. Your side knows 3/4 minus, base rock, screened fill. His schedule of values knows item 203.1, Aggregate Base, 4,100 tons at $14.25. Which of your products feed 203.1? She knows, mostly. The crosswalk lives on an index card taped to her monitor, written during a March phone call with your estimator. He built the quote that became the schedule, and he's off bidding next year's work.
In September the translation hits a wall. The tickets put cumulative base tonnage at 4,268. Item 203.1 holds 4,100, and the GC's system won't take a line past 100 percent of its scheduled quantity. She enters 4,268 and the line won't save. She has a day left, eleven other lines to finish, and nobody to ask. So she types the number the form will take, the application submits, the month closes, and 168 tons of hauled, signed-for base rock are now attached to nothing that pays.
Month end runs a second billing system
Here's what page 11 actually did: it made your office run two billing systems. The first is the one you own, where a ticket becomes a line and the lines become an invoice. The second belongs to the GC, where quantities accumulate against a fixed schedule, and your clerk is its only moving part. Every month she re-derives the job by hand: which tickets feed which item, what was billed through last month, what this month adds. No second reader, no written rule. The customer with the thickest contract gets billed through the thinnest process in the building.
The crosswalk is where it's softest. One bid item eats three of your products. One product splits across two items, base under the parking lot and base under the access road, same stone, different lines, divided by whatever the driver scrawled about where he dumped. The estimator settled all of this in March when he mapped his quote onto the architect's line items, and the settlement lives wherever he left it, which is usually nowhere. When the clerk's guess differs from his, tonnage lands on the wrong item. One line runs out early, its neighbor never fills, and both mistakes wear the same disguise: a pay application that adds up.
The trim only cuts one direction
Watch what the quantity cap does to errors, because it doesn't treat the two kinds equally.
Bill an item short and nothing happens. The system accepts 82 percent as happily as 96, the missing tons wait unflagged for a month-end that never comes looking, and the application sails through review.
Bill an item past its scheduled quantity and the system refuses, and the refusal lands on the wrong desk, at the worst hour, dressed as a formatting problem. An overrun on 203.1 means the field used more base than the drawings assumed. The extra tons were hauled and they're billable, and the paper that collects them is a change order, which your side must raise while the GC's project manager can still walk out and look at the road. Nobody told the clerk any of that. What she can see is a line that won't save and a deadline. So the quantity gets typed to fit, which is a write-down, issued at a keyboard by the politest person in the building, with no approval and no trace.
Say the job finishes at 4,487 tons against the 4,100 ton schedule: 387 tons, about $5,500 at the item price. Your own system shows the work as billed, because the invoice it printed internally was complete. The receivable never ages, because it was never born. The loss exists in exactly one place, the gap between what the tickets total and what the applications carried, item by item, and no routine in your office computes that number.
Your estimator may object, and he has a case: on a lump sum, the waste allowance was supposed to be in his number, and some overage really is yours to eat. Fine. Eat it on purpose. A write-down with a reason and a signature on it is a decision. The same dollars leaving through a capped field is just leakage with good posture.
flowchart TD
A["Job tickets: 4,268 tons of base to date"] --> B["Index card: which products feed item 203.1?"]
B --> C{"Pay app line 203.1: capped at 4,100 tons"}
C -- "clerk alone at the deadline" --> D["4,100 billed, 168 tons attached to nothing"]
D --> E["Closeout: overrun found, change order cold"]
C -- "monthly gap check in place" --> F["Overrun surfaces in September"]
F --> G["Change order raised while the job is live"]
Make the gap a number
Treat the pay app as the billing system it is and give it the two controls you'd demand of any other.
First, the crosswalk gets written down at job setup, as a table: every bid item, the products that feed it, the destinations that split it. The estimator signs it the same week the subcontract is signed, while his own mapping is still warm. That table is reference data, the same class of fact as a customer's rate, and it should outlive both the index card and the estimator.
Second, the reconciliation runs monthly, per item, cumulative: tons on tickets against tons in applications. Equal is clean. Tickets ahead means one of three things, each with its own owner. Loads waiting for next month's application is timing. Waste you agreed to absorb is a term, priced once, on purpose. Anything left is an overrun that needs a change order, and change orders spoil fast. So a refused line gets treated as a receivable event: logged the month it happens, handed to whoever can call the PM.
Termco's share of this is the arithmetic. Tickets get digitized as written, destination scrawl included. The product-to-item crosswalk lives in reference data per job, billing rules roll the cleared tickets up by bid item, and the totals your clerk types on the 23rd come off a list instead of out of a re-derivation. A ticket whose product maps to no item on its job gets flagged the day it's read. And once she notes what each month's application carried, the ticketed-versus-applied gap is a five-minute subtraction instead of a closeout surprise. The window, the books, the drivers: unchanged. If you'd like to see how your own paper rolls up, send 10-20 sample tickets from one pay-app job to hi@termco.ai and findings come back within 48 hours.
Either way, pull one finished schedule-of-values job tonight and run the subtraction: total the tickets by bid item, total what the applications carried, compare. The schedule was written in March, off plan quantities, by someone pricing a drawing. The tickets were written at the gate, off trucks, by someone watching the material leave. Where the two disagree, the difference isn't a rounding story. It's the part of the job the drawings didn't know about. And your office has been settling that disagreement in the customer's favor, one typed-to-fit quantity at a time.
More from the Termco blog.
November 16, 2026
The Rate Table Has No Yesterday
Old billing systems held one price per product, so a rate change rewrote history. Your increase week has leaked money every fall since go-live.
Read postNovember 15, 2026
Every Book Starts at One
Store-bought ticket books all start at 0001, so a missing ticket leaves no gap. Your serial audit may be checking a sequence that doesn't exist.
Read postNovember 14, 2026
Six Tons Lighter, Same Rate
Spring road postings cut every payload for eight weeks while per-ton rates stay flat. The pay cut is already written on your own scale tickets.
Read post