In a carrier-dispatch service relationship, forced dispatch describes an arrangement where the carrier does not retain the final choice over whether to take a presented load. Apex's no-forced-dispatch model keeps the accept-or-pass decision with the carrier while the dispatcher supports search, negotiation, communication and paperwork.
Direct answer
In a carrier-dispatch service relationship, forced dispatch describes an arrangement where the carrier does not retain the final choice over whether to take a presented load. Apex's no-forced-dispatch model keeps the accept-or-pass decision with the carrier while the dispatcher supports search, negotiation, communication and paperwork.
For a carrier using a dispatch service, forced dispatch means the carrier is not retaining the final choice over a presented load. Contract terms and operating relationships can differ, so carriers should confirm exactly how load approval works before signing.
The dispatcher searches and presents a load opportunity with the relevant details.
The carrier considers rate, lane, schedule, equipment fit, pickup and delivery details and business priorities.
The carrier chooses whether the load fits the operation.
If accepted, the dispatcher can continue with setup, paperwork, communication and follow-through.
Final load approval helps preserve the carrier's control over routes, home time, schedule and operating strategy.
Related Apex answers
Apex public position
Apex presents opportunities, supports negotiation and paperwork, and leaves the final load decision with the carrier.