The load board
The load board is the operational heart of Prevayl. It shows every active order across your operation, color-coded by status:
| Status | Meaning |
|---|---|
| DRAFT | Order created, not yet posted or assigned |
| POSTED | Visible to your private carrier network |
| DISPATCHED | Carrier accepted, awaiting pickup |
| IN TRANSIT | Vehicle picked up, en route to delivery |
| DELIVERED | Delivered, BOL signed |
| INVOICED | Invoice generated and sent |
| PAID | Customer payment received and reconciled |
| EXCEPTION | Manual review required (delay, damage, dispute) |
Posting orders
By default, new orders post to your private network only — your existing approved carriers. To extend visibility:
- Post to Load Board — visible to all approved Prevayl carriers in your region
- Post to Load Board + External — also syndicates to the primary industry load boards (third-party syndication, additional fee)
Both options preserve carrier vetting — only carriers with active authority, current insurance, and matching equipment can submit offers.
AI carrier matching
The AI matching engine ranks carriers for each load based on a weighted scoring of:
| Signal | Weight (default) | Configurable |
|---|---|---|
| Lane history (carrier ran this lane before) | 25% | Yes |
| Equipment fit (open vs enclosed, hazmat, etc.) | 20% | No |
| On-time delivery rate (last 90 days) | 15% | Yes |
| Current proximity (live GPS, when available) | 15% | Yes |
| Rate appetite (historical accept/decline patterns) | 10% | Yes |
| Customer compatibility (no past disputes) | 10% | No |
| Fleet utilization (open seats vs current load) | 5% | Yes |
Adjust the configurable weights under Settings → Dispatch → Matching Weights. Weights must sum to 100. Changes apply to all subsequent matches; historical assignments are not retroactively re-scored.
BOL workflow
Pickup
When the carrier arrives at pickup, they tap Start Pickup in the carrier portal. The system prompts for:
- 4-corner photo inspection of each vehicle
- Mileage reading
- Existing damage notation (free-text + photo overlay)
- Driver signature
- Shipper signature (or shipper-not-present override with reason)
The signed BOL is timestamped, geotagged, and saved as immutable record. PDF copies go to shipper, broker, carrier, and customer simultaneously.
Delivery
Same flow at delivery, with additional new-damage flagging. Any damage flagged at delivery that wasn't present at pickup automatically opens a DamageDesk case.
Exception handling
Exceptions are surfaced via the Exception Queue on the dispatch dashboard. Categories:
- Late pickup — carrier hasn't arrived within 1 hour of the scheduled window
- Late delivery — ETA missed by >2 hours, or no GPS update for >6 hours
- Damage flagged — auto-opened DamageDesk case
- Dispute — shipper or consignee filed a complaint via portal
- BOL anomaly — signature missing, photos out of compliance, mileage mismatch
Each exception has a primary owner (defaults to dispatcher who placed the load) and SLA timer. Unresolved exceptions block invoice generation.
Related
- Accounting Module — invoice generation from BOLs
- API Reference — programmatic order and dispatch operations
- Webhooks — subscribe to dispatch lifecycle events