Freight intake and dispatch

Capture the customer lane, plan the trip resources and approve requested work for scheduling.

Step by step

Capture the freight request Dispatcher

Dispatcher records the customer, origin, destination, weight unit and promised date. The capture action raises a Requested trip for the customer lane; inspect that result before handing work to planning.
- Raise Requested trip for customer lane
- Updates Freight orders, Parties, Trips
Plan resources and timing Transport Manager

Transport Manager assigns the vehicle and driver and sets the planned start and end. Check compatible capacity and weight units and review the intended operating window.
- Assign resources and planned window
- Updates Trips, Vehicles, People
Prepare the stop plan Dispatcher

Dispatcher records the trip's ordered stops with their locations and planned arrivals. Confirm the sequence with the people responsible for executing the trip.
- Record stop sequence and planned arrivals
- Updates Trip stops, Trips
Approve dispatch Dispatcher

Dispatcher approves the Requested trip through the dispatch action, which commits Scheduled. Inspect the resulting trip and resource assignment before treating the work as scheduled.
- Requested to Scheduled
- Updates Trips
ApprovalA person approves before the work moves on.

And how to keep it from happening.

Ambiguous capture result. Similar orders on the same lane can be confused. Inspect the trip created by the actual capture operation rather than selecting solely by destination.
Incompatible quantity context. Compare shipment weight and vehicle capacity using agreed units. Resolve a unit mismatch before the dispatch decision.
Unresolved resource conflict. Review maintenance status and overlapping assignments as part of planning. Agree how the team handles a vehicle or driver change.

Start free, then use Proto to change fields, steps and approvals before your team goes live.