These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Logistics ERP
- Features
- Fleet and Dispatch
Fleet and Dispatch
Plan the vehicle, driver and trip window, then approve requested transport work for scheduling.
OverviewAvailable Vehicles×
Logistics ERP · Fleet and Dispatch
New
Available Vehicles
Vehicles
| Vehicle number | Vehicle type | Capacity | Capacity unit | Status | |
|---|---|---|---|---|---|
| VHC-10979 | VT-695 | 70 | CU-575 | Available | |
| VHC-43997 | VT-788 | 540 | CU-715 | Available | |
| VHC-32521 | VT-252 | 510 | CU-570 | Available | |
| VHC-98217 | VT-136 | 100 | CU-887 | Available | |
| VHC-39800 | VT-427 | 910 | CU-214 | Available |
6 of 6 records
VT-695Vehicles · VHC-10979
AvailableCapacity70
Capacity unitCU-575
What you can do
Put an accountable plan behind the trip
Transport Manager assigns a vehicle and driver to the trip and records its planned start and end. The customer, origin and destination define the work being planned. Dispatcher checks the requested movement before approving it through the dispatch action, which commits the trip to Scheduled.
The fleet record keeps the vehicle number, type, capacity and capacity unit. Available, Assigned and Maintenance describe its current operating status. People records connect staff and drivers to platform users, with an active setting and role title. These records provide the identity and resource context the team needs before releasing a trip to its schedule.
How the work is organized
- Resource choice. Inspect the vehicle’s status and capacity context, then select the driver for the trip. Compare capacity and shipment weight using compatible units before deciding the plan is suitable.
- Scheduled window. Keep planned start and end dates with the trip. Review other assigned work and the expected stop sequence when agreeing the operating window.
- Dispatch decision. Dispatcher approves the Requested trip using the configured dispatch action. The resulting Scheduled state is the handoff into planned execution, and the team checks that result before proceeding.
What to agree during setup
Agree who maintains vehicle availability when an asset enters maintenance or finishes an assignment. Decide how Transport Manager checks overlapping trip windows and how the team handles a last-minute driver change. Make these operating checks clear before relying on the schedule for the day’s work.
Map each staff or driver identity to the correct platform user. An individual’s job title describes their work, while access comes from the permission role assigned to the user. Agree which authorized people will use a personal trip view and how their driver assignment is resolved. A dispatcher who is not the assigned driver should use the shared planning views for that trip.
Check the handoff on an actual case
Use a Requested trip for a customer lane with a known shipment weight. Transport Manager selects a suitable vehicle, checks its capacity unit and assigns the driver. Record the planned window and ask Dispatcher to explain the decision before approving the trip for scheduling.
Repeat with a vehicle marked Maintenance and with a proposed window that overlaps another assignment. Have the team resolve the resource problem before dispatch. Then change the driver in a controlled rehearsal and confirm that the schedule and personal assignment view show the intended person. Inspect the Scheduled result of the dispatch action rather than assuming that selecting a vehicle completed the approval.
What your team sees
- Trip Schedule — Planned start and end dates with the assigned vehicle and driver.
- Available Vehicles — Fleet candidates with capacity and unit context for planning.
- My Assigned Trips — Trips whose driver identity resolves to the signed-in person’s account.
Follow the work through
Use freight intake and dispatch for the approval handoff and trip execution and delivery for progress and evidence.
What it keeps track of
Data model- Vehicles
- Fleet vehicles and capacity
- People
- Staff and drivers linked to platform users
- Users
- Users
- Trips
- Planned and executed transport trips
- Trip stops
- Ordered stops on a trip
- Parties
- Customers, carriers and service providers
Who uses it
Permissions- Transport Manager
- Plans resources and maintains the fleet.
- Dispatcher
- Approves requested trips for scheduling.
- Admin
- Maintains staff and user setup; Transport Reviewer reads the plan when reviewing outcomes.
Set up Logistics ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.