A G.B. Industry companySample Full Freight Workflow Audit
This example demonstrates the expanded structure of the $499 full audit: workflow mapping, document evidence, controls, exceptions, and an implementation-ready remediation plan. It is derived from Zinvyl's cited public freight validation corpus—not a paid engagement, production deployment, or promised result.
Effective October 23, 2026
Executive disposition
Conditional candidate for controlled automation. The inspected public examples support exact extraction from separated text-readable rate confirmations. Mixed packets, missing shipment keys, and ambiguous document types must stop for review. Buyer-specific accuracy and operational value remain unproven until tested against the funded buyer's accepted document set.
End-to-end workflow map
| Stage | Actor / system | Evidence | Control |
|---|---|---|---|
| Receive | Operations inbox or approved upload | File manifest and source timestamp | Reject secrets, unsupported files, and out-of-scope workflows |
| Separate | Zero-write document processor | Page-level document boundaries | Mixed packets stop for manual separation |
| Classify | Extraction workflow | Visible document title and field evidence | Unknown or ambiguous type stops for review |
| Join | Evidence register | Shipment or load identifier present in source | Never infer a missing join key |
| Approve | Buyer-designated reviewer | Exception queue and cited source pages | No production write without a separately accepted implementation |
Illustrative evidence and exception register
| Observation | Disposition | Required evidence | Owner |
|---|---|---|---|
| Separated rate confirmation with visible load and approved rate | Eligible for bounded extraction | Page citation for every required field | Automation, then reviewer sampling |
| BOL or POD without a shared shipment key | Exception | Buyer-supplied join evidence | Buyer reviewer |
| Multiple document types in one packet | Stop | Separated pages and updated manifest | Intake owner |
| Image-only or photographed document | Outside fixed scope | Separately agreed OCR test and acceptance threshold | Buyer and Zinvyl |
Implementation-ready remediation plan
- Define the output contract. Buyer approves required fields, evidence citations, exception labels, and prohibited inferences.
- Run a held-out validation. Measure field-level results on normal and exception documents from the funded intake; do not reuse tuning examples as proof.
- Enforce review gates. Mixed packets, unknown types, missing keys, and low-evidence fields remain non-bypassable stops.
- Approve any integration separately. Read-only or write integrations require their own scope, credentials, rollback plan, and acceptance tests.
Illustrative acceptance tests
- The intake manifest contains one workflow and no more than ten text-readable PDFs.
- Every material field, handoff, and exception maps to cited evidence or a labeled ambiguity.
- Every recommendation names an owner, dependency, risk, measurable acceptance test, and unresolved assumption.
- The execution report records zero production credentials, write calls, or deployed changes.
Limits and provenance
This is a synthetic format demonstration using Zinvyl's public validation corpus. It does not establish buyer-document accuracy, OCR performance, savings, compliance, demand, profitability, delivery acceptance, or production reliability.
Open the source-level validation record · Read the complete service contract · Request the $499 full audit