It Went in the Notes Field

Ticket 5583 came home from the Fairview job with a line of driver's handwriting across the bottom: "2nd stop on Fairview, dumped half at the shop, add stop fee." In 1998, that sentence was worth $40. The clerk who priced the ticket read the whole ticket, because pricing a paper ticket means reading it, and the stop fee went on the invoice between the tons and the tax.

In 2017 a ticket just like it meets the system you bought in 2015. The clerk keys the customer into the customer field, the product into the product field, 22.6 tons into the quantity field. Then she gets to the handwriting. There's no field for a second stop. There's no code for a stop fee, and she can't create one; the configuration screens belong to whoever set the system up. So she does the diligent thing, the thing the trainer actually suggested: she types the driver's sentence into the Notes box, word for word.

The invoice engine runs that night. It reads customer, product, quantity, rate. It multiplies. It does not read prose. The stop fee, faithfully recorded, bills nothing, that month and forever.

The box where the schema gave up

Nearly every operations system sold to quarries, elevators, and hauling outfits between 2000 and 2020 had the same two-part anatomy. Part one was the schema: the vendor's idea of a load, expressed as boxes. Customer, job, product, quantity, unit, rate. Part two was a single free-text field at the bottom, called Notes.

The schema was an opinion about your work. The Notes field was the vendor conceding, quietly, that the opinion was incomplete. Whatever the day produced that the boxes couldn't hold went there. Pull the notes out of any of these systems and you'll read your own operation talking to itself: "material only, they hauled it." "Per Dave, winter rate till April." "Brought back 3 tons, credit next load." "Gate code 4411." "Add $40, second stop."

Sort that list. Some of it is memo traffic, gate codes and directions, harmless wherever it lives. The rest is money. Charges, credits, rate changes, quantity corrections. Instructions about dollars, typed into the one field guaranteed to be invisible to the invoice engine.

Here's the claim your software-minded friends will fight: in that generation of system, every dollar amount in the Notes field is a billing failure by definition. Not evidence of one. The thing itself. Anything the system could bill had a field, so what collected in Notes was precisely the work the schema couldn't price. The field was the system keeping a log of its own defeats, in your clerk's typing.

Stored is not billed

The paper margin and the Notes box look like the same thing, and the difference between them is the whole argument.

A margin note on a carbon ticket got read for a structural reason, not a virtuous one. Pricing the ticket was a human act: an eye passed over the entire page, because the page was the unit of work. The note didn't need a field. It needed a reader, and the process guaranteed one.

The Notes field broke that guarantee while looking like it kept it. Typing the note felt like recording it, and it was recorded, which is exactly what made the field dangerous. A clerk with nowhere at all to put the sentence would have waved the ticket at somebody; the gap would've been loud. Notes made the gap silent. The sentence had a home, the screen accepted it, the record looked complete. Everyone's diligence was absorbed by a box that connected to nothing.

Say your trucks produce three money-notes a week. Call the average $55. That's about $8,500 a year typed into storage, by your most careful person, feeling thorough the whole time.

The sting arrives later. Two years on, a customer disputes an old invoice and somebody finally searches the notes. There it all is, in your own records: the credits you owed him that never posted, the fees you earned that never billed, each one time-stamped. The field proves you knew. A margin note that never got keyed is at least a mystery. A note typed in and unbilled is documentation that your office recorded the charge and then didn't make it.

flowchart TD
  A["Ticket 5583: 'add stop fee' in the margin"] --> B{"Who reads the whole ticket?"}
  B -- "paper era: the pricing clerk" --> C["$40 stop fee on the invoice"]
  B -- "2015 system" --> D["Fields keyed, sentence typed into Notes"]
  D --> E["Engine bills tons x rate"]
  E --> F["Note stored, never billed"]

The rebuttal, and what it misses

The defense writes itself, because vendors wrote it for years. Train the clerks to add a line item instead. Add a custom field for stop fees. The notes are searchable; run a report.

Each answer fails in the same place. The line item needs a code, the code needs the configuration console, and the console belonged to the vendor's consultant or to whoever sat through admin training, if she still works there. The custom field just moves the boundary: build a stop-fee field and next month the note says "waited on the paver, add an hour," because the work produces one-offs faster than any schema grows. And the report assumes someone reruns it, every cycle, forever, which is another unread notes field with a print button.

Picture the owner at a 2016 demo pointing at the Notes box and asking who reads this. The vendor's answer, some version of it's all searchable, meant nobody. The owner who heard that and kept his carbon books took years of teasing for it, and kept something the buyers lost without noticing: a process where the page is the unit of work and the margin always finds an eye.

The margin is input now

That bet has paid off, because the direction of conformance flipped. Software can now read the ticket the way the driver wrote it, margin scribble included, instead of accepting only what fits in boxes and warehousing the rest. That's the posture Termco is built on. Each ticket gets digitized as written. The recurring notes stop being prose and become billing rules, a stop fee when the ticket says second stop, a credit when it says returned, with the rates and the who-gets-what held in reference data instead of in Dave's phrasing. A ticket carrying writing that no rule covers gets flagged as non-compliant for a person to price, which is what the margin always deserved: a reader, not a box. Invoice totals assemble from tickets that cleared. Nothing changes in the truck or at the window; the handwriting was never the problem.

You can size your own notes field tonight. If you ran one of these systems, export a season of notes and read two hundred, sorting memo from money. Price the money pile. If you stayed on paper, flip through last month's book, mark the tickets with writing below the quantity line, and check each one's invoice for whether the writing made it on. Either way, if you'd like a second reader on the pile, send 10-20 sample tickets to hi@termco.ai, the scribbled-on ones especially, and findings come back within 48 hours.

The driver did his job on ticket 5583. He recorded the second stop in the one place he had, the ticket, and his sentence survived every system it passed through. What it never found again, after 2015, was someone whose job was to read it.