Learn how documents and load data get into the system.
This self-paced walkthrough trains new users on the intake side of Freight Broker Payment & Dispatch Proof Pack: where load records come from, how documents attach to loads, what extraction and confidence scores mean, how misread fields get corrected the auditable way, and why every intake event triggers a fresh evaluation. Each scene uses sample data and asks you to make the call an operator would make. No account needed; nothing you do here touches live data.
1. Where load data comes from
2. Attach a document to a load
3. What happens when a document lands
4. Fix a misread field
5. Every intake event re-runs the checks
Scene 1 of 5 · Workflow step 1: Import load evidence
Where load data comes from
Learn the two intake doors: the load packet import and the document upload.
Nothing in the checkpoint is typed in from memory. Load records arrive as a structured packet exported from your TMS — reference numbers, lane, carrier, rate — and each import is tenant-scoped and recorded with who imported it and when. Carrier authority evidence is attached automatically from the federal registry at import time. Documents then attach to those loads one at a time.
Intake door 1
Load packet import
Structured export from your TMS: references, lane, carrier, rate. Tenant-scoped, attributed to the importer, and carrier authority evidence is attached automatically.
Intake door 2
Document upload
One file at a time, against a load, under a declared document type:
Rate confirmation
BOL
POD
Carrier invoice
Accessorial backup
A new load needs to enter the system. How does its data get in?
Continue training
The operator walkthrough covers what happens after intake: reading the queue, working exceptions with reason codes, and using proof receipts. Together the two tracks cover the full evidence lifecycle.