Three-way match on every delivery
A truck shows up at the laydown yard. The driver wants a signature and a fast turnaround. Someone counts pallets, not boxes, signs the ticket, and the delivery goes into the log as "received."
The problem
A truck shows up at the laydown yard. The driver wants a signature and a fast turnaround. Someone counts pallets, not boxes, signs the ticket, and the delivery goes into the log as "received."
Three weeks later, a crew is stringing modules on a row and runs out. Or the combiner boxes on the pallet are the wrong model. Or a crate sat open in the rain and nobody wrote it down. By then the driver is gone, the supplier's window to accept a claim is shrinking, and the superintendent is on the phone trying to prove what arrived.
The purchase order says one thing. The packing slip says another. The delivery ticket you signed says a third. Nobody compared them on the day, because nobody has time to do that at the tailgate.
How the agent workflow works
The agent does the comparison so the foreman doesn't have to.
What it reads. Three inputs per delivery: the purchase order (from your project folder, procurement export, or email), the packing slip, and a photo of the signed delivery ticket. The foreman or receiving lead snaps the photos on their phone and drops them in a shared folder or sends them to a set email address. Photos of the pallets and any visible damage go in the same place.
What it does. The agent pulls line items from each document: item description, part number, quantity, unit. It matches them line by line and checks three things:
- Quantity: does the PO, slip, and ticket count agree?
- Item: do part numbers and descriptions match, or did a substitution slip in?
- Condition: do the ticket notes or the photos show damage, wet packaging, or a short-shipped pallet?
What it produces. If all three agree, it writes a short receiving entry for the daily log. If any leg disagrees, it drafts a flag the same day: what the PO called for, what the slip claims, what the ticket shows, and which line is off. It can also draft a note to the supplier asking for a correction or a replacement shipment.
The human checkpoint. The agent never sends the supplier note and never edits the log on its own. The superintendent or receiving lead reviews each flag, confirms against the physical material if needed, and approves, edits, or discards the draft. Matches that come back clean still get a quick glance before they are logged.
What you need to set it up
- An AI model that can read images and PDFs, with the ability to run on a schedule or on a new file arriving.
- A shared folder or inbox where delivery photos and slips land.
- Access to purchase orders in a form the agent can read: a spreadsheet export, PDFs, or a procurement system's report.
- A simple naming habit: project, date, and supplier in the filename or email subject.
- A place for drafts to land where the superintendent will see them, such as an email thread or a shared document.
Setup time is a few hours if your POs are already digital and consistent. Plan more if they live in scattered emails. The subscriptions involved are the AI tool and whatever storage and email you already pay for.
Run it alongside your current process for a couple of weeks before you rely on it.
Where it breaks
Bad photos. A ticket shot at an angle, in glare, or with a thumb over the quantity column will produce a wrong read or no read. The agent should say when it can't read a field, and you should treat that as a flag, not a pass.
Part number drift. Suppliers abbreviate, and PO descriptions don't always match what's printed on the slip. The agent will throw false flags until you tune it with a few examples from your actual suppliers.
Counting. The agent matches paper to paper. It cannot count the boxes on the pallet. If the ticket says 20 and only 18 are there, the match passes and the shortage still surfaces at install. Someone has to do a physical count, at least on high-value or long-lead items.
Condition from photos is weak. It may catch a crushed crate. It will miss cracked cells inside intact packaging.
Missing or late POs. No PO means no match. Verbal orders and change orders that never got written down will all show up as mismatches.
The bottom line
This workflow doesn't replace receiving. It makes sure the paperwork gets compared on the day of delivery, while the driver can still be reached and the supplier can still correct it. The foreman still counts and signs. The agent catches what the tailgate rush misses, and the superintendent decides what goes back to the supplier.
Related use cases
- Long-lead gear tracker Materials
- A gate on every material order before it goes out Materials
- Two-week lookahead, built not typed Management