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.
- EV Fleet Management
- Features
- Load Planning
Load Planning
Prepare the lane, stop requirements and delivery commitment that the reviewer and dispatcher will use.
OverviewLoads Awaiting Approval×
EV Fleet Management · Load Planning
New
Loads Awaiting Approval
Approval conditions
| Record number | Subject | Organization | Counterparty | Requested units | Equipment class | |
|---|---|---|---|---|---|---|
| AL-35263 | Review al-841 | ORG-8099 | TP-5065 | 140 | EC-771 | |
| AL-70197 | Review al-676 | ORG-6795 | TP-4915 | 700 | EC-993 | |
| AL-87577 | Review al-267 | ORG-8567 | TP-9270 | 300 | EC-893 | |
| AL-46855 | Review al-313 | ORG-7396 | TP-4644 | 300 | EC-863 | |
| AL-42722 | Review al-200 | ORG-4187 | TP-4337 | 650 | EC-869 |
6 of 6 records
Review al-841All loads · AL-35263
OrganizationORG-8099
CounterpartyTP-5065
Requested units140
Equipment classEC-771
Promised delivery at17 Oct
What you can do
Give the EV load a reviewable operating scope
The Fleet Planner starts with the work the vehicle must carry out. A load identifies the lane, requested units, equipment class and promised delivery date. Its planned departure and arrival give the team a starting schedule, while the assigned owner remains responsible for resolving changes before dispatch. The transport partner and operating organization keep the commercial context with the load.
Stops describe the pickup, delivery or service work along that journey. Each stop has a sequence, location and appointment information. The planner can include a service window and the evidence reference needed later. Standard routes provide lane context, including distance and planned duration, for the team to consider when preparing the actual load.
How the work is organized
- Prepare the draft. Record the requested scope and order the stops so the dispatcher can follow the intended journey. Check that the equipment requirement and promised date are understandable before sending the load for review.
- Review the revision. The Operations Reviewer examines the current load scope and records a decision with a reason. Approved work can move toward assignment; a Returned decision tells the planner what needs attention before another eligible review.
- Carry changes forward. Keep the revised plan connected to the decision that applies to it. A later change to a stop window or equipment requirement needs a clear handoff to the dispatcher before the team relies on the earlier plan.
What to agree during setup
Agree what a requested unit means for your operation. The planner may be describing packages, containers or another agreed service quantity. Vehicle capacity is recorded in pounds, so the team must establish a defensible way to compare the load requirement with the equipment capacity rather than treating those figures as interchangeable.
Set the lane naming convention and the meaning of planned versus promised dates. A standard route can inform the plan, but the actual stop windows belong to the load being dispatched. Agree which changes require another review and who tells the dispatcher when approved scope has changed.
Check the handoff on an actual case
Use a depot delivery load with a pickup stop and a customer delivery stop. The Fleet Planner records the requested equipment class and the promised delivery date, then submits the current revision. The Operations Reviewer checks the scope and records why it can proceed or what needs correction.
Before assignment, change the delivery window in the rehearsal. Ask the dispatcher to identify the current revision and the review decision that supports it. The team should resolve the changed commitment before relying on the old assignment plan. Finish by checking that the driver and vehicle assignment, charging evidence and delivery proof can all be traced back to the same load.
What your team sees
- Active Loads — Draft, Review and Approved load scope with the lane, owner and delivery commitment together.
- Loads Awaiting Approval — Load revisions that need the Operations Reviewer’s decision.
- My Loads — Work owned by the signed-in planner, including planned departure and promised delivery dates.
Follow the work through
Follow load planning and assignment and dispatch and delivery proof to rehearse the commitment through execution.
What it keeps track of
Data model- All loads
- Planned and executed transport loads
- Load stops
- Pickup, delivery and service stops on a load
- Routes
- Standard lanes between an origin and destination
- Organizations
- Carrier, broker, shipper and operating companies using the platform
- Transport partners
- Carriers, brokers, 3PLs and shippers linked to transport work
- Team members
- Dispatch, planning, safety and maintenance staff
- Review decisions
- Approval, rejection and escalation decisions on records
Who uses it
Permissions- Fleet Planner
- , Dispatcher, Operations Reviewer, Admin.
- The planner owns the scope, the reviewer decides on its eligibility and the dispatcher uses the approved plan for assignment.
Set up EV Fleet Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.