Fleet Operations & Routing

Chapter 7
Scheduling, Dispatching and Load Planning

Post Graduate Program in Logistics
Fleet Operations & Routing   •   Post Graduate

Scheduling, Dispatching and Load Planning

Introduction

Fleet operations convert customer demand into coordinated vehicle movements. Scheduling determines when vehicles and drivers are available and when activities should occur; dispatching assigns and releases work; load planning determines what each vehicle carries, in what sequence, and under what operational constraints. These decisions are interdependent. A route that is geographically efficient may be infeasible because of an appointment window, driver hours-of-service limitation, loading delay, vehicle capacity restriction, or incompatible freight.

At postgraduate level, scheduling and dispatching should be understood as a control system rather than as clerical activities. The planner creates a feasible operating plan, the dispatcher translates it into executable instructions, and the control function continuously compares actual progress with the plan. Effective practice therefore combines optimization, operational judgment, regulatory compliance, information systems, and exception management.

Learning Objectives

By the end of this chapter, the reader should be able to:

  1. Develop vehicle and driver schedules using demand, availability, appointment windows, and hours-of-service constraints.
  2. Construct route plans that integrate service times, travel times, breaks, and depot requirements.
  3. Design load sequences for capacity, stability, accessibility, and delivery-order requirements.
  4. Explain the role of dispatching before, during, and after a trip.
  5. Incorporate backhauls, cross-docking, and real-time exceptions into fleet plans.
  6. Evaluate schedules using cost, service, utilization, safety, and resilience measures.
  7. Assess the governance, ethical, and technological implications of increasingly automated dispatch decisions.

1. The Planning Hierarchy

Fleet planning occurs at several time horizons.

HorizonMain decisionTypical information
StrategicFleet size, depot structure, vehicle mixAnnual demand, capital cost, network design
TacticalCapacity allocation and recurring schedulesWeekly demand, driver rosters, contracts
OperationalDaily routes, loads, and appointmentsOrders, traffic, vehicle and driver status
Real timeRe-routing, recovery, and exception responseGPS, delays, cancellations, new requests

A useful distinction is between a schedule, a route, and a dispatch plan. A schedule specifies time commitments and resource availability. A route specifies the sequence of locations and movements. A dispatch plan specifies the operational instructions, documents, equipment, and communications needed to execute the route.

The planning process normally follows this sequence:

  1. Consolidate orders and validate data.
  2. Classify shipments by customer, priority, temperature, hazard, and handling requirements.
  3. Establish vehicle, driver, depot, and dock availability.
  4. Generate feasible route and load alternatives.
  5. Assign drivers and vehicles.
  6. Check legal, safety, capacity, and appointment constraints.
  7. Release dispatch instructions.
  8. Monitor execution and manage exceptions.
  9. Close the trip, reconcile documents, and evaluate performance.

This sequence is iterative. A late order may require changing the load, which may alter the route, which may require a different driver because of hours-of-service limits.

2. Scheduling Models and Constraints

2.1 Time representation

For a route with locations indexed by i and activities indexed by k, the planned arrival time at location i can be represented as:

Ai = Di-1 + Ti-1,i

where Ai is arrival time at location i, Di-1 is departure time from the previous location, and Ti-1,i is travel time between the two locations. If service begins only after the opening of an appointment window, service-start time is:

Si = max(Ai, ei)

where ei is the earliest permitted service time. Feasibility requires:

Si ≤ li

where li is the latest permitted service-start time. Departure is then:

Di = Si + si

where si is service duration. All times must use the same time zone and units, normally minutes from the beginning of the planning day.

These equations assume deterministic travel and service times. In practice, planners often add a buffer. If bi is a planned buffer, then the operational travel estimate may be Ti-1,i + bi. Buffers improve reliability but reduce capacity and may conceal poor standards if added indiscriminately.

2.2 Resource constraints

A feasible schedule must satisfy several simultaneous constraints:

  • Vehicle capacity: weight, volume, pallet positions, axle limits, and compartment restrictions.
  • Driver availability: shift start, shift end, breaks, rest periods, qualifications, and contractual limits.
  • Vehicle availability: maintenance, fueling, cleaning, charging, and equipment compatibility.
  • Customer constraints: appointment windows, receiving hours, dock capacity, delivery priority, and site restrictions.
  • Cargo constraints: hazardous-material segregation, temperature control, orientation, security, and compatibility.
  • Network constraints: depot opening hours, cross-dock cut-offs, ferry or toll-road schedules, and return-to-base requirements.

