Load planning

Dispatcher creates a load with its record number, subject, operating organization, owner and transport partner. The promised delivery time stays on the load even when circumstances change. That original promise gives the team a stable point of comparison against actual delivery. Freight amount records the value associated with the movement; it does not by itself settle a carrier invoice.

A produce movement often starts with a farm collection, passes through a collection center and ends at a market or recipient. Dispatcher gives each stop a sequence, address and appointment window. A window has a start and end; actual arrival and departure are recorded separately. If the driver reaches the collection center late, the planned window remains useful to explain the exception rather than being overwritten with the arrival time.

The transport partner directory holds each partner’s code, contact and eligibility note. Dispatcher checks that the selected partner is active and appropriate for the movement. The operating organization supplies time zone and currency context. The load’s owner remains responsible for the plan and later dispatch decision.

• Load identity. The record number connects the plan, stops, assignments and later evidence.
• Stop order. A sequence distinguishes pickup from delivery and preserves the intended route order.
• Promise. The delivery commitment remains visible beside actual pickup and delivery times.

Agree who can change a promised delivery time, how operating time zones apply to appointments and which partner eligibility notes must be checked before dispatch. Define how a farm or collection center is written in the stop address, since the stop record is the shared physical instruction. Decide who resolves a missing appointment window before a vehicle is committed.

Use a load collected at a farm, transferred at a collection center and delivered to a market. Enter each stop in sequence with its own window. Ask Dispatcher to compare the selected partner with its directory entry and identify the responsible owner. Then shift the expected arrival without replacing the original delivery promise. The team should still see what was promised, what was scheduled and what actually occurred after the journey. A second person should be able to trace a stop back to the same load without relying on a message thread.

• Loads Default List — Loads waiting for a plan, with owner, partner, status and promised delivery in one row.
• Load Stops by Sequence — Pickup and delivery addresses with their appointment windows in route order.

See the operating process and implementation for the first rehearsal.