Turn trip requests into an assignable duty profile
6 min read
Lesson objectives
- Separate operational demand from a proposed vehicle and identify constraints and missing data
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
A request saying 'we need a truck tomorrow' is not enough to assign an asset. Define the duty before naming a vehicle: cargo type, mass and dimensions, number of stops, collection and delivery windows, approximate distance, road conditions, lifting or refrigeration needs, and expected dwell time. These describe the operation; they do not establish that a nominated vehicle is suitable. Separate hard constraints, such as payload capacity and required cooling, from preferences that can be traded off, such as earlier arrival or fewer empty kilometres. Mixing them can lead an optimization tool to choose a shorter trip with an overloaded vehicle. Ask the requester which record substantiates quantity and timing: a purchase order, parcel list or confirmed receiving appointment. Mark unknowns explicitly rather than filling them with a historic average. The need review also asks whether journeys can be combined or another service used without losing the required outcome; reducing vehicle use is not a success when the service fails.
Create one row per job, not one row per email. Use request number plus revision as the key, because a weight change after approval is not the original duty specification. Mark each material field as confirmed, estimated or unknown. Planned distance is often an estimate; a mass on a shipping document may be confirmed pending scale verification. Define kilograms as the mass unit and convert inputs before comparison; do not combine cubic volume with kilograms in one field. For multiple stops, capture the time window and minimum service time at each stop instead of a single final deadline. A route may appear feasible overall while missing an intermediate appointment. Record who may revise the request and when the dispatched version was frozen. This lets the dispatcher reject an incomplete job for a stated reason rather than an intuition.
Begin with mass: J41 is 18×45=810 kg, not 18 kg or 45 kg. With J42 the combined mass would be 1,110 kg, yet a morning combination is infeasible because J42 will not be ready until the afternoon. Readiness time is a separate constraint from capacity. If loading starts at 08:00 and ends at 08:25, estimated arrival at the first stop is 08:55. Waiting five minutes allows service from 09:00 to 09:20. A 35-minute drive then gives 09:55, requiring a 20-minute wait until 10:15; second-stop service ends at 10:30. The estimated sequence is feasible on time, but the calculation does not prove resilience to traffic or vehicle suitability. Record 810 kg, both windows, service and loading times, and mark van capacity 'unknown'. Do not authorize a particular van until its actual payload rating and equipment are verified, and driver, vehicle and journey checks are complete. If its card shows 750 kg, the payload constraint fails by 60 kg; use another vehicle or split the job and recheck time windows. A feasible timetable does not repair a capacity breach. If first-stop service changes from 20 to 55 minutes, second-stop arrival becomes 10:30 with the same drive and still fits its window, though with less margin. Calculate the new result rather than calling every change a failure.
When the requester changes J41's weight after the duty card is issued, do not overwrite 810 with a new number and lose the history. Create a new request revision with change time and requester, then rerun the payload and timing checks; a dispatcher may already have released a vehicle on the old version. If the boxes need refrigeration and this becomes known only at loading, the issue is not route optimization but a failed critical input: stop dispatch and retest vehicle equipment and time windows. Distinguish 'a timetable works on paper' from 'a service commitment is robust'. In the example, arrival at the first stop is 08:55, five minutes before opening, yet traffic and gate time are unknown. Record a margin and escalation route if arrival slips. Do not promise a confirmed arrival from estimated travel time or silently replace a customer's agreed window. A useful duty card preserves constraints, assumptions, revision and escalation owner so teams can reproduce the same decision.
Lesson summary
Separate operational demand from a proposed vehicle and identify constraints and missing data