A schedule can be mathematically attractive but operationally invalid. For example, a route may fit within the driver's total duty period while violating a mandatory break rule or requiring a vehicle to carry more weight on a particular axle than is legally permitted.

2.3 Hours-of-service planning

Hours-of-service (HOS) rules vary by jurisdiction and vehicle category. A planner must use the applicable legal standard rather than a generic assumption. The operational principle is consistent: driving time, on-duty non-driving time, rest, and cumulative limits must be tracked separately.

A driver's remaining legal driving time at activity t can be represented conceptually as:

Rt = L − Gt

where Rt is remaining driving allowance, L is the applicable legal allowance for the relevant period, and Gt is cumulative driving already used. This simple expression is not a substitute for the complete regulation, because many regimes include rolling windows, split rests, exemptions, and separate on-duty limits.

Scheduling software should therefore maintain an event log containing driving, loading, waiting, breaks, and rest. A driver who is waiting at a customer may still be on duty even though the vehicle is stationary. Misclassifying waiting time can create both safety and compliance risk.

3. Route Construction with Appointment Windows

A route with time windows is commonly described as a vehicle-routing problem with time windows. Each customer must be visited within an allowable interval, while the route must respect capacity and resource restrictions. The objective may be minimizing distance, total operating cost, lateness, number of vehicles, emissions, or a weighted combination.

A practical objective function can be expressed as:

Minimize Z = cd D + cv V + cl L + co O

where D is distance, V is the number of vehicles used, L is lateness or service failure, O is overtime, and the c terms are their respective cost weights. The units of each cost term must be compatible, such as monetary units per kilometre, vehicle, minute, and overtime hour. In service-sensitive operations, the penalty for a missed appointment should normally be much greater than the marginal cost of a few additional kilometres.

The objective is subject to constraints such as:

∑i wi xir ≤ Wr

where wi is the weight of shipment i, xir equals 1 when shipment i is assigned to route r, and Wr is the vehicle's usable weight capacity. A corresponding volume constraint is:

∑i vi xir ≤ Vr

where vi is shipment volume and Vr is usable vehicle volume. These constraints assume that all shipments assigned to the route are compatible and that capacity is measured in a common unit.

Worked example: appointment feasibility

A vehicle leaves a depot at 08:00. Travel to Customer A requires 45 minutes, service requires 20 minutes, and Customer A accepts deliveries from 08:30 to 09:30. Travel from A to Customer B requires 50 minutes, service requires 15 minutes, and B accepts deliveries from 10:00 to 11:00.

Arrival at A is 08:45. Service begins at 08:45 and ends at 09:05. Arrival at B is 09:55. Because B does not open until 10:00, the vehicle waits five minutes. Service begins at 10:00 and ends at 10:15. The route is feasible. If the first travel time increased by 20 minutes, arrival at A would be 09:05, departure 09:25, arrival at B 10:15, and the route would remain feasible. If travel to A increased by 40 minutes, service at A would begin at 09:25 and departure at 09:45; arrival at B would be 10:35, still feasible. The example illustrates why waiting is not automatically a failure, although excessive waiting reduces productivity.

Heuristics and optimization

Exact optimization can provide high-quality solutions for small and medium instances, but large daily problems may require too much computational time. Common practical approaches include:

  • Savings methods: combine routes when the distance saving is worthwhile and constraints remain feasible.
  • Insertion heuristics: insert a new stop at the position causing the least additional cost while preserving time windows.
  • Local search: improve a route through swaps, relocations, and two-route exchanges.
  • Large-neighborhood search: temporarily remove several stops and reinsert them in better positions.
  • Rolling-horizon planning: freeze near-term commitments while continuously optimizing later activities.

No algorithm eliminates the need for operational review. Data errors, unusual site conditions, driver familiarity, and customer relationships may not be represented adequately in the model.

4. Load Planning and Load Sequencing

Load planning is a three-dimensional and temporal problem. The planner must decide whether freight fits, whether the vehicle remains stable and legal, whether goods are protected, and whether each shipment can be accessed at the correct stop.

4.1 Capacity dimensions

Important capacity measures include:

  • gross vehicle weight and payload;
  • cubic volume;
  • pallet, roll-cage, or floor-position capacity;
  • axle and tire loading;
  • compartment or temperature-zone capacity;
  • loading-meter capacity for irregular freight;
  • hazardous-material and segregation limits.

