Load planning

Dispatcher begins with the load’s operating organization, owner and transport partner. The promised delivery time establishes the commitment the team must assess. Pickup and delivery stops add the working sequence, addresses and service windows. A load marked Planned should represent a checked operating plan that the next shift can understand.

Keep the freight amount alongside the load as commercial context. The planning decision depends on physical feasibility and authorized scope. Transport Supervisor checks the evidence behind the plan, while Admin maintains the stop and assignment details that support it. App Administrator keeps the partner and operating roster information ready for that work.

• Load ownership. Dispatcher prepares the assigned load and its current revision. The organization and counterparty references keep responsibility clear when several transport partners work similar routes or service areas.
• Stop sequence. Admin records ordered stops with their addresses and windows. Dispatcher reads that sequence when preparing pickup and delivery, then uses actual arrival and departure evidence to explain how service unfolded.
• Feasibility. Transport Supervisor examines the driver, vehicle and assignment interval supporting the plan. Open critical vehicle defects stop planning, and conflicting commitments need resolution before the load becomes an operating promise.

Choose the first operating organization and confirm its time zone before loading delivery commitments. Agree how staff interpret pickup and delivery windows, who maintains stop sequence and how a changed plan receives a fresh revision. Keep a clear owner for each load so a partner query reaches the person responsible for the next action.

Decide how equipment requirements and package weight inform the vehicle check. A parcel can appear in several milestone scans, so adding every scan’s weight would count the same parcel repeatedly. Agree the source used to establish the physical load quantity and have the supervisor inspect that basis when reviewing feasibility.

Use a load with a morning pickup and an afternoon delivery promise. Admin enters the pickup and delivery stops and their windows. Dispatcher checks the partner and the load’s owner. Transport Supervisor discovers that the selected vehicle is already committed during part of the interval, so Admin revises the assignment before planning proceeds.

Next, introduce an open critical defect on the replacement vehicle. Keep the load in preparation until the fleet evidence supports an eligible vehicle. Rehearse a planning request using an older load revision and confirm that it stops before writes. When the corrected plan succeeds, repeat the same request and check that its operation identity returns the existing result instead of creating another planning effect.

• Load planning queue — Draft and Planned loads with the promise, equipment requirement, partner and assigned owner.
• My loads — The dispatcher’s assigned load work and current revision.
• Stop handoffs — Stop windows, actual service times and proof references for handoff review.

Use Plan and dispatch to move from the plan to physical pickup, and Implementation to agree the operating rules.