Load planning

A Dispatcher starts with the load subject, operating organization and transport partner. Assign an owner and record the equipment class and promised delivery time. Those details explain what the team is preparing and who will resolve a question when the load reaches review or dispatch. Keep the freight amount in USD with the commercial context of the load.

Stop records give the movement its ordered pickup and delivery detail. Each stop belongs to the load and carries a revision, sequence and address, with an appointment window. A colleague should be able to read that sequence and understand the intended movement without reconstructing it from a conversation or a document title.

• Owned load. The Dispatcher names the responsible team member. The configured creation procedure marks the load Planned and records its planning receipt. My Loads keeps the owner’s delivery promises visible while the Dispatcher prepares stops and checks resources.
• Stop order. The stop sequence explains the intended visit order. Check the address and appointment window together before the load is handed to another dispatcher.
• Operating scope. The organization and transport partner identify the context of the movement. App Administrator resolves directory or membership issues before the team commits the plan.

Agree how load numbers and revisions are assigned and how a changed stop plan is distinguished from the earlier version. Decide who checks that stop revisions belong to the load being prepared. The person making a change should be able to explain its effect on the promised delivery and the assignment interval.

Set the time zone and date precision used for appointment windows before importing schedules. Agree how the team enters a pickup window that crosses a day boundary and how the next shift reads it. Keep the original delivery promise available when discussing a later disruption. The Dispatcher should check the plan’s feasibility before dispatch even when the load has already moved to Planned.

Prepare a dry-van movement from a distribution warehouse to a cross-dock. The Dispatcher selects the operating organization and partner, records the promised delivery and creates pickup and delivery stops in order. Use a subject that lets the next shift recognize the movement without relying on the record number alone.

Ask another Dispatcher to read the stop windows and explain the intended sequence. Then change the pickup appointment in a rehearsal revision. Check which stop detail belongs to the updated plan and whether the assignment interval still supports it. The Transport Supervisor should be able to open the load and identify the current owner, the original delivery promise and the supporting plan before considering a carrier award.

• Loads Default List — Read the load owner, equipment class and promised delivery before the next action.
• My Loads — Follow loads assigned to the signed-in team member.
• Load Stops by Sequence — Inspect stops with a positive sequence and their appointment windows.

Continue with load and assignment preparation and review the implementation plan.