1. Fleet Management System
  2. Features
  3. Load planning
Feature · Load planning

Load planning

Give each load a promised delivery time, ordered stops and an accountable Dispatcher.

OverviewLoad exceptions
Fleet Management System · Load planning

Load exceptions

Loads

New
Record numberSubjectOwnerCounterpartyPromised delivery atActual pickup at
LDS-89371Exception lds-846TP-202115 Oct20 Oct
LDS-36506Exception lds-338TP-993922 Oct29 Oct
LDS-27186Exception lds-216TP-947307 Oct13 Oct
LDS-69324Exception lds-129TP-140621 Oct24 Oct
LDS-57164Exception lds-524TP-707907 Oct13 Oct
6 of 6 records
Exception lds-846Loads · LDS-89371
Exception
CounterpartyTP-2021
Promised delivery at15 Oct
Actual pickup at20 Oct
Actual delivery at26 Oct
Revision360
Example screen with sample data

What you can do

Prepare the load that the fleet will carry

The Dispatcher starts with the load’s subject, operating organization and transport partner. The promised delivery time records the commitment against which the team will later assess delivery. Equipment class and freight amount in USD provide planning context, while the assigned owner keeps the next operating action clear.

Ordered stops describe where the load is expected to move and the planned windows at each location. The planning action records its result and advances the load to Planned. The Dispatcher then checks whether the intended driver and vehicle arrangement can perform that plan before releasing it for movement.

How the work is organized

  • Load ownership. A named owner follows the load through preparation, dispatch and any exception. The transport partner reference identifies the operating counterpart. Use the partner’s contact and eligibility note when clarifying the intended arrangement.
  • Delivery commitment. Record the promised delivery time before dispatch and retain it when discussing a later arrival estimate. The original commitment remains the reference for the eventual comparison with actual delivery.
  • Stop detail. Stop sequence, address and planned windows give dispatch an ordered plan to discuss. Each stop retains its revision, with space for actual arrival, departure and a proof reference as work proceeds. A change to the plan should be understandable to the next person handling the load.

What to agree during setup

Agree how load numbers and subjects distinguish similar movements. Confirm the operating organization’s time zone and who owns the promised delivery commitment. Decide how equipment requirements are described and how the team checks them against the intended vehicle before dispatch.

Set expectations for stop sequencing and address quality. Identify who contacts the transport partner when a window cannot be met. Freight amounts use USD, so confirm how those values enter the load record. Establish which supporting files the Dispatcher and reviewer need for the first operating cycle.

Check the handoff on an actual case

A distribution team needs an afternoon delivery with an earlier pickup at another location. The Dispatcher enters the load, its promised delivery time and the intended transport partner. Add the stops in sequence with their planned windows, then record the planning action.

Open the planned load with the Fleet Coordinator. Check the equipment class and the service interval before selecting a driver and vehicle. The team should be able to explain why the proposed assignment is feasible using the readiness, eligibility and scheduling information it has reviewed.

Now change a stop window while retaining the original delivery commitment. Revisit the assignment interval and discuss the change with the partner contact. Keep the updated stop revision and supporting information attached to the same load. When actual delivery is later recorded, the Operations Analyst should still be able to compare it with the promise that existed before dispatch.

What your team sees

  • Loads Default List — Active planning and operating work with ownership, equipment requirement and promised delivery time.
  • Load Board by Lifecycle — Loads grouped by lifecycle so the Dispatcher can identify the next operating handoff.
  • Transport Partner Directory — Partner identities, contacts and eligibility notes used during planning.

Follow the work through

What it keeps track of

Data model
Loads
Freight loads from pickup to delivery with promised windows, freight value and lifecycle
Load stops
Ordered load stops with planned windows and recorded actual arrivals and departures.
Transport partners
Transport partners with eligibility notes and linked load activity.
Organizations
Logistics operating organizations with time zone, currency and active scope
Team members
Fleet team members with their organization, platform user, role and time zone.
Operation receipts
Idempotent operation receipts recording each fleet action, its expected revision and result state.
Record attachments
Evidence attachments linked to a load, with visibility and evidence type.

Who uses it

Permissions
Dispatcher
, Fleet Coordinator, Transport Supervisor, Operations Analyst.
The Dispatcher owns the load, fleet staff support feasibility checks and the supervisor reviews exceptions that require a decision.

Set up Fleet Management System your way.

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

How to get started