By Sagar Shankaran, Founder of CallSphere
Handwritten time-and-material tags get retyped, disputed, or lost. How 2026 document readers get them into the change order log inside the notice window.
Key takeaways
Ask your project managers at the Monday staff meeting and watch what happens. Somebody says "none," somebody says "a few," and the honest one says he found four in the console of the F-250 when he cleaned it out for the auction. Each of those four is a signed time-and-material tag for work your people or your subs actually performed, which never became a potential change order, which means it was never billed and never will be.
The tag itself is a half-sheet carbon form. The sub's foreman writes the date, the sub name, a description like "cut and patch slab at CL 4 for revised sanitary, per field direction," four names with hours, an excavator with hours, and a materials line. Your superintendent signs it at the bottom over the words "signed for hours and materials only, not for entitlement." Then it goes in his shirt pocket, then the truck, then — if you are lucky — a photo text to the project engineer on Thursday.
Everything downstream of that pocket is retyping. And retyping is where the money leaks.
Every contract on your board has a notice provision. Under the AIA A201 general conditions you get 21 days from the event to give notice of a claim. Plenty of owner-drafted contracts cut that to ten days, and public work sometimes to seven. The clock starts when the work happens, not when your accounting department finds the tag.
So the tag has a shelf life. It has to become a line in the potential change order log in Procore, then a change order request to the owner's representative with backing — the tag itself, the daily field report that corroborates it, the labor rates from the subcontract exhibit, the equipment rate sheet — inside the window. Miss the window and you are not arguing about price. You are arguing about whether you gave notice, which is an argument you lose.
The tag is not the only paper doing this. The same week, your contract administrator is keying subcontractor certified payroll off scanned WH-347 forms into LCPtracker, chasing ACORD 25 certificates whose additional insured endorsement is a scanned rider with initials in the margin, and matching concrete batch tickets against the pour log.
flowchart TD
A["Foreman writes the T&M tag at the pour"] --> B["Super signs for hours, photographs it at the tailgate"]
B --> C["Reader pulls sub, cost code, names, hours, equipment, sheet reference"]
C --> D{"All twelve fields legible and inside the notice window?"}
D -->|No| E["Kicked back to the super's phone, missing field circled"]
E --> B
D -->|Yes| F["Draft PCO created in Procore with the photo attached"]
F --> G["PM decides entitlement, which the reader never does"]
G --> H["COR to the owner's rep before the 21 days run out"]
Run nine active jobs and you will see something like 140 tags a month across all of them. Each one gets keyed by a project engineer or contract administrator into the PCO log: sub, date, cost code, description, four to six names, hours per name, equipment and hours, materials, tag number, and the reference to the RFI or ASI that caused it. Call it twelve fields.
Hear it before you finish reading
Talk to a live CallSphere AI voice agent for home services in your browser — 60 seconds, no signup.
Keying error rates on handwritten source documents sit around one percent per field in most clerical work. At twelve fields, that means roughly one tag in nine leaves the desk with at least one wrong entry. A wrong hour count is what the owner's rep circles in red, and the change order request comes back for backup, and now the twenty-two-day collection cycle you planned turned into fifty.
Then there is the tag that never arrives. Four percent is a fair estimate for a busy GC — the ones in the truck console, the one the foreman wrote on the back of a delivery ticket, the one photographed so badly that nobody could read the equipment line and the project engineer set it aside to ask about and never did.
The development this year is unglamorous and it is exactly the one contractors needed. Document reading finally got good at ugly inputs — a phone photo taken at an angle in the sun with a thumb in the corner, a fax that went through twice, block-letter handwriting with a name misspelled, a scanned subcontract rider with initials in the margin. The model reads the thing itself instead of requiring a person to retype it into a clean form first.
That distinction matters more than it sounds. The 2024 versions of this wanted a flat scan of a printed form and fell apart on a crumpled carbon copy. Field paper is never flat and never printed. A reader that only works on clean documents does not work on a jobsite, which is why the last round of these tools died quietly in most contractors' offices.
Put plainly: your superintendent photographs a signed tag at the tailgate meeting and the fields land in the potential change order log, with the photo attached as backup, before he gets to his truck.
Six tags from Monday, including two from the mechanical sub for chasing an unmarked chilled water line and one from your own concrete crew. The superintendent photographs them one at a time on the hood of the truck.
By 6:40 the project engineer opens the PCO log and finds six drafts. Five are complete: sub, cost code 03-330, names matched against the sub's approved craft list, hours totaled, the excavator at the rate from the equipment exhibit, and each one linked to RFI 88, which is what caused the extra work. One is kicked back — the equipment hours line is smeared and the reader flagged it rather than guessing, so the super gets a note on his phone with that one field circled and re-photographs it at lunch.
At 9 a.m. the project manager makes the only decision that matters: is this entitlement, or is it in the base scope? He rejects one of the six outright, because the chilled water line was on the as-built the sub was given. The remaining five go out as a change order request that afternoon, day two after the work, well inside the notice window.
Assumptions: 140 tags a month, average tag value $1,420 (about 11.5 craft hours at a blended billing rate plus equipment and markup), 4 percent currently lost or unbilled, keying at 7 minutes a tag by a contract administrator at $46 an hour burdened, review of a drafted tag at 1.5 minutes. Assume the reader recovers three of the 5.6 lost tags a month, not all of them, because a tag nobody photographs is still gone.
Still reading? Stop comparing — try CallSphere live.
See the home services AI agent handle a real call — complete, industry-specific, and live in your browser. No signup.
| Line | Math | Amount per year |
|---|---|---|
| Tags recovered into the log in time | 3/mo × $1,420 × 12 | $51,120 |
| Keying time recovered | 12.8 hrs/mo × $46 × 12 | $7,066 |
| Disputes from keying errors, at half the current rate | 8 tags/mo × 0.4 hr × $46 × 12 | $1,766 |
| Reading cost, tags plus 900 other documents a month | $180/mo × 12 | −$2,160 |
| Setup and mapping into the PCO log | 30 hrs one time | −$2,400 |
| Year one | $55,392 |
The recovered billing is doing almost all of the work in that table, and it is the number to argue with hardest. Before you believe it, go count. Pull last quarter's tags, match them against the PCO log, and see what percentage never made it. Every contractor who does this exercise is surprised, and not in the good direction.
Entitlement is a human decision and it should never be automated. The reader captures what the tag says. Whether the work was a change to the contract, or something the sub owed you anyway, is the project manager's call and sometimes the project executive's. Automate the typing, never the judgment.
Your superintendent's signature still means something specific, and everybody should know what. Signing for hours and materials is not agreement on entitlement or price. If the reader ever starts producing documents that blur that line, you have made your position worse, not better.
Certified payroll is a legal certification. A person signs the WH-347 statement of compliance under penalty. Reading the numbers off a scanned form to save keying is fine. Producing the certification is not.
Lastly, a photo taken into the sun of a fourth carbon copy is unreadable by anyone. The right behavior is to flag and ask, not to guess, and you should test any tool on your worst photos rather than your best.
Do not give them one. The workflow that sticks is the one they already use: take the photo, text or email it to the same address they always have. The reading happens after the photo, not on their phone, and their habit does not change.
The drafted change order should land in whatever you already run — Procore, Autodesk Construction Cloud, CMiC, or straight into Sage 300 CRE job cost. If a vendor wants you to move your change order log to run their reader, that is a bad trade.
Those read fine now, which is the news. A twice-faxed tag with a smeared signature was the exact input that broke the older tools, and it is the input the 2026 readers were built to handle.
Two numbers, both of which you already have: tags logged as a percentage of tags written, and average days from work performed to change order request issued. If the first goes up and the second comes down, it worked. If neither moves, stop paying for it.
One related leak worth closing at the same time. Every one of those tags generates a phone call — the sub calling to ask whether it was received, whether it was approved, and when it will be in a pay application — and those calls land on the project manager during a punch walk. CallSphere builds AI voice and chat agents that answer the office line and web chat, take the caller's details and tag number, and route or book from there, day or night. It handles the call; the entitlement decision stays with your PM, where it belongs.
Written by
Sagar Shankaran· Founder, CallSphere
LinkedInSagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
How commercial GCs search restricted SSI and CUI drawing sets using AI that runs on hardware in their own server room, with a worked cost example for one job.
How general contractors keep an AI assistant inside the conformed set, ASIs and approved submittals, with citations a super can check before inspection.
Handwritten trip tickets, faxed shrimp POs and initialled cooler logs still get keyed by hand. What the 2026 document readers change, and what they will not.
Seasonal seat counts break per-seat AI pricing for general contractors. A worked comparison against hosting an open model for bid-season document reading.
Sacramento rents, heals, and does business in Hmong, Russian, Ukrainian, and Spanish. How a live AI phone interpreter helps leasing offices and clinics answer everyone.
Fruitvale, Chinatown, and East 12th do business in Spanish, Cantonese, and Vietnamese. A live AI phone interpreter lets Oakland restaurants and law offices answer in kind.
© 2026 CallSphere Inc. All rights reserved.
Made within San Francisco
Watch how CallSphere handles real customer calls, schedules appointments, and processes payments — live.
Try Live DemoBook a DemoCalculate Your ROI