Payload is calculated as:

P = G − T − E

where P is permitted payload, G is the legally permitted gross vehicle mass, T is tare vehicle mass, and E is the mass of fixed and operational equipment, such as refrigeration equipment, fuel, tools, and securing devices. The formula applies only when all masses are measured consistently and the result is also checked against axle limits.

A vehicle may have unused volume but no usable payload, or unused payload but no floor space. Consequently, utilization should be monitored by more than one measure:

Weight utilization = (loaded weight ÷ usable weight capacity) × 100%
Volume utilization = (loaded volume ÷ usable volume) × 100%

High utilization is not always desirable if it increases damage, handling time, or delivery failure.

4.2 Sequence rules

A basic rule is “last delivery loaded first and first delivery loaded last.” Freight for the final stop is placed deeper in the vehicle, while freight for the first stop remains accessible near the door. This rule must be modified for weight distribution, fragile goods, temperature requirements, and cross-dock timing.

A robust sequence normally follows these principles:

  1. Place dense and stable freight low and, where appropriate, near the vehicle's longitudinal centre.
  2. Respect axle and weight-distribution limits.
  3. Separate incompatible or hazardous products.
  4. Protect fragile goods from compression and movement.
  5. Place stop-sequenced freight to minimize unloading disturbance.
  6. Make urgent or early-stop freight accessible.
  7. Secure all freight against movement using approved equipment.
  8. Verify seals, labels, temperature settings, and documentation.

Load sequencing is therefore a constrained arrangement problem, not merely a volume calculation. A digital load plan should show position, stop, handling requirement, weight, dimensions, and any special instruction.

5. Dispatching as an Operating Control Function

Dispatching is the controlled release and supervision of work. It begins before vehicle departure and continues until the trip is closed.

Pre-dispatch activities

The dispatcher should verify:

  • route, stops, appointment times, and customer instructions;
  • vehicle roadworthiness, fuel or battery state, and equipment;
  • driver identity, qualification, legal availability, and contact details;
  • load count, weight, labels, temperature requirements, and documents;
  • loading completion and seal number;
  • weather, traffic, restrictions, and known site risks;
  • escalation contacts and communication protocols.

The dispatch release should create a common operational picture. It should identify the route sequence, expected arrival times, break plan, delivery requirements, proof-of-delivery process, and conditions under which the driver must contact control.

In-trip control

During execution, the dispatcher compares planned and actual events. Useful control indicators include:

  • departure variance;
  • arrival variance;
  • dwell time at customer sites;
  • remaining driving and duty allowance;
  • missed or threatened appointments;
  • temperature or equipment alarms;
  • vehicle location and route deviation;
  • proof-of-delivery and exception status.

A dispatcher should avoid unnecessary intervention. Excessive route changes create confusion, increase safety risk, and can worsen the original delay. Intervention is justified when it protects safety, compliance, customer service, or material cost.

Post-trip closure

Trip closure includes proof-of-delivery capture, returned-goods reconciliation, fuel or energy recording, damage reporting, hours-of-service confirmation, toll and expense reconciliation, and review of deviations. Reliable closure data improves future scheduling standards and customer performance analysis.

6. Backhauls and Cross-Docking

Backhauls

A backhaul uses a vehicle's return movement to collect freight rather than returning empty. It can reduce empty kilometres and improve asset productivity. However, a backhaul is feasible only when collection time, freight compatibility, capacity, driver legality, and return requirements align.

The incremental value of a backhaul can be assessed conceptually as:

Net backhaul benefit = Avoided empty-movement cost − Incremental backhaul cost − Risk cost

The risk cost may include probability-weighted delay, damage, missed delivery, or compliance consequences. A backhaul that generates revenue but causes a critical outbound delivery failure is not operationally beneficial.

Backhaul planning should begin with lane and time compatibility. Common sources include suppliers, customer returns, packaging recovery, and inter-branch transfers. Freight should be pre-approved for compatibility and assigned a loading sequence that does not obstruct the vehicle's remaining deliveries.

Cross-docking

Cross-docking transfers freight from inbound to outbound vehicles with little or no storage. It can reduce inventory holding and handling, but it increases dependence on timing accuracy and dock coordination.

A cross-dock schedule must synchronize:

  • inbound arrival and unloading;
  • sortation and staging;
  • outbound loading;
  • documentation and scanning;
  • departure cut-offs;
  • contingency capacity.

