Broker Portal · loads table
Load Intake & Dispatch Status
Submit loads · Track pipeline stage · Coordinate with dispatch · Exchange documents
Loading...
Active Loads
0
In pipeline
→ loads
In Dispatch
0
Dispatcher assigned
→ dispatches
Human Close
0
Dispatcher contacting you
→ dispatches
Pending Docs
1
Rate confirmation needed
→ loads
Load Intake Form
Submission → loads table · Stage: Load → Normalize · Backend API
Broker Identification
Load Specification
Submission creates record in loads table · Pipeline stage: Load → Normalize · Event logged to events table
What Happens After Submission
Your load enters the immutable pipeline. You do not select a carrier. Dispatch does.
1
Load
Load record created in loads table
You submitted the load
2
Normalize
Data validated and structured by system
No action required
3
Carrier Discovery
Matching engine queries carrier network
No action required
4
Match
Top carriers scored and ranked
No action required
5
Human Close
Dispatcher contacts you to confirm rate and pickup
Dispatcher will call
Submission Quality
Complete and accurate load data improves match scoring. Incomplete submissions delay normalization.