A G.B. Industry companyFreight Workflow Evidence Check — $199
This redacted example shows the shape and evidence discipline of the $199 founding evidence check. It uses only cited public documents and contains no paid-customer material, private demand signal, or production result.
Effective October 27, 2026
Audit one freight workflow before automating it
$199 fixed · delivered within one business day after verified funding and complete accepted inputs.
Submit two or three text-readable freight PDFs for one bounded, zero-write evidence check. The delivery identifies traceable fields, unsafe assumptions, missing join keys, exception stops, and a practical next-step plan without connecting to production systems.
Request the $199 evidence check →
Executive disposition
Conditional automation candidate. Exact extraction was observed for two inspected public rate confirmations. Mixed packets and documents without a reliable load identifier stopped for review. A buyer-specific matched invoice, rate confirmation, BOL, and POD packet has not been validated.
Bounded workflow
- Receive one text-readable freight document or an already separated page.
- Classify the document as rate confirmation, bill of lading, proof of delivery, or unknown.
- Extract only fields supported by visible source evidence.
- Stop mixed packets, ambiguous document types, and missing join keys for human review.
- Write nothing to a TMS, accounting system, shared drive, or production workflow.
Observed evidence
| Public input | Observed result | Disposition |
|---|---|---|
| RXO rate confirmation 14404811 | Rate confirmation; load 14404811; approved rate $1,300.00 | Matched inspected ground truth |
| RXO rate confirmation 14336973 | Rate confirmation; load 14336973; approved rate $600.00 | Matched inspected ground truth |
| NHTSA-hosted separated BOL page | Bill of lading; no load ID invented | Fail closed |
| Two separated POD pages | Proof of delivery; no load ID invented | Fail closed |
| Four mixed publications or packets | Unknown; mixed document types; review required | Rejected as unsplit packets |
Exception and control register
| Trigger | Required control | Decision owner |
|---|---|---|
| More than one document type in a PDF | Stop; split and re-submit pages before extraction | Buyer-designated reviewer |
| Missing or ambiguous shipment join key | Do not infer a load; record the evidence gap | Buyer-designated reviewer |
| Commercial-goods invoice resembles carrier invoice | Require freight-specific evidence before classification | Zinvyl audit logic, then buyer reviewer |
| Image-only or photographed page | Outside this fixed scope unless agreed before funding | Buyer and Zinvyl |
Prioritized implementation plan
- Run a funded, held-out pilot on two or three buyer-approved de-identified text-readable PDFs.
- Define exact required fields and page-level evidence citations before measuring accuracy.
- Keep mixed-packet detection and missing-key stops as non-bypassable review gates.
- Only after field-level acceptance, design read-only integrations; production writes remain a separate contract.
Limits and provenance
The underlying corpus contains six cited public PDFs and seven separated real-world pages. The retained regression suite passed 23 of 23 checks after five defects were found and fixed. These results do not establish buyer-document accuracy, OCR performance, demand, savings, profitability, delivery acceptance, or production reliability.
Read the invoice, BOL, and POD reconciliation checklist · Open the source-level validation record · Read the complete service contract · Request the $199 founding evidence check