Cross-docking is especially vulnerable to small delays. A late inbound vehicle may cause an outbound vehicle to miss an appointment, creating a network-wide propagation effect. The planner should therefore protect critical connections with realistic buffers and clear priority rules.

7. Real-Time Exceptions and Recovery

Exceptions include traffic congestion, vehicle breakdown, driver absence, customer closure, inaccurate address information, loading discrepancy, temperature deviation, damage, and unexpected demand. A mature control process classifies each exception by urgency, impact, and reversibility.

A practical response cycle is:

  1. Detect the deviation.
  2. Validate the information.
  3. Assess safety, legal, service, and cost consequences.
  4. Identify feasible alternatives.
  5. Select and authorize the response.
  6. Communicate revised instructions.
  7. Record the event and monitor recovery.
  8. Conduct a post-event review.

A useful decision priority is safety and legal compliance first, preservation of critical customer commitments second, and cost minimization third. This order prevents a narrow cost objective from encouraging unsafe driving or illegal HOS decisions.

Recovery options include resequencing stops, transferring freight to another vehicle, using a relay driver, rescheduling an appointment, arranging a local carrier, returning freight to a depot, or cancelling a non-critical collection. The chosen action should consider network effects rather than only the affected vehicle.

8. Performance Measurement

A balanced performance system combines efficiency, service, safety, and resilience.

DimensionExample measureInterpretation
ServiceOn-time delivery percentageReliability against agreed windows
ProductivityStops per route hourOperational output
UtilizationWeight, volume, or cube utilizationUse of available capacity
Empty runningEmpty kilometres percentageNetwork imbalance
SafetyPreventable incidents and violationsRisk control
ComplianceHOS or document exceptionsLegal and process discipline
QualityDamage, claims, and delivery errorsShipment integrity
ResilienceRecovery time after disruptionAbility to restore service

On-time delivery should have a clearly defined denominator. For example:

On-time percentage = (deliveries within the agreed window ÷ eligible deliveries) × 100%

The organization must specify whether early deliveries count, how customer-caused delays are treated, and how cancelled or rescheduled orders are classified. Otherwise, the metric can be manipulated or misinterpreted.

9. Technology, Analytics, and AI

Transport-management systems integrate orders, routing, appointment management, dispatch, proof of delivery, and billing. Telematics provides vehicle location, driver behavior, engine data, temperature, and battery information. Electronic logging systems support HOS monitoring where legally required.

AI and advanced analytics can assist with demand forecasting, estimated-time-of-arrival prediction, dynamic routing, anomaly detection, and automated appointment selection. Their value depends on data quality and governance. A model trained on historically biased service decisions may reproduce inequity between customers or geographic areas. Automated recommendations should therefore be explainable enough for dispatchers to assess, and high-risk decisions should remain subject to human review.

Important controls include access permissions, audit trails, cybersecurity, data retention, model validation, and protection of driver and customer information. GPS data can reveal sensitive personal patterns; its collection and use should be proportionate to a legitimate operational purpose.

10. Illustrative Case: Regional Food Distributor

Background

A regional food distributor operates from one depot and serves six retail stores. It has two refrigerated trucks, each with a usable payload of 8,000 kg and 30 pallet positions. Store deliveries have appointment windows between 07:00 and 14:00. The distributor also collects reusable containers from two stores and receives a supplier backhaul at 12:30.

Problem

On a high-demand day, the order total is 14,600 kg and 54 pallets. One store requires delivery before 09:00, another has limited dock capacity and accepts only between 10:00 and 11:00, and the supplier backhaul must be collected by 13:00. A simple geographic route would overload the first truck and cause the early delivery to compete with the backhaul for capacity.

Analysis

The planner first separates chilled and frozen freight, verifies pallet dimensions, and checks axle restrictions. The orders are divided between the two trucks by both weight and stop sequence rather than by customer geography alone. The early store is assigned to Truck 1 because it is closest to the depot and has a short unloading time. The constrained 10:00–11:00 store is assigned to Truck 2 with sufficient buffer for traffic.

Container returns are placed in a designated rear section that does not obstruct the first deliveries. The supplier backhaul is assigned to Truck 1 only after the early deliveries are unloaded; the load plan leaves the required floor positions and payload margin available.

Solution

The dispatcher releases two route manifests showing stop order, appointment windows, pallet count, temperature zone, and backhaul instructions. Drivers receive a pre-departure briefing covering refrigerated-unit checks, seal control, break timing, and escalation rules. Telematics alerts the dispatcher if either vehicle is projected to miss an appointment by more than 15 minutes.

