Driver assignments

A load can be planned only when its driver and vehicle commitments make sense together. Dispatcher records the chosen load, driver and vehicle with a start and end time. The assignment state distinguishes a held arrangement from a confirmed commitment and work already dispatched.

The driver roster supplies an active flag, eligibility expiry and an external authority reference. Dispatcher checks those details against the intended assignment period. App Administrator maintains the roster when a driver’s information changes, giving the operating team a named person to contact when eligibility needs clarification.

• Check the roster. Dispatcher reviews the driver’s active state and eligibility date before committing work. The external authority reference helps the team find supporting information. An eligibility date needs interpretation against the actual planned period, especially when a movement crosses midnight.
• Compare committed windows. Dispatcher examines existing start and end times for both the driver and the vehicle. A conflict may involve another load in the same shift. Resolve the overlap before confirming the new commitment, and preserve a clear association with the load being served.
• Follow the assignment state. Held, Confirmed and Dispatched help the team distinguish preparation from movement. Completed and Cancelled retain the eventual outcome. A change to the load should prompt a check of its associated assignment so the next shift reads a consistent operating picture.

Agree who supplies eligibility evidence and how App Administrator checks a requested roster update. Set a clear convention for assignment time zones. Include preparation and handoff time in the team’s scheduling discussion so the selected start and end represent the commitment being made.

Name who can maintain assignment records and who must consult Transport Supervisor when a conflict cannot be resolved. Agree when Dispatcher changes an assignment from Held to Confirmed. The duty interval review should use driver identification that the team can reconcile with the roster and the actual load assignment.

Use a driver called Morgan Reed for a rehearsal assignment ending at 14:00. Prepare another load for the same driver starting at 13:30. Dispatcher inspects the overlapping periods and keeps the second commitment from being confirmed until the plan is changed. Repeat with different drivers sharing the same vehicle to test the vehicle side of the decision.

Next, use a driver whose eligibility expires before the intended assignment. App Administrator resolves the supporting evidence before Dispatcher releases the load. The team should be able to explain which roster entry and committed window they checked. An active flag alone should not be the team’s entire eligibility decision.

Finally, compare a prepared duty interval’s driver text with the assignment. Resolve an ambiguous name against the source record before the supervisor reviews the interval.

• Load Assignments Default List — Driver and vehicle commitments with their start and end times.
• Drivers Roster — Active drivers with eligibility expiry and authority references.

Review Load to dispatch and the driver identity handoff in Duty interval import.