At 08:35, congestion delays Truck 2. The dispatcher validates the estimated delay, contacts the store, and obtains a revised receiving time of 10:20. The route remains feasible, so no unsafe speeding or major resequencing is required. Truck 1 completes the early delivery, collects reusable containers, and collects the supplier backhaul at 12:35 before returning to the depot.

Outcome

Both critical appointments are met, the backhaul is completed, and neither vehicle exceeds payload, temperature, or driver-time limits. The post-trip review identifies that the original traffic buffer was too small for the eastern corridor. The following week's schedules use a time-dependent travel standard for that corridor.

Learning points

The case demonstrates that effective fleet planning integrates appointment windows, load accessibility, temperature control, backhaul capacity, and real-time communication. It also shows that a delay should first be validated and assessed; automatic re-routing is not always the best response.

11. Challenges, Governance, and Best Practices

The most persistent challenges are inaccurate master data, unrealistic service-time standards, weak communication between warehouse and transport teams, poor visibility of driver availability, and incentives that reward utilization at the expense of safety or service. Planners should distinguish between a planned schedule and an achievable schedule. Repeated deviations are evidence that assumptions, not drivers, may require correction.

Best practices include:

  • maintain validated geocodes, service times, capacities, and customer calendars;
  • plan by legal and operational capacity, not nominal vehicle size;
  • include loading, waiting, breaks, and documentation in time standards;
  • freeze near-term commitments while optimizing later work;
  • use scenario plans for absence, breakdown, weather, and demand surges;
  • sequence freight visibly and verify it at loading;
  • establish clear escalation thresholds;
  • audit HOS, temperature, safety, and data-quality compliance;
  • review root causes rather than blaming individual drivers for systemic delay;
  • balance cost, service, safety, environmental impact, and resilience.

Ethically, organizations must not pressure drivers to violate rest rules, falsify delivery records, or operate unsafe vehicles to achieve a performance target. Governance should assign accountability for automated recommendations and preserve a channel through which drivers can report unsafe or impractical plans without retaliation.

Chapter Summary

Scheduling determines the timing and allocation of fleet resources; routing determines the movement sequence; load planning determines how freight is arranged; and dispatching controls execution. Feasible plans must integrate appointment windows, travel and service times, vehicle and driver availability, HOS requirements, capacity, cargo compatibility, and depot constraints.

Load planning requires simultaneous consideration of weight, volume, axle loading, stability, accessibility, and delivery sequence. Backhauls can reduce empty movement, while cross-docking can reduce storage but increases dependence on synchronization. Real-time exception management should prioritize safety and legal compliance, then protect critical service commitments and control cost.

Performance should be assessed through balanced measures covering service, utilization, empty running, safety, compliance, quality, and resilience. Technology and AI can improve visibility and prediction, but require data governance, cybersecurity, explainability, and human oversight. The central managerial principle is that an efficient plan is valuable only when it is feasible, safe, compliant, and executable.

Key Terms

Appointment window: The earliest and latest permitted time for service at a customer location.

Backhaul: Freight collected on a return movement that might otherwise be empty.

Cross-docking: Transferring freight from inbound to outbound transport with minimal storage.

Dispatching: Releasing, instructing, monitoring, and closing transport work.

Dwell time: Time spent waiting or being processed at a location.

Exception: A deviation from the planned or required operating condition.

Hours of service: Legal limits and requirements governing driving, duty, and rest.

Load sequence: The order and physical arrangement in which freight is loaded.

Payload: Permitted freight mass after vehicle and equipment mass are accounted for.

Rolling horizon: A planning method that repeatedly updates future decisions while protecting near-term commitments.

Service time: Time required to load, unload, inspect, document, or otherwise serve a stop.

Time window: A permitted interval for arrival or service.

Vehicle utilization: The extent to which available vehicle capacity is used.

Route feasibility: The condition in which a route satisfies all relevant operational and regulatory constraints.

Proof of delivery: Evidence that a shipment was delivered or a delivery attempt occurred.

Resequencing: Changing the order of stops during planning or execution.

Tare mass: The mass of an empty vehicle including required equipment but excluding payload.

Telematics: Technology that captures and communicates vehicle, location, driver, or cargo data.

Review Questions

Short Answer Questions

  1. Distinguish between scheduling, routing, and dispatching.
  2. Why can a route with high vehicle utilization still be operationally poor?
  3. State two reasons why backhauls may be infeasible.
  4. What information should be verified before dispatch release?
  5. Why must waiting time be represented accurately in HOS records?

Long Answer Questions

  1. Explain how appointment windows influence route construction and vehicle assignment.
  2. Discuss the principles of safe and efficient load sequencing.
  3. Evaluate the benefits and risks of cross-docking in a time-sensitive distribution network.
  4. Explain how a dispatcher should manage a major in-trip delay.
  5. Discuss the governance requirements for using AI in fleet scheduling.

Analytical / Application Questions

  1. A vehicle departs at 07:00, travels 40 minutes to Customer A, requires 25 minutes of service, travels 55 minutes to Customer B, and requires 20 minutes of service. Customer A accepts service from 07:30–09:00 and Customer B from 09:00–10:00. Determine the service-start and departure times and assess feasibility.
  2. A vehicle has a legally permitted gross mass of 18,000 kg, tare mass of 9,600 kg, and equipment mass of 400 kg. Calculate permitted payload and explain why axle limits must still be checked.
  3. Two routes each have a critical appointment. One vehicle is delayed by 35 minutes because of congestion. Design a decision process for determining whether to resequence, transfer freight, contact the customer, or retain the original plan.

Multiple Choice Questions with Answers

Question 1

Which activity primarily converts an approved route into operational instructions and monitored execution?

A. Fleet acquisition

B. Dispatching

C. Demand forecasting

D. Network redesign

Correct Answer: B. Dispatching

Question 2

A vehicle arrives at a customer before the appointment window opens. What is the correct service-start rule?

A. Begin service immediately regardless of the window

B. Cancel the stop automatically

C. Begin service at the later of arrival time and window opening

D. Begin service at the earlier of arrival time and window opening

Correct Answer: C. Begin service at the later of arrival time and window opening

Question 3

A truck has a permitted gross mass of 18,000 kg, tare mass of 9,600 kg, and equipment mass of 400 kg. What is its permitted payload before checking axle limits?

A. 8,000 kg

B. 8,400 kg

C. 9,000 kg

D. 28,000 kg

Correct Answer: A. 8,000 kg

Question 4

Which loading principle usually improves accessibility during multi-stop delivery?

A. Load the first delivery deepest inside the vehicle

B. Load all heavy freight at the rear doors

C. Place final-stop freight nearest the doors

D. Place early-stop freight where it can be accessed without disturbing later deliveries

Correct Answer: D. Place early-stop freight where it can be accessed without disturbing later deliveries

Question 5

What is the principal operational advantage of a backhaul?

A. It eliminates all loading requirements

B. It reduces empty return movement

C. It guarantees a shorter outbound route

D. It removes the need for HOS monitoring

Correct Answer: B. It reduces empty return movement

Question 6

Why can cross-docking increase network vulnerability?

A. It requires all freight to be stored for long periods

B. It eliminates the need for synchronized schedules

C. A delay in an inbound movement can disrupt an outbound connection

D. It prevents the use of appointment windows

Correct Answer: C. A delay in an inbound movement can disrupt an outbound connection

Question 7

Which priority is most appropriate when responding to a real-time exception?

A. Minimize kilometres before considering safety

B. Protect safety and legal compliance first

C. Meet the customer promise by any means necessary

D. Maximize vehicle utilization regardless of delay

Correct Answer: B. Protect safety and legal compliance first

Question 8

Which measure is calculated as eligible deliveries within the agreed window divided by eligible deliveries?

A. Volume utilization

B. Empty-kilometre percentage

C. On-time delivery percentage

D. Payload capacity

Correct Answer: C. On-time delivery percentage

Question 9

Why should a route planner consider service duration as well as travel duration?

A. Service duration affects appointment feasibility and departure times

B. Service duration determines vehicle tare mass

C. Service duration replaces the need to calculate distance

D. Service duration is relevant only after trip closure

Correct Answer: A. Service duration affects appointment feasibility and departure times

Question 10

Which governance practice is most appropriate when AI recommends a major route change?

A. Accept every recommendation without review

B. Disable all automated recommendations permanently

C. Require human review for high-risk decisions and retain an audit trail

D. Allow the model to override legal limits when service is urgent

Correct Answer: C. Require human review for high-risk decisions and retain an audit trail

Fleet Operations & Routing
Chapter 7 of 14